-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AC3 file not being created? #85
Comments
I am also on OS X 10.6.8, I tried the same command and it worked. Can you try the same command but append the debug flag "sudo ./mkvdts2ac3.sh --debug --new -d Downloads/test.mkv" |
Yeah no problem. Here's the output. The write test.ac3 command looks right, but the very next process can't find the file. Output
|
Ok, try the following: run the same command, stop (do not press enter) at "Converting DTS to AC3.", then open a new window in Terminal, type open /tmp, the file test.dts should be present in directory /tmp, if test.dts is present, go back to the previously opened window in Terminal, type ffmpeg -i "/tmp/test.dts" -acodec ac3 -ac 6 -ab 448k "/tmp/test.ac3" |
Again yeah no problem. Ran the debug, this time using the alternate ffmpeg parameters. Still looks like the ac3 file wasn't created. Oddly though no error message when removing the test.ac3 file in the muxing step Summarized output:
|
Did you try the ffmpeg command manually? ffmpeg -i "/tmp/test.dts" -acodec ac3 -ac 6 -ab 448k "/tmp/test.ac3" |
Ran another debug using ffmpeg -i "/tmp/test.dts" -acodec ac3 -ac 6 -ab 448k "/tmp/test.ac3" manually, but same results as your first suggestion. Also, I'm using ffmpeg 1.1.7, which are you using?
INFO: Moving new file over old file. DO NOT KILL THIS PROCESS OR YOU WILL EXPERIENCE DATA LOSS! |
Better yet, open a new window in Terminal and type ffmpeg? The first line of the output should be similar to "ffmpeg version 0.9.1, Copyright (c) 2000-2012 the FFmpeg developers" |
By the way, you are entering the command in the same Terminal window, that will not work! |
Ah crap my mistake. I thought just hitting enter sent a blank line to move the debugger forward, and that I could send manual inline commands. Using a second terminal window to send the ffmpeg gave me a bad cpu type error. The ffmpeg 1.1.7 version I'm using I thought was for mac intel x64.
|
Universal Media Server contains a fairly recent version of ffmpeg in directory /Applications/Universal\ Media\ Server.app/Contents/Resources/Java/osx/ |
let me try that. the latest snapshot gave me the same bad cpu type error. [edit] I used the -d flag yet mkvmerge -i shows the new ac3 track at id 4. Doesn't that mean it's not the default track as -d implies?
Again, thank you for all your help! 👍 |
Upon further investigation, the problem is clear to me! You have a 32-bit CPU. ffmpeg 1.1.7 lacks the 32-bit (i386) part, it is 64-bit (x86_64) only! |
FFmpeg Static Builds by tessus are all 64-bit only! |
That's really odd. AFAIK Intel COre i7's are 64bit but whatever. Don't care as long as it works :) Thanks. Lastly though, does that Track ID 4: audio (A_AC3) mean the -d flag didn't work? Or does default audio not matter with Track ID |
That's odd, you could email tessus as to why his build does not work on i7. You could try snapshots starting from the most recent to the oldest to figure out the latest working snapshot on i7. Track ID has nothing to do with the -d flag! Use mkvinfo Downloads/test-AC3.mkv. If the default flag is not set for a track, mkvinfo outputs Default flag: 0. Glad I could help. |
Also, don't forget, the excellent GUI: MKVToolNix |
I'm running this on OSX 10.6.8. I have all the listed pre-req libraries/binaries installed. I'm using the supplied test.mkv, but I get the same results with any mkv. I'm applying the --new and -d flags. The conversion runs all the way through, but seemingly never creates the test.ac3 file. I've tried surrounding the test.mkv file with double/single quotes in the initial mkvdts2ac3 command, I've tried using alternate working temp locations instead of /tmp. Nothing seems to help.
There's one syntax error on line 537 and a -gt: unary operator expected error on line 175.
Any help or insight would be appreciated. I'm banging my head against a wall here.
Terminal output
The text was updated successfully, but these errors were encountered: