BD Rebuilder Beta - Bug Reports Only

[Lathe]

If you selected X264/LAVF and have a source that included PINFO information -- then DirectshowSource has to be used rather than LAVF (since the AddBorders filter is associated with AVISYNTH). I'll do some testing with X264/LAVF and PINFO and make sure that it is doing it properly.

Right, okay, now I understand. I remember now your saying that DirectshowSource is ALWAYS used whenever ANY AVS is involved.

So, do you think that if on occasion that I am using a source which will definitely need, say, borders added because they have been stripped, should I just in that SPECIFIC case go ahead and change my normal selection of using the internal LAVF frame server and choose instead 'Use DirectshowSource as frame server'? Or also in ANY cases where I have added AVS script?

[jdobbs]

Right, okay, now I understand. I remember now your saying that DirectshowSource is ALWAYS used whenever ANY AVS is involved.

So, do you think that if on occasion that I am using a source which will definitely need, say, borders added because they have been stripped, should I just in that SPECIFIC case go ahead and change my normal selection of using the internal LAVF frame server and choose instead 'Use DirectshowSource as frame server'? Or also in ANY cases where I have added AVS script?You can do that in the interim. But if I find an issue with LAVF and PINFO, it will be fixed. I haven't tested it yet, but will later today.

Assuming all is working right, if you have AVS filters enabled in SETUP, DirectshowSource() will be used instead of LAVF anyway.

[Lathe]

Very good, thanks!

[jdobbs]

If you selected X264/LAVF and have a source that included PINFO information -- then DirectshowSource has to be used rather than LAVF (since the AddBorders filter is associated with AVISYNTH). I'll do some testing with X264/LAVF and PINFO and make sure that it is doing it properly.Had some issues on my video-processing yesterday (a hard drive is crapping out), so I wasn't able to test it. It takes a long time to recover data from a 3TB drive that is having read errors.

Hopefully I will be able to do some testing later today.

[Edit] I moved responses and follow-on discussion of this post to a new thread (http://forum.doom9.org/showthread.php?t=171531).

[jdobbs]

Hmmm, interesting... Yes, I was indeed talking about after the encode, that the resizing did not take place although the PINFO showed the 'add borders(0,140 0,140)' for example.

But, what is weird though is that I am NOT using MULTIPROCESS; it is not in the config file... but, I AM using Directshowsource because I use the internal LAVF frame server, right? Oh, wait a minute. I think that you said that any resizing was handled by the installation of either / or / both of the haali, FFDShow & the additional new LAV filters installation.

I think I am confused... :confused:Fixed for the next release.

[Lathe]

Fixed for the next release.

Thanks JD!

[Ch3vr0n]

Jdobbs: I rarely have an issue but i've seen the following too many times now for it to be random. The error is "Failed to build structure" and is limited to DTS-Express enabled discs in combo with DGdecNV, if encode the SAME project without changing ANY variable except switching to LAVF the project rebuilds just fine

[12/14/14] BD Rebuilder v0.50.01
[14:43:36] Source: UNDERWORLD_RISE_OF_THE_LYCANS
- Input BD size: 39,49 GB
- Approximate total content: [02:56:17.757]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Auto Quality: Good (Very Fast), ABR
- Output folder: C:\Blu-Ray Rebuilds\BDRB\
- Decoding/Frame serving: DGDecNV [2-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:43:37] PHASE ONE, Encoding
- [14:43:37] Processing: VID_00260 (1 of 13)
- [14:43:37] Extracting A/V streams [VID_00260]
- [14:43:44] Reencoding video [VID_00260]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 1.440 frames
- Bitrate: 8.244 Kbs
- [14:43:44] Reencoding: VID_00260, Pass 1 of 1
- [14:44:05] Video Encode complete
- [14:44:05] Processing audio tracks
- [14:44:05] Multiplexing M2TS
- [14:44:09] Processing: VID_00262 (2 of 13)
- [14:44:09] Extracting A/V streams [VID_00262]
- [14:58:08] Reencoding video [VID_00262]
- [14:58:08] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 133.033 frames
- Bitrate: 14.554 Kbs
- [15:12:32] Reencoding: VID_00262, Pass 1 of 1
- [15:58:02] Video Encode complete
- [15:58:02] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4356 (eng): Keeping original audio
- Track 6656 (eng): Keeping original audio
- [15:58:02] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00262.meta
- Can't open file: C:\TEMP\WORKFILES\VID_00262_2.AVS.264
[15:58:07] - Failed to build structure, aborted


All files exist afaik that are needed.

Below is my ini config. Again: if i swap the encoding variable from DGdecNV to LAVF, the entire thing completes just fine

[Options]
#video settings
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DEINTERLACE=0
OPEN_GOP=0
MOVIE_ONLY_LOOP=1
USE_FILTERS=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=1
SD_TO_1080=0
CONVERT_WIDE=0
MOVIEONLY_TYPE=0
ALTCRF=20
ALT_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
WIDE_PERCENT=40
WIDE_OFFSET=.85
RESIZE_1440=0
RESIZE_720=0
OUTPUT_3D=1
IGNORE_3D=0
NEROAAC=0
DGDECNV=1
USE_LAVF=0

#audio settings
AUDIO_TO_KEEP=dut;eng;nld;und;
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
FULL_AVCHD=0

#subtitle settings
SUBS_TO_KEEP=dut;eng;nld;und;

#output settings
REMOVE_WORKFILES=1
REMOVE_OUTPUT=1
REMOVE_IMPORT=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
PRIORITY_CLASS=1
TARGET_SIZE=23500
AUTO_BURN=2
QUICK_EXTRAS=0

#General Settings
ENABLE_TEST=1
ENABLE_BLANKING=0
BLANK_THRESHOLD=60
MULTIPROCESS=1
MINIMIZE_TO_TRAY=1
SHUTDOWN_REBOOT=1
IMPORT_FOLDER=C:\TEMP
VERBOSE_STATUS=1
BDMV_CERT_ONLY=1
AUTO_BLANK=0
UNMASK_CHAPTER=1
VERSION=0.50.0.1
COMPLETION_BEEP=1
BEEP_SOUNDFILE=C:\Program Files (x86)\ImgBurn\Sounds\Success.wav
SD_PROGRESSIVE=1
MKV_CHAPTERS=1
SUPTITLE=0
OUTPUT_SBS=0
MENU_BACKGROUND=C:\Program Files (x86)\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=1
MENU_START_WITH_MENU=1
OUTPUT_FOLDER=C:\Blu-Ray Rebuilds\BDRB\
FRIMSOURCE=0
ENCODER=0
DGDECIM=0
DECODER=2

[Paths]
WORKING_PATH=C:\TEMP\LAVF\
SOURCE_PATH=Z:\BLU-RAY\DOUBLE LAYER\DTS-E\UNDERWORLD_RISE_OF_THE_LYCANS\
DGIndexNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\DGDecodeNV.dll
DirectShowMVCSource=C:\Program Files (x86)\BD_Rebuilder\Tools\MVCtoAVI.exe\DirectShowMVCSource.dll
NeroAACPath=C:\Program Files (x86)\BD_Rebuilder\Tools\neroaacenc1.5.1\win32\neroAacEnc.exe

Could perhaps the last 2 lines under "paths" be to blame? Those are the only 2 that are no longer in existence, though i don't see them referenced in the AVS script

[12/14/14] Checking System Settings
- BD-Rebuilder v0.50.01
- Windows Version: 6.1 [7601]
- Working Path Free Space: 1.127,15GB
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[12/14/14] Systems Settings Check complete

I do NOT have any codec packs other than ffdshow installed, and i do NOT have LAV filters installed

I have noticed that in the BDRB window the source path is not fully shown. It only shows: "Z:\Blu-ray\Double"

[sonate]

This has happened once only, a Japanese version of David Lynch's "Straight Story".

The rip goes smoothly, Bdrebuilder functions flawlessly. The disc burn completes in Imageburn tool and the burned disc even plays on both standalone br player without a hitch.

What is perplexing is what happens when I try to verify the disc against the .iso using Imageburn, it freezes the computer where only a cold shutdown and reboot brings it back. Evidently the only message I get in Imageburntool is a read error almost instantly followed by the freeze. Tried 4 different types of blu ray medium thinking the defect was there, but I guess not.

Just burned a rip of Aguirre and everything including verification was normal. It is just this disc of "Straight Story"

Does anyone have an idea why?

[Lathe]

Just a quickie, and it isn't really THAT serious, but I seem to notice now, I don't know if it is since the last build (50.01) or before that, but just the initial extraction process of the A/V streams seems to take a LOT longer than it used to. Just kind of weird, really. And it doesn't seem to matter whether the rip is on my internal HDD and the working folder for BDRB is on my SSD drive, OR if both are on my SSD drive, I honestly don't remember the extraction process taking SO long.

If I remember properly, it always seemed in the past to take just a few minutes. But, for a while now, it seem like the extraction process alone takes much more time, like 10-15 minutes. And, as always, I am using the internal LAVF frame server.

Is there any reason that you can think of that would explain why it APPEARS to be so much slower now? The 1st and 2nd pass encoding time, though, seem to be comparable to what they have always been.

[omegaman7]

@sonate
Are you sure the encryption has been completely removed? I don't recall which disc, but I had same/similar issues, and a new version of Anydvd HD solved the problem.

[HWK]

@sonate
Are you sure the encryption has been completely removed? I don't recall which disc, but I had same/similar issues, and a new version of Anydvd HD solved the problem.

I doubt his issue has to do with encryption, if it was x264 or any other encoder will simply crash on garbage input. I will lean towards storage where ISO is kept maybe there are bad sectors on hard drive and imgubrn is failing during verification stage.

Recommend mount iso on virtual drive and try to play and see if something turns up.

[jdobbs]

Just a quickie, and it isn't really THAT serious, but I seem to notice now, I don't know if it is since the last build (50.01) or before that, but just the initial extraction process of the A/V streams seems to take a LOT longer than it used to. Just kind of weird, really. And it doesn't seem to matter whether the rip is on my internal HDD and the working folder for BDRB is on my SSD drive, OR if both are on my SSD drive, I honestly don't remember the extraction process taking SO long.

If I remember properly, it always seemed in the past to take just a few minutes. But, for a while now, it seem like the extraction process alone takes much more time, like 10-15 minutes. And, as always, I am using the internal LAVF frame server.

Is there any reason that you can think of that would explain why it APPEARS to be so much slower now? The 1st and 2nd pass encoding time, though, seem to be comparable to what they have always been.There really haven't been any changes to that code in a long time. The only exception would be if the source was MPEG-2 -- and that is because the source is being scanning concurrently with extraction.

[sonate]

@sonate
Are you sure the encryption has been completely removed? I don't recall which disc, but I had same/similar issues, and a new version of Anydvd HD solved the problem.

Funny that the only way I know there is a problem is with the verification. Because the disc reads and plays fine in several hardware and software blu ray players. I have even copied the entire BDMV and certificate folders from one drive to the other without any halt or read errors. It would not be so bad if Imageburn reported a bad sector or miscompare, which it doesn't, it's the crash and freeze which makes me wonder.

[sonate]

I doubt his issue has to do with encryption, if it was x264 or any other encoder will simply crash on garbage input. I will lean towards storage where ISO is kept maybe there are bad sectors on hard drive and imgubrn is failing during verification stage.

Recommend mount iso on virtual drive and try to play and see if something turns up.

I did that, even re ripped to a different harddrive, with same results.

[jdobbs]

It sounds like a bug in ImgBurn to me.

[Lathe]

There really haven't been any changes to that code in a long time. The only exception would be if the source was MPEG-2 -- and that is because the source is being scanning concurrently with extraction.

Okidoke, thanks! Probably just my skewed perception of time :)

