BD Rebuilder Beta - Bug Reports Only - Page 1019

worknstiff · 28th May 2014, 13:39

@ Diego RE: But burn a 50gb for a movie that has 27 gb it's a shame.

-- Yes it's a shame that you really don't listen to the people trying to help you. Jdobbs, Ch3vr0n, me, and others have tried to help you and you still refuse to post your BD Rebuilder logs and you're clogging up the forum with problems that no one can fix by guesswork. Machette or Machette Kills, if that's the one you're having trouble with, are both around 100 minute movie's and if you blank some previews and extras and remove some audio and down convert the HD audio that's left then maybe a 17gb movie is all you have left. Also you have reported that you had problems with two different PC's and that the resulting file freezes and you don't say what you are playing it with.

kabster · 28th May 2014, 17:12

Quote:

Originally Posted by Ch3vr0n

@kabster: that may exactly be the problem. You not supposed to use the latest versions out there! Only the ones specified in the first post. How are we and jdobbs supposed to help you if you refuse to most the required info?

Verstuurd vanaf mijn Nexus 7 met Tapatalk

Now iam baffled

!

I have post not 1 but 2 log files you have requested, i have posted the results of the checkup state in bdrb.

I know iam using the beta "test version" like most of us → if not all of us !!
Updates ussually fix/solve things

!!

btw, what version am i suppose to use ??? Since, they are all Beta versions to my knowledge !!!! sEriously?N

If you want to know more, please be specific!!
But dont you say i havent been cooperating !!

Ch3vr0n · 28th May 2014, 17:48

There's nothing to be baffled

you have posted 2 logs yes, the 1st was NOT what was requested. That was the inf file that stored the disc conversion settings NOT the conversion LOG. but the 2nd one wsa the log but did not indicate any problem. Is it that hard to do what is being asked? You were asked to go to the help, select inspect and post that result here. You didn't so we can't help you. You said "i'm using the latest versions of the helper tools", you're not supposed to use the latest versions! Those can CREATE issues! You were told what you were supposed to use, SERIOUSLY? I can't be more specific then telling you to go to WHICH menu in bdrb and click on the specific item.

until you post the result of the inspect we can't help you

worknstiff · 28th May 2014, 17:59

@ kabster RE: Now I am baffled :confused.

Hey, Now I am baffled and confused myself. I was commenting about and to Diego. NOT YOU.

kabster · 28th May 2014, 19:30

@chevron,

Not once, but twice (for the 3rd time now !!) did i mentioned that the results checked A OK . BDrb inspector gave me the green A-OK light when checking the tools !! In HOW many languages do i have post that to get it through your THICK SKULL that everything is present and in working order !!

Is it a matter of trust , WHAT ? What more can you learn from such an absurd checkup besides that everything is checked and is a-ok'd by bdrb !!?

Furthermore, i dont think i have mentioned anything about up to date tools beside the fact that i have mentioned the use of bdrb 47.06 (only beta since its in beta stage!! so what ur ranting about not using the right version anyway). But if i have, that"s because i am assuming/expect that with every new bdrb release the tools are updated too !!

mparade · 28th May 2014, 19:44

Is it possible that BD-RB is not performing inverse telecining on hard telecined sources that are marked manually as "Inverse telecine this item" in the stream window? The log says after completing one of my encodes including both hard and soft telecined streams "Inverse telecining in effect" but only by soft-telecined sources which are automatically detected. After BD-RB finishes the job and loaded the resulted m2ts into dgavcdec, the program says that the fps is still 29.976. It seems that BD-RB is not reconstructing the original 23.976 frame/s film frames by hard telecined sources which are marked manually as hard telecined according to source evaluation in dgmpgdec.

Any help would be appreciated.

Ch3vr0n · 28th May 2014, 20:28

First of all up not ranting, I'll asking for info you're refusing to give.

Quote:

Originally Posted by kabster

@chevron,

Not once, but twice (for the 3rd time now !!) did i mentioned that the results checked A OK . BDrb inspector gave me the green A-OK light when checking the tools !! In HOW many languages do i have post that to get it through your THICK SKULL that everything is present and in working order !!

And in how many languages do you need to see it to POST THOSE INSPECT RESULTS. There have been plenty of users in the past saying 'all settings were ok' when they were not.

