does dvd2avi chop off frames?

[hakko504]

Originally posted by neuron2
I could change DVD2AVIdg to use the old 1.76 style D2V file. But that might break any applications that are designed for 1.77.3. I am thinking of making a command you can put in your INI file to specify 1.76-style D2V files. Will that be OK or can you think of anything better? Why not put a checkmark in the .d2v save dialog window allowing the user to choose between v1.76 and v1.77.3 style d2v. Or even two radio buttons, one saying 1.76 and the other v1.77.3. Something like this:Use D2V stryle: [x] v1.76 [ ] v 1.77.3or[x]Use v1.76 style D2Vand in this case have the default value checked(1.76)/unchecked(1.77.3) as an INI command.

[Guest]

OK.

[NanoBot]

Originally posted by neuron2
DVD2AVI 1.77.3 changed the D2V format, the name of the luminance variable, and its sense...


Thanks for your fast reply, Donald, that answers my question 100%. I never used a Version >1.76 before and therefore I did not know that the d2v file format changed.

A agree with hakko504 that the best solution would be to place a checkmark in the save project dialog to let the user choose between the old and the new format.


C.U. NanoBot

[ssjkakaroto]

neuron2 does your version already has fixd2v in it or can incorrect d2v files still be generated?

tia

[Guest]

No, DVD2AVI just copies the flags as it finds them in the VOB. It is a good idea to incorporate the fix functionality. Thank you for suggesting it. Meanwhile, I also have to make versions of Fixd2v and Parsed2v that accept 1.77.3-style D2V files.

[Guest]

I have released beta 9, which adds the ability to save DVD2AVI 1.76-style D2V files:

http://neuron2.net/fixd2v/decodefix.html

[trbarry]

Donald -

Again, kudos & props!

I took a very brief look at your DVD2AVI source code and it does not (in getbit.cpp) seem to have any of the HDTV/ATSC support. However I'd very much like to take advantage of your changes to MPEG2DEC3, even for HDTV files.

Do you think your new MPEG2DEC3 is still compatible with using my old DVD2AVIT3?

- Tom

PS - It may even be possible to just use the getbit.cpp from my existing version of DVD2AVI with the rest of the code from your new one since you have not made any changes there. That should be full ATSC support except for the user coding the PID numbers. And Nic's got better code for that anyway. But I don't have any time to code or test anything at the moment.

[len0x]

Just wanted to congrat you, Donald, that finally all flavours of DVD2AVI and mpeg2dec3 are going to be merged, so that we don't have to choose which one to use.

Great Job!

P.S. A small suggestion: if you open vobs files with DVD2AVI, then all of them are automatically added from that dir, but when opening M2V files this doesn't happen and you have to add all of them manually. Can it be made working for M2V files as well?

[Guest]

Originally posted by len0x
P.S. A small suggestion: if you open vobs files with DVD2AVI, then all of them are automatically added from that dir, but when opening M2V files this doesn't happen and you have to add all of them manually. Can it be made working for M2V files as well? It already works. The m2v's have to be named like this:

anything1.m2v
anything2.m2v

I tested it. Is it not working for you that way? What are your file names?

There is one bug. The code supports incrementing only a single digit, so only 0-9 can be loaded.

[len0x]

Originally posted by neuron2
I tested it. Is it not working for you that way? What are your file names?


Actually what I have after DVDDecrypter is:
VTS_02_1 - 0xE0 - Video - MPEG-2 - 720x576 (PAL) - 16~9 - Letterboxed.M2V
VTS_02_2 - 0xE0 - Video - MPEG-2 - 720x576 (PAL) - 16~9 - Letterboxed.M2V
VTS_02_3 - 0xE0 - Video - MPEG-2 - 720x576 (PAL) - 16~9 - Letterboxed.M2V
and so on...

I don't see any easy parsing of this apart from just loading all m2v in sorted order...

[Guest]