[sonate]

It sounds like a bug in ImgBurn to me.

Probably, at any rate the disc is playable and BDreb is consistently doing a great job. I appreciate you and others weighing in on this.

I find that many great movies which were available on DVD in the USA haven't produced blu-ray editions so I'm left buying Asian or European versions. And often enough without English subtitles. So if I really want to watch it, I have to put some work in.

[jdobbs]

Probably, at any rate the disc is playable and BDreb is consistently doing a great job. I appreciate you and others weighing in on this.

I find that many great movies which were available on DVD in the USA haven't produced blu-ray editions so I'm left buying Asian or European versions. And often enough without English subtitles. So if I really want to watch it, I have to put some work in.You can always use the audio track from the DVD and replace it in the working folder before rebuilding. It sometimes takes a little tweaking to get sync, but it's not too bad.

You can also use the subtitles from the DVD by importing it -- and using what has been converted to BD by BD-RB.

[Ch3vr0n]

Jdobbs, could you take a look at my previous post on previous page.

Verstuurd vanaf mijn HTC Sensation met Tapatalk

[jdobbs]

Jdobbs, could you take a look at my previous post on previous page.

Verstuurd vanaf mijn HTC Sensation met TapatalkI looked at it, but it doesn't make any sense to me. I don't see a link between the .264 output of DGDecNV and another .264 output from X264/LAVF being affected by the existence of DTS Express. Either way the DTS Express stream is multiplexed independently of it.

I'm guessing the real issue might be in the fact that DGDecNV uses multiple processes, while X264/LAVF doesn't. Could you run DGDecNV with MULTIPROCESS=0 to test it?

I'll dig around and see if I can find a source to reproduce it.

[Ch3vr0n]

Sure thing, I'll run a test tomorrow and let ya know. Just got back from a union rally that lasted all day and too late to fire up pc.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[Seajunk]

What is perplexing is what happens when I try to verify the disc against the .iso using Imageburn, it freezes the computer where only a cold shutdown and reboot brings it back. Evidently the only message I get in Imageburntool is a read error almost instantly followed by the freeze. Tried 4 different types of blu ray medium thinking the defect was there, but I guess not.


Sonate, what OS are you running?
I was having the same problem with Imgburn when I moved to win 8.1. Updating the sata driver made the problem more intermittent rather completely go away. In the end i gave up and switched to nero burning rom.

[Sharc]

..........
- Corrected an issue in which attempting to
use the original BD background during import
could, rarely, result in blocky MENU output.
.............

Just to report back that this solved the problem for both of my problematic discs. Thanks!

[omegaman7]

I've verified very few discs with Imgburn. The BD burning drive has proved itself, so I haven't seen the need yet. The few discs I have verified, passed with flying colors. That's the only time I use my iHES108. It's proven to be a bad BD-ROM reader. But quality of clean discs, seems to be reliable. Tiniest imperfection on an industrial disc, and there will be pixelation, skipping, etc. Or it won't run properly through BD rebuilder. I really don't like optical technology. But... it's a necessary evil sometimes LOL!

[Lathe]

I was wondering, since I have the LAV installed, can I just uninstall the haali splitter? Do I need that for anything else? I think on the first post here don't you say EITHER install one or the other? Should I uninstall the other one that goes with the Haali too?

[jdobbs]

I was wondering, since I have the LAV installed, can I just uninstall the haali splitter? Do I need that for anything else? I think on the first post here don't you say EITHER install one or the other? Should I uninstall the other one that goes with the Haali too?It's not needed with LAV installed -- as LAV has it's own splitter.

[Lathe]

should I uninstall the FFDShow too?

[jdobbs]

If you don't need it for anything else, sure.

[Ch3vr0n]

@Jdobbs:

As requested i've re-run the same job with multiprocess=0

Conversion of the main title VID_00262 was with DGDecNV was succesful. I did notice the following though

1) for the main title, it still launched 2 processes of DGIndexNV (although i dont really know if this is bdrb's "fault" or native to DGIndexNV) but for the other smaller titles (extras, intro's, trailers) only 1 DGIndexNV process was launched

2) the x264 version that was launched for all titles was x264.exe and not x264-64.exe (although i don't really know if it's possible to launch 64bit version outside of LAVF) i figured i'd report none-the-less

So it looks like the culprit is not the fact that DGDecNV is used as frameserver, but the multiprocess=n is the culprit. Now how this is possible i don't know or how to fix it. The quickest solution i can think of is to disable multiprocess on DTS-Express enabled discs if it is enabled, unless ofcourse it is a genuine bug and you can find a better fix.

Attached is conversion log and "changed" ini file


[12/16/14] BD Rebuilder v0.50.01
[15:24:42] Source: UNDERWORLD_RISE_OF_THE_LYCANS
- Input BD size: 39,49 GB
- Approximate total content: [02:56:17.757]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Auto Quality: Good (Very Fast), ABR
- Output folder: C:\Blu-Ray Rebuilds\BDRB\
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:24:43] PHASE ONE, Encoding
- [15:24:43] Processing: VID_00260 (1 of 13)
- [15:24:43] Extracting A/V streams [VID_00260]
- [15:24:50] Reencoding video [VID_00260]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 1.440 frames
- Bitrate: 8.244 Kbs
- [15:24:50] Reencoding: VID_00260, Pass 1 of 1
- [15:25:09] Video Encode complete
- [15:25:09] Processing audio tracks
- [15:25:09] Multiplexing M2TS
- [15:25:13] Processing: VID_00262 (2 of 13)
- [15:25:13] Extracting A/V streams [VID_00262]
- [15:43:51] Reencoding video [VID_00262]
- [15:43:51] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 133.033 frames
- Bitrate: 13.757 Kbs
- [16:02:37] Reencoding: VID_00262, Pass 1 of 1
- [17:21:20] Video Encode complete
- [17:21:20] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4356 (eng): Keeping original audio
- Track 6656 (eng): Keeping original audio
- [17:21:20] Multiplexing M2TS
- [17:29:11] Processing: VID_00263 (3 of 13)
- [17:29:11] Extracting A/V streams [VID_00263]
- [17:29:31] Reencoding video [VID_00263]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 3.552 frames
- Bitrate: 9.557 Kbs
- [17:29:31] Reencoding: VID_00263, Pass 1 of 1
- [17:31:02] Video Encode complete
- [17:31:02] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:31:02] Multiplexing M2TS
- [17:31:09] Processing: VID_00264 (4 of 13)
- [17:31:09] Extracting A/V streams [VID_00264]
- [17:31:24] Reencoding video [VID_00264]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.929 frames
- Bitrate: 9.645 Kbs
- [17:31:24] Reencoding: VID_00264, Pass 1 of 1
- [17:32:31] Video Encode complete
- [17:32:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:32:31] Multiplexing M2TS
- [17:32:39] Processing: VID_00275 (5 of 13)
- [17:32:39] Extracting A/V streams [VID_00275]
- [17:32:55] Reencoding video [VID_00275]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3.097 frames
- Bitrate: 9.494 Kbs
- [17:32:55] Reencoding: VID_00275, Pass 1 of 1
- [17:34:02] Video Encode complete
- [17:34:02] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:34:02] Multiplexing M2TS
- [17:34:08] Processing: VID_00276 (6 of 13)
- [17:34:08] Extracting A/V streams [VID_00276]
- [17:34:22] Reencoding video [VID_00276]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23,976fps, 3.120 frames
- Bitrate: 8.816 Kbs
- [17:34:22] Reencoding: VID_00276, Pass 1 of 1
- [17:35:22] Video Encode complete
- [17:35:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:35:22] Multiplexing M2TS
- [17:35:28] Processing: VID_00277 (7 of 13)
- [17:35:28] Extracting A/V streams [VID_00277]
- [17:35:43] Reencoding video [VID_00277]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.929 frames
- Bitrate: 9.503 Kbs
- [17:35:43] Reencoding: VID_00277, Pass 1 of 1
- [17:36:41] Video Encode complete
- [17:36:41] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:36:41] Multiplexing M2TS
- [17:36:47] Processing: VID_00285 (8 of 13)
- [17:36:47] Extracting A/V streams [VID_00285]
- [17:36:58] Reencoding video [VID_00285]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 1.993 frames
- Bitrate: 9.493 Kbs
- [17:36:58] Reencoding: VID_00285, Pass 1 of 1
- [17:37:39] Video Encode complete
- [17:37:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:37:39] Multiplexing M2TS
- [17:37:46] Processing: VID_00286 (9 of 13)
- [17:37:46] Extracting A/V streams [VID_00286]
- [17:38:16] Reencoding video [VID_00286]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 5.545 frames
- Bitrate: 14.688 Kbs
- [17:38:16] Reencoding: VID_00286, Pass 1 of 1
- [17:40:29] Video Encode complete
- [17:40:29] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:40:29] Multiplexing M2TS
- [17:40:37] Processing: VID_00287 (10 of 13)
- [17:40:37] Extracting A/V streams [VID_00287]
- [17:41:41] Reencoding video [VID_00287]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29,970fps, 16.741 frames
- Bitrate: 14.608 Kbs
- [17:41:42] Reencoding: VID_00287, Pass 1 of 1
- [17:49:15] Video Encode complete
- [17:49:15] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:49:15] Multiplexing M2TS
- [17:49:33] Processing: VID_00288 (11 of 13)
- [17:49:33] Extracting A/V streams [VID_00288]
- [17:51:45] Reencoding video [VID_00288]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29,970fps, 35.926 frames
- Bitrate: 14.609 Kbs
- [17:51:45] Reencoding: VID_00288, Pass 1 of 1
- [18:06:53] Video Encode complete
- [18:06:54] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:06:54] Multiplexing M2TS
- [18:07:35] Processing: VID_00289 (12 of 13)
- [18:07:35] Extracting A/V streams [VID_00289]
- [18:09:04] Reencoding video [VID_00289]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29,970fps, 23.435 frames
- Bitrate: 14.612 Kbs
- [18:09:04] Reencoding: VID_00289, Pass 1 of 1
- [18:18:14] Video Encode complete
- [18:18:14] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:18:14] Multiplexing M2TS
- [18:18:35] Processing: VID_00330 (13 of 13)
- [18:18:35] Extracting A/V streams [VID_00330]
- [18:18:53] Reencoding video [VID_00330]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3.386 frames
- Bitrate: 9.317 Kbs
- [18:18:53] Reencoding: VID_00330, Pass 1 of 1
- [18:20:11] Video Encode complete
- [18:20:11] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:20:11] Multiplexing M2TS
[18:20:18]PHASE ONE complete
[18:20:18]PHASE TWO - Rebuild Started
- [18:20:18] Rebuilding BD file Structure
[18:21:22] - Encode and Rebuild complete
[18:21:22] Writing BD structure to ISO file
- ImgBurn completed successfully
- UNDERWORLD_RISE_OF_THE_LYCANS folder removed.
- WORKFILES folder removed.
[18:34:59] JOB: UNDERWORLD_RISE_OF_THE_LYCANS finished.


[Options]
#video settings
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DEINTERLACE=0
OPEN_GOP=0
MOVIE_ONLY_LOOP=1
USE_FILTERS=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=1
SD_TO_1080=0
CONVERT_WIDE=0
MOVIEONLY_TYPE=0
ALTCRF=20
ALT_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
WIDE_PERCENT=40
WIDE_OFFSET=.85
RESIZE_1440=0
RESIZE_720=0
OUTPUT_3D=1
IGNORE_3D=0
NEROAAC=0
DGDECNV=1
USE_LAVF=0

#audio settings
AUDIO_TO_KEEP=dut;eng;nld;und;
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
FULL_AVCHD=0

#subtitle settings
SUBS_TO_KEEP=dut;eng;nld;und;

#output settings
REMOVE_WORKFILES=1
REMOVE_OUTPUT=1
REMOVE_IMPORT=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
PRIORITY_CLASS=1
TARGET_SIZE=23500
AUTO_BURN=2
QUICK_EXTRAS=0

#General Settings
ENABLE_TEST=1
ENABLE_BLANKING=0
BLANK_THRESHOLD=60
MULTIPROCESS=0
MINIMIZE_TO_TRAY=1
SHUTDOWN_REBOOT=1
IMPORT_FOLDER=C:\TEMP
VERBOSE_STATUS=1
BDMV_CERT_ONLY=1
AUTO_BLANK=0
UNMASK_CHAPTER=1
VERSION=0.50.0.1
COMPLETION_BEEP=1
BEEP_SOUNDFILE=C:\Program Files (x86)\ImgBurn\Sounds\Success.wav
SD_PROGRESSIVE=1
MKV_CHAPTERS=1
SUPTITLE=0
OUTPUT_SBS=0
MENU_BACKGROUND=C:\Program Files (x86)\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=1
MENU_START_WITH_MENU=1
OUTPUT_FOLDER=C:\Blu-Ray Rebuilds\BDRB\
FRIMSOURCE=0
ENCODER=0
DGDECIM=0
DECODER=3

[Paths]
WORKING_PATH=C:\TEMP\LAVF\
SOURCE_PATH=Z:\BLU-RAY\DOUBLE LAYER\DTS-E\UNDERWORLD_RISE_OF_THE_LYCANS\
DGIndexNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\DGDecodeNV.dll
DirectShowMVCSource=C:\Program Files (x86)\BD_Rebuilder\Tools\MVCtoAVI.exe\DirectShowMVCSource.dll
NeroAACPath=C:\Program Files (x86)\BD_Rebuilder\Tools\neroaacenc1.5.1\win32\neroAacEnc.exe


There was however a rather significant size difference.

The LAVF built iso came in at 19.0GB on the dot (19.927.488kb)
The DGDC built iso came in at 20.9GB in size (21.919.936kb)

a 2GB difference and still significant for both considering the default target size of 22.95GB. The DGDecNV built one was 2GB short of the target while the LAVF built one was a whopping 4GB smaller

If you want me to run more tests, just lemme know

[Seajunk]

Hey Ch3vr0n,
Are you still running that Q9550 processor?
Im surprised its taking three hours for that underworld job at Good(very fast) with DGDecNV decoding. Mine usually run at 45 minutes (I5-4690).

[Ch3vr0n]

