Encodes only the last 5 vobs only, something, convert, problem

andy

i'm having a problem with agk, not sure if it's just me or what. i have agk 1.89 installed. i ripped with dvddecrypter, and i have what should be there. it's a huge rip, each vob is a GB large except the last, 460MB.

VTS_02_PGC_01_1.VOB through VTS_02_PGC_01_7.VOB

now when i use agk to convert it, it only does the last five VOBs. is there something i'm doing wrong.

Are you using DVD or file mode? What happents if you try the other one anyway?

hmm. that's weird. File Mode sees all 7 files. thanks. (btw, just updated to 1.90b.

but i have another problem using that mode. when i use DVD mode, it sees the subtitle streams. in file mode, it doesn't see any subtitles at all. the vobs do have subtitles when i watch them though. what can i do about that.

That's limitation of the file mode - it doesn't work with subs (although if you process them manually in VobSub then you can feed them back via CTRL-F8 option). If you upgraded to 1.90 then you can try DVD mode again as DGIndex that is responsible for picking up VOBs was updated.

wow. that's actually a good solution. will file mode ever support subtitles, or no?

i'm hardcoding the subtitles. but will the subtitles be identical to as if i were using dvd mode?

btw, DGIndex under 1.90b still did the same thing, only the last 5 vobs.

i'm actually working on the star wars dvds. i ripped each one exactly the same. the first one, i put on my C drive, the other two on my D drive. only difference is C is FAT32 and D is NTFS. i doubt that'd have anything to do with it though. when i free up room on D, i'll transfer the one on C to D and try encoding it that way, in dvd mode.

That's so weird... another solution would be to rip in one file using DVDDecrypter (i.e. don't auto split by 1Gb).

And yes, subs should be the same.

P.S. Let me see how DVD mode is processed in the code (*may be* its just picking up first vob it can find and not the actual first one. File system might matter in this case).

Ha, I was right - its a long running bug (since forever): it seems that in FAT32 files are returned to the application NOT in sorted order, that's why this bug was never really discovered (who uses FA32 these days anyway  ).

wow. ok. lol, don't make fun of me for using FAT32. just haven't gotten around to converting it. lol.

so i shall encode under NTFS asap.

I'll make a fix for FAT32 users in 1.91 anyway.

oh that would be excellent. if i still have it by 1.91, then i'll try it out.

I don't think 1.91 will be out this week unless some serious problems found in 1.90. But you can test the fix from here: AutoGK.exe

oh my. you continue to amaze me. that actually worked. now, should i wait for the official 1.91 beta release, possibly for other good upgrades/changes? or am i safe to use that?

it's just a different/upgraded executable. so it uses all the same updated files from the 1.90b update.

Yes, its safe to use the executable above - it does have all the modifications of 1.90.

Len0x maybe you should repackage the 1.90 with the new executable.

Its not serious enough to do re-packaging. Its still rare problem even on FAT32 systems. It can wait 3-4 days