BD Rebuilder Beta - Bug Reports Only

[m.rup]

Hi, is there meanwhile a solution for the donation issue?

[Ch3vr0n]

The only really available method i could see is bitcoin or something.

[Ch3vr0n]

Hah, first 3D rebuild on this new rig just finished. Damn thing used almost every bit available on a BD50. 43.73GB > 22.95 => 3h15m. Old rig: 13+ hours, 25% or less of the time it would have taken on that one ^^

[jdobbs]

@Ch3vr0n

You should be able to test it by setting MULTIPROCESS=8.

[Ch3vr0n]

great. Just got a couple new discs to try it on. Test disc: Jungle Book ^^. I'll let you know. Oh and if you've seen the video file above (nothing visible but BDRB ;)), let me know. Then i'll pull it off gdrive, or you can edit the post and remove the link

** edit ** rebuild of that 3D disc didn't go too well. Succesful log, yet the ISO is only 15GB in size and the video locks up at chapter 12 while audio continues playing and so does the playtime counter (40+min left)

[08/19/16] BD Rebuilder v0.50.18
[20:24:05] Source: BATMAN_V_SUPERMAN_DAWN_JUSTICE
- Input BD size: 43,73 GB
- Approximate total content: [02:38:47.851]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Very Fast), ABR
- Output folder: D:\Blu-ray\Rebuilds\BDRB\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[20:24:09] PHASE ONE, Encoding
- [20:24:09] Processing: VID_00052 (1 of 2)
- [20:24:09] Extracting A/V streams [VID_00052]
- [20:35:37] Reencoding video [VID_00052]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 218*209 frames
- Bitrate: 18*147 Kbs
- Using FRIMEncoder for MVC encoding
- [20:35:37] Reencoding: VID_00052, Pass 1 of 1
- [23:13:59] Video Encode complete
- [23:13:59] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:13:59] Multiplexing M2TS
- [23:22:28] Scanning for 3D CLPI info...
- [23:25:41] Processing: VID_00103 (2 of 2)
- [23:25:41] Extracting A/V streams [VID_00103]
- [23:25:49] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 8*159 frames
- Bitrate: 4*805 Kbs
- Using FRIMEncoder for MVC encoding
- [23:25:49] Reencoding: VID_00103, Pass 1 of 1
- [23:30:16] Video Encode complete
- [23:30:16] Processing audio tracks
- [23:30:16] Multiplexing M2TS
- [23:30:20] Scanning for 3D CLPI info...
[23:30:22]PHASE ONE complete
[23:30:22]PHASE TWO - Rebuild Started
- [23:30:22] Converting SSIF file references
- [23:30:55] Rebuilding BD-3D file Structure
[23:33:48] - Encode and Rebuild complete
[23:33:48] Writing BD structure to ISO file
- ImgBurn completed successfully
- BATMAN_V_SUPERMAN_DAWN_JUSTICE folder removed.
- WORKFILES folder removed.
[23:40:59] JOB: BATMAN_V_SUPERMAN_DAWN_JUSTICE finished.

gonna try again later. First 8-way jungle book

[DoctorM]

Does MULTIPROCESS work on 3D content? The help page specifically says multiple instances of x264. Multiple instances of FRIM are launched as well? That should make a huge difference.

[Ch3vr0n]

not that i know off, or the log would have indicated x-Way. Anyway 8-way split: bad idea. encoding auto-aborts after about 10-15 seconds. auto-split (4-way), happily chugs along.

[jdobbs]

not that i know off, or the log would have indicated x-Way. Anyway 8-way split: bad idea. encoding auto-aborts after about 10-15 seconds. auto-split (4-way), happily chugs along.Interesting. I can't imagine why. I've done it on my system... but it's slower than 4 way for me (I hit 100% processor utilization on all eight processors with MULTIPROCESS at 4).

Also, I can't test the file. I'm on the road with nothing but my iPad for a couple days.

[Ch3vr0n]

Oh i load all 8 cores too at 100% with auto-split. Though i'm not going to cry about 8-way manual split not working. The conversion times i have now compared to my old rig are like 4x less, i'm happy with that. About the file, no worries. Just send me a pm or tag me or something when you've had the chance to take a look. I'll leave it up until then.

[Lathe]

Two pass is actually the reverse of CRF. In CRF you are setting a desired quality level -- and the bitrate is the result of the need to keep that level. In two pass you have a fixed bitrate (computed by the requirement to hit the output target size selected). In the first pass, the encoder is determining how to distribute that bitrate across all scenes/picture elements in order to get the best quality -- with the bitrate available. In the second pass it is applying what it learned to an actual encode.

BD-RB's prediction phase tries to perform a hybrid of the two. It encodes a subset of the scenes/picture elements in the source and tries to find what CRF will result in the required target size. It then encodes using that CRF. The price for that is accuracy. Two pass is always very, very close to the desired output size. Predicted CRF will often undersize or oversize by some small amount. Not much -- but not perfect.

You are right. It is an AVERAGE bitrate. The first pass (of a two pass encode) determines where it is necessary to use higher rates (difficult scenes) and where bitrate can be lowered (simpler scenes). There is also a specified maximum bitrate (set by the fastest transfer rate a BD disc's spin speed can accommodate, for example)

Hmmm, that's good that you explain that. It seems to me then, that the 2 pass, since it does NOT set a desired CRF rate to match the size, but I guess if I understand correctly, merely is concerned with what AVERAGE bit rate it takes to fill the desired size, then to me it seems quite clear that CRF would always be preferable then (if a precise size is not necessary) because if I understand right, CRF will always try to keep a constant 'perceived quality' no matter WHAT bit rate is needed within the Blu-ray limits of course.

Seems like CRF for backup is almost always the way to go then.

Thanks JD!

[MrVideo]

Goto post 24769

[MrVideo]

Goto post 24769

[Lathe]

@Lathe
How to find out the "ultimate" CRF for a given target size:
Run BDRB in 1-pass CRF prediction mode, i.e. remove the FIXED_CRF= in your .ini, and select 1-pass CRF encode and select a target size.
BDRB then runs a number of short CRF prediction steps (kind of trial and error learning) to find out the "final" CRF which will produce the target file size. This "final" CRF is then used in the subsequent 1-pass CRF encoding.
During the CRF prediction phase you will see in the log how CRF develops towards the "final" CRF.

Thanks, I'll try that...

So, I don't have to do anything else in my ini? DirectShow doesn't work in my case, so can I try this with FRIM? I think that is the only way I can run a 1 pass CRF encode without throwing the usual error.

[MrVideo]

Goto post 24769

[Sharc]

Thanks, I'll try that...

So, I don't have to do anything else in my ini? DirectShow doesn't work in my case, so can I try this with FRIM? I think that is the only way I can run a 1 pass CRF encode without throwing the usual error.
I am afraid FRIM won't work because it does not support random seeking, which is essential for the samples selection for CRF prediction.
Internal LAVF will probably not work either because Avisynth is involved, but as I am not sure you could try it.
DirectShow should work (and it works here), but you seem to have your own very specific problems with it......
I am always using DGDecNV, but it only works with NVIDIA cards.

[Ch3vr0n]

@Jdobbs is there a way to know if hardware or software based FRIM encoding has been used? Just redid that 3D disc, this time it encoded fully but there's occasional glitching. Log below. I'm pretty sure my old Q9550 did software de- / encoding only. Are there switches to force that?

[08/20/16] BD Rebuilder v0.50.18
[05:52:21] Source: BATMAN_V_SUPERMAN_DAWN_JUSTICE
- Input BD size: 43,73 GB
- Approximate total content: [02:38:47.851]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Very Fast), ABR
- Output folder: D:\Blu-ray\Rebuilds\BDRB\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[05:52:22] PHASE ONE, Encoding
- [05:52:22] Processing: VID_00052 (1 of 2)
- [05:52:22] Reencoding video [VID_00052]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 218*209 frames
- Bitrate: 18*147 Kbs
- Using FRIMEncoder for MVC encoding
- [05:52:22] Reencoding: VID_00052, Pass 1 of 1
- [09:40:25] Video Encode complete
- [09:40:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:40:25] Multiplexing M2TS
- [09:51:54] Scanning for 3D CLPI info...
- [09:55:11] Processing: VID_00103 (2 of 2)
- [09:55:11] Extracting A/V streams [VID_00103]
- [09:55:19] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 8*159 frames
- Bitrate: 4*805 Kbs
- Using FRIMEncoder for MVC encoding
- [09:55:19] Reencoding: VID_00103, Pass 1 of 1
- [09:59:26] Video Encode complete
- [09:59:26] Processing audio tracks
- [09:59:26] Multiplexing M2TS
- [09:59:30] Scanning for 3D CLPI info...
[09:59:31]PHASE ONE complete
[09:59:31]PHASE TWO - Rebuild Started
- [09:59:31] Converting SSIF file references
- [10:00:03] Rebuilding BD-3D file Structure
[10:03:28] - Encode and Rebuild complete
[10:03:28] Writing BD structure to ISO file
- ImgBurn completed successfully
- BATMAN_V_SUPERMAN_DAWN_JUSTICE folder removed.
- WORKFILES folder removed.
[10:10:57] JOB: BATMAN_V_SUPERMAN_DAWN_JUSTICE finished.

[Lathe]

I am afraid FRIM won't work because it does not support random seeking, which is essential for the samples selection for CRF prediction.
Internal LAVF will probably not work either because Avisynth is involved, but as I am not sure you could try it.
DirectShow should work (and it works here), but you seem to have your own very specific problems with it......
I am always using DGDecNV, but it only works with NVIDIA cards.

Yeah, even with the new version of BDRB and after re-installing the current LAV/DirectShow stuff from page 1, I still get the omnipresent AnyDVD error, even though I am using the full Masters of Cinema Blu-ray of 'NOSFERATU'...

Oh well, I'll just stick with the CMD line CRF-18 which has really produced great results.

There was no real important reason to generate whatever the projected CRF would be, really. Just curious, as always...

Thanks though...

[MrVideo]

OK, here are the things that I've discovered (previous posts deleted):

In order to create a BD using the imported files, all one needs to do is burn the BD structure that is created. If one selected to back up, then recoding is done, even though FORCE_NOENCODE=1 is set. Plus, the imported chapters within the MKV file is ignored.
Chapters that are in the MKV file are used when initially imported. Good news. But, for those who do the back up, they are ignored. Bad news.
The source directory is a little weird. 1) You cannot enter a path that doesn't go to a BD structure. You should be able to enter whatever path you like, then when you do go to import files that path is used. 2) When you import MKV files, when it is done with the importing and menu building, that path now shows up in the GUI. But, it is ignored. 3) The source path that is in the INI file and GUI source path is ignored. When I go to import MKV files, the initial path that shows up is one that I used several times ago and it not being used at this point in time.
The title is placed at the top of the menu. It is not shifted down to the MENU_VERTICAL location. The reason that it needs to move is so that it doesn't step on the background image. In this case, it is the TV show's logo. Maybe a separate TITLE_VERTICAL and TITLE_CENTER for its placement?
My font selection is not being used and there is no error in the log to indicate why. I know the font is there since I installed it and verified that it is in the FONTS directory. I used the name that is displayed in the explorer (Giovanni). When using the font in Photoshop (on another box), it is listed as ITC Giovanni. I tried that as well. Though I've just noticed that double-clicking on the font brings up a window that displays the font, but calls it Giovanni Book. I'm now trying that name. That said, it would be nice if the log showed that the font was not found.
EDIT: The name used for the font display window needs to be used. Now it is using my font.


Unfortunately that stupid DVDFab media player does not like the menu. All I get is a black screen. Burning discs to test runs is too expensive. Anyone know of a free program that runs under XP that will work with BDRB's menus? And before anyone says to use VLC, it doesn't work either. All it does is show the background image.

Enhancement suggestions:

Add a menu option to display the hidden options txt file as read only. That way users can copy-n-paste an entry from that file to the INI file's editor. Or bring up the hidden txt file using wordpad, so that it can stay up while copying more than one entry from there to the INI.
Add MENU_FONT_SIZE in points. In the hidden file, list what the default is.
As mentioned above, two new options: TITLE_VERTICAL and TITLE_HORIZONTAL_CENTER
While there is a MENU font selection, how about the same for TITLE? (I know, this is getting closer to an authoring package ability)
Add TITLE_FONT_SIZE in points. In the hidden file, list what the default is.

[Nemesh]