Quote:

Is it a matter of trust , WHAT ? What more can you learn from such an absurd checkup besides that everything is checked and is a-ok'd by bdrb !!?

Yes, it's a matter of trust. We need to SEE it. Issues cannot be solved by guessing or saying "it's all ok" when it very well may not be. That's what the info you're refusing to provide is for

Quote:

Furthermore, i dont think i have mentioned anything about up to date tools beside the fact that i have mentioned the use of bdrb 47.06 (only beta since its in beta stage!! so what ur ranting about not using the right version anyway).

Oh really? how about this then

Quote:

Originally Posted by kabster

Every utility up to date (check)

That leads to believe you could potentially be using unsupported versions of the helper tools. But hey, how are we supposed to know you're not using unsupported versions and are using the correct ones if you're refusing to post the info we need to verify that.

Quote:

But if i have, that"s because i am assuming/expect that with every new bdrb release the tools are updated too !!

They're not, the only tools that often get updated are the encoders such as x264. The helper tools such as ffdshow,haali... rarely get updated

Guest · 28th May 2014, 20:44

@kabster

Stopping throwing insults or strikes will follow. Follow up to PM if you must, not here.

kabster · 28th May 2014, 22:08

@chevron

Iam gonna be very brief to the point unlike you.. no quotes = no nonsenses..

I did wrote you that bdrb checked everything A ok,
meaning ... how can i POSSIBLE END UP using the wrong tools when infact BDRB checks the revision of every tool and a-OK"d it

?

ARe you trying to say next, that iam not using the right tools even though BDRB say so ? That doesnt make any sense at all !!!

But not to waste anymore keystrokes about this nonsenses..

I just did movie only (i did chose for the Extended Edition track) and that seems to eliminate the problem ...

Atleast i hope i have helped jdobbs or others by posting my useless logs

Ch3vr0n · 28th May 2014, 22:44

oh, ffs. If you claim everything is A-OK. Then DO what is asked. How hard is it to go to help > inspect and POST THE CONTENTS so we can see it for ourselfs and KNOW it is. You can say all you want that everything is ok, until we see it for ourselfs we have nothing to go on but word. We need facts, not guesswork.

How can you possibly end up using other versions hmm. Where shall i start

1) codec packs you install before/after installing bdrb replace the recommended versions
2) video players that themselves install different versions than the recommended ones and overwrite settings causing issues

bdrb doesn't check the revision until you tell it to or it encounters an error during conversion and only then checks if everything is ok otherwise you have to do a manual check but hey. Let that just be the info your refusing to post here and the very info we NEED.

So no, you didn't help jdobbs nor others with you're "useless logs" as you still havent provided everything that is asked for. How can you expect help when you still refuse to provide the required info. The ball was and still is in your court to provide the info required.

gonca · 28th May 2014, 23:47

@Ch3vr0n
Look at kabster's history (past posts) regarding DVD_RB etc.

AmigaFuture · 29th May 2014, 05:48

Quote:

Originally Posted by gonca

@jdobbs
Do these entries from kabsters' INF look right. I'm referring to the negative signs.

That's a common misunderstanding of arguments done by basic users or users who don't "get" computer logic. "-1" is common for meaning if "1" is "Yes" then "-1" means "No". Missing the point or value of "0". It happens a lot more than you might realize.

brunchto · 29th May 2014, 11:29

Quote:

Originally Posted by brunchto

Thanks. it works fine now.

I've noticed that when making movie only film, angle selection works fine if i do a backup, but not if i do a batch backup.
in the batch info, MAIN_MPLS_ANGLE=0 instead of 3 if i 've select angle 4 of the playlist. i've changed it manually in the BDBATCH.INI and it seems to be ok after that.

Quote:

Originally Posted by jdobbs

Thanks for letting me know. I'll check it out.

ex:
after selecting angle5, and adding to batch queue:
[Batch]
MAIN_MPLS=00800.MPLS
MAIN_MPLS_ANGLE=0

mparade · 30th May 2014, 17:45

I received the following error message after inverse telecining a hard telecined 1080i source:

Code:

---------------------
[05.30.14] BD Rebuilder v0.47.06 (beta)
[08:37:36] Source:  DISTURBIA
  - Input BD size: 39,59 GB
  - Approximate total content: [02:38:15.534]
  - Target BD size: 46,26 GB
  - Windows Version: 6.1 [7601]
  - Resize: SD to HD 1080 enabled
  - Quality: Ultra High Quality (Extremely Slow), CRF
  - Output folder: E:\BD-RB\
  - Decoding/Frame serving: DirectShow
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[08:37:40] PHASE ONE, Encoding
 - [08:37:40] Blanking: VID_00011 (1 of 13)
 - [08:37:40] Blanking: VID_00068 (2 of 13)
 - [08:37:40] Blanking: VID_00009 (3 of 13)
 - [08:37:40] Blanking: VID_00066 (4 of 13)
 - [08:37:41] Processing: VID_00156 (5 of 13)
 - [08:37:41] Extracting A/V streams [VID_00156]
 - [08:37:48] Reencoding video [VID_00156]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*032 frames
 - [08:37:48] Reencoding: VID_00156, Pass 1 of 1
 - [08:40:30] Video Encode complete
 - [08:40:30] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:40:30] Multiplexing M2TS
 - [08:40:34] Processing: VID_00157 (6 of 13)
 - [08:40:34] Extracting A/V streams [VID_00157]
 - [08:40:42] Reencoding video [VID_00157]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*152 frames
 - [08:40:42] Reencoding: VID_00157, Pass 1 of 1
 - [08:43:03] Video Encode complete
 - [08:43:03] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:43:03] Multiplexing M2TS
 - [08:43:07] Processing: VID_00155 (7 of 13)
 - [08:43:07] Extracting A/V streams [VID_00155]
 - [08:43:15] Reencoding video [VID_00155]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*680 frames
 - [08:43:15] Reencoding: VID_00155, Pass 1 of 1
 - [08:47:10] Video Encode complete
 - [08:47:10] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:47:10] Multiplexing M2TS
 - [08:47:15] Processing: VID_00158 (8 of 13)
 - [08:47:15] Extracting A/V streams [VID_00158]
 - [08:47:23] Reencoding video [VID_00158]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 2*088 frames
 - [08:47:23] Reencoding: VID_00158, Pass 1 of 1
 - [08:51:30] Video Encode complete
 - [08:51:30] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:51:30] Multiplexing M2TS
 - [08:51:34] Processing: VID_00159 (9 of 13)
 - [08:51:34] Extracting A/V streams [VID_00159]
 - [08:51:43] Reencoding video [VID_00159]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 2*064 frames
 - [08:51:43] Reencoding: VID_00159, Pass 1 of 1
 - [08:57:19] Video Encode complete
 - [08:57:19] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:57:19] Multiplexing M2TS
 - [08:57:24] Processing: VID_00140 (10 of 13)
 - [08:57:24] Extracting A/V streams [VID_00140]
 - [08:57:32] Reencoding video [VID_00140]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 3*475 frames
 - [08:57:32] Reencoding: VID_00140, Pass 1 of 1
 - [09:03:44] Video Encode complete
 - [09:03:44] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [09:03:44] Multiplexing M2TS
 - [09:03:49] Processing: VID_00137 (11 of 13)
 - [09:03:49] Extracting A/V streams [VID_00137]
 - [09:04:02] Reencoding video [VID_00137]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 5*880 frames
 - [09:04:02] Reencoding: VID_00137, Pass 1 of 1
 - [09:16:31] Video Encode complete
 - [09:16:31] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [09:16:31] Multiplexing M2TS
 - [09:16:37] Processing: VID_00138 (12 of 13)
 - [09:16:37] Extracting A/V streams [VID_00138]
 - [09:17:07] Reencoding video [VID_00138]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 29,970fps, 26*714 frames
   - Inverse Telecining in effect (IVTC)
 - [09:17:08] Reencoding: VID_00138, Pass 1 of 1
 - [10:06:01] Video Encode complete
 - [10:06:01] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [10:06:01] Multiplexing M2TS
 - [10:06:01] CreateBDFiles() 00063  2004
[18:41:42]PHASE ONE aborted by user request

Any help would be appreciated.

jdobbs · 30th May 2014, 19:37

Quote:

Originally Posted by AmigaFuture

