DG NV tools [Archive] - Page 14

Guest

6th December 2009, 15:29

While that is very possible, and I hope it is so, it still remains that the files (individually indexed) added up gives 58mins, and the full demuxed audio (demuxed with dgindex(nv)) is also 58 mins :( Your 5.mpg file has dropped frames. You can see that it plays jerky at the beginning in MPCHC. A player will go by the timestamps and freeze frames so as to present frames at their presentation times. So there is no bug in DGIndex or DGIndexNV in this regard.

whatever-ever

6th December 2009, 15:44

Your 5.mpg file has dropped frames. You can see that it plays jerky at the beginning in MPCHC. A player will go by the timestamps and freeze frames so as to present frames at their presentation times. So there is no bug in DGIndex or DGIndexNV in this regard.

Thank you for clearing that up :)

Good to here there's no bug.

Keep up the good work

Guest

6th December 2009, 15:57

The new DGIndexNV seems to struggle with DTS audio tracks now, with the old V11 beta it would load up fast and just not show the DTS track. Now when I add vob files containing a DTS track, it sits there for a couple minutes "Not Responding" and still doesn't show the DTS track.

It's relative to size, a small 50MB clipped vob will load decently fast.

http://www.mediafire.com/?jtbgluijiok I'll move this to the top of the priority list.

Jeff Flowerday

6th December 2009, 18:44

I'll move this to the top of the priority list.

:thanks:

Jeff Flowerday

6th December 2009, 18:48

Please try closing the Info diaglog after starting the Save Project. Does that make a difference when not minimized?

Yes, if you close the info dialog it's just as fast as minimized.

Guest

6th December 2009, 22:13

Yes, if you close the info dialog it's just as fast as minimized. Good, that's what I suspected, that it was the overhead of updating the Info dialog that was causing it. I'll fix that and add DTS for the next beta.

Guest

7th December 2009, 02:08

Jeff Flowerday

7th December 2009, 02:17

* Eliminate overhead of updating the Info dialog while saving project. This speeds up indexing substantially.

* Add support for DTS audio in program streams.

@Jeff

Please advise if DTS support is working properly.

http://neuron2.net/dgdecnv/dgdecnv200b5.zip

I just did a test indexing with extraction of DTS and it seems to be. I'll keep you updated when I actually have something ready to fire through x264 and test the final result.

:thanks:

Jeff Flowerday

7th December 2009, 02:24

Ok I just tried throwing the resultant dts file into mkvmerge and it's giving me no valid header errors when I try to mux the dts into a MKA file.

mediainfo doesn't give me details on the resultant dts file either?

Guest

7th December 2009, 02:35

Checking it...

Guest

7th December 2009, 03:07

All fixed. Please redownload.

Jeff Flowerday

7th December 2009, 03:48

All fixed. Please redownload.

Yep, much better.

:thanks:

marcio

7th December 2009, 05:45

Neuron2,

Why AVCSource() isn't working with CCE 2.5?
Is there a work arround?

OBS: Is does work with CCE 2.7, but not with CCE 2.5...

Guest

7th December 2009, 13:56

You're in the wrong thread. This is for the NV tools. Anyway, I don't have CCE 2.5 so I can't help you.

laserfan

7th December 2009, 16:17

* Eliminate overhead of updating the Info dialog while saving project. This speeds up indexing substantially.Tried it (200b5a) and it does seem faster, but now there is no log info at all--was that your intent? My log file:

Stream Type:
Video Type: AVC
Profile:
Level:
Coded Size:
SAR:
Display Size:
Frame Rate:
Colorimetry:
Frame Structure:
Frame Type:
Coded Number:
Playback Number:
Frame Repeats:
Field Repeats:
Bitrate:
Bitrate (Avg):
Bitrate (Max):
Elapsed: 0:03:20
Remain: 0:00:00
FPS:
Info: Finished!

Version=DGIndexNV 2.0.0 beta 5
Window_Position=220,100
Info_Window_Position=4,99
YUVRGB_Scale=1
Field_Operation=2
Process_Priority=2
Playback_Speed=3
AVS_Template_Path=C:\Program Files (x86)\DGIndexNV\template.avs
Full_Path_In_Files=1
MRUList[0]=D:\video\videoOUT.264
MRUList[1]=
MRUList[2]=
MRUList[3]=
Enable_Info_Log=1
Loop_Playback=0
AVC_Extension=264
MPG_Extension=m2v
VC1_Extension=vc1
Deinterlace=0
UsePF=0
AlwaysBottomCrop=1
UseD3D=0