I hope this is the right place to post this.

I have created some Blu-Ray disc with BDRebuilder.
If I write the BD to a empty disc and start it up with my Samsung BD-H6500 player or Popcornhour C-200, the menu looks like this:

http://i942.photobucket.com/albums/ad266/MoyenneLOTS/handleiding/Screenshot1_zps7bzsw8vn.jpg

The letter of the menu look great.
Now if I open the same disc (from HD) with my Mede8er MED800x3D the menu looks like this:

http://i942.photobucket.com/albums/ad266/MoyenneLOTS/handleiding/Screenshot2_zpsqnvruecv.jpg

As you see, the Mede8er MED800X3D doesn't display the transparent grey/black field and the letters from the menu look very frayed.

I have reported this problem on the Mede8er board, but got no answer.
Is it possible that BDRebuilder creates a menu that also looks good on the Mede8er MED600/800 ?
Or is it a problem with the firmware/hardware of de MED800X3D ?

If this is the wrong place to post this, then I give you my sincere appologies.
With much regards,

Nemesh

[mparade]

I have got this message in the command line:

avs [error]: LoadPlugin: �v���O�C���������G���[
(C:\WORKING\WORKFILES\VID_01204.AVS, line 2)
x264 [error]: could not open input file `C:\WORKING\WORKFILES\VID_01204.AVS'

Maybe because DGDecNV2052 is not supported?

Any help would be appreciated.

Solved: after changing back the decoder to version 2051 the problem is solved.

[Ch3vr0n]

ignore my previous "pixellation" report. Forgot i had to test using a standalone and not software player. Initial testing indicates default frim settings just fine, no pixellation

[DoctorM]

@MrVideo - When I first bought my BD burner I also bought a 10 pack of Verbatim BD50-RW discs.
I have no idea what I would do if I didn't have them.

That said, I've tried VLC, which although it has basic BD support, can't play BD RB built menus either.
I'm hoping someone has an answer to your question about software that can play the menus.

[MrVideo]

@MrVideo - When I first bought my BD burner I also bought a 10 pack of Verbatim BD50-RW discs.
I have no idea what I would do if I didn't have them.

Good idea. I'll have to look into BD25-RW discs.

UPDATE: Just bought 10 pieces. Thanks for the tip.

[worknstiff]

I was over at the CloneBD site and got an interesting post from one of their developers, and was surprised by his comments about an analysis tool they use. I had started a thread about why when feeding BD_Rebuilder or even CloneBD backups to CloneBD to create MKV's from, they failed sometimes and this was his response.
Quote: Out of pure curiosity, we threw the results from BDRebuilder, TSMuxer and even Fab at that analysis tool. We were astonished to learn that none of them stick to the specs at all. BDRebuilder in particular makes a real mess (the max. recording rate of 48mbits is violated, restraints for audio buffering are exceeded by several factors, etc...). Obviously, through an evolutionary process, these programs were modified bit by bit until the results played on the players, so usually you're fine with them. But those files still are not ok. So I'm not surprised, when CloneBD chokes on some.
Wow, I have never had a problem playing BD_Rebuilder output on my Panasonic, Oppo, or even my Samsung Blu-ray players and they always played using TMT5 or PowerDVD too. I seem to have more trouble with the movie only partial backups with CloneBD's simple menu's using software players though. Thanks jdobbs for the GREAT WORK ON BD_Rebuilder.

[jdobbs]

I was over at the CloneBD site and got an interesting post from one of their developers, and was surprised by his comments about an analysis tool they use. I had started a thread about why when feeding BD_Rebuilder or even CloneBD backups to CloneBD to create MKV's from, they failed sometimes and this was his response.
Quote: Out of pure curiosity, we threw the results from BDRebuilder, TSMuxer and even Fab at that analysis tool. We were astonished to learn that none of them stick to the specs at all. BDRebuilder in particular makes a real mess (the max. recording rate of 48mbits is violated, restraints for audio buffering are exceeded by several factors, etc...). Obviously, through an evolutionary process, these programs were modified bit by bit until the results played on the players, so usually you're fine with them. But those files still are not ok. So I'm not surprised, when CloneBD chokes on some.
Wow, I have never had a problem playing BD_Rebuilder output on my Panasonic, Oppo, or even my Samsung Blu-ray players and they always played using TMT5 or PowerDVD too. I seem to have more trouble with the movie only partial backups with CloneBD's simple menu's using software players though. Thanks jdobbs for the GREAT WORK ON BD_Rebuilder.They're wrong. Pure and simple. You can look at the encoding command lines and see that limits are placed on X264 - which are not only within the specs, but also have a "just in case" extra buffer. No big surprise to find that they would like you to believe that you should pay for their software rather than use the free one.

As I have said before -- I ask that we don't comment on other software in this thread. It isn't that I feel any sort of sense of competition -- it's that I truly don't care what other software does.

[jdobbs]

I hope this is the right place to post this.

I have created some Blu-Ray disc with BDRebuilder.
If I write the BD to a empty disc and start it up with my Samsung BD-H6500 player or Popcornhour C-200, the menu looks like this:

The letter of the menu look great.
Now if I open the same disc (from HD) with my Mede8er MED800x3D the menu looks like this:

As you see, the Mede8er MED800X3D doesn't display the transparent grey/black field and the letters from the menu look very frayed.

I have reported this problem on the Mede8er board, but got no answer.
Is it possible that BDRebuilder creates a menu that also looks good on the Mede8er MED600/800 ?
Or is it a problem with the firmware/hardware of de MED800X3D ?

If this is the wrong place to post this, then I give you my sincere appologies.
With much regards,

NemeshEverything on that screen is simply graphic images. It's the player.

[Nemesh]

@Mr Dobbs,

Thank you very much for the fast reply sir.
Have posted this problem with the Mede8er MED600/800X3D on the Mede8er international board here. (http://www.mede8erforum.com/index.php/topic,17892.0.html)
That was on June 02, 2016 (more than 2 months ago) and never got any reply.
Now I finally got my answer, and I think it's a problem in the hardware of the Mede8er MED600/800X3D that they can't solve with a firmware fix and in a effort not to hurt their sales..........
Give you my best regards,

Nemesh

[worknstiff]

@ jdobbs RE: pay for their software rather than use the free one. Guess that sums it up. Thanks, sorry to clog up the thread. What surprised me was that their "own created BD folder", failed to create an MKV when used as a source, lol.

[kufo]

Since Version 0.50.16 I have a speed problem. Same settings as in 0.50.14, but the maximum reencoding speed is about 50fps. All further Versions up to 0.50.18 do the same. In Version 0.50.14 the speed was about 115fps.
I can´t figure out what was wrong in the last 3 Versions. It shows me x264/internal LAVF for frameserving but the speed looks like a FRIM encode.Finaly I switched the TOOLS folder from 0.50.14 into 0.50.18. While rencoding
I had a speed of 115fps.
The diffrent between both TOOLS folders is in newer Versions.x264 for example moved from 0.148.2665.0 to 0.148.2705.0
Any idea what could cause that issue?:confused:

[DoctorM]

I must be missing something. Because of the way a disc was set up (lots of branching to support foreign languages), I had to use BD Rebuilder to create first a Quick Play structure (no encoding), fix the structure and then run it through BD Rebuilder again to encode a BD5.

I know that messes with things, but I'm getting the weird issue that the DTS-HD MA tracks are being cored, but not re-encoded to DD. I have "Strict AVCHD" setting on, but I can't think of any other reason Rebuilder would copy a DTS track to an AVCHD disc.

Any suggestions or am I out of luck?

Edit 2: Dang, I always forget that BD RB doesn't like Full Backup with AVCHD output.
Unchecked 'Do not convert DTS to AC3 (Blu-Ray only)' and it works fine now.

[geheim]

Since Version 0.50.16 I have a speed problem. Same settings as in 0.50.14, but the maximum reencoding speed is about 50fps. All further Versions up to 0.50.18 do the same. In Version 0.50.14 the speed was about 115fps.
I can´t figure out what was wrong in the last 3 Versions. It shows me x264/internal LAVF for frameserving but the speed looks like a FRIM encode.Finaly I switched the TOOLS folder from 0.50.14 into 0.50.18. While rencoding
I had a speed of 115fps.
The diffrent between both TOOLS folders is in newer Versions.x264 for example moved from 0.148.2665.0 to 0.148.2705.0
Any idea what could cause that issue?:confused:

I can confirm this issue! Since 0.50.16 the encoding speed with LAVF as frameserver reaches only 50 fps in the max. All versions before reached Speeds up to 120fps on my Intel i7. Using the tools folder from older versions on the latest releases results in speeds of 120fps again.

So, @jdobbs or anyone else, do you have any idea why this issue happens??

Thanks!

[marco421]

I started to use version 50.18 and Norton removed it as bad. I rebooted and shut down Norton, re-downloaded ver. 50.18 and extracted all. clicked on bdrb.exe and got an error msg: 'component mscomctl.ocx or one of it's dependencies not correctly registered. a file is missing or invalid'
help please. how do I fix this?

[lauguru]

jdobbs@
It is possible to add in setup bdrebuilder use DGDecNV x64 , only suport 32 bits.

the DGDecNV build 2052 suport x64

thanks

http://image.prntscr.com/image/9147badb0ace4023a4107c7c14738238.png

@jdobbs You could do something with this?Please.

[varekai]

I started to use version 50.18 and Norton removed it as bad. I rebooted and shut down Norton, re-downloaded ver. 50.18 and extracted all. clicked on bdrb.exe and got an error msg: 'component mscomctl.ocx or one of it's dependencies not correctly registered. a file is missing or invalid'
help please. how do I fix this?
Have a look here:
http://forum.doom9.org/showthread.php?p=1357838#post1357838

[kufo]

Speed problem in encoding, introduced in v. 0.50.16. Since this version there is an encodig speed of only 50fps. See #24580 +24582. I found out that the reason is in x264/x264-64 higher than v. 0.148.2705.0
V. 0.148.2705.0 was used in 0.50.14 Tools folder and it worked fine for me. Is there no other opportunity as replacing this manualy by the old version in newer BD-Rebuilder releases?
I can´t imagine that is is a coincidence, what happens to geheim an d me.
Is there no one else with this problem?

[jdobbs]

Since Version 0.50.16 I have a speed problem. Same settings as in 0.50.14, but the maximum reencoding speed is about 50fps. All further Versions up to 0.50.18 do the same. In Version 0.50.14 the speed was about 115fps.
I can´t figure out what was wrong in the last 3 Versions. It shows me x264/internal LAVF for frameserving but the speed looks like a FRIM encode.Finaly I switched the TOOLS folder from 0.50.14 into 0.50.18. While rencoding
I had a speed of 115fps.
The diffrent between both TOOLS folders is in newer Versions.x264 for example moved from 0.148.2665.0 to 0.148.2705.0
Any idea what could cause that issue?:confused:The version of X264 included with BD-RB was upgraded in v0.50.16 (to r2705). That's the only thing I can imagine that would cause a speed decrease. But I've not personally seen any slowdown, nor have I received any other reports of slowdown. It's possible your speed may have been affected by an incorrect version of SPLIT.EXE if you have set the MULTIPROCESS hidden value -- but that only happened for one version (v0.50.17).

[kufo]

The version of X264 included with BD-RB was upgraded in v0.50.16 (to r2705). That's the only thing I can imagine that would cause a speed decrease. But I've not personally seen any slowdown, nor have I received any other reports of slowdown. It's possible your speed may have been affected by an incorrect version of SPLIT.EXE if you have set the MULTIPROCESS hidden value -- but that only happened for one version (v0.50.17).
@jdobbs.
Thanks for your quick reply. Good to know that nothing changed except for the x264 Version. I´ve done some testing with the split.exe, but nothing changed with the speed. When I use standard settings in Rebuilder V. 0.50.18 with only changes in language and custom output size the speed is allright. I see there must be a conflict with the settings i used to utilize and the new x264 Version. I´ll have to compare standard settings with my own. This is the only way to solve my problrem with the speed, I think.

[jdobbs]

@jdobbs.
Thanks for your quick reply. Good to know that nothing changed except for the x264 Version. I´ve done some testing with the split.exe, but nothing changed with the speed. When I use standard settings in Rebuilder V. 0.50.18 with only changes in language and custom output size the speed is allright. I see there must be a conflict with the settings i used to utilize and the new x264 Version. I´ll have to compare standard settings with my own. This is the only way to solve my problrem with the speed, I think.What settings do you use/mean? Some settings can have a significant impact on speed.

[jdobbs]

@jdobbs You could do something with this?Please.It's not a matter of me doing something with it -- it simply doesn't work.

[lauguru]

It's not a matter of me doing something with it -- it simply doesn't work.

I do not understand, does not work under bd rebuilder? or not working DGDecNV x64?

the DGDecNV x64 works for me outside rebuilder bd.

http://image.prntscr.com/image/7befeb0810314c058cf2476a31386767.png

[jdobbs]

It has been explained before -- please search for it.

[lauguru]

It has been explained before -- please search for it.

this post?

http://forum.doom9.org/showpost.php?p=1774996&postcount=24534

(Open up a DOS window and type SET and enter. It will list all the environment variables.

Or, if you prefer, you can go to Control Panel>System and Security>System>Advanced System Settings and click on "Environment Variables"

I just ran a test of "Revenant" using your settings and am getting 4 instances of X264. The one thing I had to change, though, was from DGDecNV to Directshow. I upgraded my video machine to Windows 10, and my Nvidia GT520 video card is one of the ones that isn't supported yet (by DGDecNV) on Win10, so I can't use DGDecNV anymore.)
__________________

[jdobbs]

I don't get the connection to that link... so, again:

Using a 64 bit plugin requires that you also use the 64 bit version of AVISYNTH. There are multiple reasons why you can't use the 64 bit version of AVISYNTH with BD-RB -- including incompatibility with many filters (that have no 64 bit equivalent) and 32 bit applications. And frankly, for the minimal increase in speed you might get, it just isn't worth the effort.

[lauguru]

I don't get the connection to that link... so, again:

Using a 64 bit plugin requires that you also use the 64 bit version of AVISYNTH. There are multiple reasons why you can't use the 64 bit version of AVISYNTH with BD-RB -- including incompatibility with many filters (that have no 64 bit equivalent) and 32 bit applications. And frankly, for the minimal increase in speed you might get, it just isn't worth the effort.

ok thanks for the reply, a shame that you can not.

[Groucho2004]

ok thanks for the reply, a shame that you can not.
I'm curious - What do you think you'll gain by using the 64 bit version of DGDecodeNV.dll? The decoding speed advantage is purely academic when you consider that other filters and the encoder are the bottleneck in almost every case.

[lauguru]

I'm curious - What do you think you'll gain by using the 64 bit version of DGDecodeNV.dll? The decoding speed advantage is purely academic when you consider that other filters and the encoder are the bottleneck in almost every case.


I just think that x64 bits, should be better and more RAM memory management GPU DGDecNV, my gpu uses half ram available in 32-bit version. Thank you


http://image.prntscr.com/image/8f0df5fc578a4be89700b1a16ee529e1.png

[kufo]

What settings do you use/mean? Some settings can have a significant impact on speed.
Thats´s what I´ll have to test. I didn´t change the settings for a very long time, because they worked fine for me. In meantime some default settings have changed but up to V. 0.50.14 there were no problems at all. I´m allways doing doing a full backup with a custum size of 23900 MB using some settings from the HIDDENOPTS folder. Last change was the opportunity for 3D encoding with it´s settings about 2 years ago ( I think it was V. 0.47.07 )I´ll bring the Config File in alphabetical order and and compare one by one with working Version ( 120fps speed ) of 0.50.18.

I sign up if I have found the culprit:thanks:

[Groucho2004]

I just think that x64 bits, should be better and more RAM memory management GPU DGDecNV, my gpu uses half ram available in 32-bit version. Thank you


http://image.prntscr.com/image/8f0df5fc578a4be89700b1a16ee529e1.png
Even with several parallel decoding processes and 1080p material, the decoding will still use less than 1 GB. So, you have quite some headroom even with "just" 4 GB.

[jdobbs]

Even with several parallel decoding processes and 1080p material, the decoding will still use less than 1 GB. So, you have quite some headroom even with "just" 4 GB.There's going to be very little speed gain in using the 64 bit plugin, if there is any at all. Personally I doubt it.

[Groucho2004]

There's going to be very little speed gain in using the 64 bit plugin, if there is any at all. Personally I doubt it.
Yes, I mentioned that in post #24796.