|
|
| DarrellS |
| Posted: Jun 29 2010, 09:20 AM |
 |
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
I'm having the same problem with muxing. Everything was working great a week ago, now I can't mux anything.
Before, when I got the muxing error, it still left the 264 and aac files in the output folder. Now when it errors, it deletes the files that it just created. That's a whole lot of wasted time encoding h264 over and over with nothing to show for it.
Guess I need to delete all my encoder sets and encoders and start all over.
It seems like a lot less trouble just to use the x264 encoder and then mux the x264 file into an mp4 or mkv container with the same muxers that Virtualdub refuses to mux with. |
|
| DarrellS |
| Posted: Jun 30 2010, 02:06 AM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
I reverted windows back to a week ago and I can now mux to mkv but no matter what I do, I cannot mux to mp4. No big deal since my media player supports mkv. I just redid all my encoder sets to use mkvmerge to mux with.
Before reverting back, I also noticed that I lost all aac encoding capabilities.
Not sure what happened but everything got messed up. Not for anything else (all my other programs that use these encoders work just fine) except for Virtualdub's external encoder. I tried everything to fix the issue including removing everything out of the Tools folder and redownloading everything and starting over but nothing worked.
Oh yeah, I still get the muxing error with mkv but when I check the finished file, it is there and works just fine. That was happing before all my problems also. Not sure why. |
|
| phaeron |
| Posted: Jun 30 2010, 03:55 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
I need to put in an option to disable the delete.
Can you try deleting the multiplexer from the encoding set? This should cause the video and audio encoders to run, and then leave the output files. You can then run the multiplexer manually to see what happens.
|
|
| DarrellS |
| Posted: Jun 30 2010, 05:36 AM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
| QUOTE (phaeron @ Jun 29 2010, 08:55 PM) | I need to put in an option to disable the delete.
Can you try deleting the multiplexer from the encoding set? This should cause the video and audio encoders to run, and then leave the output files. You can then run the multiplexer manually to see what happens. |
Yeah, that works.
It's just got me bumfuzzled cause' everything worked a week ago. I don't know why mp4box would suddenly stop working. The arguments are the same as they always were. |
|
| v0lt |
| Posted: Jun 30 2010, 01:46 PM |
|
|
Advanced Member
Group: Members
Posts: 119
Member No.: 26125
Joined: 5-September 09
|
DarrellS
I have no problem with mp4. I do not see warnings with mkv.
My command lines:
video:
-----
x264.exe --crf 20 --stdin yuv -o "%(tempvideofile)" - %(width)x%(height) --fps %(fpsnum)/%(fpsden)
%(outputname).video.264
audio:
-----
faac.exe -q 500 -w -o "%(tempaudiofile)" -
%(outputname).audio.m4a
(WAV file + Bypass compression)
-----
neroAacEnc.exe -q 0.6 -ignorelength -if - -of "%(tempaudiofile)"
%(outputname).audio.m4a
(WAV file + Bypass compression)
muxer:
-----
mkvmerge.exe -o "%(outputfile).mkv" --default-duration 0:%(fpsnum)/%(fpsden)fps "%(tempvideofile)" "%(tempaudiofile)"
-----
MP4Box.exe -add "%(tempvideofile)" -add "%(tempaudiofile)" "%(outputfile).mp4" -fps %(fps)
-w option for FAAC is required. Otherwise, mkvmerge will swear.
|
|
| DarrellS |
| Posted: Jul 1 2010, 04:41 AM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
| QUOTE | | -add "%(tempvideofile)" -add "%(tempaudiofile)" "%(outputfile).mp4" -fps %(fps) |
This worked.
I was using...
-add "video.264" -add "audio.aac" -fps %(fps) "%(outputname)"
...which was working but stopped.
Thanks for the command line above. I'll use that one instead. I was using the one in the guide.
Hopefully this thread stays here a long time. It's full of valuable information that I would not have a clue without.
EDIT: The only problem with your commandline is that the temp tile is called xxx.mp4 so the output file is called xxx.mp4.mp4
How do I fix it to make it say xxx.mp4 and not have to erase the last .mp4? I removed mp4 from file extension in the encoder set but that did nothing. I also tried removing .mp4 from the commandline but the muxer crashed. |
|
| stephanV |
| Posted: Jul 1 2010, 06:43 AM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
I've written a more general tutorial here:
http://forums.virtualdub.org/index.php?act...=ST&f=3&t=18840
It also has example command lines and setups.
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
| DarrellS |
| Posted: Jul 1 2010, 08:08 AM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
I've tried both your's and Loadus' (his was working a week ago) and neither work.
I tried to register the js32.dll to see if that would help but I got an error telling me it couldn't find the file so I copied the dll into the system 32 folder and tried again. It still couldn't register the dll but I was able to get v0lt's commandline to work correctly without adding the extra .mp4 at the end. Neither your's or Loadus's commandlines will work for me though. I don't know what happened to make Loadus's commandline stop working for me.
The only thing I've done in the last week is overclock my cpu to work with H264 files. I wouldn't think that would affect things since my temps are fine and I only have my Q6600 OCed to 3.2Mhz.
It's driving me crazy why your's and Loadus commandlines don't work since his was working and your's is almost identical to v0lt's except for the .mp4 but as long as I can get v0lt's to work then I guess I should be happy.
You wouldn't happen to know the commandline to make the DivX H.264 CLI work would you? I'm curious to see if it's any faster than the x264 encoder.
|
|
| stephanV |
| Posted: Jul 1 2010, 08:42 AM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
You need to have the js32.dll in the same directory as mp4box.exe.
For the rest 'doesnt work' is not very helpful. You can enable the error logging in the muxer profile and see what goes wrong in the log. I've tested all the commandlines and encoder sets in various permutations personally so I know they work. That doesn't mean nothing can go worng, but it should be something that is traceable. 
| QUOTE | | You wouldn't happen to know the commandline to make the DivX H.264 CLI work would you? I'm curious to see if it's any faster than the x264 encoder. |
No. But speed doesn't mean anything if the quality is horrible. Also, if you want x264 to be faster use '--preset veryfast' (or superfast, ultrafast, faster or fast)
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
| DarrellS |
| Posted: Jul 1 2010, 06:48 PM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
The js.dll seems to have no affect at all. I have it in two folders with mp4box and one without and with all three folders, I get the same outcome.
Like I keep saying, everything worked fine a week ago but suddenly stopped working and I didn't have the js.dll when it was working, only after you recommended that rjisinspired install it.
EDIT: I added v0lt's "%(outputfile).mp4" to both your's and Loadus's commandlines and now they both work and I placed mp4box.exe in it's own folder without the js.dll to use as the muxer so js.dll has no affect.
Loadus...
-add "video.264" -add "audio.aac" -fps %(fps) "%(outputfile).mp4"
stephanV...
-add "%(tempvideofile)" -add "%(tempaudiofile)" "%(outputfile).mp4" -fps %(fps)
The error that I was getting before was...
Mux: Cannot open destination file 1.mp4: Invalid IsoMedia File
Adding the .mp4 to the commandline fixed the problem. |
|
| stephanV |
| Posted: Jul 1 2010, 06:49 PM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
You shouldn't have to add it. The encoder set should cover the extension. Strange...
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
| DarrellS |
| Posted: Jul 1 2010, 09:36 PM |
|
|
Advanced Member
Group: Members
Posts: 567
Member No.: 1061
Joined: 28-November 02
|
I'm gonna bite the bullet and restore my computer to an image I took a month ago. Something has gone wrong somewhere. I'll have to reinstall a few things but I've backed up a bunch of files I've downloaded since then so I should be alright. |
|
| rjisinspired |
| Posted: Jul 2 2010, 03:07 AM |
|
|
Advanced Member
Group: Members
Posts: 1256
Member No.: 20008
Joined: 12-October 06
|
I've been successful using ffmpeg as the muxer but not mp4box for some reason even with the js32.dll file is in the same directory as that program.
I had extension issues too. If not added manually you get extension-less files. I thought whatever program used would add them by default. |
|
| phaeron |
| Posted: Jul 2 2010, 04:20 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
The encoding set supplies the default extension to be used in the file dialog. If you don't have one, then you will only get an extension on the filename if you type it in manually. You can add the extension to the command line for the output encoder/multiplexer, but this is not recommended as it means that VirtualDub can't track the output file -- which means, among other things, that the overwrite check in the file dialog won't work, and it can't tell you if there is a problem with the output filename until the very end of the encoding.
IIRC, MP4Box doesn't like it if the output file already exists. By default, VirtualDub pre-creates the output file as zero bytes in order to ensure it is writable beforehand. You need to check "Delete output file before starting" on the MP4Box encoder entry to make sure that this file is removed before MP4Box is run. If the encoding set was exported from an older test release, it may not have this flag. |
|
| stephanV |
| Posted: Jul 2 2010, 05:55 AM |
|
|
Spam killer ;)
Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04
|
| QUOTE (phaeron @ Jul 2 2010, 06:20 AM) | | IIRC, MP4Box doesn't like it if the output file already exists. By default, VirtualDub pre-creates the output file as zero bytes in order to ensure it is writable beforehand. You need to check "Delete output file before starting" on the MP4Box encoder entry to make sure that this file is removed before MP4Box is run. If the encoding set was exported from an older test release, it may not have this flag. |
Confirmed. I'll add it to my guide.
--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ |
|
