BD Rebuilder Beta - Bug Reports Only

[Yordan5]

The heart of my current PC setup is Intel Core i7-4770. BD-RB now takes around 7 hours (High Quality VBR) to shrink a BD movie. Just wondered if the new AMD Ryzen 1800X (8 cores) processessor (and the rumored 16 cores one) would be able to halve the processing time?

[jdobbs]

The heart of my current PC setup is Intel Core i7-4770. BD-RB now takes around 7 hours (High Quality VBR) to shrink a BD movie. Just wondered if the new AMD Ryzen 1800X (8 cores) processessor (and the rumored 16 cores one) would be able to halve the processing time?Can't say about the Ryzen... but 7 hours seems like a lot. I run an AMD FX8350, which should be inferior to your i7, and it takes about half that long. Of course it would depend a lot on the particular disc and total length of the encoding... but 7 hrs still seems long.

[Rodger]

@jdobbs...your FX8350 is hardly faster than a i7-3770.
i7-4770 has about 10% more power than the i7-3770. That should make it a little faster than the FX8350.
Ryzen is a completely different thing. It has a lot more horsepower per clock and it has it strength offsides from gaming. Encoding should be one of the best things to run on Ryzen. While gaming my i7-7700K is clearly the better choice, but it stands no chance while encoding.

I´d recommend the x1700 over the x1800. The price gap is too big for the little more performance I think.
And I strongly recommend x370 boards if you have plans for many m.2 SSDs aka Top speed storage.

[jdobbs]

@jdobbs...your FX8350 is hardly faster than a i7-3770.
i7-4770 has about 10% more power than the i7-3770. That should make it a little faster than the FX8350.
Ryzen is a completely different thing. It has a lot more horsepower per clock and it has it strength offsides from gaming. Encoding should be one of the best things to run on Ryzen. While gaming my i7-7700K is clearly the better choice, but it stands no chance while encoding.

I´d recommend the x1700 over the x1800. The price gap is too big for the little more performance I think.
And I strongly recommend x370 boards if you have plans for many m.2 SSDs aka Top speed storage.Well... I guess you missed my point completely. Maybe you should re-read my post. Yes, his i7 should be significantly faster than the FX8350. But, based on his post, it isn't. So the point is: he may have some other issue if it's taking that long to do a disc.

[Rodger]

naah....just a vocabulary error on my side. Sorry for that.
"inferior" is worse not better :o

7 hours is really a long run...I guess he is using some extreme settings with a doubtful result as I find.
Using the preset with maximum quality in BD Rebuilder should be the way to go for him.

[Yordan5]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?

[jdobbs]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?I would suggest you install LAV filters (see the first post of this thread), and then simply select "DirectshowSource" from the SETUP menu.

[mparade]

Is there an alternative way in BD-RB to make 3D full-backups (output is BD-25, keeping 3D content as 3D, 2D content as 2D on the same disc) compared to Frim Encoder?

Is it possible to make full 3D-backups in e.g. half-sbs, full-sbs formats as well?

I would like to start to archive my 3D BDs as well with the "best possible quality".
Is the "only" current solution to use Frim Encoder with 1-pass ABR?

Thank you for an answer in advance.

[worknstiff]

Don't know if this constitutes a "Bug" or not but I am having a hard time getting BD Rebuilder to allow blanking of quite a few extras on the Fantastic Beasts blue ray. I have tried to change the min m2ts size setting and there is still a load of m2ts files not listed in FULL or EDIT mode. Is this just a limitation of how many items can be listed or are they hidden from BD Rebuilder's processing somehow? Thanks again jdobbs for the most excellent BD Rebuilder program, I only wish other video editing programs were designed to be as simple to use as this one.

[Sharc]

Is there an alternative way in BD-RB to make 3D full-backups (output is BD-25, keeping 3D content as 3D, 2D content as 2D on the same disc) compared to Frim Encoder?

Is it possible to make full 3D-backups in e.g. half-sbs, full-sbs formats as well?

I would like to start to archive my 3D BDs as well with the "best possible quality".
Is the "only" current solution to use Frim Encoder with 1-pass ABR?

Thank you for an answer in advance.
Similar has been discussed a while ago. Summarizing -- as far as I remember:
- SBS (full or half) is limited to movie-only backups
- Full 3D backup with BD-RB requires FRIM
- There is no free 3D MVC alternative to FRIM

Edit:
I found the last post of this discussion. You may want to trace the full discussion backwards from there.
I have been asking about full disk 3D backups SBS.
http://forum.doom9.org/showpost.php?p=1794225&postcount=25538

[jdobbs]

Yeah. I wasn't positive, but looked at it, and it doesn't do SBS full backups right now. I'm going to go back and see how hard it would be to make the changes... but no promises. In order to do that, it will have to appear like a 2D disc that just happens to have half SBS or half O/U where the 3D features used to be.

[Mark_Venture]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?If you want to... take a look at this thread -> http://forum.doom9.org/showthread.php?t=173601 my INI file is posted there, and some times from tests I ran (with both my old PC and after upgrades)... try those settings to see if it speeds things up. If you have the same exact blurays, you can better compare to the speeds I see.

Granted I'm going for good quality that doesn't take "all night" (i.e. I'm trying to balance video quality and speed), I'm not going for "exact quality" (i.e. I'm not looking for "best quality no matter how long it takes).

Since I setup BD-Rebuilder long ago, I followed the OP exactly. At that time for step 2, only step 2B was available. When 2A & 2C was added, I did that. And I usually have set as DGDecNV for Frame Serving (since i donated and have a license)

[mparade]

@Sharc and jdobbs

I think I will start to make some tests on a BD-25 media using the Frim Encoder in BD-RB. In the worst case, hopefully it is enough to
cut down the HD and throw out the unused audio tracks to reach a similar quality level to x264's CRF~18-20. I am very satisfied with the results of x264 but don't know Frim at all.

[Sharc]

@mparade
I think you won't be disappointed by the FRIM quality when backing up to a 25GB disc as the bitrate is comfortable.

[jdobbs]

@mparade
I think you won't be disappointed by the FRIM quality when backing up to a 25GB disc as the bitrate is comfortable.I agree. It might be different if you're trying to squeeze everything into the size of a DVD -- but at BD-25 bitrates I think it looks great (at least for most discs, there may be a giant one out there somewhere that might be an exception).

[meadrocks]

Boondock Saints works great on x264, fails in hevc. I included all the input files. This is a brand new PC I built, I've only installed bd-rebuilder. My old PC would take 6-10 hours to do a rebuild, this 1 did the x264 in 75 minutes.

alternate:
[00001]
caption=MKV Container, 1920x1080, AutoGOP, Auto-AC3
vBitrate=3000
aBitrate=*
aType=0
vFormat=5
vKeyint=Auto
cType=1
[00002]
caption=MKV Container, HEVC 1920x1080, Auto-AC3
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=0
vFormat=5
cType=1

bdrebuilder.ini:
[Options]
VERSION=0.50.0.23
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
MOVIEONLY_TYPE=2
ALTCRF=22
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
WORKING_PATH=E:\T1\
SOURCE_PATH=C:\DVDRIP\BOONDOCK_SAINTS\

bd-rebuilder.log
[04/06/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 104.87GB
- 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
[04/06/17] Systems Settings Check complete
----------------------
[04/06/17] BD Rebuilder v0.50.23
[12:07:49] Source: BOONDOCK_SAINTS_00001
- Input BD size: 32.94 GB
- Approximate total content: [01:48:21.661]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:07:49] PHASE ONE, Encoding
- [12:07:49] Processing: VID_00115 (1 of 7)
- [12:07:49] Extracting A/V streams [VID_00115]
- [12:12:02] Reencoding video [VID_00115]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 56,920 frames
- [12:12:02] Reencoding: VID_00115, Pass 1 of 1
[12:12:03] - Failed video encode, aborted

boondocksaints.inf
[Status]
LABEL=BOONDOCK_SAINTS
VERSION=v0.50.23
SOURCE_SIZE=35370577920
SOURCE_VIDEO_SIZE=35370577920
TARGET_SIZE=4686086144
REDUCTION=.132485427707708
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=2
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=1.5
[00115]
AUDIO=100
PGS=11
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1716350997

Thanks for your time & help.

[MrVideo]

Enhancement suggestions:

Both of these apply to the editing of the menu text.

1) Allow the ability to select multiple titles to move. I've run into a situation where time would have been saved if I could have moved more than one title at once.

2) When titles are too long, instead of just removing the text, how about turning those characters red instead. There are times when looking at the titles where I have missed that text had been truncated. By having the text changed to red instead, it tends to catch the eye more than missing text. Plus, by still having the text on the line, when other characters are removed, they will be there so that they can again be used and turned black.

Thanks.

[jdobbs]

1) Allow the ability to select multiple titles to move. I've run into a situation where time would have been saved if I could have moved more than one title at once.I don't understand this request.

[Denner]

Hi, I have built a dedicated x264 encoding rig, it has a Ryzen 1700, 750gb SSD and 16gb ram, only thing on the machine is Windows 10 and BD-Rebuilder as it will only be used for blu-ray re-encoding.
System is stress tested and with Prime 95 ( 24 hour run ) and OCCT ( 12 hour run ) and is 100% stable when overclocked to 3800GHz and ofcause at stock speed of 3000GHz.

Problem is that I BD-Rebuilder keeps crashing or x264 does and I keep getting a pop up window with this message "x264.exe has stopped working...." , I have now tried installing RipBot to see if this crashes x264 too, but no problems there at all, RipBot have been running for 12 hours straight encoding a lot of blu-ray rips that crashes BD-Rebuilder without crashing, so I tried encoding with BD-Rebuilder again this morning and same problem is still there, I am at a loss, because I have the excact same setup on my "normal" pc except it is an intel processor and it never crashes, even on the same disk ?

Here is the log from BD-Rebuilder:

[04-09-17] BD Rebuilder v0.50.23
[14:42:53] Source: UPB1_625529
- Input BD size: 32,05 GB
- Approximate total content: [02:18:19.248]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:42:54] PHASE ONE, Encoding
- [14:42:54] Processing: VID_00013 (1 of 23)
- [14:42:54] Extracting A/V streams [VID_00013]
- [14:42:59] Reencoding video [VID_00013]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 648 frames
- Bitrate: 19.105 Kbs
- [14:42:59] Reencoding: VID_00013, Pass 1 of 2
- [14:43:04] Reencoding: VID_00013, Pass 2 of 2
- [14:43:23] Video Encode complete
- [14:43:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:43:23] Multiplexing M2TS
- [14:43:27] Processing: VID_00046 (2 of 23)
- [14:43:27] Extracting A/V streams [VID_00046]
- [14:43:31] Reencoding video [VID_00046]
- [14:43:31] Keeping original video (no reencode)
- [14:43:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:43:31] Multiplexing M2TS
- [14:43:35] Processing: VID_00270 (3 of 23)
- [14:43:35] Extracting A/V streams [VID_00270]
- [14:43:40] Reencoding video [VID_00270]
- [14:43:40] Keeping original video (no reencode)
- [14:43:40] Processing audio tracks
- [14:43:40] Multiplexing M2TS
- [14:43:44] Processing: VID_00301 (4 of 23)
- [14:43:44] Extracting A/V streams [VID_00301]
- [14:44:55] Reencoding video [VID_00301]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 103.173 frames
- Bitrate: 21.909 Kbs
- [14:44:55] Reencoding: VID_00301, Pass 1 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 350,12GB
- AVISYNTH Version: 2.6.0.5, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[14:57:07] - Failed video encode, aborted

I am using x264's internal LAVF for frameserving and the only tweak I have enabled is tune film for BD-Rebuilders second pass, have tried with no tweaks enabled but it still crashes :(

Have anyone had the same prolem and what did you do to solve it ?

[jdobbs]

Your system probably isn't stable. I've seen this a hundred times with people trying other stress tests -- they are meaningless. The only real stress test is X264. Slow down your clock and see if it goes away.

It's also possible it could be an incompatibility with the version of X264 included with BD-RB that is used for X264/LAVF (it's different than the one used for other frame-serving types). Try using DirectshowSource.

[mparade]

@jdobbs

Maybe a bug?:

I have just finished testing a bit the Quick-play menu feature of BD-RB. After importing my complete Tom&Jerry Classic DVD Collection Volume 1. I just wanted to burn them (6xDVD5) directly to a BD-25 media. I have used my own menu page for this job. The bug I recognized described in steps as follows to be able to repeat:

- I played an item from the Quick-play menu;
- During play I changed audio from English to e.g. Hungarian and the subtitle language to e.g. Hungarian;
- After watching 3 items sequentially I entered the Quick-play menu to play an other item from the end;
- During watching that one I realized that both the audio and subtitle language had set back to English, however I finished playing the previous item with a Hungarian audio and subtitle language chosen;

It seems after entering the Quick-play menu both the audio and subtitle language tracks chosen set back to the defaults due to some unknown reason. If I play items sequentially without entering the menu, the tracks will not be set back.

It is not really convenient because each time I enter the menu (for the purpose of playing an other item among the 70-80pcs in this case) and play an other item I have to set back my preferred language manually using my remote controller both for the subtitle and the audio tracks which has already been done previously.

Please help.

Thank you very much.

[Denner]

Your system probably isn't stable. I've seen this a hundred times with people trying other stress tests -- they are meaningless. The only real stress test is X264. Slow down your clock and see if it goes away.

It's also possible it could be an incompatibility with the version of X264 included with BD-RB that is used for X264/LAVF (it's different than the one used for other frame-serving types). Try using DirectshowSource.

Just tried a DirectshowSource encode, no problems at all, no x264 crashing, but problem is that both first and second pass are way slower than using x264 LAVF, is there any way of settin up BD-Rebuilder so that it can mach the encoding speed achieved by x264 LAVF ?

If not what is the fastest setting when not using x264 LAVF ?

Also tried replacing the x264L-64 with the x264 version RipBot is using and just renamed it to x264L-64, and encoding with that version of x264 using x264/LAVF as fremserver caused no crashing, ut it had a painfully slow first pass with around 40fps and with the original x264L-64 i get aroud 160fps in the first pass.....

[jdobbs]

Just tried a DirectshowSource encode, no problems at all, no x264 crashing, but problem is that both first and second pass are way slower than using x264 LAVF, is there any way of settin up BD-Rebuilder so that it can mach the encoding speed achieved by x264 LAVF ?

If not what is the fastest setting when not using x264 LAVF ?

Also tried replacing the x264L-64 with the x264 version RipBot is using and just renamed it to x264L-64, and encoding with that version of x264 using x264/LAVF as fremserver caused no crashing, ut it had a painfully slow first pass with around 40fps and with the original x264L-64 i get aroud 160fps in the first pass.....That's the reason a different version is used. Something has changed in X264 that makes the use of LAVF extremely slow. So I used one of the old versions for X264/LAVF encoding. You could try other old version (look at the version of X264L-64 in BD-RB and work back from there).

My own tests of X264 don't show much difference between X264/LAVF and DirectshowSource -- but different processors can make a big difference.

[jdobbs]

@jdobbs

Maybe a bug?:

I have just finished testing a bit the Quick-play menu feature of BD-RB. After importing my complete Tom&Jerry Classic DVD Collection Volume 1. I just wanted to burn them (6xDVD5) directly to a BD-25 media. I have used my own menu page for this job. The bug I recognized described in steps as follows to be able to repeat:

- I played an item from the Quick-play menu;
- During play I changed audio from English to e.g. Hungarian and the subtitle language to e.g. Hungarian;
- After watching 3 items sequentially I entered the Quick-play menu to play an other item from the end;
- During watching that one I realized that both the audio and subtitle language had set back to English, however I finished playing the previous item with a Hungarian audio and subtitle language chosen;

It seems after entering the Quick-play menu both the audio and subtitle language tracks chosen set back to the defaults due to some unknown reason. If I play items sequentially without entering the menu, the tracks will not be set back.

It is not really convenient because each time I enter the menu (for the purpose of playing an other item among the 70-80pcs in this case) and play an other item I have to set back my preferred language manually using my remote controller both for the subtitle and the audio tracks which has already been done previously.

Please help.

Thank you very much.I'll have to look at it. But I'm guessing it's because the menu is using the default track and doesn't have other languages as an option.

[MrVideo]

I don't understand this request.
With BDRB, multiple menu items cannot be selected. If you click on one item and then do a ctrl-left-mouse click on another item, the first one is deselected. (Or shift-left-mouse click to select a range of items).

The selection of an item is to allow for editing of the text and potential moving of the item within the menu.

If multiple items are selected, just blank the area that is used for text editing until only a single item is selected. This will still allow for the move of the selected items to a new location in the menu.

[Lathe]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

Yep, just realized the other day that I hadn't gotten any notifications from this thread in a LONG time (I'm a bit slow... :rolleyes: ) so, I'm just NOW seeing your post about 3 weeks later :)

[Lathe]

It's started to work again for me too. Just a temporary glitch, I guess.

It must be because of something with my personal system or setup, but like when I've used CC Cleaner before, I always have to come back and choose 'instant e'mail notifications' on the threads or I won't get notified. Perhaps whatever happened here had the same effect where in MY case it didn't come back on.

[Lathe]

Hi, I have built a dedicated x264 encoding rig, it has a Ryzen 1700, 750gb SSD and 16gb ram, only thing on the machine is Windows 10 and BD-Rebuilder as it will only be used for blu-ray re-encoding.
System is stress tested and with Prime 95 ( 24 hour run ) and OCCT ( 12 hour run ) and is 100% stable when overclocked to 3800GHz and ofcause at stock speed of 3000GHz.

Problem is that I BD-Rebuilder keeps crashing or x264 does and I keep getting a pop up window with this message "x264.exe has stopped working...." , I have now tried installing RipBot to see if this crashes x264 too, but no problems there at all, RipBot have been running for 12 hours straight encoding a lot of blu-ray rips that crashes BD-Rebuilder without crashing, so I tried encoding with BD-Rebuilder again this morning and same problem is still there, I am at a loss, because I have the excact same setup on my "normal" pc except it is an intel processor and it never crashes, even on the same disk ?

Here is the log from BD-Rebuilder:


I am using x264's internal LAVF for frameserving and the only tweak I have enabled is tune film for BD-Rebuilders second pass, have tried with no tweaks enabled but it still crashes :(

Have anyone had the same prolem and what did you do to solve it ?

Hmmm, don't know if it's relevant, but I've not been able to use 'tunings' in BDRB or 'tune film' as a 'tweak' It didn't accept it. I just put in the cmd line codes separately.

[gonca]

I've not been able to use 'tunings' in BDRB or 'tune film' as a 'tweak'
It's working fine on my system
Must be on your end, Lathe:cool:

[Lathe]

It's working fine on my system
Must be on your end, Lathe:cool:

Gonca, if I've told you once, I've told you twice...

Don't talk about my END! :angry:

... and, if it's any of your business, the last time I checked it, there was nothing ON it!

[mparade]

I'll have to look at it. But I'm guessing it's because the menu is using the default track and doesn't have other languages as an option.

OK. Thank you. Simpler said, I think the missing feature of the current Quick-Play Menu is that it should simply "recall" (because the problem only happens when entering the menu) the audio and subtitle language tracks that were set by the user last time manually on remote.

Maybe you should even consider adding hidden opts (to help for the Quick-Play Menu to choose the language required at first loading) like:

IMPORT_DEFAULT_SUB_LANG=s
IMPORT_DEFAULT_AUDIO_LANG=s

Your help is much appreciated.

[Denner]

That's the reason a different version is used. Something has changed in X264 that makes the use of LAVF extremely slow. So I used one of the old versions for X264/LAVF encoding. You could try other old version (look at the version of X264L-64 in BD-RB and work back from there).

My own tests of X264 don't show much difference between X264/LAVF and DirectshowSource -- but different processors can make a big difference.

Cool and thanks, is there a place where I can download older versions of bd-rebuilder?
On ryzen 8 core cpu the difference is huge...

Noticed that when encoding with DirectshowSource x264 32bit version is used, is this normal or am i doing something wrong?

[gonca]

the last time I checked it, there was nothing ON it!
How can you see all the way back there:D

[jdobbs]

Cool and thanks, is there a place where I can download older versions of bd-rebuilder?
On ryzen 8 core cpu the difference is huge...

Noticed that when encoding with DirectshowSource x264 32bit version is used, is this normal or am i doing something wrong?You can't use the 64 bit version with 32 bit AVISYNTH. In my tests the difference in speed between the 32 and 64 bit versions is negligible.

[Denner]

You can't use the 64 bit version with 32 bit AVISYNTH. In my tests the difference in speed between the 32 and 64 bit versions is negligible.

Cool, thanks, right now I am testing with the x264 64bit version from BD-RBV04414 and so far no problem /crashing with this version of x264, best thing is that I am getting 35fps on second pass using the Highest ( very slow) compared to 22fps ( second pass ) on the same settings encoder settings using directshow, so that is quiet a boost in encoding speed using x264 vs directshow :)

Thanks for the help so far :thanks:

[AmigaFuture]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

Yep. I've been occupied by other things and hadn't gotten a message in a bit. Recently I got 2 and there were more than 2 new replies.

[Denner]

A quick update, I found a version of x264, that seemes to be optimal for encoding with Ryzen 8 core cpu's, where I am hitting 40 to 60fps, slowest setting, on the second pass, depending on the encoding bitrate and it almost maxes out all 8 cores in both first and second pass... and most important no crashes....
If any one am having the same problems with Ryzen and bd-rb crashing I would be glad to help and share the x264 version I am using :)

[Taurus]

@ Denner:
Please share your insight.
I'm about to buy a Ryzen and everything cleared beforehand
is stopping me from wasting time on experiments.:D
Thank you.

[Lathe]

A quick update, I found a version of x264, that seemes to be optimal for encoding with Ryzen 8 core cpu's, where I am hitting 40 to 60fps, slowest setting, on the second pass, depending on the encoding bitrate and it almost maxes out all 8 cores in both first and second pass... and most important no crashes....
If any one am having the same problems with Ryzen and bd-rb crashing I would be glad to help and share the x264 version I am using :)

Wow, dude that REALLY is fast! Getting that speed using the ridiculously ultra-slow setting is bloody amazing! I just use the 'High' setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, granted, with a couple of x264 'tweaks' on the 2nd pass I MIGHT get like 5 or 6 fps, usually slower... I guess that's what 8 frigg'n smok'n cores will do for you :)

[gonca]

:sly:@Lathe
Mr. Anal,... cracks
You are trying to make it easy

[Denner]

@ Denner:
Please share your insight.
I'm about to buy a Ryzen and everything cleared beforehand
is stopping me from wasting time on experiments.:D
Thank you.

I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it :)

You can find the version here:https://www.videohelp.com/software/BD-Rebuilder/old-versions

[Denner]

Wow, dude that REALLY is fast! Getting that speed using the ridiculously ultra-slow setting is bloody amazing! I just use the 'High' setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, granted, with a couple of x264 'tweaks' on the 2nd pass I MIGHT get like 5 or 6 fps, usually slower... I guess that's what 8 frigg'n smok'n cores will do for you :)


Yup the power of a Ryzen 1700 overclocked to 3.8 GHz, love this CPU, easiest overclock I ever did :)

[mparade]

Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?

[jdobbs]

Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.

[mparade]

Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.

Sorry...I left IVTC turned on in the setup dialog. I thought it had no effect on pure progressive content at all. But now, I see.

[Yordan5]

I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it :)

You can find the version here:https://www.videohelp.com/software/BD-Rebuilder/old-versions

Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.

[Lathe]

:sly:@Lathe

Quote:
Mr. Anal,... cracks

You are trying to make it easy

You ask, you plead, you beg, and this is what you get...


http://lathe-of-heaven.com/sigh1.gif

[Lathe]

Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.

That's about what mine runs at the same setting. If I add a couple of x264 'tweaks', it might take a bit longer.

JD, do YOU recommend replacing the current BDRB version with this particular version of x264 (BDRB 5011) and renaming it as suggested above?

[Thaddäus]

I've been using BD Rebuilder for many discs during the last months and recognized that there's always more than 1 GB space left on a BD25 when I'm using the BD25 target size-preset. Sometimes there's even more left - last week I tried a backup of "Deepwater Horizon" and the output-size was only 20,9 GB so 10% of the disc space (should be around 23,1 GB) is still free.

Has someone tested BD Rebuilder with a custom-target size to use the whole capacity of a BD25? I'm using the highest quality-settings and two pass-encoding, so BD Rebuilder should be able to calculate the optimal bitrate and make the most of the availiable space. I'm only keeping the German and English audio-tracks in HD (if availiable) and do a backup of the full disc with all bonus features. I read about the problem in other boards and they were discussing that deleting some audio tracks can result in miscalculation of the target size. But in the case of "Deepwater Horizon" those two were the only audio-tracks availiable, so that can't be the reason for that big miscalculation BD Rebuilder did. Did someone recognize similar problems and is there a workaround for this (maybe a certain custom target size) to get the best results possible?

EDIT: Don't know if it's going to help but here's the logfile of my "Deepwater Horizon"-backup

----------------------
[04.16.17] BD Rebuilder v0.50.23
[12:28:07] Source: DEEPWATER_HORIZON
- Input BD size: 45,62 GB
- Approximate total content: [04:20:30.916]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:28:07] PHASE ONE, Encoding
- [12:28:07] Processing: VID_00005 (1 of 15)
- [12:28:07] Extracting A/V streams [VID_00005]
- [12:28:17] Reencoding video [VID_00005]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 2.193 frames
- Bitrate: 11.316 Kbs
- [12:28:17] Reencoding: VID_00005, Pass 1 of 2
- [12:28:41] Reencoding: VID_00005, Pass 2 of 2
- [12:30:27] Video Encode complete
- [12:30:27] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:30:27] Multiplexing M2TS
- [12:30:33] Processing: VID_00006 (2 of 15)
- [12:30:33] Extracting A/V streams [VID_00006]
- [12:30:46] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.373 frames
- Bitrate: 11.640 Kbs
- [12:30:46] Reencoding: VID_00006, Pass 1 of 2
- [12:31:23] Reencoding: VID_00006, Pass 2 of 2
- [12:34:12] Video Encode complete
- [12:34:12] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:34:12] Multiplexing M2TS
- [12:34:17] Processing: VID_00007 (3 of 15)
- [12:34:17] Extracting A/V streams [VID_00007]
- [12:34:29] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.332 frames
- Bitrate: 11.634 Kbs
- [12:34:29] Reencoding: VID_00007, Pass 1 of 2
- [12:35:03] Reencoding: VID_00007, Pass 2 of 2
- [12:37:54] Video Encode complete
- [12:37:54] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:37:54] Multiplexing M2TS
- [12:38:00] Processing: VID_00021 (4 of 15)
- [12:38:00] Extracting A/V streams [VID_00021]
- [12:52:40] Reencoding video [VID_00021]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 155.028 frames
- Bitrate: 4.059 Kbs
- [12:52:40] Reencoding: VID_00021, Pass 1 of 2
- [13:21:01] Reencoding: VID_00021, Pass 2 of 2
- [14:46:33] Video Encode complete
- [14:46:33] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- Track 4353 (eng): Keeping original audio
- [14:46:33] Multiplexing M2TS
- [14:51:41] Processing: VID_00101 (5 of 15)
- [14:51:41] Extracting A/V streams [VID_00101]
- [14:53:50] Reencoding video [VID_00101]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 73.335 frames
- Bitrate: 5.650 Kbs
- [14:53:50] Reencoding: VID_00101, Pass 1 of 2
- [15:05:52] Reencoding: VID_00101, Pass 2 of 2
- [15:49:51] Video Encode complete
- [15:49:52] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:49:52] Multiplexing M2TS
- [15:50:21] Processing: VID_00102 (6 of 15)
- [15:50:21] Extracting A/V streams [VID_00102]
- [15:51:05] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 26.229 frames
- Bitrate: 6.615 Kbs
- [15:51:05] Reencoding: VID_00102, Pass 1 of 2
- [15:55:28] Reencoding: VID_00102, Pass 2 of 2
- [16:12:39] Video Encode complete
- [16:12:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [16:12:39] Multiplexing M2TS
- [16:12:53] Processing: VID_00103 (7 of 15)
- [16:12:53] Extracting A/V streams [VID_00103]
- [16:13:40] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 24.797 frames
- Bitrate: 6.636 Kbs
- [16:13:40] Reencoding: VID_00103, Pass 1 of 2
- [16:17:45] Reencoding: VID_00103, Pass 2 of 2
- [16:33:31] Video Encode complete
- [16:33:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [16:33:31] Multiplexing M2TS
- [16:33:46] Processing: VID_00104 (8 of 15)
- [16:33:46] Extracting A/V streams [VID_00104]
- [16:34:52] Reencoding video [VID_00104]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 39.288 frames
- Bitrate: 5.650 Kbs
- [16:34:52] Reencoding: VID_00104, Pass 1 of 2
- [16:40:57] Reencoding: VID_00104, Pass 2 of 2
- [17:03:25] Video Encode complete
- [17:03:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:03:25] Multiplexing M2TS
- [17:03:47] Processing: VID_00105 (9 of 15)
- [17:03:47] Extracting A/V streams [VID_00105]
- [17:04:27] Reencoding video [VID_00105]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 23.385 frames
- Bitrate: 5.656 Kbs
- [17:04:27] Reencoding: VID_00105, Pass 1 of 2
- [17:07:52] Reencoding: VID_00105, Pass 2 of 2
- [17:20:36] Video Encode complete
- [17:20:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:20:37] Multiplexing M2TS
- [17:20:51] Processing: VID_00106 (10 of 15)
- [17:20:51] Extracting A/V streams [VID_00106]
- [17:21:01] Reencoding video [VID_00106]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.030 frames
- Bitrate: 5.386 Kbs
- [17:21:01] Reencoding: VID_00106, Pass 1 of 2
- [17:21:33] Reencoding: VID_00106, Pass 2 of 2
- [17:23:19] Video Encode complete
- [17:23:19] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:23:19] Multiplexing M2TS
- [17:23:24] Processing: VID_00401 (11 of 15)
- [17:23:24] Extracting A/V streams [VID_00401]
- [17:23:32] Reencoding video [VID_00401]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.204 frames
- Bitrate: 5.388 Kbs
- [17:23:32] Reencoding: VID_00401, Pass 1 of 2
- [17:23:55] Reencoding: VID_00401, Pass 2 of 2
- [17:25:03] Video Encode complete
- [17:25:03] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:25:03] Multiplexing M2TS
- [17:25:08] Processing: VID_00402 (12 of 15)
- [17:25:08] Extracting A/V streams [VID_00402]
- [17:25:17] Reencoding video [VID_00402]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 3.384 frames
- Bitrate: 5.385 Kbs
- [17:25:17] Reencoding: VID_00402, Pass 1 of 2
- [17:25:57] Reencoding: VID_00402, Pass 2 of 2
- [17:28:01] Video Encode complete
- [17:28:01] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:28:01] Multiplexing M2TS
- [17:28:07] Processing: VID_00403 (13 of 15)
- [17:28:07] Extracting A/V streams [VID_00403]
- [17:28:14] Reencoding video [VID_00403]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.162 frames
- Bitrate: 5.678 Kbs
- [17:28:14] Reencoding: VID_00403, Pass 1 of 2
- [17:28:38] Reencoding: VID_00403, Pass 2 of 2
- [17:29:49] Video Encode complete
- [17:29:49] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:29:49] Multiplexing M2TS
- [17:29:54] Processing: VID_00404 (14 of 15)
- [17:29:54] Extracting A/V streams [VID_00404]
- [17:30:02] Reencoding video [VID_00404]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.880 frames
- Bitrate: 5.387 Kbs
- [17:30:02] Reencoding: VID_00404, Pass 1 of 2
- [17:30:30] Reencoding: VID_00404, Pass 2 of 2
- [17:31:58] Video Encode complete
- [17:31:58] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:31:58] Multiplexing M2TS
- [17:32:03] Processing: VID_00405 (15 of 15)
- [17:32:03] Extracting A/V streams [VID_00405]
- [17:32:14] Reencoding video [VID_00405]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3.480 frames
- Bitrate: 6.341 Kbs
- [17:32:14] Reencoding: VID_00405, Pass 1 of 2
- [17:32:52] Reencoding: VID_00405, Pass 2 of 2
- [17:35:22] Video Encode complete
- [17:35:22] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:35:22] Multiplexing M2TS
[17:35:27]PHASE ONE complete
[17:35:27]PHASE TWO - Rebuild Started
- [17:35:27] Rebuilding BD file Structure
[17:35:37] - Encode and Rebuild complete
[17:35:37] JOB: DEEPWATER_HORIZON finished.

[jdobbs]

I haven't had any issues with sizing. But, then again, I never use the "Highest (Very Slow)" setting for encoding. I'm guessing that is the source of the sizing impact. No matter what setting you choose BD-RB will calculate a set of bitrates that is required to fill the target size. It's possible, though, that if you set a higher quality setting, the encoder might reach its maximum quality level and not output at a size that matches the specified bitrate.