View Full Version : BD Rebuilder Beta - Bug Reports Only
omegaman7
12th April 2014, 06:12
i got everything working correctly again :D no more audio out of sync issues with the mkv imports. all i did was uninstall all the programs including bd-rebuilder and started over from scratch. i believe ffdshow was the problem. i am straight now :D thanks for your help jdobbs.
I find that very interesting. Are you sure you don't have some EXTRA codec installed?
Yordan5
12th April 2014, 13:48
Just a word of warning to those like me who are using Dune 3D players - full 3D backups and movie-only backups using BDRB do not play. I suspect the firmware does not support the format without SSIF folders.
I am in the same boat. Full back up of a 3D rip with version 47.04 will not play in Dune 3D. It plays on PS3 but is heavily pixelated with:
FORCE_INMUX_3D=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
.....................................
[04/09/14] BD Rebuilder v0.47.04 (beta)
[17:52:24] Source: RESIDENT_EVIL_RETRIBUTION_3D
- Input BD size: 29.69 GB
- Approximate total content: [01:35:37.731]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[17:52:24] PHASE ONE, Encoding
- [17:52:24] Processing: VID_00000 (1 of 1)
- [17:52:24] Extracting A/V streams [VID_00000]
- [17:59:33] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 137,568 frames
- Bitrate: 28,243 Kbs
- Using FRIMEncoder for MVC encoding
- [17:59:33] Reencoding: VID_00000, Pass 1 of 1
- [18:30:23] Video Encode complete
- [18:30:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:30:23] Multiplexing M2TS
- [18:38:34] Scanning for 3D CLPI info...
[18:42:16]PHASE ONE complete
[18:42:16]PHASE TWO - Rebuild Started
- [18:42:16] Rebuilding BD-3D file Structure
[18:42:17] - Encode and Rebuild complete
[18:42:17] JOB: RESIDENT_EVIL_RETRIBUTION_3D finished.
Glarioo
12th April 2014, 15:31
I did a back-up of Jasper en Julia (English title: Justin and the Knights of Valour) 2D version. BD-RB did "Rebuilding BD-3D file Structure". The result of the back-up is 2D.
Is it possible to disable the MVC 3D output? I'll never do 3D BD's.
[04/12/14] BD Rebuilder v0.47.04 (beta)
[15:54:28] Source: JASPER_EN_JULIA_00000
- Input BD size: 20,59 GB
- Approximate total content: [01:35:54.832]
- Target BD size: 46,26 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:54:28] PHASE ONE, Encoding
- [15:54:28] Processing: VID_00017 (1 of 2)
- [15:54:28] Extracting A/V streams [VID_00017]
- [16:01:38] Reencoding video [VID_00017]
- [16:01:38] Keeping original video (no reencode)
- [16:01:38] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (nld): Keeping original audio
- Track 4354 (nld): Keeping original audio
- [16:01:39] Processing: VID_00015 (2 of 2)
- [16:01:39] Extracting A/V streams [VID_00015]
- [16:01:42] Reencoding video [VID_00015]
- [16:01:42] Keeping original video (no reencode)
[16:01:42]PHASE ONE complete
[16:01:42]PHASE TWO - Rebuild Started
- [16:01:42] Rebuilding BD-3D file Structure
[16:13:49] - Encode and Rebuild complete
[16:13:49] JOB: JASPER_EN_JULIA finished.
[Status]
LABEL=JASPER_EN_JULIA
VERSION=v0.47.04 (beta)
SOURCE_SIZE=22104889344
SOURCE_VIDEO_SIZE=22104889344
TARGET_SIZE=49666850816
REDUCTION=2.24687172340364
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
FRIMSOURCE=0
SSIF_MODE=-1
QUICK=0
ENCODE_STEP=0
COMPLETED=2
REBUILD_COMPLETE=1
[00017]
USE_ORIGINAL=1
AUDIO=111
PGS=11
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=49666767987
NSIZE=0
FLINK=0
MLINK=0
[00015]
USE_ORIGINAL=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=82829
AUDIO=
NSIZE=0
FLINK=0
MLINK=0
setarip_old
12th April 2014, 17:57
@Glarioo
Hi! I'll never do 3D BD's.Can't you simply buy (less expensive?) 2D versions?
sieve
12th April 2014, 18:58
Ripped DVDs to file using AnyDVD.
File, Import, DVD(s).
Assembled the compilation I wanted.
Did the import process, DVD source files converted to blu-ray file.
Total file size <23.5GB, no shrink needed.
Ran full backup, created .iso file.
Burned .iso file to BD.
BD has nice looking menu, all episodes play.
In all episodes, audio track runs slower than video track.
BDR works great when copying BD to BD, so BDRB.exe, FFDSHOW, Haali Matroska Splitter and AVISYNTH 2.58 should all be OK.
Files attached.
HWK
12th April 2014, 19:20
Is it possible to disable the MVC 3D output? I'll never do 3D BD's.
Put "IGNORE_3D=1" in BDREBUILDER.ini file and restart program, know it will process all 3d disc and make 2d backup. If you ever decide to do 3D again set value to 0
Another thing you can do is open program and go under setting and choose option "Process 3D video sources as 2D for backup" which basically set above flag on it's own.
Glarioo
12th April 2014, 20:10
@Glarioo
Hi! Can't you simply buy (less expensive?) 2D versions?
2D and 3D on 1 disc...
Sharc
12th April 2014, 20:19
I just noticed that this thread passed the 20'000st post today.
Congratulations and a big thanks to jdobbs for his work and continuous support of DVD-RB and BD-RB over many years!
:thanks:
Glarioo
12th April 2014, 20:32
Put "IGNORE_3D=1" in BDREBUILDER.ini file and restart program, know it will process all 3d disc and make 2d backup. If you ever decide to do 3D again set value to 0
Another thing you can do is open program and go under setting and choose option "Process 3D video sources as 2D for backup" which basically set above flag on it's own.
Thanks for your help. I've choosen the option "Process 3D video sources as 2D for backup" and it worked fine.
raul124
12th April 2014, 22:37
JDobbs: hat off to you, for this wonderful software and congrats on over 20,000 post!!
Cedvano
12th April 2014, 22:49
All encoding it's ok for me. I was lost not see two M2TS files, but it's ok.
Thank you for your great job.
It's possible to change the FRIMencode level (6 to 7)? I am a poor configuration and I would like to encode more faster.
Peter_A
13th April 2014, 14:41
It's no secret. It would be more informative if I could tell you a disc that DIDN'T do this for me.
Regardless of what disc I test, BD-RB does not deduct the stripped/core extracted audio from the calculations for disc size. It always assumes the movie's original size divided by target is the compression needed.
I can't find anything where the calculation does work properly.
Maybe it's something weird about my setup, maybe most people just aren't noticing because the calculation still includes a reduction for the stripped audio so the difference is small for most discs. Maybe no one is bothering to do the math since the numbers are reported in bytes.
The point being, assuming it's just me, I'm afraid it's probably irreproducible. No mystery.
It's not just you. I am also still finding this behavior in all of the newer versions. As we had previously discussed, it works properly in v0.45.05, on all the discs that I've tried. In every 0.46 or newer version that I've tried, BD-RB always re-encodes the video, even if the original is only slightly larger than the target size (and the HD Audio will be converted to AC3). It seems to not be accounting for the space that will be saved by converting the audio (my best way to explain it). Like you, DoctorM, I have not found 1 disc that does not exhibit this behavior. jdobbs has stated that the algorithm for calculations has not changed, but something has changed the behavior (don't know what that is).
Discs tried:
- The Artist
- The 39 Steps
- Eyes Wide Shut
- A Clockwork Orange
sieve
14th April 2014, 16:14
In all episodes, audio track runs slower than video track.
Got some advice and redid one BD.
Change made was to have "full backup" checked during import process (previously, "movie only" was checked during import and I switched to full backup when doing the actual backup).
Problem gone!
Not sure why the backup settings would matter during the input process?
Sharc
14th April 2014, 19:58
@jdobbs
I like to report back that version 0.47.04 (beta) handles this problem (http://forum.doom9.org/showpost.php?p=1676371&postcount=19935)correctly. :)
Added:
My joy was a bit too early: The problem with the bogus (35 hours) .mpls is solved, but the encoding of the menu backdrop still fails and gets replaced by the default night sky background.
Anyway a minor and exceptional case, I suppose.
jdobbs
14th April 2014, 23:41
Got some advice and redid one BD.
Change made was to have "full backup" checked during import process (previously, "movie only" was checked during import and I switched to full backup when doing the actual backup).
Problem gone!
Not sure why the backup settings would matter during the input process?
It shouldn't.
bobvig
15th April 2014, 10:39
One question remains open: it would be possible to eliminate the "jumps" during the conversion from 23,976 to 25 fps? I see that DVDFab does a better job (although not perfect): it leaves to 23,976 the fps for a NTSC standard DVD. It ensures more fluidity.
Great program, bd-rebuilder, anyway.
thanks
Ch3vr0n
15th April 2014, 12:49
it doesn't do a better job. Conversion or not PAL requires 25 or 50FPS. If it converts to PAL but leaves 23.976fps then its not a pal disc.
jdobbs
15th April 2014, 19:26
One question remains open: it would be possible to eliminate the "jumps" during the conversion from 23,976 to 25 fps? I see that DVDFab does a better job (although not perfect): it leaves to 23,976 the fps for a NTSC standard DVD. It ensures more fluidity.
Great program, bd-rebuilder, anyway.
thanks
What jumps? I'm not seeing a any? There isn't even really a change in the frame count, just a rate change (the same way the studios convert it) -- so how could there be a "jump"?
Also, as said, 23.976 isn't even legal on DVD -- the only way it can exist is with pulldown -- making it NTSC at 29.97, not PAL. That certainly isn't a "conversion of 23.976 to 25fps"????
worknstiff
15th April 2014, 22:11
--- OK, Here goes my latest puzzle with 3D & BD Rebuilder. The Hobbit Part I Disk 2 3D iso is only 29.9 gb to start with. I used BD Rebuilder 47.04 to convert it using many different custom sizes and it keeps generating low completed sizes. Most are arounfd the 21.4 to 22.0 range and it doesn't matter if you keep all the files or all the audio it still comes out small. This is considering if I force it to not encode, it comes out around 24.9 gb. This is with all the audio and all the files selected, even a weird 00038.m2ts that if you check the file size in explorer it is 3.35 gb, but in the BD Rebuider selection screen it says it's 4,430.99 MB's. When previewed this weird 1:02:23 file appears to only be a warning in many different languages and seems to be there only for padding out the file size. Even after blanking this file the NO-ENCODE completed folder is still 24.9 gb. I can live with the 22.0 file but I wonder why this disk is behaving so much different than the Part 1 Disk 1 encode that is really shorter 1:15 minutes compared to Disk 1 that is 1:33 minutes.That disk comes out at exactly 23.0 with a custom size of 24,850. I am stumped why this can happen, BD Rebuilder took an hour to compress the garbage 00038.m2ts file down to a final size of 2.07 gb of wasted space. Thanks to jdobbs for this wonderful program that keeps me up so late at night, lol.
----------------------
[04/15/14] BD Rebuilder v0.47.04 (beta)
[11:23:53] Source: HOBBIT_PT1_D2
- Input BD size: 29.89 GB
- Approximate total content: [02:27:54.865]
- Target BD size: 24.22 GB
- Windows Version: 6.1 [7601]
- Quality: High Quality (Default), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[11:23:54] PHASE ONE, Encoding
- [11:23:54] Processing: VID_00006 (1 of 3)
- [11:23:54] Extracting A/V streams [VID_00006]
- [11:30:08] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 109,252 frames
- Bitrate: 27,318 Kbs
- Using FRIMEncoder for MVC encoding
- [11:30:08] Reencoding: VID_00006, Pass 1 of 1
- [14:13:18] Video Encode complete
- [14:13:18] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (fra): Keeping original audio
- Track 4354 (spa): Keeping original audio
- Track 4355 (por): Keeping original audio
- [14:13:18] Multiplexing M2TS
- [14:23:07] Scanning for 3D CLPI info...
- [14:26:14] Processing: VID_00031 (2 of 3)
- [14:26:14] Extracting A/V streams [VID_00031]
- [14:26:22] Reencoding video [VID_00031]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 8,159 frames
- Bitrate: 7,447 Kbs
- Using FRIMEncoder for MVC encoding
- [14:26:22] Reencoding: VID_00031, Pass 1 of 1
- [14:31:35] Video Encode complete
- [14:31:35] Processing audio tracks
- [14:31:35] Multiplexing M2TS
- [14:31:41] Scanning for 3D CLPI info...
- [14:31:42] Processing: VID_00038 (3 of 3)
- [14:31:42] Extracting A/V streams [VID_00038]
- [14:32:25] Reencoding video [VID_00038]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 89,749 frames
- Bitrate: 7,447 Kbs
- Using FRIMEncoder for MVC encoding
- [14:32:25] Reencoding: VID_00038, Pass 1 of 1
- [15:31:21] Video Encode complete
- [15:31:21] Processing audio tracks
- [15:31:21] Multiplexing M2TS
- [15:31:43] Scanning for 3D CLPI info...
[15:32:05]PHASE ONE complete
[15:32:05]PHASE TWO - Rebuild Started
- [15:32:05] Converting SSIF file references
- [15:32:37] Rebuilding BD-3D file Structure
[15:32:38] - Encode and Rebuild complete
[15:32:38] JOB: HOBBIT_PT1_D2 finished.
[Status]
LABEL=HOBBIT_PT1_D2
VERSION=v0.47.04 (beta)
SOURCE_SIZE=32099473745
SOURCE_VIDEO_SIZE=31535185920
TARGET_SIZE=26004684800
REDUCTION=.806730521251355
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;spa;
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
FRIMSOURCE=0
SSIF_MODE=-1
QUICK=0
ENCODE_STEP=0
COMPLETED=3
REBUILD_COMPLETE=1
[00006]
AUDIO=1111
PGS=1111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=21351385049
RATE=27318
NSTART=27000000
NEND=232052347
NSIZE=19650514944
FLINK=0
MLINK=0
[00031]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=340753059
RATE=7447
NSTART=27000000
NEND=42313423
NSIZE=186531840
FLINK=0
MLINK=0
[00038]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=3748258867
RATE=7447
NSTART=27000000
NEND=195447654
NSIZE=2226948096
FLINK=0
MLINK=0
DoctorM
16th April 2014, 01:39
Possible vague bug/thingee/whatever that you can feel free to ignore since it's me and I'm an unreliable source...
I've been doing some weird tests, no disc in particular, but it appears if there is there is no apparent main movie (just extras or something fragmented like Red 2) and try to do a 1-pass CRF encoding, BD RB errors out (I think 00053 2810 preditandencode).
I don't know if this is just me, but if it's really there, there should be something to catch that error before it happens.
DVD-RB on one-pass mode tests for the Q value for each asset separately, does BD-RB not do the same?
pottzman
16th April 2014, 14:32
According to what I have learned if I "UNCHECK" CRF and ABR modes I should end up with 2 pass encoding but everytime I start my encode I get 1 pass ABR mode. see attached. can anyone help me with this.
Thanks in advance
Yordan5
16th April 2014, 18:35
According to what I have learned if I "UNCHECK" CRF and ABR modes I should end up with 2 pass encoding but everytime I start my encode I get 1 pass ABR mode. see attached. can anyone help me with this.
Thanks in advance
I don't think there's 2 pass encoding for 3D titles in BD-RB. It only applies to 2D titles as x264 is used there. For 3D encoding BD-RB uses FRIM encoder which as far as I know only does one pass.
worknstiff
16th April 2014, 18:47
@ Yordan5 RE: For 3D encoding BD-RB uses FRIM encoder which as far as I know only does one pass.
I think FRIM needs to do a second pass. maybe that's why I can't get BD Rebuilder to generate a decent sized encode for, " The Hobbit Disk 2."
jdobbs
16th April 2014, 21:19
I don't think there's 2 pass encoding for 3D titles in BD-RB. It only applies to 2D titles as x264 is used there. For 3D encoding BD-RB uses FRIM encoder which as far as I know only does one pass.Exactly.
jdobbs
16th April 2014, 21:20
@ Yordan5 RE: For 3D encoding BD-RB uses FRIM encoder which as far as I know only does one pass.
I think FRIM needs to do a second pass. maybe that's why I can't get BD Rebuilder to generate a decent sized encode for, " The Hobbit Disk 2."In all my testing (and I've done a lot) FRIMEncoder has been very exact in its sizing. I've already ordered "The Hobbit 3D (Desolation of Smaug)" and I expect it in the next day or two, so I'll do some testing with that one. I don't believe I have Part I in 3D, but I'll check.
pottzman
17th April 2014, 00:14
Okay thanks guys for your replies. And yes it is The Hobbit pt 1 in 3D, and yes it is my own copy. And lets just say for example that I was gay but wasn't actually ready to "come out" yet and this movie was in fact an adult movie, I wouldn't want people seeing such titles then would I. If I am to post screenshots I always blur such things, just me I guess.
Anyway thanks again for the help?
worknstiff
17th April 2014, 00:19
@ jdobbs RE: In all my testing (and I've done a lot) FRIMEncoder has been very exact in its sizing. I've already ordered "The Hobbit 3D (Desolation of Smaug)" and I expect it in the next day or two, so I'll do some testing with that one.
I have backed up, "The Desolation of Smaug 3D", and after BD Rebuilder completed the results were 22.6 for disk 1 and 23.0, for disk 2. I did have to play around with the custom size to get those results though. It will be interesting to see what you find out from your system processing them compared to mine. I like that the extras are on an extra disk and that parts 1 & 2 are on separate disks. That makes this a perfect test disk for evaluating how effectively different CPU's can use the FRIM process. Thanks again jdobbs, for all your hard work perfecting BD Rebuilder.
dfsooner
17th April 2014, 14:59
I have noticed a very annoying behavior with BDRB. Apparently BD_REBUILDER.INI gets re-written whenever a project is opened and, as a result, some of the parameters that existed before are not there afterward. So, when switching back to a previous project, the user is not really getting the same project parameters as expected.
jdobbs
17th April 2014, 15:04
I have noticed a very annoying behavior with BDRB. Apparently BD_REBUILDER.INI gets re-written whenever a project is opened and, as a result, some of the parameters that existed before are not there afterward. So, when switching back to a previous project, the user is not really getting the same project parameters as expected.I'm sorry, but that just doesn't happen. There are a few parameters that return to defaults (like audio track selections) because they have to -- but no INI values are overwritten.
jdobbs
17th April 2014, 16:19
@ jdobbs RE: In all my testing (and I've done a lot) FRIMEncoder has been very exact in its sizing. I've already ordered "The Hobbit 3D (Desolation of Smaug)" and I expect it in the next day or two, so I'll do some testing with that one.
I have backed up, "The Desolation of Smaug 3D", and after BD Rebuilder completed the results were 22.6 for disk 1 and 23.0, for disk 2. I did have to play around with the custom size to get those results though. It will be interesting to see what you find out from your system processing them compared to mine. I like that the extras are on an extra disk and that parts 1 & 2 are on separate disks. That makes this a perfect test disk for evaluating how effectively different CPU's can use the FRIM process. Thanks again jdobbs, for all your hard work perfecting BD Rebuilder. I'm not surprised by those numbers at all. You do know that a BD-25 is limited to 23.3 GB total storage, right? BD-RB aims at 22.94 GB by default. It does that purposely to account for inaccuracies in muxing overhead and encoding as well as leaving a little space in the outer surface (due to well-known weaknesses there in retaining data).
So from what I see in your response, even your worst case uses 98.5% of the targeted space and your other example actually uses more. That doesn't seem unreasonable to me.
DoctorM
17th April 2014, 18:18
Trying a rebuild on Tinker Bell and The Lost Treasure the last few days.
I have my "MIN_M2TS_SIZE=" lowered enough that the menus got re-encoded... and that broke the disc. (Black screen and dashes on the counter.)
Copying the original menu elements to the rebuilt disc fixed it.
Is this common (and the reason why the threshold is where it is) or is it something new and odd?
If the latter I will attempt to provide more detailed information so it can be reproduced.
jdobbs
17th April 2014, 18:22
Trying a rebuild on Tinker Bell and The Lost Treasure the last few days.
I have my "MIN_M2TS_SIZE=" lowered enough that the menus got re-encoded... and that broke the disc. (Black screen and dashes on the counter.)
Copying the original menu elements to the rebuilt disc fixed it.
Is this common (and the reason why the threshold is where it is) or is it something new and odd?
If the latter I will attempt to provide more detailed information so it can be reproduced.Of course it isn't common, or at least not for the other several thousand people who are using it. Saying so is insulting. The minimum size is there to save time and effort involved re-encoding things for no real benefit. Changing it serves very little (if any) purpose.
Your posts are becoming increasingly disrespectful and inflammatory -- and frankly I don't appreciate it.
worknstiff
17th April 2014, 23:10
@ jdobbs. RE: 98.5% of the targeted space and your other example actually uses more. That doesn't seem unreasonable to me.
-- Oh!, I'm not really complaining about the size so much as I am perplexed that if you use a custom size of 24,250 and the result is 22.4 and you increase the custom size to 24,750 it should increase by that amount to maybe 22.8. It doesn't, it will not increase by a slightly increased custom size at all until you increase it to around 25,000 and then the resulting disk is 24.9, which is also the original disk size with all the auxiliary audio and subs removed. There is really nothing else on this disk to remove that would make estimating the final size that difficult to do. I guess I just don't have a good understanding of how the algorithm for bitrate works and just think it should be linear in scale. Don't get me wrong, I love that it gets that close to a full disk, especially a 3D disk that was only possible to do a short time ago. Kudos for such a big leap for BD Rebuilder.
PS: Looking back at what I just wrote, I forgot to mention that "The Hobbit, Disk 2 was the one I was having a hard time with. I was getting a size of 21.8 for a requested custom size of 24,800. If you go over anything above 24,800, it arbitrary jumps up to 24.9. I am just confused why.
hansolo77
18th April 2014, 00:19
Hey all, I started an encode batch with about 5 different movies last night. Checked today, and they all all completely successfully except the X-Files (Fight the Future). I just tried to run it again, but it's still not working. It gave me no output, but the log is reporting some errors with the audio not being synchronized?
I'm not sure what all you need to help me troubleshoot, so here's the Settings Log, Rebuilder Log, and the INF...
---
[04/17/14] Checking System Settings
- BD-Rebuilder v0.47.04 (beta)
- Windows Version: 6.1 [7601]
- Working Path Free Space: 280.55GB
- 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 "libmpeg2": 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
[04/17/14] Systems Settings Check complete
----
[04/17/14] BD Rebuilder v0.47.04 (beta)
[17:02:22] Source: X_FILES1
- Input BD size: 38.80 GB
- Approximate total content: [04:31:11.672]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[17:02:23] PHASE ONE, Encoding
- [17:02:23] Processing: VID_00012 (1 of 13)
- [17:02:23] Extracting A/V streams [VID_00012]
- [17:02:27] Reencoding video [VID_00012]
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29.970fps, 30 frames
- [17:02:28] Reencoding: VID_00012, Pass 1 of 1
- [17:02:37] Video Encode complete
- [17:02:37] Processing audio tracks
- [17:02:37] Multiplexing M2TS
- [17:02:41] Processing: VID_00007 (2 of 13)
- [17:02:41] Extracting A/V streams [VID_00007]
- [17:02:49] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,776 frames
- [17:02:49] Reencoding: VID_00007, Pass 1 of 1
- [17:04:17] Video Encode complete
- [17:04:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:04:17] Multiplexing M2TS
- [17:04:23] Processing: VID_00015 (3 of 13)
- [17:04:23] Extracting A/V streams [VID_00015]
- [17:04:32] Reencoding video [VID_00015]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,088 frames
- [17:04:32] Reencoding: VID_00015, Pass 1 of 1
- [17:05:59] Video Encode complete
- [17:05:59] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:05:59] Multiplexing M2TS
- [17:06:04] Processing: VID_00008 (4 of 13)
- [17:06:04] Extracting A/V streams [VID_00008]
- [17:06:13] Reencoding video [VID_00008]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,856 frames
- [17:06:13] Reencoding: VID_00008, Pass 1 of 1
- [17:08:26] Video Encode complete
- [17:08:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:08:26] Multiplexing M2TS
- [17:08:32] Processing: VID_00009 (5 of 13)
- [17:08:32] Extracting A/V streams [VID_00009]
- [17:08:42] Reencoding video [VID_00009]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,240 frames
- [17:08:42] Reencoding: VID_00009, Pass 1 of 1
- [17:11:29] Video Encode complete
- [17:11:29] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:11:29] Multiplexing M2TS
- [17:11:36] Processing: VID_00010 (6 of 13)
- [17:11:36] Extracting A/V streams [VID_00010]
- [17:11:45] Reencoding video [VID_00010]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,336 frames
- [17:11:45] Reencoding: VID_00010, Pass 1 of 1
- [17:14:47] Video Encode complete
- [17:14:47] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:14:47] Multiplexing M2TS
- [17:14:54] Processing: VID_00014 (7 of 13)
- [17:14:54] Extracting A/V streams [VID_00014]
- [17:15:04] Reencoding video [VID_00014]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,864 frames
- [17:15:04] Reencoding: VID_00014, Pass 1 of 1
- [17:18:26] Video Encode complete
- [17:18:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:18:26] Multiplexing M2TS
- [17:18:34] Processing: VID_00002 (8 of 13)
- [17:18:34] Extracting A/V streams [VID_00002]
- Extracting video streams [VID_00002]
- Extracting secondary video [VID_00002]
- Extracting audio streams [VID_00002]
- [17:19:04] Reencoding video [VID_00002]
- [17:19:04] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,531 frames
- Bitrate: 8,206 Kbs
- [17:19:05] Reencoding: VID_00002, Pass 1 of 2
- [17:19:06] Reencoding: VID_00002, Pass 2 of 2
- [17:21:32] Video Encode complete
- [17:21:32] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4355 (eng): Keeping original audio
- Track 4356 (eng): Keeping original audio
- Track 6656 (eng): Keeping original audio
- [17:21:32] Multiplexing M2TS
- [17:21:40] Processing: VID_00004 (9 of 13)
- [17:21:40] Extracting A/V streams [VID_00004]
- [17:21:59] Reencoding video [VID_00004]
- [17:21:59] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,017 frames
- Bitrate: 9,846 Kbs
- [17:22:27] Reencoding: VID_00004, Pass 1 of 2
- [17:22:27] Reencoding: VID_00004, Pass 2 of 2
- [17:26:25] Video Encode complete
- [17:26:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4355 (eng): Keeping original audio
- Track 4356 (eng): Keeping original audio
- Track 6656 (eng): Keeping original audio
- [17:26:25] Multiplexing M2TS
- [17:26:37] Processing: VID_00011 (10 of 13)
- [17:26:37] Extracting A/V streams [VID_00011]
- [17:27:20] Reencoding video [VID_00011]
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29.970fps, 48,330 frames
- [17:27:20] Reencoding: VID_00011, Pass 1 of 1
- [17:37:26] Video Encode complete
- [17:37:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:37:26] Multiplexing M2TS
- [17:37:37] Processing: VID_00013 (11 of 13)
- [17:37:37] Extracting A/V streams [VID_00013]
- [17:39:08] Reencoding video [VID_00013]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 60,045 frames
- [17:39:08] Reencoding: VID_00013, Pass 1 of 1
- [18:32:49] Video Encode complete
- [18:32:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:32:49] Multiplexing M2TS
- [18:33:26] Processing: VID_00003 (12 of 13)
- [18:33:26] Extracting A/V streams [VID_00003]
- Extracting video streams [VID_00003]
- Extracting secondary video [VID_00003]
- Extracting audio streams [VID_00003]
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized.
Please, verify stream fps. File name: D:\X_FILES1\BDMV\STREAM\00003.m2ts
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized.
Please, verify stream fps. File name: D:\X_FILES1\BDMV\STREAM\00003.m2ts
[18:41:17] - Failed to retrieve audio, aborted
----
[Status]
LABEL=X_FILES1
VERSION=v0.47.04 (beta)
SOURCE_SIZE=41660412022
SOURCE_VIDEO_SIZE=38419587072
TARGET_SIZE=24641536000
REDUCTION=.557026055743236
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
FRIMSOURCE=0
SSIF_MODE=0
QUICK=1
ENCODE_STEP=0
COMPLETED=11
[00012]
AUDIO=
PGS=
APULLDOWN=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=13689
SPLITS=1
NSTART=27000000
NEND=27045045
NSIZE=18432
FLINK=0
MLINK=0
[00007]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=103393162
SPLITS=1
NSTART=26998605
NEND=30333330
NSIZE=113707008
FLINK=0
MLINK=0
[00015]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=120439978
SPLITS=1
NSTART=26998605
NEND=30918915
NSIZE=93548544
FLINK=0
MLINK=0
[00008]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=166467406
SPLITS=1
NSTART=26998605
NEND=32360355
NSIZE=109473792
FLINK=0
MLINK=0
[00009]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=181741435
SPLITS=1
NSTART=26999190
NEND=33081075
NSIZE=180504576
FLINK=0
MLINK=0
[00010]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=184345857
SPLITS=1
NSTART=27000000
NEND=33261255
NSIZE=225183744
FLINK=0
MLINK=0
[00014]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=215331978
SPLITS=1
NSTART=27000000
NEND=34252245
NSIZE=237391872
FLINK=0
MLINK=0
[00002]
AUDIO=100111
PGS=11111111
APULLDOWN=0
S1440=0
SPLITS=1
VIDEO2=376822.478991597
V2MBRATE=7000
M2TS_TARGET=269757585
RATE=8206
NSTART=26999955
NEND=27450450
NSIZE=255811584
FLINK=-1
MLINK=0
[00004]
AUDIO=100111
PGS=11111111
APULLDOWN=0
S1440=0
SPLITS=1
VIDEO2=14021498.9495798
V2MBRATE=7000
M2TS_TARGET=457201185
RATE=9846
NSTART=26999955
NEND=36416282
NSIZE=440469504
FLINK=-1
MLINK=0
[00011]
AUDIO=1
PGS=
APULLDOWN=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1231320079
SPLITS=1
NSTART=27000000
NEND=99567493
NSIZE=624654336
FLINK=0
MLINK=0
[00013]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2670049851
SPLITS=1
NSTART=27000000
NEND=117157565
NSIZE=2889934848
FLINK=0
MLINK=0
[00003]
AUDIO=100111
PGS=11111111
omegaman7
18th April 2014, 05:07
If I'm not mistaken, a "Buffer Overflow", can be caused by a bad rip. You may have a bad copy on your hands. While it may play on the PC fine, encoders(or other tools), may turn their nose up at it.
And for your information, small scratches don't bother good disc drives. Finger prints however, can be a nuisance. If there are finger prints on a disc, use a super soft cloth and clean it ;) But blu-ray's are pretty forgiving to most clothing I wear :D
hansolo77
18th April 2014, 12:43
Thanks. I didn't notice anything on the surface, but I'll try to clean it and re-rip it.
Yordan5
19th April 2014, 11:20
Does version 47.04 support re-encoding and outputting to ISO with SIFF folder as this seems my only option to play the results on Dune HD Base 3D?
jdobbs
19th April 2014, 13:14
Does version 47.04 support re-encoding and outputting to ISO with SIFF folder as this seems my only option to play the results on Dune HD Base 3D?Yes. But it is only available for movie-only output. You enable it by adding OUTPUT_3D_ISO=1 to the INI file.
emilio99
19th April 2014, 20:02
Thanks for improving 3D support!
Is this manual for ripping 3D in full SBS still active:
1. Mount your source ISO.
2. Select the source in BD-RB. Set BD-RB to movie-only mode
3. Make sure "Enable SBS 3D Movie-Only output" is not selected in BD-RB's SETUP dialog
4. Make sure "Process 3D Video sources as 2D for backup" isn't selected
5. Click "Backup"
Is there a way to speed up FRIM encoding? It runs with default setting and take looooooooooong...
jdobbs
19th April 2014, 20:15
Thanks for improving 3D support!
Is this manual for ripping 3D in full SBS still active:
1. Mount your source ISO.
2. Select the source in BD-RB. Set BD-RB to movie-only mode
3. Make sure "Enable SBS 3D Movie-Only output" is not selected in BD-RB's SETUP dialog
4. Make sure "Process 3D Video sources as 2D for backup" isn't selected
5. Click "Backup"
Is there a way to speed up FRIM encoding? It runs with default setting and take looooooooooong...It looks right to me.
Sorry, but FRIMEncode's speed is out of my control. On the other hand, it is by far the fastest freeware MVC encoder there is (given the fact that it is the only one :)).
If you have an Intel processor that supports Quick-Sync it is extremely fast.
raul124
19th April 2014, 21:19
Would Intel processor (i7 4770k) be faster?
Ch3vr0n
19th April 2014, 21:25
that one does support intel quicksync, so yes it would be (alot) faster
emilio99
19th April 2014, 22:15
Hmm, I don't find Information if my Intel Processor supports quicksync?
http://ark.intel.com/de/products/65732/Intel-Xeon-Processor-E3-1230-v2-8M-Cache-3_30-GHz
Here is a log from Bold 3D, i cancelt after 6 hours when it startrt encoding the next file...
[04.19.14] BD Rebuilder v0.47.04 (beta)
[17:15:15] Source: BOLT_00001
- Input BD size: 32,03 GB
- Approximate total content: [01:36:21.775]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
- Audio [2] set to default.
- Resuming from previously started job.
[17:15:19] PHASE ONE, Encoding
- [17:15:19] Processing: VID_00002 (1 of 2)
- [17:15:20] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 71.283 frames
- Bitrate: 29.994 Kbs
- Using FRIMEncoder for MVC encoding
- [17:15:20] Reencoding: VID_00002, Pass 1 of 1
- [22:47:27] Video Encode complete
- [22:47:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (deu): Reencoding audio to AC3...
- [22:52:02] Processing: VID_00003 (2 of 2)
- [22:52:02] Extracting A/V streams [VID_00003]
- [22:57:44] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 67.341 frames
- Bitrate: 29.866 Kbs
- Using FRIMEncoder for MVC encoding
- [22:57:44] Reencoding: VID_00003, Pass 1 of 1
jdobbs
19th April 2014, 22:47
Hmm, I don't find Information if my Intel Processor supports quicksync?
http://ark.intel.com/de/products/65732/Intel-Xeon-Processor-E3-1230-v2-8M-Cache-3_30-GHz
Here is a log from Bold 3D, i cancelt after 6 hours when it startrt encoding the next file...
[04.19.14] BD Rebuilder v0.47.04 (beta)
[17:15:15] Source: BOLT_00001
- Input BD size: 32,03 GB
- Approximate total content: [01:36:21.775]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
- Audio [2] set to default.
- Resuming from previously started job.
[17:15:19] PHASE ONE, Encoding
- [17:15:19] Processing: VID_00002 (1 of 2)
- [17:15:20] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 71.283 frames
- Bitrate: 29.994 Kbs
- Using FRIMEncoder for MVC encoding
- [17:15:20] Reencoding: VID_00002, Pass 1 of 1
- [22:47:27] Video Encode complete
- [22:47:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (deu): Reencoding audio to AC3...
- [22:52:02] Processing: VID_00003 (2 of 2)
- [22:52:02] Extracting A/V streams [VID_00003]
- [22:57:44] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 67.341 frames
- Bitrate: 29.866 Kbs
- Using FRIMEncoder for MVC encoding
- [22:57:44] Reencoding: VID_00003, Pass 1 of 1In order to take advantage of the Quick-Sync you'd have to first make sure the video processor is enabled, and then add FRIM_SW_DECODE=0 and/or FRIM_SW_ENCODE=0 to your INI file. Software decoding/encoding is the default.
HWK
20th April 2014, 05:04
Hmm, I don't find Information if my Intel Processor supports quicksync?
http://ark.intel.com/de/products/65732/Intel-Xeon-Processor-E3-1230-v2-8M-Cache-3_30-GHz
Here is a log from Bold 3D, i cancelt after 6 hours when it startrt encoding the next file...
[04.19.14] BD Rebuilder v0.47.04 (beta)
[17:15:15] Source: BOLT_00001
- Input BD size: 32,03 GB
- Approximate total content: [01:36:21.775]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
- Audio [2] set to default.
- Resuming from previously started job.
[17:15:19] PHASE ONE, Encoding
- [17:15:19] Processing: VID_00002 (1 of 2)
- [17:15:20] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 71.283 frames
- Bitrate: 29.994 Kbs
- Using FRIMEncoder for MVC encoding
- [17:15:20] Reencoding: VID_00002, Pass 1 of 1
- [22:47:27] Video Encode complete
- [22:47:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (deu): Reencoding audio to AC3...
- [22:52:02] Processing: VID_00003 (2 of 2)
- [22:52:02] Extracting A/V streams [VID_00003]
- [22:57:44] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 67.341 frames
- Bitrate: 29.866 Kbs
- Using FRIMEncoder for MVC encoding
- [22:57:44] Reencoding: VID_00003, Pass 1 of 1
In order to take advantage of the Quick-Sync you'd have to first make sure the video processor is enabled, and then add FRIM_SW_DECODE=0 and/or FRIM_SW_ENCODE=0 to your INI file. Software decoding/encoding is the default.
@ emilio99, jdobbs advice does not apply to you. Your processor is based on xeon and these processor are workstation based with no gpu or quicksync tech.
emilio99
20th April 2014, 09:53
Damn :( That's sound not good.... but there are so many possible speedups like CUDA or Hyper-Threading??
I actually tried a new recode with the two FRIM-Parameters but with no effect:
Speed: 0,19x ETA: 04:08:15 FPS: 4,53
Hajnal
20th April 2014, 12:19
good fast
http://thumbnails111.imagebam.com/32184/43da3e321836052.jpg (http://www.imagebam.com/image/43da3e321836052)
sparkyar
20th April 2014, 16:55
I have an i7 2600, anyone noticed quality differences between "Software" and "Quick Sync enabled" FRIMencoder? thx
jdobbs
20th April 2014, 17:31
@Hajnal
That's pretty impressive. I'm usually hanging around 10fps -- and you're using a higher quality mode than I normally do.
DMagic1
20th April 2014, 19:56
Man these 70+ fps guys are killing me. It takes me 10-12 hours for most films. I know I need an upgraded but dang.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.