DGMPGDec 1.4.3 Final!

[CptRobby]

OK..I'm having trouble right now working with a DVD that has multiple angles...I wanted to avoid posting a question that's already been posted before, so I did a little searching before hand and found that, apparantly, multi-angle processing is currently not (and/or has no plans to be) supported in DGIndex.

I also found a bit of information on how the multi-angles work, both from searching the forumns and also using tools like Chapter-X-tractor to look at the files and came up with a (workable) solution to this problem and also happens to be a feature I've been hoping to see for a while for other reasons...

Since angles are stored on different vob-ids (ex: with the one I'm working on, angle 1 is on vob-id 8 and angle 2 is on vob-id 9) if you could put in an option to select which part you want to use by vob-id (and possibly cell-id too) (kinda like the way vobsubconfigure works) then I could just select the vob-ids for the angle that I want to use and rip away...

It would certainly be preferable if you could select the vob-ids/cell-ids non sequentially (ie: 1 - 3 - 4 - 6) But if that's not possible, or requires too much meddling, then just being able to create 3 simple D2Vs (1, and 3 - 4, and 6) would be enough. Then I could just create AVS files and throw them together in VirtualDubMod.

The other reason why I would like this feature is because I do alot of anime and TV episodes, and like Esc was saying before, often times you want to just select certain vob/cell-ids at a time. This would certainly make it alot easier to do!

Anyways, it could be that you've already gotten a suggestion along this line and found that it's not possible to do. I didn't find anything when I tried to search for it, but if that's the case, then just slap me with a link to it and continue what you were working on. lol

And thank you very much for all your hard work!
Robby :)

[Esc]

CptRobby, are you trying to use DGIndex directly on DVD? Because DVDDecrypter in ifo mode does select only one of the angles and you have no problem if you rip the dvd with it first.

[Zep]

Not formally as in contributing code. I had posted at the VirtualDub forum asking how he achieved playback pacing in VirtualDub, and he responded with some valuable ideas. Here is the posting for those interested to see it:

ahhh ok


http://forums.virtualdub.org/index.php?act=ST&f=11&t=9985

interesting read. yup he does know the ways of low level timing lol
some of his numbers were surprising. 9x 55ms OUCH.

[Guest]

OK, folks, unless bugs are found, this will be the last RC. This release has two nice little surprises. One is pretty obvious. See if you can find the other one. No fair looking at the changes list! First person to spot it gets an atta-boy.

http://neuron2.net/dgmpgdec/dgmpgdec141rc4.zip

I also added dvd2svcd to the Credits listing in the DGIndex manual, as I had inadvertently dropped him. If I've missed anyone else, please let me know. Thank you.

[Cyberia]

Oh....Oh....Oh.....I know!!!

[CptRobby]

CptRobby, are you trying to use DGIndex directly on DVD? Because DVDDecrypter in ifo mode does select only one of the angles and you have no problem if you rip the dvd with it first.

No, I'm using DGIndex on a ripped copy on my HD...And Yes, I do know about DVDDecrypter's IFO mode...I've tried it once before and it caused the copy I made to not work so I just always used the file mode and copied everything...I've never had a problem like this before...

But really this isn't about making it so that I can get this copy to work, that's not really important since I can just rip it again in IFO mode (hopefully I can figure out how to get it to work this time)

The reason why I made the suggestion was because I think it would be a good feature to have in general. And really what I was suggesting was only a WORKABLE solution to the problem of multi-angles...I wouldn't suggest making an actual solution to the multi-angle situation at this stage because it would require changing alot of stuff in the code (it would have to analize the IFO file to detect multiple angles at the very least along with a bunch of other stuff) in addition to making it able to select specific vob/cell ids. I can't imagine that there would be a way to do it without that functionality.

So anyways, I just think that this is the best next step in the evolution of DGIndex (on this front anyways, I'm sure there are probably other things that others have noticed that might even be more important than this...) ;)

Robby :)

Edit after DLing release:
There's a DGDecode manual...coolness! :)

[CptRobby]

SPIKE! LOL He IS the uber coolness! ;)

[Guest]

Oh....Oh....Oh.....I know!!! Atta boy! ;)

[Guest]

So anyways, I just think that this is the best next step in the evolution of DGIndex... User suggestions are always welcome. Thank you for yours.

[SeeMoreDigital]

User suggestions are always welcome. Thank you for yours.Errrrm!

Could it be possible to make it so we can place our own images/logo's in the start-up panel (I can feel the knives in my back already)?

And how about some links under the "Help" button pointing to those lovely new "html" documents?


Cheers

[Guest]

Could it be possible to make it so we can place our own images/logo's in the start-up panel (I can feel the knives in my back already)? What, you don't like Spike? That has some very sentimental meaning to me, which manono will understand well. And it's got to be an improvement over a black rectangle. I'll consider it for the next version. Skins for DGIndex...LOL.

