DGMPGDec Development List

[WorldofRoss]

Thanks :)

[Cyberia]

I was'nt expecting to see it under the christmastree the 24. of september. :p

The 24th of September is my birthday, and I definately don't expect to see it under the Christmas tree then. ;)

[FreQi]

My FOX station recently went full power, and I've discovered they go from 5.1 448kbit AC3 audio for the episode to 2.0 192kbit AC3 for the commercials. That change in bitrate messes up VDubMod when I do a direct stream copy to demux the trimmed parts of the show.

I would like to propose adding an option to DGIndex to replace 2_0 AC3 audio with 3_2 silence like you can do with ProjectX.

Thanks
- FreQi

[stax76]

I've seen people moving around their files and wonder why their d2v file don't work any longer because they don't realize they break absolute path information. Could relative paths like in Visual Studio projects be used?

[Guest]

I've seen people moving around their files and wonder why their d2v file don't work any longer because they don't realize they break absolute path information. Could relative paths like in Visual Studio projects be used? Relative to what?

[mg262]

The directory that the d2v file is in, I think. (Nothing else would be resilient against moving.)

[stax76]

Visual Studio project files encode code filepaths like this:

C:\level1\level2\project.vbproj

this is the most commonly used case

C:\level1\level2\file.vb => file.vb

if it's not a big problem, some more case's ;)

C:\file.vb => ..\..\file.vb
C:\level1\file.vb => ..\file.vb
C:\level1\level2\level3\file.vb => level3\file.vb

C:\level1\level2b\file.vb => ..\level2b\file.vb
...

Without this you wouldn't be able to move a Visual Studio project from one location to another, sources downloaded from the internet wouldn't compile.

[Guest]

@stax

I can't figure out what you are talking about; it's just too terse and I'm not into guessing games.

[mg262]

I have a file called

E:\dub\dvd\1 dvd.d2v

which contains the line

E:\dub\dvd\BS_1\VTS_01_PGC_03_1.VOB

He is suggesting that it instead store

BS_1\VTS_01_PGC_03_1.VOB

(or if you prefer .\BS_1\VTS_01_PGC_03_1.VOB )

Then, for example, if I were to move the entire E:\dub\ directory to another drive, the d2v file would still work.

(I hope I've put that clearly enough.)

[stax76]

Exactly, personally I have the vob and d2v file always in the same dir so a limited/lightweight implementation would be fine for me:

C:\level1\level2\file.d2v
C:\level1\level2\file.vob => file.vb

It's not a big issue for people who now it's hardcoded otherwise somebody would have mentioned it earlier but posibly it could help some newbies. You know, I always try to take care of them. :)

[mg262]

FWIW, I think this is a very convenient feature to have.

You know, I always try to take care of them.http://redwing.hutman.net/~mreed/warriorshtm/eaglescout.htm :)

[FreQi]

Funny, relative paths was exactly what my next request was going to be.

I tend to make my .d2v in the same location as my source files, and sometimes I move them from one machine to another. Directly editing the .d2v to reflect the new path of the source files is possible, but cumbersome when I have 60+ .ts files in the .d2v. Perhaps a rootPath could be "set" at the beginning of the .d2v that could be edited so when they do get moved, only a single line needs to be modified.

[PhillipWyllie]

Thanks for a great utility. What'd be nice is to log the timecode as well. This would allow users to see when a particular quantisation matrix was being used.

[PhillipWyllie]

When I select this on a 29.970 fps clip and save project and demux the resulting demuxed clip is still at 29.970 fps. Shouldn't it be 23.976fps?(for a 100% film clip).

[FreQi]

