View Full Version : BD Rebuilder Beta - Bug Reports Only
Limobar
3rd May 2010, 12:12
I tried to use the hidden options, by using my own 1st and 2nd pass. Unfortunately it didn't work. The default passes keep getting used. This is most probably not a bug, but my mistake.
This is what I added to the config file:
TWEAK_PASS_ONE=--preset veryslow --tune film --pass 1 --bitrate 13033 --stats --deblock -2:-2 --no-mbtree --aq-mode 0 --merange 32 --subme 9 --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --thread-input --stats --pass 1 --output NUL
TWEAK_PASS_TWO=--preset veryslow --tune film --pass 2 --bitrate 13033 --aq-mode 0 --merange 32 --subme 9 --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --thread-input --stats --pass 2 --output
Please help me by telling me what I'm doing wrong.
jdobbs
3rd May 2010, 14:19
I tried to use the hidden options, by using my own 1st and 2nd pass. Unfortunately it didn't work. The default passes keep getting used. This is most probably not a bug, but my mistake.
This is what I added to the config file:
TWEAK_PASS_ONE=--preset veryslow --tune film --pass 1 --bitrate 13033 --stats --deblock -2:-2 --no-mbtree --aq-mode 0 --merange 32 --subme 9 --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --thread-input --stats --pass 1 --output NUL
TWEAK_PASS_TWO=--preset veryslow --tune film --pass 2 --bitrate 13033 --aq-mode 0 --merange 32 --subme 9 --profile high --level 4.1 --bframes 3 --ref 4 --slices 4 --aud --nal-hrd vbr --b-pyramid strict --keyint 24 --min-keyint 2 --vbv-bufsize 30000 --vbv-maxrate 40000 --sar 1:1 --thread-input --stats --pass 2 --output
Please help me by telling me what I'm doing wrong. BD Rebuilder enforces BD compliance and therefore doesn't allow (and removes) many of the commands thay you have entered.
jdobbs
3rd May 2010, 14:26
Here's an interesting problem with Red Cliff, the movie encoded fine and failed at like 96% at file 00520 which happened to be a trailer. I replaced that file with another trailer from another Blu-ray, renamed it to 00520 and over-wrote the file, BD-Rebuilder continued fine with the encode after doing this but then it happened again on the next file 00521, another trailer and had to replace it as well for it to continue. Has this happened to anyone else with specific files not being able to encode?
[00:05:27] BD Rebuilder v0.33.06 (beta)
- Source: RED_CLIFF_THEATRICAL
- Input BD size: 45.41 GB
- Approximate total content: [05:34:41.528]
- Target BD size: 23.78 GB
- Windows Version: 6.0 [6002]
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
- Resuming from previously started job.
[00:05:35] PHASE ONE, Encoding
- [00:05:35] Reencoding: VID_00520 (10 of 13)
- [00:05:35] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,084 frames
- Bitrate: 13,621 Kbs
- [00:05:35] Reencoding: VID_00520, Pass 1 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.33.06 (beta)
- Windows Version: 6.0 [6002]
- AVISYNTH Version: 2.5.7.0, Ok
Where is the rest?
[00:06:12] - Failed video encode, aborted Are you editing out the rest of the settings report before posting? I just looked at the code -- and I see no way that only the Windows and AVISYNTH versions are reported. There should also be information provided for HAALI, FFDSHOW, the three video codecs under FFDSHOW, and a check of all the BD-RB supporting software.
JohnnyB.Good : Nope, because I always blank trailers before rebuilding. And the few AVC 23.976fps 1080p trailers I kept always worked. RED CLIFF trailer of RED CLIFF BD included.
Limobar : I think the --output flag is not a good idea. --pass 1 and 2 are useless (and filled twice), etc etc... It's tweaks there, not the command line. Optimize, remove duplicate/irrelevant flags in checking the lastcmd.txt file generated by BDRebuilder.
gwendal13
3rd May 2010, 18:01
Please don't post "it don't work", that doesn't help anyone -- post specific results, what happened and when, and the log from the encode.
I reencode a disk
The firts file before encoding
11028
The same after encoding
11029
jdobbs
3rd May 2010, 19:49
I'm doing "Star Trek, The Original Series, Season 1, Disc 7" Region 1. It looks like you're keeping HD audio, though, and I wasn't (I should have noticed that from your log). I'll try it again with that set. Just wanted to note that it worked correctly with HD Audio as well.
PurpleMan
3rd May 2010, 20:46
@jdobbs,
I've mentioned this a long time ago, but it now resurfaced. Some movies (notably Disney titles) have the main movie split across many m2ts files. Backup-wise, this isn't much of a problem as BD-RB encodes each and every one of them just fine, the only problem I experienced (in contrast to the original disc) is that I would get slight freezes during playback in positions where it transitions from one m2ts to another.
I tested this on both PowerDVD7 and PowerDVD9 (both of which played the original disc with no hiccups whatsoever, as opposed to the backup), so I figured - SOMETHING is different.
Then I read the following post today by a guy named SoniG on Pelican9's BDEdit thread:
I'm trying to rebuild some BD which contain a multiple versions main movie. These kind of BD contain movie playlists of multiple m2ts files that are played sequentially. When I try to reencode these BD, my player stutter at each m2ts transition playback. I noticed differences between original mpls/clpi files and those generated by tsmuxer or BDRebuilder. First the IN time are not the same (00:00:11.650 for the original and 00:10:00.000 for the remuxed), and the clpi ATC_delta_entries informations are removed. It normally contains the following m2ts datas. For example in the mpls you have the sequence 00001.m2ts+00002.m2ts+00003.m2ts, then in the 00001.clpi file, 00002.m2ts would be filled in the ATC entries. I'm not sure but I think this lack of informations could cause some players to have this stutter/freeze behavior, and I would like to resolve this issue in testing these settings thanks to your software.
I think he might be on to something. I can also confirm that the problem still exist on the latest version (I tested it with the movie "21", region A). Still slight freezes every time there's an m2ts transition (and with that movie, that's almost like every 2 minutes, HIGHLY annoying).
What do you think?
-PurpleMan
jdobbs
3rd May 2010, 22:01
@jdobbs,
I've mentioned this a long time ago, but it now resurfaced. Some movies (notably Disney titles) have the main movie split across many m2ts files. Backup-wise, this isn't much of a problem as BD-RB encodes each and every one of them just fine, the only problem I experienced (in contrast to the original disc) is that I would get slight freezes during playback in positions where it transitions from one m2ts to another.
I tested this on both PowerDVD7 and PowerDVD9 (both of which played the original disc with no hiccups whatsoever, as opposed to the backup), so I figured - SOMETHING is different.
Then I read the following post today by a guy named SoniG on Pelican9's BDEdit thread:
I think he might be on to something. I can also confirm that the problem still exist on the latest version (I tested it with the movie "21", region A). Still slight freezes every time there's an m2ts transition (and with that movie, that's almost like every 2 minutes, HIGHLY annoying).
What do you think?
-PurpleMan The timing difference isn't an issue, TSMUXER just uses a different offset at the start. BD Rebuilder adjusts for it. I'll check out the second ATC_Delta point raised and see what I can find out.
Interesting, though, that you'd see that -- as my players play these back without issue.
jdobbs
3rd May 2010, 22:03
3. Encoding "Sin City" gives me a pop-up that states:
BD Rebuilder experienced an error 1605 [11:26:08] ExtractAudioSubs () 0053 1605
-----------------------
[11:18:06] BD Rebuilder v0.33.06 (beta)
- Source: SIN_CITY_D1
- Input BD size: 26.87 GB
- Approximate total content: [02:04:03.685]
- Target BD size: 4.27 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[11:18:07] PHASE ONE, Encoding
- [11:18:07] Extracting A/V streams [VID_00614]
- Extracting A/V to M2TS [VID_00614]
- [11:26:08] ExtractAudioSubs() 00053 1605
- Error in attempt to extract audio/subs.
- Muxing time: 10 min 58 sec
[11:27:15] - Failed to retrieve audio, aborted
I have attempted the alternate movie only backup method (it brings up 2 in the list, both fail with the same error) to no avail, with all 3 methods giving me the same error. I've also attempted using "AUD_004 AC3, Multi-Ch, English" vs. "AUD_001 DTS-HD XLL Multi-Ch English"
Thank you so much for reading this and assisting me getting this resolved. I gave it my best effort to resolve these issues on my own, and while I hate admitting defeat, I have no choice at this point. I hope I've included all the information necessary, but please advise me of how I can be of further help, if I have not.
PS Thanks jdobbs for you continued efforts on this project. Once I have all my issues resolved, you sir, are receiving a donation from me. Thank you kindly. Just to let you know the status -- I got my copy of "Sin City" delivered today and I can confirm the issue. I'll take a look at it and hopefully will get the fix into the next release.
PurpleMan
3rd May 2010, 22:11
The timing difference isn't an issue, TSMUXER just uses a different offset at the start. BD Rebuilder adjusts for it. I'll check out the second point raised and see what I can find out.
Interesting, though, that you'd see that -- as my players play these back without issue.
I agree that the timecode is a non-issue, I myself was refering to the 2nd point.
I can conclude that some players have issue with whatever it is that's wrong, and some don't. For instance, TMT3 and PS3 play the backed-up discs just fine (even tho PDVD7, PDVD9 and other standalone players don't). But that only means that they can see past the bug and are more flexible about content playback.
Either way, if the same player doesn't have a problem with the original disc but exhibits a problem with the backed up disc we shouldn't ignore it :)
Thanks again,
-PurpleMan
Do a search for PS3BDFix. It is a small executable program that sets the copy protection bit off. I had some movies that did not work on a PS3 while others did. When I used PS3BDFix on the MT2S files, the BD movies then worked. I did BD25 full disk copies Region A.
Just to be clear, don't throw out your existing copies. Copy the rips back to your harddrive, use the PS3BDFix program and then burn back to a new disk. This worked for me!
Let me know how it works.
Moviewatcher666
I got PS3BDFIX.exe and ran it for every m2ts file and it said "0 packets modified" for every single one. So does this mean that the copy protection bit was not set on it? I am afraid to burn the output and make another coaster.
Has ANYONE gotten a full backup on BD25 of any of these movies to work on the PS3?
Surrogates
The Informant!
Star Trek (2009)
jdobbs
3rd May 2010, 22:41
I agree that the timecode is a non-issue, I myself was refering to the 2nd point.
I can conclude that some players have issue with whatever it is that's wrong, and some don't. For instance, TMT3 and PS3 play the backed-up discs just fine (even tho PDVD7, PDVD9 and other standalone players don't). But that only means that they can see past the bug and are more flexible about content playback.
Either way, if the same player doesn't have a problem with the original disc but exhibits a problem with the backed up disc we shouldn't ignore it :)
Thanks again,
-PurpleManAbsolutely. I'm reading the spec now. I'm pretty sure I'm going to have to modify the CLPI created by TSMUXER. There are a couple of other things that concern me about it and I was actually thinking about creating the CLPI myself rather than using the one from TSMUXER. If I do, I may also be able to fix the "can't use DTS Express for secondary" issue as well.
The downside would be that I would have to do a complete scan of the M2TS in order to get the necessary information to build the CLPI -- and that will add more time to the process... so I only want to do that as a last resort.
jdobbs
3rd May 2010, 22:44
I got PS3BDFIX.exe and ran it for every m2ts file and it said "0 packets modified" for every single one. So does this mean that the copy protection bit was not set on it? I am afraid to burn the output and make another coaster.
Has ANYONE gotten a full backup on BD25 of any of these movies to work on the PS3?
Surrogates
The Informant!
Star Trek (2009) You can't use a BD-RE? I'd be broke if I had to use a BD-R every time I wanted to test something.
DGenerateKane
3rd May 2010, 22:54
Just wanted to note that it worked correctly with HD Audio as well.
Bugger. No idea what it could be? Should I try reinstalling everything and trying again?
In regards to your above post, I can't use BD-RE's either, I've already wasted $30 on BD-RE's that are not compatible with my PS3.
Hi jdobbs, hi PurpleMan! You say you manage to play well these backups with TMT3. I'm surprised because with me, it stutters with all the software players. I would even say I have less important stutters with Powerdvd than TMT. Can you give me some titles that works well for you? For additional information, I think powerdvd and TMT manage really differently the BDs playback. TMT seems to really give first importance to m2ts files, while Powerdvd respect more what is written on the mpls/clpi files. I take the liberty to say that because when for example I try to blank some m2ts files (useless trailers or whatever), just in replacing the original m2ts by another 'Placebo' m2ts that is only a 2s black footage for example, TMT just play the replaced footage and continue his way, while Powerdvd (and I would say WinDVD) sometimes will play the footage, but always with the duration of the original one. So instead of playing 2s, it will playblack for let's say 1mn30, the original 1mn30 trailer, as black! Sometimes, and I'm nearly sure it's because the Video/Audio/Subtitles specs of the replaced m2ts is not the same as the original, it will just crash the software, or stop the playback with an error message. This example says a lot about the way each players, hardware players included, can manage differently BDs playback and mpls/java... behaviors. But that's true, all manage to play originals flawlessly. That's why I began to make many tests with tsmuxer without any success, and now I'm working with BDedit to test/modify mpls/clpi structures which I think is the key of the solution. And just to finish in saying that unfortunately I think more and more BD will use this structure to enhance or extend the user experience, I'm more and more stuck by this, have already about 10 BD I let in standby, old or recent movies, that even use this for other reason than multi version movies, and even some BD, that use it for nothing (Robocop)! I also read some people who have the issue with their hardware players. So it's not a software/PC isolated issue. I will continue to work on this and will inform you if I find something useful.
jdobbs
4th May 2010, 01:48
Bugger. No idea what it could be? Should I try reinstalling everything and trying again?
In regards to your above post, I can't use BD-RE's either, I've already wasted $30 on BD-RE's that are not compatible with my PS3. Yes, I would try that.
What did you use to rip it? It could be a bad rip.
Have you tried the Sony BD-RE's? You can get them at Target for about $15.
DGenerateKane
4th May 2010, 02:23
I ripped it with the current version of AnyDVD (At the time around sept-oct) but I doubt it was a ripping error. Back then I ran them through the current version of BD Rebuilder with no errors. I didn't watch them until now and found bad stutter every time it switched from the original scenes and the new remastered scenes so I ran them through BD Rebuilder again using the now current version.
I'll look into the Sony BD-RE's.
I just noticed my version of FFDSHOW is not the same as the one linked in the first post, I haven't kept up with this thread so I wasn't aware you had updated it. Hopefully that fixes the problem.
Audiophile1178
4th May 2010, 02:26
I'd like to backup "A Perfect Getaway" and it has the theatrical version, as well as, the Director's Cut. Unfortunately, Universal didn't use seamless branching but instead put two VC-1 encodes of each movie. Is there a way to do a full backup keeping the Director's Cut and delete (not include) the theatrical version? That way there would be little to no reduction in the encode. Just by deleting the theatrical version it brings the total file size down to 24 GB.
JohnnyB.Good
4th May 2010, 02:50
JohnnyB.Good : Nope, because I always blank trailers before rebuilding. And the few AVC 23.976fps 1080p trailers I kept always worked. RED CLIFF trailer of RED CLIFF BD included.
Limobar : I think the --output flag is not a good idea. --pass 1 and 2 are useless (and filled twice), etc etc... It's tweaks there, not the command line. Optimize, remove duplicate/irrelevant flags in checking the lastcmd.txt file generated by BDRebuilder.
How do you blank the trailers?
Moviewatcher666
4th May 2010, 03:34
I'll have to get it and run a test. If I can repeat it I can fix it.
Hi jdobbs,
Did you ever get a chance to test the Monsters vs Aliens and the out of sync secondary video and audio?
I have tried the last 2 updates and they are still out of sync.
Thanks!
Moviewatcher666
Hi jdobbs, got this problem
[07:32:38] BD Rebuilder v0.33.06 (beta)
- Source: RILEY_PERFECT_PET_BDROM
- Input BD size: 22.44 GB
- Approximate total content: [02:37:16.473]
- Target BD size: 7.72 GB
- Windows Version: 5.1 [2600]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[07:32:38] PHASE ONE, Encoding
- [07:32:38] Extracting A/V streams [VID_00000]
- [07:32:42] Reencoding: VID_00000 (1 of 12)
- [07:32:42] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 887 frames
- [07:32:42] Reencoding: VID_00000, Pass 1 of 1
- [07:33:25] Video Encode complete
- [07:33:25] Reencoding audio tracks (if req'd)
- [07:33:25] Multiplexing M2TS
- [07:33:26] Extracting A/V streams [VID_00003]
- [07:33:29] Reencoding: VID_00003 (2 of 12)
- [07:33:29] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,800 frames
- [07:33:29] Reencoding: VID_00003, Pass 1 of 1
- [07:37:10] Video Encode complete
- [07:37:10] Reencoding audio tracks (if req'd)
- [07:37:10] Multiplexing M2TS
- [07:37:12] Extracting A/V streams [VID_00007]
- [07:37:18] Reencoding: VID_00007 (3 of 12)
- [07:37:18] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 2,326 frames
- [07:37:18] Reencoding: VID_00007, Pass 1 of 1
- [07:40:21] Video Encode complete
- [07:40:21] Reencoding audio tracks (if req'd)
- [07:40:21] Multiplexing M2TS
- [07:40:25] Extracting A/V streams [VID_00005]
- [07:40:32] Reencoding: VID_00005 (4 of 12)
- [07:40:32] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,636 frames
- [07:40:32] Reencoding: VID_00005, Pass 1 of 1
- [07:44:06] Video Encode complete
- [07:44:06] Reencoding audio tracks (if req'd)
- [07:44:06] Multiplexing M2TS
- [07:44:09] Extracting A/V streams [VID_00001]
- [07:44:17] Reencoding: VID_00001 (5 of 12)
- [07:44:17] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 3,899 frames
- [07:44:17] Reencoding: VID_00001, Pass 1 of 1
- [07:48:24] Video Encode complete
- [07:48:24] Reencoding audio tracks (if req'd)
- [07:48:24] Multiplexing M2TS
- [07:48:28] Extracting A/V streams [VID_00006]
- [07:48:36] Reencoding: VID_00006 (6 of 12)
- [07:48:36] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,521 frames
- [07:48:36] Reencoding: VID_00006, Pass 1 of 1
- [07:51:21] Video Encode complete
- [07:51:21] Reencoding audio tracks (if req'd)
- [07:51:21] Multiplexing M2TS
- [07:51:24] Extracting A/V streams [VID_00004]
- [07:52:08] Reencoding: VID_00004 (7 of 12)
- [07:52:08] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,555 frames
- [07:52:08] Reencoding: VID_00004, Pass 1 of 1
- [07:54:46] Video Encode complete
- [07:54:46] Reencoding audio tracks (if req'd)
- [07:54:46] Multiplexing M2TS
- [07:54:48] Extracting A/V streams [VID_00009]
- [07:54:57] Reencoding: VID_00009 (8 of 12)
- [07:54:57] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,415 frames
- [07:54:57] Reencoding: VID_00009, Pass 1 of 1
- [07:58:41] Video Encode complete
- [07:58:41] Reencoding audio tracks (if req'd)
- [07:58:41] Multiplexing M2TS
- [07:58:44] Extracting A/V streams [VID_00008]
- [07:58:54] Reencoding: VID_00008 (9 of 12)
- [07:58:54] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 4,174 frames
- [07:58:54] Reencoding: VID_00008, Pass 1 of 1
- [08:03:35] Video Encode complete
- [08:03:35] Reencoding audio tracks (if req'd)
- [08:03:35] Multiplexing M2TS
- [08:03:40] Extracting A/V streams [VID_00010]
- [08:03:52] Reencoding: VID_00010 (10 of 12)
- [08:03:52] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 4,321 frames
- [08:03:52] Reencoding: VID_00010, Pass 1 of 1
- [08:08:53] Video Encode complete
- [08:08:53] Reencoding audio tracks (if req'd)
- [08:08:53] Multiplexing M2TS
- [08:09:27] Extracting A/V streams [VID_00011]
- [08:09:53] Reencoding: VID_00011 (11 of 12)
- [08:09:53] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 22,872 frames
- [08:09:53] Reencoding: VID_00011, Pass 1 of 1
- [08:41:52] Video Encode complete
- [08:41:52] Reencoding audio tracks (if req'd)
- [08:41:52] Multiplexing M2TS
- [08:43:09] Extracting A/V streams [VID_00002]
- Error in attempt to extract audio/subs.
-
[08:47:15] - Failed to retrieve audio, aborted
jdobbs
4th May 2010, 03:47
Hi jdobbs,
Did you ever get a chance to test the Monsters vs Aliens and the out of sync secondary video and audio?
I have tried the last 2 updates and they are still out of sync.
Thanks!
Moviewatcher666 No, I haven't. I actually forgot about that one. I'll have to pick up a copy so I can test it. I hope my donations pick up, I'm really running in the hole with all these discs I have to get for debugging.
Capsbackup
4th May 2010, 03:48
Absolutely. I'm reading the spec now. I'm pretty sure I'm going to have to modify the CLPI created by TSMUXER. There are a couple of other things that concern me about it and I was actually thinking about creating the CLPI myself rather than using the one from TSMUXER. If I do, I may also be able to fix the "can't use DTS Express for secondary" issue as well.
The downside would be that I would have to do a complete scan of the M2TS in order to get the necessary information to build the CLPI -- and that will add more time to the process... so I only want to do that as a last resort.
IMHO, :) this would be a welcome change, especially since the updates from tsMuxeR stopped at least one year ago and does not appear to be updated again!
You have made so many speed improvements already, I'm quite sure most people would not be disappointed in a longer time process. Besides, with my experience using DVD Rebuilder, there is no better muxing software than what you created with it! So I'm comfortable and confident with your capabilities along these lines. :cool:
Even though I am not the biggest PiP fan, I do wish that on those titles that have it and DTS Express secondary audio, that my full backups to BD-25 would have this included, being as close to the original as possible.
So I will support this completely if you decide to make this change, and will test as many titles as possible to help perfect your already excellent program!! :)
DGenerateKane
4th May 2010, 04:15
I reinstalled everything but all three discs still fail at the same spot. :( Guess I'll have to forget about them for now.
jdobbs
4th May 2010, 04:17
I reinstalled everything but all three discs still fail at the same spot. :( Guess I'll have to forget about them for now. I still say it was either a bad rip or the file has been corrupted, especially since it works on my end. I'd suggest you rerip.
cwh060
4th May 2010, 14:54
Has ANYONE gotten a full backup on BD25 of any of these movies to work on the PS3?
Surrogates
The Informant!
Star Trek (2009)
I have ripped, processed and burned all three to a 25G BDRE using AnyDVD and BD-RB and played back on my PS3 with no issues at all.
I usually run the files into MultiAVCHD, take out the commercials and trailers, then process with BD-RB. Works every time.
I have heard the latest PS3 update severly limits playback of AVCHD file structures. I have not updated my PS3 firmware.
cwh
jdobbs
4th May 2010, 15:00
I have ripped, processed and burned all three to a 25G BDRE using AnyDVD and BD-RB and played back on my PS3 with no issues at all.
I usually run the files into MultiAVCHD, take out the commercials and trailers, then process with BD-RB. Works every time.
I have heard the latest PS3 update severly limits playback of AVCHD file structures. I have not updated my PS3 firmware.
cwh Unfortunately it seems that when Sony breaks something in a new firmware release, everyone thinks it's BD Rebuilder's responsibility to somehow fix it. But I guess that's the nature of the beast, and I'll try to do what I can.
I'm too getting some weird reports during the last week, but not sure how related they are to the problem. I didn't update my PS3 (currently running FW 3.15) and never had any problems.
I'll post if I find that a PS3 user with newer FW has troubles with multiAVCHD, too.
DarWun
4th May 2010, 19:36
I haven't had any problems with AVCHD disks since upgradging my PS3's firmware to v3.30. I created a couple movie only disks over the weekend, and they played fine. I'll go back and check some older disks when I get home tonight to see if they have a problem.
Audiophile1178
4th May 2010, 21:42
jdobbs, I know you're busy but would you be able to answer my questions?
http://forum.doom9.org/showthread.php?p=1396732#post1396732
http://forum.doom9.org/showthread.php?p=1397083#post1397083
jdobbs
4th May 2010, 23:06
jdobbs, I know you're busy but would you be able to answer my questions?
http://forum.doom9.org/showthread.php?p=1396732#post1396732
http://forum.doom9.org/showthread.php?p=1397083#post1397083 1. The secondary video is encoded at a fixed CRF level (the default is 25) in order to save time. So the size isn't the driver... so in some cases it may be small, others large. The intent is to give the secondary a fixed level of quality as opposed to size. You can adjust the quality level with the SECONDARY_CRF=n hidden parameter. Making the value greater reduces secondary video quality while size gets smaller, lowering it does the opposite.
You can also add SECONDARY_USE_QUALITY=1. That will lower the size of the output -- but make the encoding slower.
2. I'll have to test that disc to see if I can repeat the audio sync problem But it has been a long time since I've seen any reports of sync problems (other than one report related to secondary audio).
3. You need to remove those files after the rip and before the encode with BD-RB. I personally only copy the BDMV and CERTIFICATE folders to hard drive when I'm backing up a disc.
As for the disc with two versions on it... a future version of BD-RB will have the ability to blank video, but that's a way down the road.
steveg32
4th May 2010, 23:45
FYI TO ALL,
AnyDVD HD latest version 6.6.4.2 has fix to AVATAR processing errors:
6.6.4.2 2010 05 04
- New (Blu-ray): Added support for new BD+ protections, e.g. "Avatar"
Just finished rip. No errors.
Audiophile1178
5th May 2010, 00:20
jdobbs, thanks for the fast reply. Sorry to have to ask twice but I felt like I was getting buried.
One other suggestion, would it be possible to change the Shutdown after REBUILD to something else like sleep or create options in the setup that'll tell it what to do? I like to sometimes login remotely to my computer and can't turn it on if it's shutdown.
Thank you again for all you great work!
I have ripped, processed and burned all three to a 25G BDRE using AnyDVD and BD-RB and played back on my PS3 with no issues at all.
I usually run the files into MultiAVCHD, take out the commercials and trailers, then process with BD-RB. Works every time.
I have heard the latest PS3 update severly limits playback of AVCHD file structures. I have not updated my PS3 firmware.
cwh
I am not using MultiAVCHD (I don't know what that is). I just do a full disc backup with everything and the original file structure (use DVDFAB usually), so I keep trailers and everything. Like I said, the weird thing about the informant was that it played the trailers fine, but not the movie (just blank screened). Movie only backups with strict AVCHD compliance checked in BD Rebuilder of these titles work fine. I am starting to suspect the problem may be DVDFAB, but I can't prove that (well I guess I could re-rip with ANYDVD, but I don't want to risk another coaster).
I'm gonna go buy a BD-RE Sony. I am tired of making BD-R coasters.
What did you rip these titles with, DVDFAB or ANYDVD? Mine did not work with the old firmware or the new firmware.
jangai
5th May 2010, 10:31
Running PS3 slim FW 3.30 since two weeks without BD-RB backups reading difficulties (Last one was Avatar).
These last days, PS3 reading persists with error "invalid disk" with an Apollo13 backup... I tried all what I could imagine without success...
BD-RB does'nt seems to see any difficulty with this backup - My computer config seems OK...
Any idea or advice welcome... :confused:
Hi jdobbs, just to say I finished testing all the possibilities to make work multi-m2ts movies with stuttering free but I had absolutely no success. A guy said it was the way TSMUXER demux/remux files that is not really compliant. He posted something to deal with these kind of BD in remuxing one of the mpls to have a one m2ts joined version, unfortunately it's more a workaround than a solution and can't be processed automatically (http://forum.doom9.org/showthread.php?t=150511). I heard you about your clpi interest and you are maybe right. I couldn't test the ATC values as nothing allow to edit it. So now I think only you or Pelican can go further about this. And I'm agree with Capsbackup about TSMUXER. Without saying it's a fantastic tool, I think this is just a good beginning and for many things it had to be improved. If you need help, someone to test things, I'm here.
jdobbs
5th May 2010, 14:50
Running PS3 slim FW 3.30 since two weeks without BD-RB backups reading difficulties (Last one was Avatar).
These last days, PS3 reading persists with error "invalid disk" with an Apollo13 backup... I tried all what I could imagine without success...
BD-RB does'nt seems to see any difficulty with this backup - My computer config seems OK...
Any idea or advice welcome... :confused: Yes. Send a nasty letter to Sony and tell them to stop screwing up the PS3's firmware (either that or tell them to fire the moron who made the changes). Or even better, buy a real player like the Sony BDP-S360 (about $100) instead of a game that pretends to be a player.
Sorry. I have nothing against the PS3 -- but it obviously is not a BD player.
jdobbs
5th May 2010, 14:54
Hi jdobbs, just to say I finished testing all the possibilities to make work multi-m2ts movies with stuttering free but I had absolutely no success. A guy said it was the way TSMUXER demux/remux files that is not really compliant. He posted something to deal with these kind of BD in remuxing one of the mpls to have a one m2ts joined version, unfortunately it's more a workaround than a solution and can't be processed automatically (http://forum.doom9.org/showthread.php?t=150511). I heard you about your clpi interest and you are maybe right. I couldn't test the ATC values as nothing allow to edit it. So now I think only you or Pelican can go further about this. And I'm agree with Capsbackup about TSMUXER. Without saying it's a fantastic tool, I think this is just a good beginning and for many things it had to be improved. If you need help, someone to test things, I'm here. I know what it is, and I'm working on it. All I really have to do is transfer some information from the original into the new CLPI and adjust the ATC_Delta based upon the new bitrate. Unfortunately the majority of players play back fine (including my two), so the issue doesn't exist for most users and has gone unnoticed. The kicker is that I'll have to "farm out" the debugging (I'm looking for volunteers) since I can't repeat it on my systems.
I'll probably have a fix in the next release. TSMUXER isn't creating a non-compliant stream -- it just doesn't know there is seamless branching involved so there isn't any timing adjustments and links added to the CLPI. I highly recommend that no one try to merge the files together as a solution. That's just silly and will cause more problems than it solves. Patience is a virtue.
When tsMuxeR creates playlists with seamlessly connected m2ts, the clpi files are properly generated, so it is not a bug in tsMuxeR. (edit: Well I must I've looked at something else - camcoder files - tsMuxeR clpi generated files do not contain the ATC for seamless connection).
Once you add the delta entries it will probably be okay. I guess that since all individually encoded m2ts files start with nal/aud and IDR frames, most players manage to quickly continue the playback without noticeable glitch or stutter - especially when using software players or BD players with lower access times to the physical media.
An important thing to mention is that the physical layout of 2 or more seamlessly connected clips (m2ts files) it also important. The maximum read-access time allowed for repositioning between the end of one and the start of the next is 706ms for single layer and 710ms for dual layer discs.
If by any chance the burning application (like ImgBurn) decides to put these clips far apart, the access time from one to another may exceed the max allowed and cause a slight stutter, too.
A simple example would be seamlessly connected AV clips 00001.m2ts 00603.m2ts 00311.m2ts 00000.m2ts. Their physical order on the media (BD-R disc) will most probably be SORTED, thus causing longer access times when doing the connection.
Even with the correct delta entries the stutter may occur if the connected clips are not properly written to / positioned in the physical layer of the disc.
If ImgBurn respects the order when project file is parsed to it, a simple test solution would be to parse CERTIFICATE and BDMV folders with their subfolders (except the BDMV\STREAM folder) and then add the m2ts files in respect to their usage in the main movie playlist and then add the rest of the m2ts files (those for extras, menus, etc).
Dean
jdobbs :My BD are in standby mode! :) I told you some other guys have the issue with their hardware players. Maybe players as I would say Powerdvd deal better to manage this, but if it's to well manage despite missing datas... When you say you can't repeat it on your systems, did you just tried to install TMT3 and test your backups with it? I don't know what you mean by 'I'll have to "farm out" the debugging (I'm looking for volunteers)', but if I can help...
deank : Interesting minds. These kind of files/playback management that cause issues are so obvious and could come from so many places. Unfortunately, from 3 frames freeze, everybody can see it!
jdobbs
5th May 2010, 17:33
jdobbs :My BD are in standby mode! :) I told you some other guys have the issue with their hardware players. Maybe players as I would say Powerdvd deal better to manage this, but if it's to well manage despite missing datas... When you say you can't repeat it on your systems, did you just tried to install TMT3 and test your backups with it? I don't know what you mean by 'I'll have to "farm out" the debugging (I'm looking for volunteers)', but if I can help...
deank : Interesting minds. These kind of files/playback management that cause issues are so obvious and could come from so many places. Unfortunately, from 3 frames freeze, everybody can see it! I don't test with software players -- they have more bugs than BD-RB does, and you'd never be able to put your finger on anything. I only test on standalone players.
By "farm out" -- I mean I'll have to ask someone who actually experiences the issue to test it for me before I release it. Since the software is "beta" I should be able to do it anyway -- but a lot of people are using as if it is a final product no matter what I say (as can be seen by some of the post referencing "coasters" or "wasted time") -- so I have to be careful with releases that change formats considerably so I don't get inundated with comments.
crl2007
5th May 2010, 17:46
What deank and SoniG are trying to say is to use eac3to as a demuxer, because tsMuxer has a bug when it comes to joining m2ts files from branched titles. It freezes on standalone players at the joining point. It continues, but it stutters where tsmuxer joins them. But if you demux with eac3to and recompile with tsmuxer it is ok. Tested.
@crl2007: No. You miss the point and that's the reason for your posts in the BDEdit thread. Neither eac3to or tsMuxeR can recreate a branched playlist.
crl2007
5th May 2010, 17:54
They can't, but demuxing with eac3to by eac3to.exe -demux movie.mpls would result a h264 stream that will not stutter in standalone players. For keeping the branched structure, you have to edit every single mpls by hand.
jdobbs
5th May 2010, 17:56
@crl2007: No. You miss the point and that's the reason for your posts in the BDEdit thread. Neither eac3to or tsMuxeR can recreate a branched playlist. Exactly. BD Rebuilder rebuilds the playlist using the original and information from the new encoding. Besides, what we're talking about here is the CLPI file...
@crl2007: It's inaccurate to call it a bug in TSMUXER... it was never designed to create seamless branched titles. That's like saying a hammer has a bug because it doesn't saw wood very well. By the way, there also isn't a bug in the way it demuxes seamless titles -- you just have to know how to use it correctly, and most people don't.
I know how the CLPI is supposed to be built, and I'll rebuild it for seamless branched & multiangled titles. Now whether that will get around any seek/latency issues based on physical location of M2TS files on the disc remains to be seen. I'm optimistic, though, especially since the majority of standalone players don't even show issues with no ATC_Delta at all...
crl2007
5th May 2010, 18:17
Yes, standalone players don't show issues if ATC Delta entries aren't present.
I've done 3 tests:
1. Only tsMuxer and in standalone stuttered at join point.
2. demuxed elementary streams with eac3to and feed them to tsmuxer, worked like a charm in standalone. ( no ATC in clpi )
3. Used ClownBD ( eac3to + tsmuxer ) and the resulted BD disc played with no stutters in standalone player. ( no ATC in clpi )
BD-RB is not a tool for re-authoring, it just does for BD's what DVD Rebuilder does for DVD's. But I tell you, those ATC entries aren't the stutter cause.
hi, jdobbs
sorry i know you're been busy
if you have time to look the problem i got
have try it again , but still have same problem
By "farm out" -- I mean I'll have to ask someone who actually experiences the issue to test it for me before I release it. You can count on me, if you care about my poor software players. By the way I don't know what bugs you are talking about, TMT3 plays my originals and manage stuffs from them perfectly well!
jdobbs
5th May 2010, 18:42
Yes, standalone players don't show issues if ATC Delta entries aren't present.
I've done 3 tests:
1. Only tsMuxer and in standalone stuttered at join point.
2. demuxed elementary streams with eac3to and feed them to tsmuxer, worked like a charm in standalone. ( no ATC in clpi )
3. Used ClownBD ( eac3to + tsmuxer ) and the resulted BD disc played with no stutters in standalone player. ( no ATC in clpi )
BD-RB is not a tool for re-authoring, it just does for BD's what DVD Rebuilder does for DVD's. But I tell you, those ATC entries aren't the stutter cause.Well, your opinion is yours. I'm absolutely certain you are wrong and I can also assure you that the problem isn't TSMUXER vs EAC3TO. But let's just leave it at that. If you follow the specs it will work (unless the player violates the spec). Right now there needs to be an adjustment to TSMUXER's seamless branching code in order to correct it to spec (for seamless branching only).
You're also making some apples to oranges comparisons that don't apply at all. What in the world does your ClownBD movie-only output have to do with this issue even in the slightest????? Hell, BD-RB's movie-only output doesn't have the issue either.
jdobbs
5th May 2010, 18:45
hi, jdobbs
sorry i know you're been busy
if you have time to look the problem i got
have try it again , but still have same problem
To everyone:
A quote from the first post of this thread:If you decide to download and test -- please post any errors you find in this thread. Don't push bug resolution or keep asking for a fix. I will get to the reported bugs, but only when I can find the time.
I work on issues at a macro level, not an individual level. I prioritize based upon importance of the issue and the number of people I think are affected. Please do not keep asking about your individual issues. I will fix all bugs -- but I will do it at the time I think is most appropriate in the grand scheme of things.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.