Originally posted by trbarry
Do you think your new MPEG2DEC3 is still compatible with using my old DVD2AVIT3?It should be, with two caveats: that version of DVD2AVI will lose frames, and if the first GOP is open your RFF flags will be misaligned. But that was true of the previous MPEG2DEC3, so nothing is lost.

PS - It may even be possible to just use the getbit.cpp from my existing version of DVD2AVI with the rest of the code from your new one since you have not made any changes there. That should be full ATSC support except for the user coding the PID numbers. And Nic's got better code for that anyway. But I don't have any time to code or test anything at the moment. OK, thanks. I'll keep that in mind when I add the transport support.

[Guest]

@len

The code works by backing off 4 chars from the end of the filename and then incrementing the digit (if any) there:

anything1.m2v

But the rule could be changed to increment the 8th character in the filename:

VTS_02_1 - 0xE0 - Video - MPEG-2 - 720x576 (PAL) - 16~9 - Letterboxed.M2V

I haven't ripped with enough tools to know if this would break anything. What do you think?

[len0x]

Originally posted by neuron2
I haven't ripped with enough tools to know if this would break anything. What do you think?

As for DVDDecrypter (which most ppl use as it's bundled with GK) it operated in two modes:
1) VOB mode with filenames like vts_02_1.vob
2) Stream mode with filenames like I posted already.

So your suggestion about digit number 8 will do for both cases.

I don't remember exactly which naming SmartRipper uses, but afair it produces the same vob structure as first mode of DVDDecrypter.

[Guest]

It works fine for Smart Ripper, so go get beta 10!

[len0x]

Originally posted by neuron2
It works fine for Smart Ripper, so go get beta 10!

well, actually it's still not working for the files I described earlier...

[Guest]

Silly me. Standby...

EDIT: OK, try beta 11. The leading path info was screwing it up. The way it does it now is it scans from the end of the path name looking for a _ character. Then it increments the number after the _ character.

[len0x]

super, it's working nicely now.
10x!

[DDogg]

Load 1.76 project in DVD2AVIdg.exe > F5

Donald, wanted to mention that preview does not activate when a 1.76 project file is loaded just in case this was not your design intention.

[Guest]

Beta 12 fixes DVD2AVI this way:

* can now open 1.76 or 1.77.3 D2V files.
* Preview now delivers all frames.
* Save AVI now delivers all frames.

Remaining work:

* fix VFAPI to deliver all frames.
* make command line version.
* make transport stream version.
* ???

[hakko504]

Originally posted by neuron2
Remaining work:

fix VFAPI to deliver all frames.
make command line version.
make transport stream version.
??? make DVD2AVI use BeSweet for audio processing.

Let me clarify: the demux code can be left as is, but downsampling/normalisation etc should benefit from the use of BeSweet.

[Wilbert]

About transport streams ...

It would be very nice if it also could demux the aac stream from a mpeg2-ts stream :) Just like TSdemux.

[MLS]

Wow, thank you very much for fixing all of this stuff Neuron!

/MLS

[len0x]

Just done an encode of Godfather with new DVD2AVI/mpeg2dec3 and sound was sooo out of sync (may be it's ok just first 15 min then it's progressively more and more out of sync). That never happened to me before (with AC3 sound). Gonna do the same encode with older versions to make sure that new ones indeed have issues...