And how about some links under the "Help" button pointing to those lovely new "html" documents? Done. Thank you for the suggestion.

You seem to have changed your avatar. :confused:

[SeeMoreDigital]

What, you don't like Spike? That has some very sentimental meaning to me, which manono will understand well. I'll consider it for the next version.I thought I'd been hacked when I first fired up RC4 :scared:

If you do decide to offer image selectivity. How about offering it in a similar way to MediaPlayer Classic?

You seem to have changed your avatar. :confused:Yep... It's an still from "House" (http://www.tv.com/house/show/22374/summary.html?q=House) and was cropped from this picture: -

http://tinypic.com/b80lrp.jpg


Wonderful

[Guest]

If you do decide to offer image selectivity. How about offering it in a similar way to MediaPlayer Classic? Would you care to enlighten me about that, as I do not use that software? Thank you.

[SeeMoreDigital]

I'm unable to tell you how it's done... but you are given a choice of stock logo's. Plus the option of navigating and selecting any image of your choice...

Like this: -

http://img6.imageshack.us/img6/3595/mpcexample0ku.gif


Hope that helps?

[Guest]

I'm unable to tell you how it's done... That's the easy part. I didn't know what their UI was for it. I can do that in 1.4.2.

BTW, if you (or anyone else) would like to submit a BMP before I go final, I'd consider using it. It has to be the size of the DGIndex window with no file loaded. It can be a little bigger (due to clipping), but no smaller.

[SeeMoreDigital]

Blimey... I thought this was going to be really difficult to do.... So ideally proposal images need to be 480x270 pixels?


Cheers

[Guest]

So ideally proposal images need to be 480x270 pixels?
498 x 312 is good.

[Cyberia]

I uploaded five pics as my submissions.

cyb_pics.zip

[Guest]

I like the Dali. (But they have to be BMP files, not JPGs.)

I changed DGIndex to use Spike unless you put your own BMP file in the DGIndex.exe directory.

[Guest]

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

[Leak]

I changed DGIndex to use Spike unless you put your own BMP file in the DGIndex.exe directory.
Are you sure Bandai/Sunrise is going to like this? :eek:

(Not that I don't own all of Cowboy Bebop, but still...)

np: Pedestrian - The Toss & Turn (Anticon Label Sampler)

[Guest]

Are you sure Bandai/Sunrise is going to like this? Fair point.

I changed the executable so that it doesn't load a default Spike. If anybody downloads splash screens from my web site and puts them in their DGIndex directory, I don't know anything about it.

[SeeMoreDigital]

Donald you're a star!

Thanks so much for adding the single frame advance feature (while still displaying the frame number).... I feel truly blessed :D


Faaaaantastic!

[Guest]

Thanks so much for adding the single frame advance feature (while still displaying the frame number) You're welcome. But be careful...the frame numbers in the Info dialog start from the point where playback starts; they're not valid frame numbers in the whole file.

[SeeMoreDigital]

As a matter of interest, how much detail can DGIndex be configured to reveal about an MPEG-1 or 2 stream?

For instance, would it be possible to flick thru' a stream, one frame at a time and know whether it's an I, P or B frame?


Cheers

[Tima]

Donald, thank you for your work!

Could you make "Information" window a little narrower? It'd be much more comfortable to use DgIndex at 1024x768. :)

BTW, why dgindex.exe is 2x bigger than 1.40?

[sorry for my bad Eng.]

[Guest]

As a matter of interest, how much detail can DGIndex be configured to reveal about an MPEG-1 or 2 stream?

For instance, would it be possible to flick thru' a stream, one frame at a time and know whether it's an I, P or B frame? I don't know what you mean by "configured" in this context. I could expose anything with appropriate coding.

[Guest]

Could you make "Information" window a little narrower? That's too vague to respond too. Do you mean 1 pixel, 5, 15.... ?

BTW, why dgindex.exe is 2x bigger than 1.40? I'll update the distribution with a version without the "Spike" resource.

[SeeMoreDigital]

I don't know what you mean by "configured" in this context. I could expose anything with appropriate coding.With me not being a techie in such matters I guess I'm using the wrong expressions...

But when I was scanning thru' one of my .VOB files at one frame at a time, I got the idea that it might be kinda neat to know what type of frame (I, P, B) I was on!


Cheers

[Guest]

With me not being a techie in such matters I guess I'm using the wrong expressions... You're not? Now you've disillusioned me.

I've been trying to catch up to your post count for years. Now I'm closing in. Can't you take a vacation or something. I hear Brasil is an attractive destination.

But when I was scanning thru' one of my .VOB files at one frame at a time, I got the idea that it might be kinda neat to know what type of frame (I, P, B) I was on! You can see it in DGDecode's info display, but it might be worth adding to DGIndex. Maybe some extra fields could appear when single step mode is on.

[Tima]

That's too vague to respond too. Do you mean 1 pixel, 5, 15.... ?
I think about something like this:
http://for_spam.gorodok.net/Inf_new.GIF
(sketch, made in mspaint :) )

