BD-REBUILDER backup disc does'nt start

[jangai]

My experience with BD-R : Several "Movie only" backups (1 video track and 1 audio track) with full success and satisfaction for BD9s for my PS3 and HC AV ampli ... Many thanks jdobbs ...

INTO THE WILD zone 2 is my first run for almost full backup to BD 25 target. Settings were to keep subs and audio tracks in english and french (my language) and not to convert DTS english track into AC3.
Process seemed to be OK and log seemed to be clean....
But after (as usual) burning my BD-R 25 in UDF with Toast (in Macintosh) : disc does'nt start up in PS3 and stays indefinitely running into a "dummy noname no duration track" ...
Seeing that main movie track m2ts was declared as 4.1 profile, I remuxed it with 5.1 profile in TSmuxeR 1.8.18... Same result...

Anybody seeing my fault ? Here are the infos :
Log :
-----------------------
[23:25:34] BD Rebuilder v0.20.03 (beta)
- Source: INTO_THE_WILD
- Input BD size: 42,62 GB
- Approximate total content: [03:09:57.018]
- Target BD size: 22,90 GB
[23:25:34] PHASE ONE, Encoding
- [23:25:34] Extracting audio/subs [VID_00023]
- [23:25:48] Reencoding: VID_00023 (1 of 4)
- [23:35:23] Extracting audio/subs [VID_00024]
- [23:35:34] Reencoding: VID_00024 (2 of 4)
- [23:43:20] Extracting audio/subs [VID_00025]
- [23:43:26] Reencoding: VID_00025 (3 of 4)
- [23:48:38] Extracting audio/subs [VID_00026]
- [23:59:03] Reencoding: VID_00026 (4 of 4)
[05:49:25]PHASE ONE complete
[05:49:25]PHASE TWO - Rebuild Started
- [05:49:25] Rebuilding BD file Structure
[05:49:30] - Encode and Rebuild complete
[05:49:30]JOB: INTO_THE_WILD completed.

Param list :
[Status]
LABEL=INTO_THE_WILD
VERSION=v0.20.03 (beta)
SOURCE_SIZE=45762660743
SOURCE_VIDEO_SIZE=45503213568
TARGET_SIZE=24589107200
REDUCTION=.534680039435935
RESIZE_1080=0
AUDIO_TO_KEEP=eng;enm;fra;fre;
SUBS_TO_KEEP=eng;enm;fra;fre;frm;
BACKUP_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=4
REBUILD_COMPLETE=1
[00023]
AUDIO=1
PGS=11100
M2TS_TARGET=568629912
RATE=2930
NSIZE=567238656
FLINK=0
MLINK=0
[00024]
AUDIO=1
PGS=11100
M2TS_TARGET=428117435
RATE=2781
NSIZE=427886592
FLINK=0
MLINK=0
[00025]
AUDIO=1
PGS=
M2TS_TARGET=222622906
RATE=10153
NSIZE=215863296
FLINK=0
MLINK=0
[00026]
AUDIO=1110
PGS=1110010
M2TS_TARGET=23110289772
RATE=17245
NSIZE=22553051136
FLINK=0
MLINK=0

Thanks in advance for your help...

[infiniter]

I had the same problems. Though I do not use Toast, but Nero, even if it was set to UDF 2.50 for burning, it somehow went wrong. So I used ImgBurn - and no problem anymore.

Try to test the BD25 on your PC first. If it runs on PowerDVD, then it will most probably run on the PS3. Don't know what tool to use on a Mac to play BDs.

A third idea is to check of there's a folder called CERTIFICATE on the disc. I also tried this and copied the content of the original disc to that folder on the copy, because BD-RB does not. Don't know exactly if this helps, but it won't hurt either.

[jdobbs]

BD-RB does not???? It copies everything that is in the path you specify. I have a CERTIFICATE folder on every disc I've done with BD-RB.

[jangai]

I had the same problems. Though I do not use Toast, but Nero, even if it was set to UDF 2.50 for burning, it somehow went wrong. So I used ImgBurn - and no problem anymore.
I think Toast not guilty because me and others have burned many BD25 with "BDMV input" without any problem... It is a special saled extension for Roxio Toast V9 and V10 for burning BD content... I

Try to test the BD25 on your PC first. If it runs on PowerDVD, then it will most probably run on the PS3. Don't know what tool to use on a Mac to play BDs.
I am making a new "rebuild" actually, but I haven't found a param flaw... I am afraid to produce the same problem. But, if not good, I will try a Win PowerDVD run...

I
A third idea is to check of there's a folder called CERTIFICATE on the disc. I also tried this and copied the content of the original disc to that folder on the copy, because BD-RB does not. Don't know exactly if this helps, but it won't hurt either.
I must recognize that when using BDMV burning with Toast, we never copy Certificate and Toast regenerate a "CERTICATE" file which seems never have produced difficulties...
But I will also try an ImgBurn burning from Windows and stay this thread informed... :thanks:

[jangai]

@infiniter

Your third proposal was the good one...
After attempts with Toast Mac OS and ImgBurn Windows : culprit has been at least unmasked...

When I use ImgBurn : I give the path of all BD backup folder to the program (certificate included...) and all runs fine.

When I use Toast : I point and slide only BDMV folder into Toast window and toast "regenerate" a new certificate folder... the whole problem is here !

When I copy BDMV AND CERTIFICATE folder into Toast : All runs fine with PS3...

Thanks again for your help. I am glad to have given necessary time for all these tests rather than incriminate a ghost bug with BD-REBUILDER which for me, till now, works perfectly well...
:thanks:

[nwg]

I found on my Sony S350 player that I need to omit the certificate folder and burn just the BDMV folder when using a DVD but include it on a BD.

If anyone want to burn just the BDMV, untick create audio_ts in the build options of Imgburn. It needs turning back on for when dealing with proper DVD's.

[infiniter]

If anyone want to burn just the BDMV, untick create audio_ts in the build options of Imgburn. It needs turning back on for when dealing with proper DVD's.
ImgBurn should actually not add this folder in BUILD mode when building a BD9. Are you sure you're doing it the correct way?

[GaPony]

ImgBurn should actually not add this folder in BUILD mode when building a BD9. Are you sure you're doing it the correct way?

ImgBurn will include whatever you include as your source. If you don't want the certificate folder, it should be omitted or deleted before dragging the source files over into ImgBurn. Its the same whether making a BD5, BD9, or BD25 disc.

[LIGHTNING UK!]

nwg is correct, ImgBurn will make a CERTIFICATE folder if that option is enabled and one isn't present when either a BDAV or BDMV folder exists in the root of the image it's about to build.

Piggy backing that option was obviously not very logical and so this 'feature' has its own checkbox in v2.4.3.0.

It's just a bit annoying that some devices seem to not want that folder at all, others are happy if it's present full stop (i.e. present but empty) and the rest need it to be present and have the correct (original) files in it.