*EDIT* Another issue on the second movie I was encoding was - that it just crashed during second pass of the encode. Rebuilding the project with old DVD2AVI and using old mpeg2dec3 (Nic's 1.10) helped - no crashes...

[int 21h]

Did you have forced film on? Because, the R1 version of Godfather, as far as I can remember, is definitely not a 3:2 pulldown, it needs proper IVTC.

[len0x]

I have PAL version (R2). I compared two d2v files (from 1.77.3 and beta 12) and they are quite different (well, im' not an expert in the d2v file format, so I can't really explain what difference means) - it seems like beta 12 files have more digits "2" in lots of lines...

[RB]

I just backed up "Signs" PAL RC2 using beta 12 tools and the result is perfect, no issues.

[Guest]

@len0x

Can you please email me the two D2V files so that I can assess the differences? What is the number of frames reported when served into VirtualDub for the two solutions? If the number of frames is correct I can't think of any way DVD2AVIdg/MPEG2DEC3dg could be responsible for async.

My email address is neuron2@comcast.net.

Crashing is not good. If you can duplicate it, then I'm going to need to get the VOB(s), possibly via normal mail.

I'm very keen to clear up all issues, so your continued assistance will be greatly appreciated.

[hakko504]

@ len0x

could you run fc 1773.d2v DGb12.d2v from a command prompt or the 'run' start menu item? If they turn out to be significantly different, have you tried parseD2V and FixD2V (from Don's site (http://neuron2.net)) to make sure the DVD is correct in itself? And a PAL DVD should hav a lot of 2's in it. :D

:devil: Too slow, Don posted while I was writing :devil:

[len0x]

@Neuron

I've sent you an email with both projects.
Regarding frame difference - there is one. DG version has 1 more frame in it...

@Hakko
I did fc straight away when I got them and got 300K difference...
I'll try using fixd2v and report back.

*EDIT* fixd2v found no errors in both 1.77.3 and DG versions.

[Guest]

Thank you. What happened with the re-encode with the original tools regarding the async condition?

[len0x]

Originally posted by neuron2
Thank you. What happened with the re-encode with the original tools regarding the async condition?

I'll be able to tell you exactly tomorrow morning :)
(I had to do some urgent encodings before that, but anyway - I'll keep Godfather's VOBs as long as needed).

[Cyberia]

I suggest giving these new DVD2AVI and MPEG2DEC3 instances a new version number higher than any existing version. (DVDV2AVI 2.0?, MPEG2DEC3 v1.11?)

[Guest]

@len0x

I'm sorry but I forgot that my POP cleaner deletes mails with large attachments. Would you terribly mind resending the D2V files? To bypass the POP cleaner include the word MAGIC (in upper case) in the subject line of each mail.

Thank you and sorry for the inconvenience.

[len0x]

lol :)
Np, I'll resend it tomorrow morning(from work where I have them) along with my test results (I'm doing two encodes: DVD2AVI 1.77.3+mpeg2dec3.dll 1.10 and DVD2AVIdg + mpeg2dec3.dll 1.10)

[jfcarbel]

posted as a new thread (per neurons request)

[jfcarbel]

Reposted to a separate thread as per neuron's request

[Zeul]

@neuron2

how close do you feel this is being to a public release? I only ask because a new version of NuMenu4U is to be released in the next day or so, and if possible the thought of being able to use the new fixed versions of dvd2avi and mpeg2dec3 appeals to me. apart from the obvious of using all frames the fact that the audio delay will now be exact is also of great benefit. Are these new 'fixed' versions only compatabile with avisynth 2.5+?

Zeul

[len0x]

