BD Rebuilder Beta - Bug Reports Only

[datman]

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine

for what it's worth I converted a BDRB file dated 1-20-09 to ISO tonight and it will mount and play.

I have had the "Stricter AVCHD compliance for movie-only" checked since about this time

[jdobbs]

what should it be, I checked and it is set =3
That's correct for the "High Quality" setting. That variable is set by the selection on the ENCODER SETTINGS menu. But I added a couple of "hidden" settings for testing (mainly to speed things up). I accidentally left one set in the INI I sent out in the v0.18.8 ZIP file.

[dmancornell]

2nd update on my above post. the stuttering was a problem with powerdvd, so the image is fine.

trying again now with tsmuxer 1.8.8 beta

[hlonipha]

I have Nero 9 or Img burn. could someone post a step by step on how to burn to a dvd5 please ?


Thanks

Hlonipha

[klas]

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine

May be necessary to update the PowerDVD 8. I've done tests with Amadeus and the target=8150 and every
thing ok.

[mmace]

I gotta' tell you. If I had to wait 12 days for an encode, I'd probably just buy an extra copy of every movie... more likely though, I'd buy a new computer. You must get tired just from shoveling coal into the rear of that one. ;)Ha ha, I know what you mean, I will have a nice new i7 by the end of the month. I didn't even need the shrink I was doing, I was just testing the software and was determined for it to work!

[DIVX2009]

JDOBBS...I HAVE THIS ERROR:

[07:36:49] BD Rebuilder v0.18.8 (beta)
- Source: HI-DEFINITION REFERENCE DISC 2008 BLU-RAY 1080I AVC LPCM7.1
- Input BD size: 16.56 GB
- Approximate total content: [00:57:38.955]
- Target BD size: 4.27 GB
[07:36:50] PHASE ONE, Encoding
- [07:36:53] Reencoding: VID_00000 (1 of 64)
- [07:39:36] Reencoding: VID_00001 (2 of 64)
- [07:40:13] Reencoding: VID_00002 (3 of 64)
- [07:44:28] Reencoding: VID_00003 (4 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:44:41] Reencoding: VID_00004 (5 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:44:52] Reencoding: VID_00005 (6 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:45:10] Reencoding: VID_00006 (7 of 64)
- [07:46:52] Reencoding: VID_00007 (8 of 64)
- [07:50:38] Reencoding: VID_00008 (9 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:52:15] Reencoding: VID_00009 (10 of 64)
- [07:56:29] Reencoding: VID_00010 (11 of 64)
- [07:59:54] Reencoding: VID_00011 (12 of 64)
- [08:05:57] Reencoding: VID_00012 (13 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:06:41] Reencoding: VID_00013 (14 of 64)
- [08:11:04] Reencoding: VID_00014 (15 of 64)
- [08:15:05] Reencoding: VID_00015 (16 of 64)
- [08:19:33] Reencoding: VID_00016 (17 of 64)
- [08:25:43] Reencoding: VID_00017 (18 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:26:02] Reencoding: VID_00018 (19 of 64)
- [08:27:17] Reencoding: VID_00019 (20 of 64)
- [08:38:06] Reencoding: VID_00020 (21 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:38:49] Reencoding: VID_00021 (22 of 64)
- [08:47:10] Reencoding: VID_00022 (23 of 64)
- [08:53:10] Reencoding: VID_00023 (24 of 64)
- [08:57:26] Reencoding: VID_00024 (25 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [10:28:38] Reencoding: VID_00025 (26 of 64)
- [10:29:52] Reencoding: VID_00026 (27 of 64)
- [10:37:26] Reencoding: VID_00027 (28 of 64)
- [10:43:22] Reencoding: VID_00028 (29 of 64)
- [10:50:24] Reencoding: VID_00029 (30 of 64)
- [10:55:23] Reencoding: VID_00030 (31 of 64)
- [11:03:09] Reencoding: VID_00031 (32 of 64)
- [11:05:01] Reencoding: VID_00032 (33 of 64)
- [11:06:13] Reencoding: VID_00033 (34 of 64)
- [11:11:41] Reencoding: VID_00034 (35 of 64)
- [11:17:48] Reencoding: VID_00035 (36 of 64)
- [11:21:48] Reencoding: VID_00036 (37 of 64)
- [11:29:45] Reencoding: VID_00037 (38 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [11:30:26] Reencoding: VID_00038 (39 of 64)
- [11:34:26] Reencoding: VID_00039 (40 of 64)
- [11:41:23] Reencoding: VID_00040 (41 of 64)
- [11:43:23] Reencoding: VID_00041 (42 of 64)
- [11:48:09] Reencoding: VID_00042 (43 of 64)
- [11:50:41] Reencoding: VID_00043 (44 of 64)
- [11:54:29] Reencoding: VID_00044 (45 of 64)
- [12:01:26] Reencoding: VID_00045 (46 of 64)
- [12:05:30] Reencoding: VID_00046 (47 of 64)
- [12:12:38] Reencoding: VID_00047 (48 of 64)
- [12:15:43] Reencoding: VID_00048 (49 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [12:16:37] Reencoding: VID_00049 (50 of 64)
- [12:22:27] Reencoding: VID_00050 (51 of 64)
- [12:24:34] Reencoding: VID_00051 (52 of 64)
- [12:32:42] Reencoding: VID_00052 (53 of 64)
- [12:40:51] Reencoding: VID_00053 (54 of 64)
- Reached retry limit. Aborting.
- [12:41:50] Reencoding: VID_00054 (55 of 64)
- [12:43:22] Reencoding: VID_00055 (56 of 64)
- [12:45:36] Reencoding: VID_00056 (57 of 64)
- [12:49:03] Reencoding: VID_00057 (58 of 64)
- [12:53:35] Reencoding: VID_00058 (59 of 64)
- Reached retry limit. Aborting.
- [12:57:43] Reencoding: VID_00059 (60 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [13:07:27] Reencoding: VID_00060 (61 of 64)
- [13:10:27] Reencoding: VID_00061 (62 of 64)
- Reached retry limit. Aborting.
- [13:12:46] Reencoding: VID_00062 (63 of 64)
- [13:13:39] Reencoding: VID_00063 (64 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
[13:14:02]PHASE ONE complete
[13:14:02]PHASE TWO - Rebuild Started
- [13:14:02] Rebuilding BD file Structure
- [13:14:09] CorrectMPLS() 00009 5
[13:14:11] - Aborted at user request

???

[jdobbs]

The 21 times that you got "Reached retry limit. Aborting" is not a good sign... that means that each of those sections of the disc did not finish encoding. That would logically create a problem in the rebuild.

Something is causing X264 to fail in encoding those segments. I would suggest you step back to the previous version of X264.

[jdobbs]

Ok I copied the last command into a command prompt to execute it and came up with this..

C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>x264.exe "E:\
BLU-RAY WORKING\WORKFILES\VID_00123.AVS" --bitrate 4651 --level 4.1 --sar 1:1 --
aud --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --vbv-maxrate 17500 --filter
0,0 --subme 2 --me hex --bframes 3 --8x8dct --direct auto --weightb --trellis 0
--analyse none --threads auto --thread-input --progress --no-psnr --no-ssim --st
ats "E:\BLU-RAY WORKING\WORKFILES\VID_00123.AVS.264.stats" --pass 1 --output NUL

avis [info]: 1920x1080 @ 23.98 fps (8409 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile High, level 4.1
[0.1%] 8/8409 frames, 28.17 fps, 0.00 kb/s, eta 0:04:58
C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>

Hope that helps..... When it crashes, can you select the "more info" (or whatever it says) button on the popup and see where it says it happened? That way we can see if it was in the encoder or possibly the CODEC.

Interestingly I have done a number of encodes with this version of X264 and haven't had a crash yet. Is there anything unique about your setup, codecs, configuration?

What worries me is that the issue seems to go away by stepping back to X264 r1082... but all I have are reports, no personal experiences -- I guess I'll just change back in the next release, but I was hoping more info would come in that we could pass over to the X264 developers. I hate to lose all those speed improvements that have been implemented.

[jdobbs]

Just as a test, could one of the folks who is experiencing "crashes" with X264, please download this version (http://www.jdobbs.net/freeware/x264.exe) (r1112) and see if (by some chance) the issue has resolved itself?

A quick response would be appreciated. I'd like to put out a new BD-RB release. Thanks.

[tekmobile]

Is there any hidden settings that will allow a previously processed disc to just be rebuilt without having to re-encode the entire disc.

Many Thanks
keep up the good work

[Fishman0919]

Just as a test, could one of the folks who is experiencing "crashes" with X264, please download this version (http://www.jdobbs.net/freeware/x264.exe) (r1112) and see if (by some chance) the issue has resolved itself?

A quick response would be appreciated. I'd like to put out a new BD-RB release. Thanks.

I was having an issue with "Tropic Thunder". Solved the crashing for me.

[jdobbs]

Is there any hidden settings that will allow a previously processed disc to just be rebuilt without having to re-encode the entire disc.

Many Thanks
keep up the good work It will do it automatically unless you have changed settings that require a reencode.

[jdobbs]

I was having an issue with "Tropic Thunder". Solved the crashing for me.Great news. Thanks.

Anyone else?

[bowie]

yes, seems to work now.

[MR.WaynesWorld]

When it crashes, can you select the "more info" (or whatever it says) button on the popup and see where it says it happened? That way we can see if it was in the encoder or possibly the CODEC.

Interestingly I have done a number of encodes with this version of X264 and haven't had a crash yet. Is there anything unique about your setup, codecs, configuration?

What worries me is that the issue seems to go away by stepping back to X264 r1082... but all I have are reports, no personal experiences -- I guess I'll just change back in the next release, but I was hoping more info would come in that we could pass over to the X264 developers. I hate to lose all those speed improvements that have been implemented.

I'll try this tonight when I get home from work and let you know...

[MR.WaynesWorld]

Just as a test, could one of the folks who is experiencing "crashes" with X264, please download this version (http://www.jdobbs.net/freeware/x264.exe) (r1112) and see if (by some chance) the issue has resolved itself?

A quick response would be appreciated. I'd like to put out a new BD-RB release. Thanks.

Will also give this a try as well.... I'll keep you posted..

Thanks,

Wayne

[jdobbs]

Looks like it may have been a glitch specific to the r1109 release. I'll include r1112 in a release today.

[YolkiePolkie]

Update with Galapagos:

The m2ts file ripped by AnyDVD would only play audio using VLC media player. With Cyberlink Power DVD I got the attached picture with the expected audio.

Perhaps this is a AnyDVD problem. What do you think JDobbs?

I've just found this thread where someone was having similar problems with Galapagos blu-ray, but no solution has been found

http://forum.doom9.org/archive/index.php/t-144282.html

[jdobbs]

I've just posted a link to v0.18.09 (beta) on the first post of this thread. The changes are:
- Changed the method for determining fps/framecounts
and other file info so that AVISYNTH returns are
used only as a backup. Small speed improvement.
- Made changes that lower the likelihood that video
encodes will end in unspecific "failure".
- Enhanced error detection to more clearly identify
specific error locations.
- Updated X264 version to r1112. Seems to fix errors
that some received on r1109 -- but not repeatable
on reference machine in testing.
- Added code to automatically back into X264 r1082
after two failed attempts to encode.
- Other minor corrections and cosmetic fixes.

[DaMacFunkin]

Although i aint been watching the ps3 skipping thread, will it be possible to re-rip an already re-encoded disk and have the program remux all the streams to make them ps3 compliant, if you follow what i'm trying to say. :confused:

[jdobbs]

I'd just demux it with TSMUXER and then remux it.

[Furiousflea]

Update with Galapagos:

The m2ts file ripped by AnyDVD would only play audio using VLC media player. With Cyberlink Power DVD I got the attached picture with the expected audio.

Perhaps this is a AnyDVD problem. What do you think JDobbs?

I've just found this thread where someone was having similar problems with Galapagos blu-ray, but no solution has been found

http://forum.doom9.org/archive/index.php/t-144282.html

Your problem is nothing to do with this thread or any program.

It is because Galapagos is 1080i source and there is no directshow decoder available for free that can decode 1080i VC1 properly...

It is NOT a problem with AnyDVD HD\BD-Rebuilder

EDIT - Just checked that thread and you're just spamming I posted myself in that thread with an answer as concise as you are going to get - take your question to that thread if you need more help because it doesn't belong here. (no offense)

[YolkiePolkie]

Nope I'm not spamming - that wasn't me on that thread. If you read this thread from page 61 I originally thought it may be bug with BD Rebuilder as I was getting failed video encode messages. I was updating jdobbs that I think it's no longer a bug for him to think about. I didn't want to waste his time anymore with this. I will forgive you because you're getting over flu ;-)

EDIT - thanks for pointing out what you think the problem is. That's honestly appreciated.

[dmancornell]

Try running the mux from the command line:

"c:\path\to\bd-rb\tools\tsmuxer.exe" "c:\working\path\mux_00000.meta" "c:\working\path\TMP"

See what error is occurring.

tried with tsmuxer 1.8.8, still get the same bitstream error. Looks like it's a tsmuxer problem so I'm giving up.

[jdobbs]

It is because Galapagos is 1080i source and there is no directshow decoder available for free that can decode 1080i VC1 properly... I think the WMV11 codec will do 1080i correctly (I've used it on several) -- it's the hybrid sources of interlaced/progressive I think are where there is still a problem.

[MikeyBK]

I've just posted a link to v0.18.09 (beta) on the first post of this thread. The changes are:
- Changed the method for determining fps/framecounts
and other file info so that AVISYNTH returns are
used only as a backup. Small speed improvement.
- Made changes that lower the likelihood that video
encodes will end in unspecific "failure".
- Enhanced error detection to more clearly identify
specific error locations.
- Updated X264 version to r1112. Seems to fix errors
that some received on r1109 -- but not repeatable
on reference machine in testing.
- Added code to automatically back into X264 r1082
after two failed attempts to encode.
- Other minor corrections and cosmetic fixes.

Thanks for the update JD, will run this tonite...
Just FYI though, 0.18.8 with the x264 r1109 was actually successful for me on 3 out of four encodings....with only crashes when attempting Pride & Glory (which was the only VC-1 encoded BD out of the four).... so I attempted other VC-1 BD's and they also crashed that version of x264
....perhaps a glitch in that version of x264 related to VC-1 encoded Blurays? Just thought that might be useful info for Dark Shikari and the other developers of x264...
EDIT: never mind, I see one of the guys had the same with Tropic Thunder, and that one is encoded in h264... I'll just stick to posting about the new version of BD-Rebuilder...lol

[cyberdoggy]

O.K. I am using v0.18.9 doing a full movie encode and it gets to a particular vid_00003 and a box pops up and says "xvidcore.dll not found, can anyone clue me in on what that pertains too? Thanks and keep up the great work to all of us here testing this phenomenal little app. :)

[laserfan]

I think the WMV11 codec will do 1080i correctly (I've used it on several) -- it's the hybrid sources of interlaced/progressive I think are where there is still a problem.I wonder how one would identify these (hybrids)? It was Mamma Mia! where I encoded some of the extras separately (using DG's tool) because BD-RB failed on them--is there a tool (or method) to id when a clip has both IL and Prog content?

[laserfan]

O.K. I am using v0.18.9 doing a full movie encode and it gets to a particular vid_00003 and a box pops up and says "xvidcore.dll not found, can anyone clue me in on what that pertains too? Thanks and keep up the great work to all of us here testing this phenomenal little app. :)What disc is that (with an Xvid embedded)?!?!

[jdobbs]

O.K. I am using v0.18.9 doing a full movie encode and it gets to a particular vid_00003 and a box pops up and says "xvidcore.dll not found, can anyone clue me in on what that pertains too? Thanks and keep up the great work to all of us here testing this phenomenal little app. :) Did you install and configure the FFDSHOW package? If so, I can't imagine why an XVID dll is being called.

Is this a real disc or something that has been built by other packages? That XVID call sure seems suspicious.

[Furiousflea]

Not sure if anyone has asked already but I noticed you haven't re-enabled subtitle removal support again since a few 0.17.xx releases?

I've tried editing ini but to no avail, BD-Rebuilder pays no attention to the setting when changed to "1" to enable. Is this a deliberate choice for compatibility sake?

Not sure it's that beneficial many Blurays have 500-800mb+ of subtitle date, makes BD9\5 backups extremely wasteful. Sorry if asked already did go back a few pages but nobody seems to mind?

I'd really appreciate it anyway as I'm stuck using 0.17.xx for now and I'm sure that this version has screwed my BD9 full backup of "The Matrix" (no audio or subs audible or selectable for main feature, but audio fully present in all extras etc)...

Any ideas? Thanks jdobbs, sorry about not providing that last cmd thing feelin bit better this evening and looks like it was just a dodgy version of x264 :)

[datman]

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine



for what it's worth I converted a BDRB file dated 1-20-09 to ISO tonight and it will mount and play.



I have had the "Stricter AVCHD compliance for movie-only" checked since about this time


Stricter AVCHD compliance for movie-only was my problem. I did Patton today and it will play the ISO and I thought I forgot to uncheck the Do not covert dts to ac3 because I have the DTS 1509kbps sound. The only option I had checked in setup was limit one track for each language:confused:

What I did do is change the quality setting from 3 to 2. Last night when I started the encode I thought if 5 is bad 2 must be better than 3. Either way the picture looks great I would say perfect (100%) and with better audio saved to a BD9 size done 8 1/2 hours. Unless you advice otherwize I'm sticking with this setting.

The Stricter AVCHD compliance for movie-only must have been why I kept getting 448 ac3 audio files when I was encoding Independence day.

What does the Stricter AVCHD compliance for movie-only option do? and why would you want to use it?

[jwjohnson]

Not sure if anyone has asked already but I noticed you haven't re-enabled subtitle removal support again since a few 0.17.xx releases?

He disabled those menu choices on purpose since he said it was not intended to be working.

[cyberdoggy]

What disc is that (with an Xvid embedded)?!?!
I was doing EARTH_BIOGRAPHY_D1_US but I think I just have too many damn codecs on this box, are we using the klcodec pack or the Combined Community Codec Pack I am starting to get really confused :(

[jdobbs]

My personal opinion is: if you have FFDSHOW installed you pretty much don't need anything else... so what's the point of all the others?

[Dark Shikari]

My personal opinion is: if you FFDSHOW installed you pretty much don't need anything else... so what's the point of all the others?You need a splitter too, like Haali's. And VSfilter is useful for many users.

Those three (plus MPC-HC) are pretty close to all of CCCP.

[MR.WaynesWorld]

Downloaded 18.9 and trying Hancock again. I did not get the x264 error but I do have Encode Failed - Retrying. Is there any other info that may help with this.

[cyberdoggy]

O.K. word to who-ever out there! I uninstalled many, many, codecs that came in various codec packs and cleaned my registry and temp files out real good, and rebooted started up BD-RB and it was instant smooth sailing so far on a file I could not get going for nothing. So in conclusion if you are getting new errors allot try what I did Jdobbs is correct, there really is no need for extra BS on the system. Thanks jd. ;)

[smnckl]

@jdobbs

...
Interestingly I have done a number of encodes with this version of X264 and haven't had a crash yet. Is there anything unique about your setup, codecs, configuration?
...


I have not had any issues with the .08b version at all.
Only time it crashed was due to my own fault as I hit a senior moment right on the head. :devil:

Since it was in pass 2, I just ran the command line from the LASTCMD.TXT and it is chugging away happily.
I assume that when x264 is done, I can just run BD-RE and continue from there with the re-muxing and BD structure build?

While I have your attention, a quick question. Is BD-RE (and x264) coded optimized for SSE? enabled CPUs? When I run on this system, an Athlon 62 X2, it gives me pretty decent FPS during encoding. However, on an Intel P4 with HyperThreading, it gives me under 2 during pass 2. And on my Lenovo T60 laptop with a Centrino Duo, Max Payne ran at 0.1 FPS. THAT was a real PAIN. :devil:
I aborted after 4 days.

All this numbers from .08b.

[Dark Shikari]

While I have your attention, a quick question. Is BD-RE (and x264) coded optimized for SSE? enabled CPUs? When I run on this system, an Athlon 62 X2, it gives me pretty decent FPS during encoding. However, on an Intel P4 with HyperThreading, it gives me under 2 during pass 2. And on my Lenovo T60 laptop with a Centrino Duo, Max Payne ran at 0.1 FPS. THAT was a real PAIN. :devil:
I aborted after 4 days.

1. x264 is the most heavily assembly-optimized program I have ever seen. It has over 420 hand-written assembly functions (and we keep adding more). I would be unsurprised if it had more x86 assembly code than ffmpeg--despite ffmpeg being an encoder and decoder for hundreds of formats instead of just an encoder for one. Over 20% of the codebase is assembly code. It is primarily optimized for Core 2 CPUs, but of course it contains optimizations for everything else too (that's just our primary target).

2. The Pentium 4 is an awful CPU. It's going to be slow as hell no matter what you do.

3. "Centrino" is the name of a chipset, not a CPU.

[Furiousflea]

@jdobbs



I have not had any issues with the .08b version at all.
Only time it crashed was due to my own fault as I hit a senior moment right on the head. :devil:

Since it was in pass 2, I just ran the command line from the LASTCMD.TXT and it is chugging away happily.
I assume that when x264 is done, I can just run BD-RE and continue from there with the re-muxing and BD structure build?

While I have your attention, a quick question. Is BD-RE (and x264) coded optimized for SSE? enabled CPUs? When I run on this system, an Athlon 62 X2, it gives me pretty decent FPS during encoding. However, on an Intel P4 with HyperThreading, it gives me under 2 during pass 2. And on my Lenovo T60 laptop with a Centrino Duo, Max Payne ran at 0.1 FPS. THAT was a real PAIN. :devil:
I aborted after 4 days.

All this numbers from .08b.

Yes x264 has pretty much every optimisation under the sun and will certainly make use of advanced instruction sets (which ones, I dunno ;)) Irrelevent really, point is that a Pentium 4 no matter how fast will be SLOW SLOW SLOW...SLOW. I believe "Centrino" laptops are just Pentium M based laptops with wireless to satisfy the "Centrino" criteria and use that name. These are the first Pentium M chips - again S-L-O-W.

To be quite honest it's not really worth the bother on anything less than a fast dual core Athlon X2, even then...The amount of electric your setup will be using to do an encode, it might not even be cost effective.

[smnckl]

@Dark Shikari

1. x264 is the most heavily assembly-optimized program I have ever seen. It has over 420 hand-written assembly functions (and we keep adding more). I would be unsurprised if it had more x86 assembly code than ffmpeg--despite ffmpeg being an encoder and decoder for hundreds of formats instead of just an encoder for one. Over 20% of the codebase is assembly code. It is primarily optimized for Core 2 CPUs, but of course it contains optimizations for everything else too (that's just our primary target).

I don't doubt the info you are giving us here. While not a programmer, I do know that apps that use asm code are the fastest and most compact available. Reminds me of the time when I had an Atari and had to type in asm code to get a word processor and spreadsheet to use. :)

2. The Pentium 4 is an awful CPU. It's going to be slow as hell no matter what you do.

Compared to today's CPU offerings, the P4 is what a 8086 was to a 286 or 386sx. :p

3. "Centrino" is the name of a chipset, not a CPU.

Sorry, fingers went faster than brain. It is actually a Core Duo T2400, but still a P4...

Was running the encode on that to see how it would turn out. Just an exercise in futility, you could say, but to me a step in my venture into getting movie backups done.

Can't afford a Quad-core, much less an i7 rigjht now, so I;m just trying to make do with what I have gotten over the years.

Thanks for the clarification.

@Furiousflea


...
To be quite honest it's not really worth the bother on anything less than a fast dual core Athlon X2, even then...The amount of electric your setup will be using to do an encode, it might not even be cost effective.

I'll probably look on eBay for some better CPUs. Unless I hit a lottery jackpot and can get me a couple of i7 systems to do my movie backups. :p

[Capsbackup]

Has anyone tried a full movie backup of X-Files 2, NTSC, to BD-5 or BD-9 and been successful? Or a different title that has two versions of the movie on the disc. I can get BD-RB to complete successfully, and the menu works fine as does the trailers and the theatrical version of the movie. But when I try to play back the extended version, I get no audio from my Sony BX1. The movie plays back ok, but no sound or subtitles are present or selectable. I have had this no audio playback issue before on single versions of a full backup , but this was the first full backup of a multi-version movie that I have tried, with one version working and the other not.

[jdobbs]

Has anyone tried a full movie backup of X-Files 2, NTSC, to BD-5 or BD-9 and been successful? Or a different title that has two versions of the movie on the disc. I can get BD-RB to complete successfully, and the menu works fine as does the trailers and the theatrical version of the movie. But when I try to play back the extended version, I get no audio from my Sony BX1. The movie plays back ok, but no sound or subtitles are present or selectable. I have had this no audio playback issue before on single versions of a full backup , but this was the first full backup of a multi-version movie that I have tried, with one version working and the other not.I have that one, I'll give it a try. I can tell you that there is something odd about the audio -- as TSMUXER always kicks out an error when you try to load the MPLS files.

[MikeyBK]

Downloaded 18.9 and trying Hancock again. I did not get the x264 error but I do have Encode Failed - Retrying. Is there any other info that may help with this.

I did have x264 r1112 crash on Pride & Glory again, but JD's code to have it automatically revert back to x264 r1082, worked flawlessly.... it's encoding as I post... will report back in the morning.

[Dark Shikari]

I did have x264 r1112 crash on Pride & Glory again, but JD's code to have it automatically revert back to x264 r1082, worked flawlessly.... it's encoding as I post... will report back in the morning.Seriously, can people give me the information I need to fix the crash or, if you don't know, ask how? I get incredibly aggravated when people constantly talk about x264 crashing as if there isn't anyone sitting around who wants to fix it! It's like I simply don't exist--like walking into your own home and having nobody notice that you're there, like an episode of the Twilight Zone.

Dropping back 30 revisions is not a solution; giving backtraces of the crashes to the developers is!

And if you need to know how to make a backtrace, just download gdb and a debug build of x264 (can often be found in the Current Patches thread; if not, harass someone in #x264 to make you one) and:

gdb x264.exe
set args your arguments to x264 go here
(wait)
(it crashes)
bt
(you post the output of this here)

An attempt at getting me the information I need here would be greatly appreciated.

(I apologize if I seem unnecessarily aggravated, but a crash in x264 is a big deal--and it is annoying to be completely and utterly ignored.)

[laserfan]

I get incredibly aggravated...In the spirit of Doom9's philosophy of forum etiquette, might I gently suggest to you sir that this is quite obvious, and therefore just *might* be part of the problem.

[Dark Shikari]

In the spirit of Doom9's philosophy of forum etiquette, might I gently suggest to you sir that this is quite obvious, and therefore just *might* be part of the problem.Do I not have the right to be aggravated when a dozen people tell me "your software is bugged" and then quietly slink away, unwilling to spend 5 minutes to help me fix it... despite spending hours and hours and hours testing and helping BD-Rebuilder?

I am not psychic and I cannot fix bugs unless people give me the information I need.

[jdobbs]

Perhaps if I pasted a giant "donations" link in my signature people might help me????? Is this a dig aimed at me? I'd make more from mowing lawns once a week than I get in donations... and if I can't ask for an occasional buck or two (with no requirement at all) for my effort I'll be happy to dump this whole project and spend an occasional hour my wife.

I can't help you with the crash -- because it has never happened to me. I put the automatic switch back in so I can continue to debug this program... and I can't do that when all I get are people telling me they are crashing.

You have the right to be aggravated for sure. But you don't have the right to rag on me. Pick another target.