DGMPGDec 1.4.4 Final!

[Esc]

neuron2,
how hard would it be to mark the selection start with Home key and the selection end with End key (like in VDub)?

[Guest]

how hard would it be to mark the selection start with Home key and the selection end with End key (like in VDub)? Let's just say that it is so easy that I've already coded, tested, and documented it. It will be in the next release. Thank you for your suggestion.

[Guest]

That eliminates some amount of manual labour. Thank you very much.It's always interesting to hear the user perspective. Here I am sitting here thinking "Oh my Darwin, I've been wrong all along about these transitions. Pulldown has been broken since the first release of mpeg2dec3dg (later mutated to DGDecode)!" But you guys see it as "Ho hum, things are a bit easier now." Believe me, I lose sleep over this stuff. Lemme tell you, I'm just glad I discovered all this before someone told me. :)

I'm a bit surprised (but relieved) that no one has reacted to the paradigm shift that has occurred.

[TripleA]

I'm a bit surprised (but relieved) that no one has reacted to the paradigm shift that has occurred.

That's probably because the changes are invisible to the user. Except as a small reduction in work-load, in some cases.

[Marius-the-Mad]

* Colorimetry was reported incorrectly for MPEG2 in some cases. This has been fixed.I just want to say "Thank you!" to everyone involved. :) It was a really weird case.

So: thank you all! :thanks:

[mg262]

Mmmm. This is my broad perspective: (for me) there isn't time to understand everything related to video work; so I deliberately choose to focus on understanding things that can improve video quality (AVISynth filters and also capturing for analogue material) and not those that can't (MPEG decoding*, IFOs, CCE, XVid, H.264, Matroska, etc.). For the latter I read the manuals, FAQs, guides, and some posts and then stay close to default settings; when problems occur I deal with them. I am happy (and grateful) that other people write free software that lets me work this way; and as I chose not to put in the time to understand the technology properly, I'm hardly in a position to criticise anything, let alone the suboptimal two-stage (Create+Fix) implementation of a procedure where one stage sufficed. I am also happy that you (via software) choose between x.d2v or x.d2v.bad as opposed to my deciding myself -- partly because it's less work but also because the decision is much more likely to be correct.

Not having 52 extra x.d2v.bad files created is also a bonus ;).

*Nearly all my sources are PAL, so no telecine to worry about.

[Inventive Software]

Great! With the amount of new releases there are I'm updating your fine product almost every week!

[Esc]

Let's just say that it is so easy that I've already coded, tested, and documented it. It will be in the next release. Thank you for your suggestion.
Happy, happy, happy! Thanks a lot. Now it does everything I ever wanted.

[midnightsun]

Hello neuron2!

I think I've spotted a minor mistake in the documentation:

I was reading the dgdecode user manual and noticed that in the mpeg2source() filter syntax section, it reads:i420: true/false (default: false)

Output I420 Colorspace.
Possibly required by some legacy applications.
Ignored if the input is not YV12 (4:2:0), or if upConv=true.
- true: Output I420
- false: Output YV12

but in fact upConv no longer takes true/false as an argument.

Is that correct or am I missing something there? :)

[Guest]

Yes, that's a mistake. Thank you. I'll fix it for release 1.4.4.

[MacAddict]

Perhaps I missed the reason in another thread but I was wondering why the 'info' dialog doesn't stay open anymore as you drag the slider. Not a big deal, just curious :-)

Thanks again for all the effort!

[Guest]

The info dialog information is valid only during a play/preview. So as not to mislead users, I kill the info dialog when its contents may no longer be true.

Yes, I know some of the fields are still valid, but I don't consider it worth the bother to code it conditionally.

Note that the info dialog stays open when single stepping.

[MacAddict]

I see. Are you talking about the '<>' buttons for single stepping though? For me when I click them the info dialog disappears.

[Guest]

No. I'm talking about using > when playing/previewing with the playback speed set to single step.

[Guest]

DGMPEGDec 1.4.4 is now released:

http://neuron2.net/dgmpgdec/dgmpgdec.html

The only change from RC2 was adding the HOME and END keys as synonyms for the [ and ] buttons respectively.

[MacAddict]

Arghhh...sorry Donald. I see what you mean. I apparently haven't had enough coffee this AM :-) Thx again.

[Guest]

Yeah, I'm only halfway through my first cup too. Freshly ground Sumatra beans. Yum!

[Amnon82]

11. Fixed an indexing bug in DGIndex that caused incorrect random frame
access in DGDecode in some rare cases.

THX for this fix. Keep on going ;)

[Inventive Software]

Yay! My favourite MPEG-2 decoder for AviSynth goes stable once more! Great job, keep it up!

I have a suggestion. How plausible is it to allow users to change the naming convention of the files when they are demuxed from the VOBs? I'm not bashing it as such, it's detailed which is great, but it's more than I require, and I feel others may feel the same.

[Guest]

How plausible is it to allow users to change the naming convention of the files when they are demuxed from the VOBs? How so? I can't support every convention any random user might want, so you'd have to be more specific. OTOH, the source code is there for any changes that you desire.

[mg262]

Or you can rig up a batch file to call DGIndex and then rename the files?

[benten2000]

Ripped an anamorphic 16:9 720x48 DVD using Decrypter but when servered into DGIndex the info box says its a 4:3 720x480.

So what could be wrong?

[hannah]

Just my humble thanks..

[Guest]

Ripped an anamorphic 16:9 720x48 DVD using Decrypter but when servered into DGIndex the info box says its a 4:3 720x480. Please provide a source VOB fragment if you want me to look at this.

Also, see here: http://www.videohelp.com/forum/archive/t174200.html

It's not necessarily wrong to have a 4:3 encoded MPEG DAR for a widescreen movie.

[Guest]

Just my humble thanks.. Welcome to the forum, hannah! And thank you for your kind words. If you ever run into any problems, please let me know and I'll try to assist you.

[Inventive Software]

Quote:
Originally Posted by Inventive Software
How plausible is it to allow users to change the naming convention of the files when they are demuxed from the VOBs?

How so? I can't support every convention any random user might want, so you'd have to be more specific. OTOH, the source code is there for any changes that you desire.


I know that, but to give an example, when you extract in say Exact Audio Copy or CDEX, you can specify the naming convention by %T for the title, or %A - %T (%Y) to give the artist - song title (year). Something similar would be nice.

I'd like to take a look at the sources, but unfortunately my knowledge of C and/or C++ is very limited.

[EpheMeroN]

First off, great work with the latest final release neuron2. Glad to know someone is keeping this project current.

I noticed some new iDCT algorithms and just wanted to know what the differences were from the rest? "Skal SSE MMX" was chosen as default, and is this the best quality iDCT algorithm to choose? IIRC the last time I looked into it, the IEEE-Reference one was the best but it took longer to decode.

[planet1]

I noticed some new iDCT algorithms and just wanted to know what the differences were from the rest? "Skal SSE MMX" was chosed as default, and is this the best quality iDCT algorithm to choose? IIRC the last time I looked into it, the IEEE-Reference one was the best but it took longer to decode.

Well maybe Peter Gubanov could update the iDCT part of the manuals.

[Guest]

See DGDecode reference manual appendix. Also, read this thread and everything that it links:

http://forum.doom9.org/showthread.php?t=94925&highlight=idct+comparison