First, I resent the d2v files to you, Don. Both encodes I did overnight came out perfectly sync. So if the problem exist it can only be in the new mpeg2dec3 (which again I'm testing as we speak). Later today I should have more info for you.

[len0x]

Originally posted by neuron2
Remaining work:
* make command line version.


Btw, is there estimation date when this feature gonna be implemented?
(GK supplies now two version of DVD2AVI 1.76CLI and 1.77.3 simply because R4R requires CLI version. But I'd pretty much would like to get rid of them both in favour of you version actually :) )

[Zeul]

ditto

[len0x]

OK, it's the new mpeg2dec3.dll which is faulty. To sum up:
DVD2AVI 1.77.3 + mpeg2dec3.dll 1.10 = sync OK
DVD2AVI DG + mpeg2dec3.dll 1.10 = sync OK
DVD2AVI DG + mpeg2dec3.dll DG = out of sync

[hakko504]

Before this turns into a 'I want this feature' and 'Why don't you do this' type of thread, can I just gently remind everybody about the free pies (http://forum.doom9.org/showthread.php?s=&threadid=7770). I'm just as eager as anybody else to see this project completed, but I'm sure neuron2 is already putting as much effort into this as he possibly can, and that we will see the final result within moments of it's completion.

[Guest]

@len0x

Can you please describe exactly what software, codec, and process you used that produced the async result?

If I send you a mailing address would you be willing to send me the VOB(s) to enable me to duplicate the issue?

Thank you.

I can get a CLI version out quickly but we have to solve this issue first, obviously.

[len0x]

I hope nobody thought that I was pushing Neuron :)
My question was just informative... (unfortunately I have to ask those kind of questions to be able to plan releases of GK properly)

[len0x]

Originally posted by neuron2
Can you please describe exactly what software, codec, and process you used that produced the async result?


Divx 5.05 (two passes + b-frames) + ac3 track done by GK 0.28.5.2 which uses VirtualDubMod 1.5.1.1a(b1639) + avisynth 2.5.2 (Lanczos resize, no other filters)

Originally posted by neuron2
If I send you a mailing address would you be willing to send me the VOB(s) to enable me to duplicate the issue?


How big vob (well actually I have m2v + ac3 demuxed files only) are we talking about? Total size is 7Gb... I don't think it's feasible to sent it over...

I checked more closely and found that out of sync started to be visible after 20 min of a movie, which is probably where switch from first M2V file to the second occurs...

*EDIT* Actually my calculation indicate that switch should be around 26min, so probably it's still in the first M2V, but hardly noticable
(by the end of the movie it's at least 3-4 sec delay though!)

[hakko504]

Originally posted by len0x
I hope nobody thought that I was pushing Neuron :)
No, my post should be interpreted as a pre-emptive move before things get out of hand.

[len0x]

I can also run this configuration:
DVD2AVI 1.77.3 + mpeg2dec.dll DG
Does it make sense to try ?

[Guest]

@len0x

I don't know GKnot so I don't understand your process. :(

What is the length of the demuxed audio before processing? What is the length of the final movie? Does the audio get ahead or behind? Is the frame rate in the D2V and the final movie exactly correct?

It is easily feasible to put the files on 2 DVDs for mailing, assuming you have a burner. The question is: How badly do you want this to be solved?

[len0x]

Originally posted by neuron2
@len0x
I don't know GKnot so I don't understand your process. :(


OK. Lets say we're doing this manually then:
1) I have AVS file (with just LoadPlugin("mpeg2dec3.dll"), mpeg2source(), crop(), LanczosResize()) I can provide exact file here...
2) I have target bitrate to be set for codec (710Kbps, 2CD rip)
3) I open it in VDubMod and do fast recompress to Divx5 (first, then second pass) using b-frames there
4) Then open resulting avi files in VDubMod, add stream with AC3 track
(in my case I have 0 ms delay, so I don't have to set the delay) settings interleaving to 2 frames.
5) Save avi in direct copy mode.

that's it...

Originally posted by neuron2

What is the length of the demuxed audio before processing? What is the length of the final movie? Does the audio get ahead or behind? Is the frame rate in the D2V and the final movie exactly correct?


Video: 252100 frames or 2:48:04h(if encoded with 1.10 of mpeg2dec3.dll it's 252098 frames, if used old dvd2avi and old mpeg2dec3 then 252096 frames)
Audio: 2:48:03.968 h
Final movie always have the same number of frames as video.
Frame rate is always 25.000fps

Audio is behind video.

Hope this helps.

Originally posted by neuron2

It is easily feasible to put the files on 2 DVDs for mailing, assuming you have a burner. The question is: How badly do you want this to be solved?

Oh, I misunderstood you here :) I do have a friend with a burner and can indeed try to mail it to you... (if we run out of ideas here)

[CruNcher]

i have another Bug to report neuron2 for VOB this looks ok now but for DVB mpg streams their allways 2 shit frames encoded now @ the beginning with it maybe LOLi didnt introduced this 2 frames difference accedantialy because i know he streams HDTV hmm ?