Yours runs at 45min because it's a completely different architecture. And FYI with dgdecnv it's the GPU that does the work not the CPU. But yes I still run that CPU and it still works perfectly. I'd love to replace it with and i7 but then I'd have to replace the motherboard and ram too, and I just don't have the cash to build a completely new system. To much debt to still pay.

Now back on topic, it's not a system discussion topic. I've got an issue that needs solving.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

1) for the main title, it still launched 2 processes of DGIndexNV (although i dont really know if this is bdrb's "fault" or native to DGIndexNV) but for the other smaller titles (extras, intro's, trailers) only 1 DGIndexNV process was launched

2) the x264 version that was launched for all titles was x264.exe and not x264-64.exe (although i don't really know if it's possible to launch 64bit version outside of LAVF) i figured i'd report none-the-less1. Are you positive? I've done a lot of testing and I switch back-and-forth all the time. I'm very confident that setting MULTIPROCESS=0 will disable multiple processes correctly.

2. AVISYNTH is 32 bit, so the 32 bit version of X264 has to be used with it. 64 bit is only used with LAVF (because the frame serving is done internally).

I'll have to do some testing to see if I can reproduce sizing discrepancies.

[robbie74]

i have tried 2 different films to shrink down to 25gb ( gravity & guardians of the galaxy both 3d )
I took off all audio track except HD & blanked extras & kept menu, but after 6 1/2 minutes the audio just goes off & does not come back.
I have latest version installed & codecs installed as per instructions.

Can anyone help me with this problem ??

the log attached is from gravity

Thanks

rob

[Ch3vr0n]

100%, I'd be happy to run it again.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[DoctorM]

Bringing up the quick play menus on AVCHD again. Out of curiosity today I took the output from BD RB and dropped it into multiAVCHD in reauthor mode.
For the output I selected AVCHD (Strict).

Nothing appeared to be altered or re-encoded, but the final disc, when burned to a DVD-rw, played fine on my Sony BDP-S790.
The only thing I'm trouble by is I'm not certain that really, truly 'strict' AVCHD is supposed to have animated menus and music.

So, maybe this info will help you out, jdobbs... or not.

[Sharc]

i have tried 2 different films to shrink down to 25gb ( gravity & guardians of the galaxy both 3d )
I took off all audio track except HD & blanked extras & kept menu, but after 6 1/2 minutes the audio just goes off & does not come back.
I have latest version installed & codecs installed as per instructions.

Can anyone help me with this problem ??

the log attached is from gravity

Thanks

rob
Cinavia?

[jdobbs]

i have tried 2 different films to shrink down to 25gb ( gravity & guardians of the galaxy both 3d )
I took off all audio track except HD & blanked extras & kept menu, but after 6 1/2 minutes the audio just goes off & does not come back.
I have latest version installed & codecs installed as per instructions.

Can anyone help me with this problem ??

the log attached is from gravity

Thanks

robThere's really not a lot that could go wrong. The original audio was used. But I always wince when I see this: - AnyDVD Remove Short Titles: Incompatible
- AnyDVD Remove Annoying Adverts: Incompatible It means AnyDVD is playing with it before BD-RB does. I'd suggest you turn those options off and try again.

There's always a chance of Cinavia -- but it I'm not sure whether 6 1/2 minutes is enough time, and you usually get a warning from the player.

[jdobbs]

100%, I'd be happy to run it again.

Verstuurd vanaf mijn Nexus 7 met TapatalkPlease do. I see no way BD-RB could create two instances of DGDecNV if MULTIPROCESS=0. That is unless there is one running already...

[jdobbs]

Bringing up the quick play menus on AVCHD again. Out of curiosity today I took the output from BD RB and dropped it into multiAVCHD in reauthor mode.
For the output I selected AVCHD (Strict).

Nothing appeared to be altered or re-encoded, but the final disc, when burned to a DVD-rw, played fine on my Sony BDP-S790.
The only thing I'm trouble by is I'm not certain that really, truly 'strict' AVCHD is supposed to have animated menus and music.

So, maybe this info will help you out, jdobbs... or not.The menu is 100% AVCHD compatible (with the exception of the version headers), so no surprise there. Animated menus are supported via HDMV. The reason BD-5/9 isn't supported yet is because the Quick-Play logic follows the execution path of a full backup, and that is restricted to BD-25+.

It may take a while to support it, as changing how it works isn't a simple fix.

[Ch3vr0n]

@Jdobbs:

As requested. Attached image shows everything DURING EXTRACTION OF THE MAIN TITLE
So you don't get confused i'll say it in advance: There are 2 BDRB windows open. The left one is actively extracting, the RIGHT ONE is inactive open on the same source and only used to show the current BDRB ini config settings. I've highlighted in red the important parts.

Multiprocess=0, yet on the main title 2 DGIndecNV.exe processes are launched. After that i aborted the encode, then resumed cause i wanted to check if 2 processes of x264 were launched too, which strangely enough was NOT the case during encoding of the secondary video nor main video.

[jdobbs]

@Jdobbs:

As requested. Attached image shows everything DURING EXTRACTION OF THE MAIN TITLE
So you don't get confused i'll say it in advance: There are 2 BDRB windows open. The left one is actively extracting, the RIGHT ONE is inactive open on the same source and only used to show the current BDRB ini config settings. I've highlighted in red the important parts.

Multiprocess=0, yet on the main title 2 DGIndecNV.exe processes are launched. After that i aborted the encode, then resumed cause i wanted to check if 2 processes of x264 were launched too, which strangely enough was NOT the case during encoding of the secondary video nor main video.Ok. I'll see if I can repeat it.

[DoctorM]

The menu is 100% AVCHD compatible (with the exception of the version headers), so no surprise there. Animated menus are supported via HDMV. The reason BD-5/9 isn't supported yet is because the Quick-Play logic follows the execution path of a full backup, and that is restricted to BD-25+.

It may take a while to support it, as changing how it works isn't a simple fix.

I can understand it isn't a simple fix, but at least I have a way to finish the project in the short term.

I was worried that you said it used the full backup path that maybe there would be other reason the output isn't AVCHD spec, but I see that the max bitrate of the files are still 15mbps so it's probably JUST the menus that don't meet spec and multiAVCHD patches that.

Thanks for your time.

[jdobbs]

I can understand it isn't a simple fix, but at least I have a way to finish the project in the short term.

I was worried that you said it used the full backup path that maybe there would be other reason the output isn't AVCHD spec, but I see that the max bitrate of the files are still 15mbps so it's probably JUST the menus that don't meet spec and multiAVCHD patches that.

Thanks for your time.It may not be there for the next release... but possibly the one after that.

[jdobbs]

@Ch3vr0n

I've tried over-and-over, and I can't get more than one DGIndexNV instance to run when MULTIPROCESS=0.

I'll try with some different settings, but it sure looks like it works from here.

[Edit] Wait a minute, now that I think about it, BD-RB never runs more than one instance of DGIndexNV. That's because DGDecNV is frame accurate, and the starting/ending frame for each encode instance is specified in the multiple X264 command lines.

[Ch3vr0n]

I don't see how it's possible either. Don't see what more I can send you. My exact INI settings have been posted. I'll try tomorrow and check if its limited to that underworld disc but I don't think it is.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

I don't see how it's possible either. Don't see what more I can send you. My exact INI settings have been posted. I'll try tomorrow and check if its limited to that underworld disc but I don't think it is.

Verstuurd vanaf mijn Nexus 7 met TapatalkSee my post again, I corrected it.

[Ch3vr0n]

Then why do 2 of them show up in task manager? I'll launch the job again and check if the file actively gets split into 2 files as well. But that's just the weird part of it all. 2 index processes get launched and one would think that 2 x264 would get launched too to encode both parts. But only 1 x264 got launched. It doesn't make sense

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

Then why do 2 of them show up in task manager? I'll launch the job again and check if the file actively gets split into 2 files as well. But that's just the weird part of it all. 2 index processes get launched and one would think that 2 x264 would get launched too to encode both parts. But only 1 x264 got launched. It doesn't make sense

Verstuurd vanaf mijn Nexus 7 met TapatalkIt won't get split. That only happens with Directshow. You don't need to do a split when the frame-server is frame accurate.

It never shows up as two instances on my computer. Try killing one of them and see what happens. Is there any chance there is an instance "hung" out there that is always there?

Maybe there is some setting in DGIndexNV that can change how it works???? I notice that in my task window it says the size of the process is 52,088K while both of yours are much smaller than that. BTW, I'm still using DGIndexNV version 2046.

[Ch3vr0n]

No hung ones. I recently formatted to it's a clean os. Both get launched when bdrb starts indexing main title. I'll launch the job again shouldn't take more than a few minutes before it starts indexing the main title. There's only 1 clip before it. I'll get back to you in a few minutes

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

... or maybe your card is different than mine and DGIndexNV works differently????