[RESOLVED] DGdecNV 2052 + BDRB = fail

Support forum for DGDecNV
Post Reply
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

[RESOLVED] DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

I'm having trouble getting build 2052 to work with my GTX 1080. The license.txt file contents matches the license gen so that's not the problem. BDRB goes through te first stage ok like "Extracting/indexing stream..." but once that's done, it goes to a SECOND stage of "Indexing stream...." and aborts.

According to jdobbs:

The issue sure sounds like the card isn't supported. The second stage is simply a retry after failure of the first one (only limiting what is being extracted)

I'd appreciate any input.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

Please link me to your source sample that does this. Thanks.
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

What sample. I'm trying to process a full disc. BDRB does everything by cli i think.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

Does it do it for all disks? If not what is the title and region? Do you have the BDRB log file?
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

Yup, all discs. FFDshow & x264's internal work just fine.

BDRB log

Currently confirmed with Independence day (barcode 8712626054221) and teenage mutant ninja turles 2 (barcode 5053083074210). Running latest nvidia drivers 375.70.

[[11/01/16] BD Rebuilder v0.50.18
[23:28:24] Source: INDEPENDENCE_DAY_RESURGENCE
- Input BD size: 40,93 GB
- Approximate total content: [04:08:51.998]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Good (Very Fast), ABR
- Output folder: D:\Blu-ray\Rebuilds\BDRB\
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[23:28:25] PHASE ONE, Encoding
- [23:28:25] Processing: VID_00152 (1 of 32)
- [23:28:25] Extracting A/V streams [VID_00152]
- [23:28:34] Reencoding video [VID_00152]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3 479 frames
- Bitrate: 6 346 Kbs
- [23:28:34] Reencoding: VID_00152, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.50.18
- Windows Version: 6.2 [9200]
- Working Path Free Space: 175,13GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[23:28:37] - Failed video encode, aborted

Disabling 4way doesn't work either.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

The encode failed. DGDecNV is a decoder. Can't you log the commands that BDRB does and the results. Surely jdobbs can say what tool failed and why. It could be so many different things. Only jdobbs knows what BDRB is doing internally.

And is this 3D transcoding (I see FRIM)?

Have you tried to do manual things with DGDecNV? Can you open the M2TS files in DGIndexNV and index them? If so, can you serve them to VirtualDub with an Avisynth script?
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

yeah i know it's a decoder. But as jdobss said. The first attempt of extracting/indexing only semi-works. The extracting works but indexing fails, which is why he said it tried to index a 2nd time. I checked out the temp files and the only thing i can see that's "off" is the indexing file?

Filename VID_00152.DGI.dgi (yes double extension)

everything else looks fine

00152.track_xxxx.ac3 (xxxx = number)
00152.track_xxxx.sup
AUD_00152.meta
AUD_00152.4352.AVS
VID_00152.AVS
VID_00152.AVS.264
VID_00152.CHP

Build 2050 WORKS!!! (no double DGI.dgi extension)

i don't have 2051, lying around anymore. Could you pm me a link? I think we're on to something here
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

The indexing would appear to have succeeded if you get a good DGI file. So specifically what are you saying failed in indexing and what did BDRB sense to determine that a failure occurred? What was off about the index file? Can you link me to it?

I'm not going off into past versions. I need full information on the failure with the latest 2052. Please re-download it as there have been many slipstreams.

Again, have you tried things manually? That could quickly locate a system issue for you. Does everyone else also see this?
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

the only thing "off" i could see was the double file extension ".DGI.dgi" So while the indexing may have worked, the file extension is wrong. Since build 2050 works and only creates files with .DGI, it's safe to assume BDRB expects a single ".DGI" extension. Which is why encoding fails due to ".DGI.dgi"

i'm not skilled enough to interpret things or do it manually.

I have the 2nd to last slipstream i think. I downloaded build 2052 at 20:52:27 CET (brussels time) on oct 31st.

Could you please provide a build 2051? I'll then redo the test. If 2051 also only creates files with ".DGI", the problem is native to build 2052 only.

*edit* found build 2051 at the binaries. Retesting

** edit 2 ** Testing confirmed. Build 2051 works as well and only creates files with .DGI extension. The problem is limited to the build 2052 (i downloaded the above time). Build 2052 creates index files with extension ".DGI.dgi" instead of the expected ".DGI". The file contents itself within the .DGI.dgi file seems right.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

OK, I know what the problem is from your first sentence. Thank you. :bravo:

Stand by for a fix...
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

Well i did say that in post #7 ;)
Filename VID_00152.DGI.dgi (yes double extension)
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

I see that now. :wow:

Please re-download DGDecNV 2052 and update DGIndexNV.exe.

Who would have thought that a 3rd-party app would make command lines with uppercase extensions. 8-)

Thank you for your report and concise information. Sometimes the significance of things is not immediately apparent. :P
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

Redownloaded, fix confirmed. Single .DGI extension and encode properly starts :)

i'm guessing it's "hardcoded" based on previous filenames. Since the file itself has a double extension ".DGI.dgi", BDRB's command line can't find the file it's expecting (filename.DGI or filename.dgi for that matter) because only "filename.DGI.dgi" exists. If you knock me up a "private"? build that uses .dgi instead of .DGI, i'd be happy to run another test to see if .DGI vs .dgi matters.
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: DGdecNV 2052 + BDRB = fail

Post by admin »

It doesn't matter now because I allow for both, so no worries. Thank you for the offer.

My good friend MeteorRain, bless his soul, had pointed out that for CLI, -o filename crashes. So I was trying to be helpful and if ".dgi" was not present at the end of the filename, I added it. But I forgot about case in my comparison. :oops:

Now some wise guy will try filename.dGi :facepalm: Don't get me wrong; jdobbs is a very wise guy. :bow:
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: [RESOLVED] DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

Glad i could help. The important thing is, the issue is solved. What installing a brand new piece of hardware can do lol, find a bug in a software application :)
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: [RESOLVED] DGdecNV 2052 + BDRB = fail

Post by admin »

The HW change was a total coincidence, but still, we can be thankful for your acute analytical sense, your attention to detail, and your superb problem reporting. Your contribution is greatly appreciated here in DG land.
DAE avatar
Ch3vr0n
Posts: 11
Joined: Fri Jul 11, 2014 4:15 pm

Re: [RESOLVED] DGdecNV 2052 + BDRB = fail

Post by Ch3vr0n »

Don't worry about doom9. When i encountered the problem i posted in the BDRB debug thread that i'd keep them updated. After the solution was found & fix, i posted in an edit post that everyone that was using build 2052 downloaded prior to today needed to redownload 2052 and replace the DGIndexNV.exe file to fix the issue and avoid DGDecNV issues.

Ta!
User avatar
admin
Posts: 4551
Joined: Thu Sep 09, 2010 3:08 pm

Re: [RESOLVED] DGdecNV 2052 + BDRB = fail

Post by admin »

Thanks for that!
Post Reply