Guest

7th December 2009, 16:52

Not my intent. :)

Will fix.

dgeise

7th December 2009, 22:18

I can't duplicate that with 2.0.0 beta 4. Give me an exact filename and tell me how you make it fail.

I can no-longer reproduce this in beta 5.

Thanks.

Guest

8th December 2009, 02:33

Tried it (200b5a) and it does seem faster, but now there is no log info at all. Please re-download and try again. It disables the log after 100 frames when saving project.

GearX

8th December 2009, 06:17

Hello,

I'm having trouble with DGIndexNV 2.0.0 beta 5 crashing when attempting to index 29.970 fps 1080i (pure interlaced) VC1 video in a Matroska file: SAMPLE (http://www.mediafire.com/?zmmym2gqdjw)

F4/Save Project almost immediately crashes, with the Windows error dialog DGIndexNV.exe has encountered a problem and needs to close etc. I get a zero-byte DGV file and no log.

However, F5/Preview works fine (!) Display proceeds through the clip, and I get this log upon exit:

Stream Type: Matroska
Video Type: VC1
Profile: Advanced
Level: 3
Coded Size: 1920x1088
SAR: 16x9
Display Size: 1920x1080
Frame Rate: 29.970030 fps
Colorimetry: Reserved [2]
Frame Structure: Field Interlaced
Frame Type: P-P
Coded Number: 150
Playback Number: 216
Frame Repeats: 0
Field Repeats: 133
Bitrate: 8.502
Bitrate (Avg): 9.368
Bitrate (Max): 13.730
Elapsed: 0:00:05
Remain: 0:00:00
FPS: 26.64
Info: Finished!

I tried saying No to bottom-cropping but that did not help.
I can enable PureVideo deinterlacing and see its effect(s) in Preview, but Save Project still crashes the same way.
Disabling the display in the Video menu also did not help.

I read through the User Manual files but didn't see anything warning against pure interlaced VC1. (Apologies if I missed it.)
The mkv was created by remuxing a blu-ray with eac3to, then mkvmerge to trim out a sample clip and separate the video from the audio. (I wouldn't normally do the second part, but here I did so while troubleshooting to eliminate the audio as a cause of the problem.)

NVidia GeForce 8800 GT, driver version 195.62
Windows XP-SP3, Intel Core2 6600 at 2.4GHz (no OC), 2 GB RAM

Any thoughts on what might be going wrong?

Let me know if the Windows error report would be useful, and I will supply it.

Thanks!

GearX

8th December 2009, 06:40

I also noticed this in the User Manual under Enable PureVideo Deinterlacer (my emphasis added):

Check Use progressive_frame if you want the deinterlacing to honor NVCUVID's progressive_frame indication. If single or double rate deinterlacing is enabled and this option is checked, then only frames marked as progressive by NVCUVID will be deinterlaced. If single or double rate deinterlacing is enabled and this option is not checked, then all frames will be deinterlaced.

Shouldn't that say "...only frames NOT marked as progressive..." ?

Guest

8th December 2009, 14:56

I also noticed this in the User Manual under Enable PureVideo Deinterlacer (my emphasis added) Where did you see that? In the 2.0.0 beta 5 zip, it is not that way.

Guest

8th December 2009, 15:13

I'm having trouble with DGIndexNV 2.0.0 beta 5 crashing when attempting to index 29.970 fps 1080i (pure interlaced) VC1 video I know what's wrong but it may take a few days to fix it. Thank you for your sample.

GearX

8th December 2009, 16:20

Where did you see that? In the 2.0.0 beta 5 zip, it is not that way.

Well, actually it is. There are five HTML files in the zip, three of which are DG*IndexNVManuals, and all three say the same thing.

dgdecnv200b5/DGVC1IndexNVManual.html#Deinterlace
dgdecnv200b5/DGAVCIndexNVManual.html#Deinterlace
dgdecnv200b5/DGMPGIndexNVManual.html#Deinterlace

I suppose they are old files anyway? Checking further, the pages are titled like this:

DGAVCIndexNV 1.0.14 beta 11
DGMPGIndexNV 1.0.3 beta 11
DGVC1IndexNV 1.0.7 beta 11

Was it perhaps your intent to include only one HTML file for the new combined DGIndexNV?

GearX

8th December 2009, 16:21

I know what's wrong but it may take a few days to fix it. Thank you for your sample.

No rush. Thanks!

Guest

9th December 2009, 14:25

* Pure interlaced VC1 (field interlace) is now supported.

http://neuron2.net/dgdecnv/dgdecnv.html

Jeff Flowerday

9th December 2009, 15:39

* Pure interlaced VC1 (field interlace) is now supported.

http://neuron2.net/dgdecnv/dgdecnv.html

Awesome, just in time to handle my AC/DC No Bull HD-DVD.

:thanks:

GearX

9th December 2009, 16:14

* Pure interlaced VC1 (field interlace) is now supported.

http://neuron2.net/dgdecnv/dgdecnv.html

"A few days" :cool: Thanks!

laserfan

9th December 2009, 16:17

"A few days" :cool: Thanks!neuron2's avatar belies his work ethic. We know he has a day job, what we don't know is when he sleeps!!! :)