The video you're processing probably doesn't use pulldown flags. Instead it actually has the frames in it to make it 29.97fps. The fact that some of those frames are dupes or blended (if interlaced) is what makes it get detected as FILM. Those frames get dropped when you IVTC it to bring it back down to 23.976 (as close to FILM as you'll get).

[Guest]

Please don't post questions/problems in this thread. Thank you.

When you Ignore Pulldown Flags, DGIndex does not change the framerate; it just reports the stream value. Using general pulldown, the base rate could be anything. If DGIndex ignores the flags, he can't guess the base rate, so he just reports the stream value.

[PhillipWyllie]

Thanks and sorry. I know it has flags as I encoded the clip with flags. I just thought that DGIndex could work out the new frame rate and apply the flag to the newly demuxed MPEG-2.

[Cyberia]

DGIndex always demuxes the original stream. It does not alter it, except for cuts. So, any of the options under Video (pulldowns, luminance, colorspace) are not 'applied' to the demuxed stream.

[FreQi]

I recently posted a request for replacing 2.0 AC3 with 5.1 silence (http://forum.doom9.org/showthread.php?p=714255#post714255). I'd like to slightly revise that.

I'd like to be able to replace 2.0 AC3 with 5.1 AC3 of the same bitrate that remains in the audio stream (or be able to select a bitrate for the silence).

For example, I have a stream with 5.1 @ 384k that switches to 2.0 @ 384k. When using ProjectX to replace the 2.0, it repalces it with a silent sample at 448k. It should be 384k, but I have no way of telling it to do that...

[Yuri Khan]

I was slightly surprised to find that there was once a standalone, batch-scriptable DGParse but now it’s integrated in the GUI. It would be really good to have it accessible via the CLI.

[Sajan]

When I open file in DGIndex I can't find information window (only when playing or previewing). Sometimes it's wanted to see information while frame-by-frame seeking.

[tahir]

I convert alot of songs DVD's into VCD using DGIndex. I Rip the DVD in DVD Decrypter using IFO Mode and File Spliting is set to "By Chapter". So I have to manualy create projects for all the chapters.
I would like you to implement a feature in DGIndex that Automaticaly Creates D2V and AVS files per chapter (IFO Parsing).

And thank you for such a great tool.
:thanks:

[Tatsh]

The AMD Turion 64 laptop processor changes speed constantly using multipliers 4, 8, and 10. When I encode with VirtualDub, the speed stays at 2GHz (10 x 200), but when I make a D2V in DGIndex, the speed is at 1.6GHz (8 x 200). I think, because I had a AMD Athlon 64 2.2GHz PC before, that this 400MHz might make a difference in speed (consider: 3 minutes for a normal length movie with Skal SSE MMX on the Athlon 64 processor although it was 2.2Ghz not 2Ghz, 15 minutes for this Turion 64 at 1.6GHz with Skal SSE MMX) So somehow, DGIndex would somehow need to tell the processor or OS drivers to keep the speed to the maximum (or prioritize). Windows prioritizing does not work on this.

I don't know much on the subject, but somehow the processor or VirtualDub know to keep the speed at 2GHz for encoding.

Or, is the speed because of the laptop HD speed (4200 RPM)? Even with 7200 RPM a USB2 HD, it seems to be about the same.

[Zep]

Or, is the speed because of the laptop HD speed (4200 RPM)? Even with 7200 RPM a USB2 HD, it seems to be about the same.

yes odds are you are disk I/O bound and there is no need for the CPU to be running faster. If you are writing the d2v file to the same drive as reading the source stream then that would make it even worse and XP likes to pageout a lot and if this on the same drive also... yuck :)

[kypec]

Hi neuron2,

I just downloaded your 1.4.8 Final release and found out that the File version (File->Properties | Version tab)
of both DGIndex.exe and DGDecode.dll is still showing 1.4.7.0
although the Product version in details tab reports properly 1,4,8,0
Could you please re-release those files so that no users would be confused about version numbers inconsistency? :confused:

[Guest]

I updated the zip files to correct this. Thanks for pointing it out.

(May I ask next time can you please not wait for my final release to report things? The 1.4.8 beta has been ongoing for a long time, at any point of which you could have reported this.)

[kypec]

(May I ask next time can you please not wait for my final release to report things? The 1.4.8 beta has been ongoing for a long time, at any point of which you could have reported this.)
I'm really sorry about not mentioning it earlier but the only beta I had downloaded before was 1.4.8 beta 7.
At that time I didn't check the file properties at all because I was eager to try it out after reading all included documentation and help files.
Anyway, it's a terrific piece of work you made on it, keep it up :cool:

[devaster]

Hi neuron2 i have problem with linking dgdecode from latest sources from your web
link says that a symbols @simple_idct_mmx and @Skl_Dct16_SSE defined in asm files (simple_idct_mmx.asm and skl_dct_sse.asm) are unknown (compiling is ok...)...
whath i may do to fix it ???

[Guest]

Make sure these are in the project:

simple_idct_mmx.asm
skl_dct_sse.asm

Then you need NASM installed to build them.

Everything is setup correctly in the shipped project file. You probably don't have NASM.

[devaster]

I have:
- both asm in project
- nasm is installed and functional

as i have wrote compiling is ok (when i havent a nasm then woudnt compile due a custom build step error) :confused:
only linking is a problem

today at 23:00 ill sent to this forum a full error statement from VS from my home - it would be better

[devaster]

okay there is this error strings:
Error 1 error LNK2019: unresolved external symbol @simple_idct_mmx@4 referenced in function "public: int __thiscall CMPEG2Decoder::Open(char const *)" (?Open@CMPEG2Decoder@@QAEHPBD@Z) vfapidec.obj
Error 2 error LNK2001: unresolved external symbol @simple_idct_mmx@4 AVISynthAPI.obj
Error 3 error LNK2019: unresolved external symbol @Skl_IDct16_Sparse_SSE@4 referenced in function "public: int __thiscall CMPEG2Decoder::Open(char const *)" (?Open@CMPEG2Decoder@@QAEHPBD@Z) vfapidec.obj
Error 4 error LNK2001: unresolved external symbol @Skl_IDct16_Sparse_SSE@4 AVISynthAPI.obj
Error 5 error LNK2001: unresolved external symbol simple_idct_mmx@4 DGDecode
Error 6 fatal error LNK1120: 3 unresolved externals .\Debug/DGDecode.dll

[devaster]

Please help !!!

[Nic]

@devaster: Please don't double post.
Your unresolved errors are due to the either the ASM not being compiled (correctly) or the resulting .obj files not being finally linked at the end. Ensure they are being compiled inside the DGDecode project correctly. If they are, then find the .obj files created by NASM and add them directly into the project, that will ensure they get linked by the linker.

-Nic

[Guest]

Please put bug reports in the relevant beta thread. This is for feature discussion/scheduling/tracking. Thank you.

[winnydows]

I use your program in XviD4PSP (http://www.winnydows.com/xvid4psp.html). And realy miss one simple feature of your program - print % progress in DGindex title on Project Saving. Add this simple feature please.

[Guest]

I use your program in XviD4PSP (http://www.winnydows.com/xvid4psp.html). And realy miss one simple feature of your program - print % progress in DGindex title on Project Saving. Add this simple feature please. OK, sure. I have it working in my latest build. It will be in the next beta.

[The Scientist]

This may seem trivial, but is there any chance you could remove, or give a switch to remove the 'ping' at the end of the indexing process when DGIndex is ran via the command line.

I'm not sure whether the problem is the 'ping' or something that gets executed at the same time but it removes focus away from the app that's called it, which means I have to force a topmost command to bring my app back to view/focus which can be annoying if a user is currently doing something in another app that will force them to lose focus.

Hope that makes sense...

Thanks :D

[Guest]

This may seem trivial, but is there any chance you could remove, or give a switch to remove the 'ping' at the end of the indexing process when DGIndex is ran via the command line. Done. It'll be in the next beta.

[The Scientist]

Cheers :)

[Zarxrax]

Could you please add drag/drop support to the open file dialog?

[Guest]

I don't see the point. You can already drag and drop onto the open DGIndex window or a Windows shortcut to DGIndex.

[Zarxrax]

Haha, ok I'm just stupid then. I didn't try it that way :p

[Guest]

You can try reading the Users Manual to learn about these obscure features. :)

[JeffAlso]

Any chance of adding support for EVOB files??

[Guest]

I'm looking at H264 support first.

[winnydows]

10x for % adding.

One more small request:
Trim feauture exists in GUI, but missed in CLI mode. Can you add Trim to CLI mode in next beta ? Please.

[Guest]

How will you determine and specify the trim points?

[winnydows]

Determine and set frames I do inside XviD4PSP (4.107 RC2). Then set in DGIndex trim points, like --trim 12345:23445 (in frames). I think it will be better than extract full d2v and than trim in avs.

[Guest]

But DGIndex is not frame accurate.

[winnydows]

Seconds trim not bad too.