That's a common misunderstanding of arguments done by basic users or users who don't "get" computer logic. "-1" is common for meaning if "1" is "Yes" then "-1" means "No". Missing the point or value of "0". It happens a lot more than you might realize.

Anything other than 0 is a true value. In a signed integer a -1 is a value in which every bit is set to "1". It is the default when you set an integer to TRUE. The -1 shows in the INI when I write the value of the integer directly.

jdobbs · 30th May 2014, 19:44

Quote:

Originally Posted by mparade

I received the following error message after inverse telecining a hard telecined 1080i source:

Code:

---------------------
[05.30.14] BD Rebuilder v0.47.06 (beta)
[08:37:36] Source:  DISTURBIA
  - Input BD size: 39,59 GB
  - Approximate total content: [02:38:15.534]
  - Target BD size: 46,26 GB
  - Windows Version: 6.1 [7601]
  - Resize: SD to HD 1080 enabled
  - Quality: Ultra High Quality (Extremely Slow), CRF
  - Output folder: E:\BD-RB\
  - Decoding/Frame serving: DirectShow
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[08:37:40] PHASE ONE, Encoding
 - [08:37:40] Blanking: VID_00011 (1 of 13)
 - [08:37:40] Blanking: VID_00068 (2 of 13)
 - [08:37:40] Blanking: VID_00009 (3 of 13)
 - [08:37:40] Blanking: VID_00066 (4 of 13)
 - [08:37:41] Processing: VID_00156 (5 of 13)
 - [08:37:41] Extracting A/V streams [VID_00156]
 - [08:37:48] Reencoding video [VID_00156]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*032 frames
 - [08:37:48] Reencoding: VID_00156, Pass 1 of 1
 - [08:40:30] Video Encode complete
 - [08:40:30] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:40:30] Multiplexing M2TS
 - [08:40:34] Processing: VID_00157 (6 of 13)
 - [08:40:34] Extracting A/V streams [VID_00157]
 - [08:40:42] Reencoding video [VID_00157]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*152 frames
 - [08:40:42] Reencoding: VID_00157, Pass 1 of 1
 - [08:43:03] Video Encode complete
 - [08:43:03] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:43:03] Multiplexing M2TS
 - [08:43:07] Processing: VID_00155 (7 of 13)
 - [08:43:07] Extracting A/V streams [VID_00155]
 - [08:43:15] Reencoding video [VID_00155]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 1*680 frames
 - [08:43:15] Reencoding: VID_00155, Pass 1 of 1
 - [08:47:10] Video Encode complete
 - [08:47:10] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:47:10] Multiplexing M2TS
 - [08:47:15] Processing: VID_00158 (8 of 13)
 - [08:47:15] Extracting A/V streams [VID_00158]
 - [08:47:23] Reencoding video [VID_00158]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 2*088 frames
 - [08:47:23] Reencoding: VID_00158, Pass 1 of 1
 - [08:51:30] Video Encode complete
 - [08:51:30] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:51:30] Multiplexing M2TS
 - [08:51:34] Processing: VID_00159 (9 of 13)
 - [08:51:34] Extracting A/V streams [VID_00159]
 - [08:51:43] Reencoding video [VID_00159]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 2*064 frames
 - [08:51:43] Reencoding: VID_00159, Pass 1 of 1
 - [08:57:19] Video Encode complete
 - [08:57:19] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [08:57:19] Multiplexing M2TS
 - [08:57:24] Processing: VID_00140 (10 of 13)
 - [08:57:24] Extracting A/V streams [VID_00140]
 - [08:57:32] Reencoding video [VID_00140]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 3*475 frames
 - [08:57:32] Reencoding: VID_00140, Pass 1 of 1
 - [09:03:44] Video Encode complete
 - [09:03:44] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [09:03:44] Multiplexing M2TS
 - [09:03:49] Processing: VID_00137 (11 of 13)
 - [09:03:49] Extracting A/V streams [VID_00137]
 - [09:04:02] Reencoding video [VID_00137]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 23,976fps, 5*880 frames
 - [09:04:02] Reencoding: VID_00137, Pass 1 of 1
 - [09:16:31] Video Encode complete
 - [09:16:31] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [09:16:31] Multiplexing M2TS
 - [09:16:37] Processing: VID_00138 (12 of 13)
 - [09:16:37] Extracting A/V streams [VID_00138]
 - [09:17:07] Reencoding video [VID_00138]
   - Source Video: MPEG-2, 1920x1080
   - Rate/Length: 29,970fps, 26*714 frames
   - Inverse Telecining in effect (IVTC)
 - [09:17:08] Reencoding: VID_00138, Pass 1 of 1
 - [10:06:01] Video Encode complete
 - [10:06:01] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [10:06:01] Multiplexing M2TS
 - [10:06:01] CreateBDFiles() 00063  2004
[18:41:42]PHASE ONE aborted by user request

Any help would be appreciated.

Hold that thought. I'm away from my office and won't be working any bugs for a few weeks.

mrputtputt · 1st June 2014, 02:01

great s/w. been a user for a while. I have 0.47.06.

has something changed? i noticed it doesn't create the folder anymore other than the workfiles to burn. has it been made efficient that the folder we use to burn is the workfiles? this is only happening in the current version.

i don't/didn't change the settings. i usually am a simplistic user where all i change is either movie only or the entire disk, or size (usually dvd-5).

my working directory is the same (c:\temp\bd\)

worknstiff · 1st June 2014, 03:54

@ mrputtputt, RE: Has something changed? i noticed it doesn't create the folder anymore other than the workfiles to burn.

No, It's same as it ever was in my computer. It always creates a new folder in the working folder and is the same name as whatever the movies location name is.

colinhunt · 1st June 2014, 16:31

Did about a dozen movie-only 3D backups on the 0.47.06 in the past few days, running HW decode & encode, with interesting results.

I. Some titles finish without issues on the first try, while others crash FRIMEncode and have to be resumed. On "Cloudy with a chance of Meatballs 2" I had to resume the job a few times, but it finished fine eventually and the output appears to be OK:

Code:

[05.30.14] BD Rebuilder v0.47.06 (beta)
[02:25:58] Source:  CLOUDY_2_00001
  - Input BD size: 29,94 GB
  - Approximate total content: [01:34:50.684]
  - Target BD size: 23,83 GB
  - Windows Version: 6.1 [7601]
  - MOVIE-ONLY mode enabled
  - Quality: Ultra High Quality (Extremely Slow), ABR
  - Output folder: M:\_ENCODES\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[02:25:58] PHASE ONE, Encoding
 - [02:25:58] Processing: VID_00344 (1 of 3)
 - [02:25:58] Extracting A/V streams [VID_00344]
 - [02:33:24] Reencoding video [VID_00344]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 10*903 frames
   - Bitrate: 30*863 Kbs
   - Using FRIMEncoder for MVC encoding
 - [02:33:24] Reencoding: VID_00344, Pass 1 of 1
 - [02:36:25] Video Encode complete
 - [02:36:25] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
   - Track 4355 (eng): Keeping original audio
 - [02:36:25] Processing: VID_00345 (2 of 3)
 - [02:36:25] Extracting A/V streams [VID_00345]
 - [02:36:31] Reencoding video [VID_00345]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 425 frames
   - Bitrate: 28*308 Kbs
   - Using FRIMEncoder for MVC encoding
 - [02:36:31] Reencoding: VID_00345, Pass 1 of 1
[12:26:00] - Failed video encode, aborted
----------------------
[05.30.14] BD Rebuilder v0.47.06 (beta)
[12:27:04] Source:  CLOUDY_2_00001
  - Input BD size: 29,94 GB
  - Approximate total content: [01:34:50.684]
  - Target BD size: 23,83 GB
  - Windows Version: 6.1 [7601]
  - MOVIE-ONLY mode enabled
  - Quality: Ultra High Quality (Extremely Slow), ABR
  - Output folder: M:\_ENCODES\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[12:27:05] PHASE ONE, Encoding
 - [12:27:05] Processing: VID_00345 (2 of 3)
 - [12:27:05] Reencoding video [VID_00345]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 425 frames
   - Bitrate: 28*308 Kbs
   - Using FRIMEncoder for MVC encoding
 - [12:27:05] Reencoding: VID_00345, Pass 1 of 1
 - [12:27:13] Video Encode complete
 - [12:27:13] Processing: VID_00346 (3 of 3)
 - [12:27:13] Extracting A/V streams [VID_00346]
 - [12:36:02] Reencoding video [VID_00346]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 125*112 frames
   - Bitrate: 30*086 Kbs
   - Using FRIMEncoder for MVC encoding
 - [12:36:02] Reencoding: VID_00346, Pass 1 of 1
[12:42:09] - Failed video encode, aborted
----------------------
[05.30.14] BD Rebuilder v0.47.06 (beta)
[12:42:12] Source:  CLOUDY_2_00001
  - Input BD size: 29,94 GB
  - Approximate total content: [01:34:50.684]
  - Target BD size: 23,83 GB
  - Windows Version: 6.1 [7601]
  - MOVIE-ONLY mode enabled
  - Quality: Ultra High Quality (Extremely Slow), ABR
  - Output folder: M:\_ENCODES\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[12:42:13] PHASE ONE, Encoding
 - [12:42:13] Processing: VID_00346 (3 of 3)
 - [12:42:13] Reencoding video [VID_00346]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 125*112 frames
   - Bitrate: 30*086 Kbs
   - Using FRIMEncoder for MVC encoding
 - [12:42:13] Reencoding: VID_00346, Pass 1 of 1
 - [13:15:12] Video Encode complete
[13:15:12]PHASE ONE complete
[13:15:12]PHASE TWO - Rebuild Started
 - [13:15:12] Rebuilding BD-3D file Structure
[14:07:39] - Encode and Rebuild complete
[14:07:39] JOB: CLOUDY_2 finished.

II. Another peculiar thing is that if the WORKFILES directory is not empty, BD-RB pops up an error message about not being able to retrieve audio:

[05.30.14] BD Rebuilder v0.47.06 (beta)
[14:11:39] Source: THROUGH_THE_NEVER_3D_00020
- Input BD size: 33,84 GB
- Approximate total content: [01:32:45.643]
- Target BD size: 23,83 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Ultra High Quality (Extremely Slow), ABR
- Output folder: M:\_ENCODES\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:11:41] PHASE ONE, Encoding
- [14:11:41] Processing: VID_00000 (1 of 2)
- [14:11:41] Extracting A/V streams [VID_00000]
- [14:11:41] ExtractAudioSubs() 00055 1601
[14:11:44] - Failed to retrieve audio, aborted

But since BD-RB deletes workfiles during this attempt I only need to restart the job, and the error message is not displayed again.

