BD Rebuilder Beta - Bug Reports Only - Page 1002

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

Quote:

Originally Posted by pottzman

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

Quote:

Originally Posted by Yordan5

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

Quote:

Originally Posted by worknstiff

@ 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

Quote:

Originally Posted by dfsooner

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

Quote:

Originally Posted by worknstiff

@ 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

Quote:

Originally Posted by DoctorM

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...

---

Code:

[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

----

Code:

[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

----

Code:

[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

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

Quote:

Originally Posted by Yordan5

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

Quote:

Originally Posted by emilio99

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.

16th April 2014, 14:32	#20021 \| Link
pottzman Registered User Join Date: Jun 2009 Posts: 12	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 Attached Images

17th April 2014, 14:59	#20028 \| Link
dfsooner Registered User Join Date: Nov 2009 Location: North Las Vegas, NV Posts: 112	Bd_rebuilder.ini 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.

17th April 2014, 23:10	#20033 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ 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. Last edited by worknstiff; 18th April 2014 at 12:11. Reason: Additional Info

18th April 2014, 05:07	#20035 \| Link
omegaman7 Registered User Join Date: Jan 2010 Location: USA, Oregon Posts: 791	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 __________________ Only one rooster, need be in the hen house... Last edited by omegaman7; 18th April 2014 at 05:14.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

16th April 2014, 18:47	#20023 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ 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."

17th April 2014, 00:14	#20026 \| Link
pottzman Registered User Join Date: Jun 2009 Posts: 12	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?

17th April 2014, 00:19	#20027 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ 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.

17th April 2014, 18:18	#20031 \| Link
DoctorM Registered User Join Date: Sep 2005 Posts: 561	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.

18th April 2014, 12:43	#20036 \| Link
hansolo77 Registered User Join Date: Mar 2014 Posts: 4	Thanks. I didn't notice anything on the surface, but I'll try to clean it and re-rip it.

19th April 2014, 11:20	#20037 \| Link
Yordan5 Registered User Join Date: Aug 2010 Posts: 76	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?

19th April 2014, 20:02	#20039 \| Link
emilio99 Registered User Join Date: Apr 2011 Posts: 22	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...