#716 megui "one click encode" problem.

[stinger2]

When using the "One Click Encoder" method, and encoding VOBs by folder containing multiple .vob files, i get the error "The audio tracks 1 and 2 are identical. Are you sure you want to proceed? (Yes) (No)". A google search produces 0 results.

they are NOT identical. They are ac3-6ch and ac3-2ch.

i'm not sure how MeGUI determines that the audio tracks are identical first of all. How could it? Is it really any of MeGUI's business? for example, maybe 1 track is music with explicit lyrics censored and the 2nd track is not censored. these tracks would appear identical except for a couple beeps in the music.

You can click "yes" to continue and it continues, but after the "one click encoder" encodes the first file, it will ask you again for the next and remaining files. If you have 60 .vob files, this can be a pain and makes much more than "One Click" :) You have to stick around your PC and be clicking yes every couple minutes.

this problem seems to be related to the "name" of the audio track. if you just encode 1 file at a time and specify unique names ie. "ac3 5.1" and "ac3 2.0" then you don't get this error, but again, requires input for each file.

Solutions i can think of:

1. have the "One Click Encoder" auto generate names for each audio track including codec name and channels maybe ie. "ac3 6ch"?
2. if there was a way of naming audio tracks in the .vob files and have MeGUI auto load them, that would work. Except, i don't think you can name audio tracks in a .vob file.

[Zathor]

• Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,3 @@
-
 When using the "One Click Encoder" method, and encoding VOBs by folder containing multiple .vob files, i get the error "The audio tracks 1 and 2 are identical. Are you sure you want to proceed? (Yes) (No)".  A google search produces 0 results.

 they are NOT identical.  They are ac3-6ch and ac3-2ch.

• status: open --> pending

[Zathor]

Which MeGUI build are you using? 2339 (latest development build)? Please upload always the log file.

[Zathor]

Ok, I just made a test with 2308 (latest stable). The described problem can be reproduced there but it is already solved in 2339. A new stable will likely be released in the next hours/days, but you can switch to the development update server to receive it sooner.

[Zathor]

Thanks for your report. 2341 is now live on the stable update server.

[stinger2]

awsome. sorry i didn't check back here sooner. i was using the stable (2308). Got 2341 now. thanks.