Or maybe he ONLY takes "cat naps"!

Guest

9th December 2009, 17:09

I find time to sleep and swim. Let's just say I'm a fast coder. When you've been doing it professionally for 35 years, it comes easy. :)

laserfan

9th December 2009, 17:59

It disables the log after 100 frames when saving project.Ok here's prolly a softball for you. Tried b6 on an old project here and it doesn't appear to write a complete log. First a very old log, made prolly with DGAVCIndexNV 1.0.13 and DGDecodeNV v1.0.0 (the .dga sez DGAVCIndexFileNV2):

Stream Type: AVC Elementary
Profile: High
Level: 4.1
Frame Size: 1920x1080
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 23.976024 fps
Colorimetry: BT.709* [2]
Frame Structure: Frame
Frame Type: I
Coded Number: 80016
Playback Number: 80016
Frame Repeats: 0
Field Repeats: 0
Bitrate: 0.037
Bitrate (Avg): 22.422
Bitrate (Max): 41.114
Elapsed: 0:06:08
Remain: 0:00:00
FPS:
Info: Finished!

And now the latest b6 log on the same h264 file:

Stream Type: Elementary
Video Type: AVC
Profile: High
Level: 4.1
Coded Size: 1920x1088
SAR: 1:1
Display Size: 1920x1080
Frame Rate: 23.976024 fps
Colorimetry: BT.709* [2]
Frame Structure: Frame
Frame Type: I
Coded Number: 100
Playback Number: 100
Frame Repeats: 0
Field Repeats: 0
Bitrate: 26.377
Bitrate (Avg): 12.585
Bitrate (Max): 26.377
Elapsed: 0:07:36
Remain: 0:00:00
FPS:
Info: Finished!
Only 100 frames. Of course the .dga itself is fine, dunno why it would be slower but that's no concern for me.

Maybe I don't understand what the intent of the change was; I myself couldn't duplicate Jeff Flowerday's "faster when minimized" results.

DonDan

9th December 2009, 18:40

* Pure interlaced VC1 (field interlace) is now supported.

http://neuron2.net/dgdecnv/dgdecnv.html

Confirmed, interlaced VC1 works again, great work! As always^^

:thanks:

Guest

9th December 2009, 19:07

Confirmed, interlaced VC1 works again This is the first time it has worked, so I'm not sure what you mean by "again". Never mind, let's just be happy that it is working now. :)

Guest

9th December 2009, 19:10

Only 100 frames. It's a workaround until I find time to investigate the slowdown for some people.

Is the missing information important to you? The counts are available in the index file.

laserfan

9th December 2009, 19:20

It's a workaround until I find time to investigate the slowdown for some people.

Is the missing information important to you? The counts are available in the index file.Didn't realize you were still looking at it--no, it's no problem for me at all... :)

GZZ

10th December 2009, 08:57

Boardlord

10th December 2009, 10:12

I have an issue when I try to run DGIndexNV on my workstation using Remote desktop.

When I start DGIndexNV.exe it gives me the following error straigth from start: ERROR: cuInit failed (100)

I noticed this issue too if I use Remote Desktop to connect to my home machine. However, if I use RemotelyAnywhere (essentially Logmein), it works as it should.