It is not very much, but IS better, IMHO. I'm not sure this is worth bothering.. well I'm not the one to decide.. :)


And here is a bug suspicion: sample, 428032 bytes (http://for_spam.gorodok.net/VTS_01_1.VOB). DGIndex doesn't decode it properly when stepping forward through frames right after importing. When stepping backwards, it's OK. Also, it's impossible to REselect the whole length of the clip using the timebar and selection buttons.

Thanks.

[Guest]

And here is a bug suspicion Do you guys wait for the release to report these things just to torment me? :)

FWIW, if you generate a project and serve the video it is correct.

I'll look into it.

EDIT: The video has 7 frames, each coded as a sequence with a sequence end code, and each one specifying different quant matrices. The sequence end codes were stopping DGindex from picking up the new quants. I'll fix it in the next beta. Fortunately, it's very unusual video. Thanks for bringing it to my attention.

[SeeMoreDigital]

You're not? Now you've disillusioned me.

I've been trying to catch up to your post count for years. Now I'm closing in. Can't you take a vacation or something. I hear Brasil is an attractive destination. Arrr.... your posts however are.... quality consistent!

When I look back at some of my earlier posts they make me want to cringe! So I don't suppose I'm up to being "Moderator" material ;)

You can see it in DGDecode's info display, but it might be worth adding to DGIndex. Maybe some extra fields could appear when single step mode is on.I must admit in my enthusiasm for DGIndex I've neglected DGDecode.... I must start thinking "outside of the box" more!


Thanks again DG

[Tima]

EDIT: The video has 7 frames, each coded as a sequence with a sequence end code, and each one specifying different quant matrices. The sequence end codes were stopping DGindex from picking up the new quants. I'll fix it in the next beta. Fortunately, it's very unusual video. Thanks for bringing it to my attention.

Wow, It's really unusual :) Thanks for the explanation.

[d'Oursse]

neuron2: there are only "minor" changes in this version (for dgindex) ? No change of design ?

[Doom9]

the size of the executable has gone up dramatically, undoubtedly due to the inclusion of the background image. Since it adds nothing in terms of functionality, somebody has to be the devil's advocate and ask if that kind of cosmetics was really necessary.

[Cyberia]

the size of the executable has gone up dramatically, undoubtedly due to the inclusion of the background image. Since it adds nothing in terms of functionality, somebody has to be the devil's advocate and ask if that kind of cosmetics was really necessary.

He already answered this. (not often I can catch d9, so I had to do it)

I'll update the distribution with a version without the "Spike" resource.

[Cyberia]

@Tima: The width of the Info panel is directly tied to the font it uses. I was going to ask neuron2 if he was married to that font.

@neuron2: Are you married to that font? (That the Info Panel uses?)

[Guest]

neuron2: there are only "minor" changes in this version (for dgindex) ? No change of design ?The changes listing describes at least one major design change regarding the slice/macroblock layer.

Was there something else you were hoping for? I don't recall hearing any suggestions from you.

I'm sorry to have disappointed you. I'll try harder next time.

[Guest]

Are you married to that font? (That the Info Panel uses?) AFAIK, it's determined by Windows. Anyway, what's the big deal? And again, all this time developing 1.4.1 and it's only *after* I release it that it becomes an issue!?

Sometimes I wonder why I bother.

Good night, all. I'll try to do better next time. If there is one.

[Guest]

neuron2: there are only "minor" changes in this version (for dgindex) ? No change of design ? I consider the slice/macroblock parsing changes to be major.

Was there something in particular you were hoping for? I don't recall hearing any suggestions from you. As you know, I always welcome suggestions and I try as hard as I can to respond to issues and problems.

[d'Oursse]

I consider the slice/macroblock parsing changes to be major.

Was there something in particular you were hoping for?
A change of design would have make my previous work useless
I don't recall hearing any suggestions from you. As you know, I always welcome suggestions and I try as hard as I can to respond to issues and problems.
Suggestions ? If I succeed in writing this lib, a big part of the remaining code needs to be rewritten. I didn't made any because when I started that, you were already writing the 1.4.1 version.

ok,, here are some ideas/suggestions (for dgindex only).

The main problem for me is that the gui is not apart from the remain of the code. There are global variables that are used for everything, everywhere, which make the code very hard to read and understand for someone who has not written it. Macros are used in a same manner. All the macros in getbits.c, for example.

So, I would create a global structure that contains all the variables that the gui needs. I would cut dgindex in 3 parts :

1) the parsing/creation of the d2v file/demuxing of audio.
2) the decoding of the video
3) the gui

