AutoMKV doesn't recognize spaces in the input path. For e.g: if I extract AutoMKV to C:\Program Files\AutoMKV, and then start the encoding, during the audio encoding step, it flashes a commandline window saying C:\Program is not a recognized internal or external command. At least, that's what I could make out from it because the command window was flashing wildly (it was rapidly getting closed and re-created again. Very annoying - only way was to end the process from the Task Manager).

Actually, audio doesn't seem to work at all. I tried all Nero AAC options, none worked. It was always in the line of

I noted that you are not indexing the video and demuxing the audio tracks using DGIndex before this. That might be the reason why it is not able to find the audio streams.

In all of the above cases, the flashing window problem occurs and the only way out of it is to end task it.

OK, so then I selected no audio and DGIndex craps out with a No Video Sequence Header Found error (the kind you used to get if you opened an avs in DGIndex before) followed by a No data. Check your PIDs error. Looks like the PIDs are not being set, for whatever reason.

Whew, that's it for now. Got to leave for work. Will test later tonight if I am sober enough.

P.S: Are you allowed to distribute neroAacEnc? Note that the MeGUI folks aren't distributing it at the moment because of licensing issues.

what si your input file ? a dvd structure ? if so the main problem is with ifo parsing... try pointing at main ifo file. or at vob... and at end (before removing all) at an already created d2v

Quote:

OK, so then I selected no audio and DGIndex craps out with a No Video Sequence Header Found error (the kind you used to get if you opened an avs in DGIndex before) followed by a No data. Check your PIDs error. Looks like the PIDs are not being set, for whatever reason.

TS input ? i found an ugly bug... please wait for next update

and about neroaacenc: no, i haven't any right to publish, i have replaced the original package... when i published the package i have included my neroenc... thank again for pointing it out

what si your input file ? a dvd structure ? if so the main problem is with ifo parsing... try pointing at main ifo file. or at vob... and at end (before removing all) at an already created d2v

All my testing was on a DVD input. DGIndex is used, but are you using it *before* encoding audio? If I select Nero AAC-Stereo as the audio format, AutoMKV immediately fires up the commandline for encoding the audio with neroAacEnc.exe. But I don't recollect a step happening where the AC3 is being demuxed out of the VOBs. I am pretty sure this was the case, but I will check the logs again tonight.

The input was indeed the main IFO file and I reckon vstrip_ifo.exe parsed it without any issues too.

Quote:

Originally Posted by buzzqw

TS input ? i found an ugly bug... please wait for next update

Nope. DVD input. Which makes the error all the more weird.

Also here are some suggestions:

The GPL license included, COPYING, doesn't have an extension. Make it COPYING.txt.

Audio part is working now. Now that I am home and checking the logs, I can confirm that there is no sign of DGIndex in them as you claimed. So what was the problem with that part of the code? Was I correct in my observation that you weren't demuxing the tracks before and hence the reason the audio encoding was failing?

Another problem now is that DGIndex's Information window is suppressed when running (Is it because of -MINIMIZE?). So I am not able to see any progress. To add to the problem, AutoMKV GUI itself totally disappears from view once DGIndex is fired off. A progress bar is a must here, IMO. Either enable the Information window of DGIndex or have AutoMKV itself display the log real-time (like in AutoGK), and if possible, both.

So it is encoding at the moment (at least I think so, since x264.exe got invoked now, but nothing in sight). I am out for the night. Will check back tomorrow for more.

Quote:
Originally Posted by buzzqw
Space : should be fixed (finger crossed)
No, not fixed.

thanks again... i will try to reproduce and resolve the problem

Quote:

Audio part is working now. Now that I am home and checking the logs, I can confirm that there is no sign of DGIndex in them as you claimed. So what was the problem with that part of the code? Was I correct in my observation that you weren't demuxing the tracks before and hence the reason the audio encoding was failing?

no. I use dgindex as demuxer, and if audio is working then dgindex is launched minimized, and at the and audio is encoded.

Quote:

Another problem now is that DGIndex's Information window is suppressed when running (Is it because of -MINIMIZE?). So I am not able to see any progress.

just right click on dgindex minimized and click "restore"

Quote:

AutoMKV GUI itself totally disappears from view once DGIndex is fired off. A progress bar is a must here, IMO

... not so easy (for me...). but i will try

Quote:

AutoMKV itself display the log real-time (like in AutoGK), and if possible, both

no. I use dgindex as demuxer, and if audio is working then dgindex is launched minimized, and at the and audio is encoded.

I don't think you got me. *Now* audio part is working fine (as of v0.05 I tested). Because you are launching DGIndex *before* the audio step, how it should be. This was NOT what you were doing in v0.03, where there wasn't any DGIndex step *before* the audio encoding step. You used to attempt to encode the audio, but without an input track in hand (because it was never demuxed out of the VOB container!). But anyway, good that it is fixed now.

Quote:

Originally Posted by buzzqw

just right click on dgindex minimized and click "restore"

I had tried all that. Restoring doesn't restore the information window. It only restores the main window. Does it work for you?

Quote:

Originally Posted by buzzqw

read mkvmagic.log in destination folder

I am not sure I got what you mean here. Are you saying that you will read mkvmagic.log (and hence maybe display the log in the AutoMKV window) or are you asking me to go read it if I want to know the progress? Former is fine, latter isn't. A newbie user wouldn't want to go looking in the source directory and read the logs to know the progress. Btw, why mkvmagic.log? You should rename it to automkv.log to reflect the name of the tool.

OK, now that the encode is done (with v0.05) , I see that it is undersized (I asked for 700 MB, it gave me 692.2 MB) and it wasn't IVTC'd. It should have been (QMF not working properly?). I am also 99.99% sure, I had selected the width to be 720, but the resultant file has a width of 704 (will confirm this later).

More suggestions..

You are creating a ton of stuff in the source directory and it is confusing. You should be moving all the intermediate files into a temp directory. The source directory should only contain the input files & the output files (movie+subs). You could even create an output directory and put the movie+subs there.

i can confirm that dvd input was broken in 0.03 , and it is ok from 0.05

Quote:

I had tried all that. Restoring doesn't restore the information window. It only restores the main window. Does it work for you?

yes (as autogk faq..), anyway now dgindex is lauched not minimized

Quote:

you asking me to go read it if I want to know the progress? Former is fine, latter isn't. A newbie user wouldn't want to go looking in the source directory and read the logs to know the progress. Btw, why mkvmagic.log? You should rename it to automkv.log to reflect the name of the tool.

... i will try to implement a direct log into main window... but i am a newby developer... be patient
about renaming... of course, i have reused some routines from my mkvmagic ... log will be now automkv.log

Quote:

OK, now that the encode is done (with v0.05) , I see that it is undersized (I asked for 700 MB, it gave me 692.2 MB) and it wasn't IVTC'd

is previus version (prior to 0.6) dbautodeint wasn't correctly launched on path with space in name... please retry with 0.08 build (on a short vob). About undersize... i will try to do better compute... (try with 0.08)

Quote:

. I am also 99.99% sure, I had selected the width to be 720, but the resultant file has a width of 704 (will confirm this later).

check mkvmagic.log should be written. Anyway the new log (0.08) will be filled with more information

Quote:

Y The source directory should only contain the input files & the output files (movie+subs). You could even create an output directory and put the movie+subs there.

added a "Del Temp File" check. But remember since this software is in beta status, i analyze many temporary file for debugging