III. Then there was a title called "Out of Inferno" which, no matter how many times I tried, did this (failed mux, can't open file):

Code:

[05.30.14] BD Rebuilder v0.47.06 (beta)
[23:34:25] Source:  OUT_OF_INFERNO_3D_00001
  - Input BD size: 27,36 GB
  - Approximate total content: [01:47:19.516]
  - Target BD size: 23,83 GB
  - Windows Version: 6.1 [7601]
  - MOVIE-ONLY mode enabled
  - Quality: Ultra High Quality (Extremely Slow), ABR
  - Output folder: M:\_ENCODES\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
  - Subtitle [3] is defaulted ON.
[23:34:28] PHASE ONE, Encoding
 - [23:34:28] Processing: VID_00000 (1 of 1)
 - [23:34:28] Extracting A/V streams [VID_00000]
 - [23:34:28] ExtractAudioSubs() 00055  1601
[23:34:30] - Failed to retrieve audio, aborted
----------------------
[05.30.14] BD Rebuilder v0.47.06 (beta)
[23:34:35] Source:  OUT_OF_INFERNO_3D_00001
  - Input BD size: 27,36 GB
  - Approximate total content: [01:47:19.516]
  - Target BD size: 23,83 GB
  - Windows Version: 6.1 [7601]
  - MOVIE-ONLY mode enabled
  - Quality: Ultra High Quality (Extremely Slow), ABR
  - Output folder: M:\_ENCODES\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
  - Subtitle [3] is defaulted ON.
[23:34:35] PHASE ONE, Encoding
 - [23:34:35] Processing: VID_00000 (1 of 1)
 - [23:34:35] Extracting A/V streams [VID_00000]
 - [23:42:10] Reencoding video [VID_00000]
 - [23:42:10] Keeping original video (no reencode)
 - [23:42:10] Processing audio tracks
   - Track 4352 (zho): Keeping original audio
[23:42:10]PHASE ONE complete
[23:42:10]PHASE TWO - Rebuild Started
 - [23:42:10] Rebuilding BD-3D file Structure
 - Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
 - Can't open file: F:\_BDRB_OUTPUT\WORKFILES\00001.track_4114.mvc
[23:42:14] - Failed to REBUILD

Another donation made, btw.

Addendum: Universal Soldier 3D kept on crashing FRIMEncoder repeatedly, so I installed the latest HD4000 beta drivers from Intel. Rebooted and ran BD-RB using the exact same settings as before. This time encoding fps climbed quickly from 25 to 60, then began coming down slowly. After approx. 20 minutes encoding runs at 18fps only. But at least FRIMEncoder hasn't crashed.

Update: Found even newer drivers (v3621) which Intel claims are for NUC but they work with all compatible CPUs. Installed those and BD-RB finished a movie-only backup of Universal Soldier 3D a moment ago without a single FRIMEncoder crash.

Success might not be solely due to the new drivers, because I remembered I had earlier taken libmfxhw32.dll and libmfxhw64.dll from driver v3496 and copied them to BD-RB's Tools directory as well as a directory on Win7 PATH. I deleted those dlls before running this encoding job. Not sure where FRIMEncoder looks for the HW dll since there's only the SW dll in BD-RB's Tools directory originally.

colinhunt · 1st June 2014, 21:01

Through empirical testing I have now reached the conclusion that FRIMEncode runs well, without crashing, only the first encode after rebooting. Something isn't flushed or reset properly at the end of an encoding job, it seems.

Aww hell... that trick worked great for a total of 3 encodes, then FE started crashing after reboot, too.

28th May 2014, 13:39	#20361 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ Diego RE: But burn a 50gb for a movie that has 27 gb it's a shame. -- Yes it's a shame that you really don't listen to the people trying to help you. Jdobbs, Ch3vr0n, me, and others have tried to help you and you still refuse to post your BD Rebuilder logs and you're clogging up the forum with problems that no one can fix by guesswork. Machette or Machette Kills, if that's the one you're having trouble with, are both around 100 minute movie's and if you blank some previews and extras and remove some audio and down convert the HD audio that's left then maybe a 17gb movie is all you have left. Also you have reported that you had problems with two different PC's and that the resulting file freezes and you don't say what you are playing it with. Last edited by worknstiff; 28th May 2014 at 15:17. Reason: 4

28th May 2014, 17:48	#20363 \| Link
Ch3vr0n Registered User Join Date: Jan 2009 Posts: 1,368	There's nothing to be baffled you have posted 2 logs yes, the 1st was NOT what was requested. That was the inf file that stored the disc conversion settings NOT the conversion LOG. but the 2nd one wsa the log but did not indicate any problem. Is it that hard to do what is being asked? You were asked to go to the help, select inspect and post that result here. You didn't so we can't help you. You said "i'm using the latest versions of the helper tools", you're not supposed to use the latest versions! Those can CREATE issues! You were told what you were supposed to use, SERIOUSLY? I can't be more specific then telling you to go to WHICH menu in bdrb and click on the specific item. until you post the result of the inspect we can't help you Last edited by Ch3vr0n; 28th May 2014 at 17:56.

28th May 2014, 19:30	#20365 \| Link
kabster Registered User Join Date: Jun 2007 Posts: 80	@chevron, Not once, but twice (for the 3rd time now !!) did i mentioned that the results checked A OK . BDrb inspector gave me the green A-OK light when checking the tools !! In HOW many languages do i have post that to get it through your THICK SKULL that everything is present and in working order !! Is it a matter of trust , WHAT ? What more can you learn from such an absurd checkup besides that everything is checked and is a-ok'd by bdrb !!? Furthermore, i dont think i have mentioned anything about up to date tools beside the fact that i have mentioned the use of bdrb 47.06 (only beta since its in beta stage!! so what ur ranting about not using the right version anyway). But if i have, that"s because i am assuming/expect that with every new bdrb release the tools are updated too !! Last edited by Guest; 28th May 2014 at 20:42. Reason: 13

28th May 2014, 19:44	#20366 \| Link
mparade Registered User Join Date: Nov 2013 Posts: 577	Inverse telecine hard telecined sources Is it possible that BD-RB is not performing inverse telecining on hard telecined sources that are marked manually as "Inverse telecine this item" in the stream window? The log says after completing one of my encodes including both hard and soft telecined streams "Inverse telecining in effect" but only by soft-telecined sources which are automatically detected. After BD-RB finishes the job and loaded the resulted m2ts into dgavcdec, the program says that the fps is still 29.976. It seems that BD-RB is not reconstructing the original 23.976 frame/s film frames by hard telecined sources which are marked manually as hard telecined according to source evaluation in dgmpgdec. Any help would be appreciated.

1st June 2014, 21:01	#20380 \| Link
colinhunt Registered User Join Date: Dec 2002 Posts: 1,022	Through empirical testing I have now reached the conclusion that FRIMEncode runs well, without crashing, only the first encode after rebooting. Something isn't flushed or reset properly at the end of an encoding job, it seems. Aww hell... that trick worked great for a total of 3 encodes, then FE started crashing after reboot, too. Last edited by colinhunt; 2nd June 2014 at 00:49.

28th May 2014, 17:59	#20364 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ kabster RE: Now I am baffled :confused. Hey, Now I am baffled and confused myself. I was commenting about and to Diego. NOT YOU.

28th May 2014, 20:44	#20368 \| Link
Guest Guest Join Date: Jan 2002 Posts: 21,901	@kabster Stopping throwing insults or strikes will follow. Follow up to PM if you must, not here.

28th May 2014, 22:08	#20369 \| Link
kabster Registered User Join Date: Jun 2007 Posts: 80	@chevron Iam gonna be very brief to the point unlike you.. no quotes = no nonsenses.. I did wrote you that bdrb checked everything A ok, meaning ... how can i POSSIBLE END UP using the wrong tools when infact BDRB checks the revision of every tool and a-OK"d it ? ARe you trying to say next, that iam not using the right tools even though BDRB say so ? That doesnt make any sense at all !!! But not to waste anymore keystrokes about this nonsenses.. I just did movie only (i did chose for the Extended Edition track) and that seems to eliminate the problem ... Atleast i hope i have helped jdobbs or others by posting my useless logs

28th May 2014, 22:44	#20370 \| Link
Ch3vr0n Registered User Join Date: Jan 2009 Posts: 1,368	oh, ffs. If you claim everything is A-OK. Then DO what is asked. How hard is it to go to help > inspect and POST THE CONTENTS so we can see it for ourselfs and KNOW it is. You can say all you want that everything is ok, until we see it for ourselfs we have nothing to go on but word. We need facts, not guesswork. How can you possibly end up using other versions hmm. Where shall i start 1) codec packs you install before/after installing bdrb replace the recommended versions 2) video players that themselves install different versions than the recommended ones and overwrite settings causing issues bdrb doesn't check the revision until you tell it to or it encounters an error during conversion and only then checks if everything is ok otherwise you have to do a manual check but hey. Let that just be the info your refusing to post here and the very info we NEED. So no, you didn't help jdobbs nor others with you're "useless logs" as you still havent provided everything that is asked for. How can you expect help when you still refuse to provide the required info. The ball was and still is in your court to provide the info required.

28th May 2014, 23:47	#20371 \| Link
gonca Registered User Join Date: Jul 2012 Posts: 1,213	@Ch3vr0n Look at kabster's history (past posts) regarding DVD_RB etc.

1st June 2014, 02:01	#20377 \| Link
mrputtputt Registered User Join Date: Jan 2011 Posts: 1	great s/w. been a user for a while. I have 0.47.06. has something changed? i noticed it doesn't create the folder anymore other than the workfiles to burn. has it been made efficient that the folder we use to burn is the workfiles? this is only happening in the current version. i don't/didn't change the settings. i usually am a simplistic user where all i change is either movie only or the entire disk, or size (usually dvd-5). my working directory is the same (c:\temp\bd\)

1st June 2014, 03:54	#20378 \| Link
worknstiff Registered User Join Date: Jun 2009 Posts: 314	@ mrputtputt, RE: Has something changed? i noticed it doesn't create the folder anymore other than the workfiles to burn. No, It's same as it ever was in my computer. It always creates a new folder in the working folder and is the same name as whatever the movies location name is.

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