When I say "cut", I mean that they are really independant. Point 1) and 2) depend only on the global structure that is mentioned above. They are just libs with an API. Point 3) calls the functions that are exported by these 2 libs in their api.

For eah point, i would follow some general ideas. For example, for point 1), I do the following:
a) I create a structure that contains all the needed variables. They can also just lie in a "private" file that is only usuable in this lib.
b) I have separate the audio and the video in separate files and separate directories. At least, someone who reads the code know where to look for if he wants to look at/debug the code.
c) I put the exported function in several files, so that it makes the code more readable.

The advantages:
a) It's easy to make a CLI for each part, which does not depend on useless part of the code. Small code for the work we ask for. No useless code.
b) The gui depends on the lib only by the api, which makes porting dgindex to other platforms (linux :D) easy, as only this part needs to be rewritten (I suppose that point 1) and 2) can be coded in C ANSI).
c) the pleasure of writing a beautiful code :)

Finally, I finish by the structure of the directories I would have create for this project (that thing is important for me):


dgindex
+-build
| +-linux
| +-win32
|
+-doc
| +-API
| +-Manual
|
+-src
+-bin (platform dependant code)
| +- Here lies the binaries, that is the gui_win32.c, gui_linux.c files, and the CLIs.
| Maybe the CLIs can be platform independant, or at least with small modifications.
|
+-lib (platform independant code)
+-parsing
| +-audio
| +-video
|
+-decoding (I have no idea for the directories i would make for the decoding)

I have other suggestions, but I stop here and wait for your comments.

[Guest]

I have other suggestions, but I stop here and wait for your comments. There is zero chance that I would ever undertake such a massive re-engineering. But feel free to tackle it as you proceed with your Linux port.

[Doom9]

He already answered this.I forgot the character was named Spike.

On another matter, would it be possible to turn the source selection into a cutting tool? I guess the video part of it wouldn't be too problematic, but I figure audio might be a pain, especially when audio is not being decoded.

[Guest]

I don't usually like to do this, but I thought it was important to get Tima's bug fixed, i.e., improper handling of sequence end codes. Therefore, here is version 1.4.2. The only change is the fix for sequence end code handling.

http://neuron2.net/dgmpgdec/dgmpgdec142.zip

Source code is released at my web site.

@Tima

Your stream decodes properly with 1.4.2.

@Doom9

Can you please explain more by what you would want in the cutting feature? Thank you.

[davidf]

A small request for the next version of dgindex -(maybe not so small :) ) I looked at the code myself and sorta got lost, plus lack of c knowledge hindered me a little.

Would it be possible with the cli version to output things such as audio filenames and a/v delays to a text file. this would make life much easier when programatically using the cli version then creating scripts to do such things as audio resampling and a/v muxing.

TIA.
David

[Doom9]

Can you please explain more by what you would want in the cutting feature?Right now you have the [ and ] buttons right to the timeline - they allow you to select only parts of the source. There's one "in" cut and one "out" cout and everything in between is indexed when you create a project. Rather than just have one in and out cut, I'd like to have multiple ones, so that if I have a 10'000 frames source for instance, I could create a project containing frames 2000-3000, 4000-5000 and 6000-9999, and all in one project rather than creating three separate projects, one for each of the regions I mentioned.

[Tima]

Here are some other bugs with at least THAT sample:

- DGIndex doesn't displays the second frame when viewing the frames in reverse order (using arrows)

- When _clicking_ on the time bar, DGIndex displays nothing at all. :)

-[not a bug] The Super Slow mode isn't really super slow. :) Maybe 1fps would be more appropriate?

- when changing to any mode except Single Step, the '>' button is greyed out. It restores only after switching to Single Step.

[mgh]

When I load an mpg (1), i get warning saying force film is not advisable and am i sure.This happens regardless of the option chosen.It proceeds only when i say yes and then the d2v fails to load via avisynth. I have tried only with PAL mpgs,don't haveNTSC ones. :confused:
Have gone back to 1.4.0

[Guest]

When I load an mpg (1), i get warning saying force film is not advisable and am i sure.This happens regardless of the option chosen.It proceeds only when i say yes and then the d2v fails to load via avisynth. I have tried only with PAL mpgs,don't have NTSC ones. :confused:
Have gone back to 1.4.0 I duplicated the erroneous warning but not the failure to load via Avisynth. I cranked a new version 1.4.3 to fix the warning. Try it and post again if you still have problems.

http://neuron2.net/dgmpgdec/dgmpgdec143.zip