Desaster Dan

10th December 2009, 11:43

hi neuron,
just testet dgindexNV beta 6.
my goal is to make it working within staxrip....

so i tested some files (VOB and m2ts) with the command-line.
C:\Programme\dgdecnv\DGIndexNV.exe -i %source_files% -o "%working_dir%\%source_name%" -f 0 -y 1 -a -h

Everthing works fine, exept audio demuxing and exiting the prog. after finish. (DGIndexNV.exe is still visible in the task-manager).
I get only the *.dgm, *.m2v, *.avs files. - no audio.
Any Ideas?

Guest

10th December 2009, 14:44

I can't duplicate either of those two issues. Can you provide a stream that fails?

Also, give me the expanded command line, without the %% stuff.

Jeff Flowerday

10th December 2009, 16:28

Neuron2.

I have an issue when I try to run DGIndexNV on my workstation using Remote desktop.

When I start DGIndexNV.exe it gives me the following error straigth from start: ERROR: cuInit failed (100)

It cant be a license issue, because my machine ID macth my license key (even over remote desktop) and it works just fine when I'm not using it over remote desktop.
You have any idea why this happen ?

PS: Using 2.0 Beta6, this issue has been there for as long I remember.

There is no issue. Cuda simply isn't available via Windows Remote Desktop. Doesn't matter which cuda reliant app.

Reason: Microsoft uses a custom software graphics driver in place of the video card and disables access to the GPU.

Boardlord

10th December 2009, 16:42

There is no issue. Cuda simply isn't available via Windows Remote Desktop. Doesn't matter which cuda reliant app.

Reason: Microsoft uses a custom software graphics driver in place of the video card and disables access to the GPU.

Thanks!

I'll use RemotelyAnywhere then whenever I want to start an encode from afar :)

GZZ

10th December 2009, 19:06

There is no issue. Cuda simply isn't available via Windows Remote Desktop. Doesn't matter which cuda reliant app.

Reason: Microsoft uses a custom software graphics driver in place of the video card and disables access to the GPU.

I also created a logmein account and then it works just fine. Didnt know M$ used its own driver.

Esurnir

10th December 2009, 19:20

Thanks to the adobe flash beta nvidia FINALY released 195.62 drivers for 9M series.

DonDan

10th December 2009, 19:58

This is the first time it has worked, so I'm not sure what you mean by "again". Never mind, let's just be happy that it is working now. :)

Weird^^

Until beta 4 all the VC-1 blurays that didn't work in betas 4 and 5 have always been working for me. The support for interlaced VC-1 was why I switched to your great tools. But then again I have a habit to mix things up from time to time :P

But let's move on back to the issue I first brought up in the wrong (the one about the avc version of the DG tool) thread and then again in post 614 of this thread:
The Bluray I cut this sample from still crashes the encoding process: http://www.mediafire.com/?zjm4jyywmdl [retail Bluray, ripped with anydvd hd, sample cut with tsMuxer - Is this real interlaced VC-1? As this worked for me in all versions up to beta 3 (besides the crash in this special sample)]

I think you had fixed it for beta 4 adding this change to the release log:

* Prevent crash due to stream corruption erroneously causing the decoder to try to create a frame size bigger than 1920x1088.

As beta 4 and 5 didn't work with interlaced VC-1 I couldn't test the file. Now in beta 6 the file crashes again.

Guest

10th December 2009, 22:01

Please re-upload because that link is invalid.

DonDan

10th December 2009, 23:21

Oops, they deleted the old link and I didn't check it...
Here's a brand new one: http://www.mediafire.com/?yym0mvzw2cw

Guest

11th December 2009, 04:00

Jeff Flowerday

11th December 2009, 04:37

FYI: performance is still as good if not better with the information update changes you made with beta 6.

DonDan

11th December 2009, 17:44

OK, I updated the beta 6 with a fixed DGIndexNV that doesn't crash when you Save Project. But it isn't going to help you much because the stream is corrupted, as I told you before, and you'll get picture decode errors when serving it.

I can live with some glitches, that's far better then being unable to encode it due to a crashing cuvidserver ;)
You are the last one to blame for some picture issues resulting from a broken mastering.

Edit: I could click through the errors while encoding now and keep on encoding, shall see how bad the resulting picture errors will be, but it seems to be working perfectly!