BD Rebuilder Beta - Bug Reports Only

[AmigaFuture]

Okay...Yup, I'm tired at the moment. Wow. The config file isn't in the archive. It's made After the first time it's run, correctly. You extract the archive with WinRAR to the Desktop. You'll get a directory called "BD_Rebuilder" from the archive BD-RBV04009.zip.
Within that directory, BD_Rebuilder double click the file BDRB. The INI should be made and you should see the program.

[AmigaFuture]

I wouldn't use a download manager at this point until you know things are functioning as they should. Just use Firefox as per normal.

[hifreak]

I have problems with low fps always on second pass not even 10 fps per second. My computer is new I7 2700K and I have 8GB of memeory, so I don´t believe it is my hardware who cause the problem. Here is my settings:

[Options]
VERSION=0.40.0.9
MODE=2
ENCODE_QUALITY=2
Movies shorter than 100 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -1,-1 --no-psy --aq-mode 0 --no-mbtree
Movies shorter than 100 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --aq-mode 0 --no-mbtree
Movies between 100 and 130 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -2,-2 --me umh --merange 32
Movies between 100 and 130 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --merange 32 --trellis 2
Movies longer than 130 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --subme 10 --merange 64 --b-adapt 2 --trellis 2
Movies longer than 130 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --subme 10 --merange 64 --b-adapt 2 --trellis 2 --psy-rd 1.0:0.15
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=chi;dan;eng;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24500
TARGET_SIZE=23500
AUTO_BURN=2
MOVIEONLY_TYPE=0
ALTCRF=20
ALT_TARGET=1000
ALTMETHOD=0
ALTAUTOCROP=0
COMPLETION_BEEP=0
PRIORITY_CLASS=0
DGDECNV=0
WORKING_PATH=D:\BD-RBV04009\BD_REBUILDER\WORKING\
SOURCE_PATH=D:

[AmigaFuture]

@Revgen

When using WinRAR from the Desktop, Right-Click on the archive and a list will show. Left-Click "Extract here". The directory "BD_Rebuider" will be made and all files need are within it.
If you want to use XP's Internal Zip Handling.. Double click the archive. XP will display the contents of the archive. Drag And Drop the directory BD_Rebuilder to your Desktop (for now). Once extracted, locate it, double click the new directory and then BDRB. You should see the program running soon after if your XP install is functioning correctly. :-)

[jdobbs]

@hifreak

What does your system do on pass 2 if you remove the tweaks? If it's better, than the tweak is the problem.

Either way, it is definitely not the software. One other probable cause is that your system is overheating and the processor is slowing itself down to control the heat. Run a monitor (like CPUID HWMonitor) while encoding pass 2 -- if you see the CPU voltages drop during encoding, then that's why you are slow.

[hifreak]

@hifreak

What does your system do on pass 2 if you remove the tweaks? If it's better, than the tweak is the problem.

Either way, it is definitely not the software. One other probable cause is that your system is overheating and the processor is slowing itself down to control the heat. Run a monitor (like CPUID HWMonitor) while encoding pass 2 -- if you see the CPU voltages drop during encoding, then that's why you are slow.

Ok I will try to monitor I maybe have a feeling that it can be the heat now you mentioned that.

[hifreak]

I tried to monitor with Aida64 while I am running the 2 pass. Is it too hot I don´t think so right?

http://img846.imageshack.us/img846/1231/monitort.jpg

[RobertM]

I tried to monitor with Aida64 while I am running the 2 pass. Is it too hot I don´t think so right?
No, your temps certainly don't seem to be a problem.

A couple of other questions:
1. What is the CPU % usage during pass 2?
2. What quality setting are you using? I run an i7-950, mildly overclocked, and (just from memory here) I think I usually get around mid-teens for pass 2 FPS. If I swithced to "very high" then I wouldn't be surprised to see 10 FPS or less.
3. Maybe post your log too. I'm not saying that would contain the answer, but we'd have a more complete picture anyway.

[hifreak]

No, your temps certainly don't seem to be a problem.

A couple of other questions:
1. What is the CPU % usage during pass 2?
2. What quality setting are you using? I run an i7-950, mildly overclocked, and (just from memory here) I think I usually get around mid-teens for pass 2 FPS. If I swithced to "very high" then I wouldn't be surprised to see 10 FPS or less.
3. Maybe post your log too. I'm not saying that would contain the answer, but we'd have a more complete picture anyway.

I run high quality, but my CPU usage is very high 99-100 percent and I don´t have any other big things running. Is that normal?

[RobertM]

I run high quality, bu my CPU usage is very high 99-100 percent and I don´t have any other bigs running. Is that normal?

CPU usage SHOULD be around 100%, so that is certainly normal.

I'm not particularly familiar with the 2700K, but I imagine that if I removed my overclock my FPS would drop to the 10 FPS range. So I wouldn't think that anything major is broken in your system. Try disabling the tweaks, as per JDobbs suggestion, and see if that makes any difference.

[jdobbs]

@hifreak

Use CPUID HWMONITOR, as I suggested. It's free and is easy to find with Google. Keep it running during the encode of pass 2, and it will tell you the high/current/low temps over the course of the encode. Your CPU might speed up and slow down many times during an encode, so looking at the temp and wattage at any one point in time doesn't give any useful information. If you find that the "low" value for CPU wattage is different than current or high -- you know your processor is overheating and slowing itself down at different points, dramatically affecting speed.

I overclock, so I watch this very closely when setting up a system -- and believe me, this is something that happens on a lot, and people don't even know it. When the CPU fan gets to full speed (via PWM), and the processor is still pegged at a high temp, the ACPI will lower the CPU wattage to prevent damage from overheating. When that happens you might be running at 1/3 speed and there is no way of knowing it without monitoring.

The "Very High" setting will certainly bring the FPS down considerably. I never recommend that setting. It's just there for those who just can't live without it for some reason.

[hifreak]

@jdobbs

What is the tweak you are both talking about? I really don´t know so if it is enabled I am sure I did not knew how to do that ;)

[jdobbs]

@jdobbs

What is the tweak you are both talking about? I really don´t know so if it is enabled I am sure I did not knew how to do that ;)

????

This is what you posted:Movies shorter than 100 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -1,-1 --no-psy --aq-mode 0 --no-mbtree
Movies shorter than 100 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --aq-mode 0 --no-mbtree
Movies between 100 and 130 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -2,-2 --me umh --merange 32
Movies between 100 and 130 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --merange 32 --trellis 2
Movies longer than 130 minutes, (almost) no grain) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --subme 10 --merange 64 --b-adapt 2 --trellis 2
Movies longer than 130 minutes, grainy) = "TWEAK_PASS_TWO=--filter -3,-3 --me umh --subme 10 --merange 64 --b-adapt 2 --trellis 2 --psy-rd 1.0:0.15 I assumed that if you have this in your INI, you are using them... if not, where did they come from? BD-RB certainly didn't add those lines to your INI.

[Revgen]

Went into Safemode today and got it to work properly. Obviously there is something wrong with my normal WinXP setup. Not sure exactly what since my other programs work fine.

[Imperial Zeppelin]

Wondering if I'm the only one seeing this, but it seems that the latest release runs much hotter, >10 ºC hotter than I've ever seen before? No other application is showing unusually hotter temperatures.

[AmigaFuture]

Ravgen, use MSConfig (Windows Key+R then type it and press enter) since Safemode allowed access. A driver or other software is running in the background causing challenges..or something else. You could also start killing processes from Task Manger to see, remember Task Manager doesn't show ~Everything~. Because of your BD Rebuilder experience that indicates something else could also be that you've not ~yet~ noticed. :-) Nice to know you notice it worked in Safemode, does that also mean BDRB ran AND runs in Normal mode, including changes to INT being saved?

[omegaman7]

Wondering if I'm the only one seeing this, but it seems that the latest release runs much hotter, >10 ºC hotter than I've ever seen before? No other application is showing unusually hotter temperatures.

The 940 runs fairly hot. The revision I had anyway. I had to add a top exhaust fan to help it out. It dropped the temps 8 - 10C under load. Summer is approaching, and I'm due to blow out my case! ;)

[Audiophile1178]

jdobbs, regarding my post here (http://forum.doom9.org/showthread.php?p=1575401#post1575401) that I and dfsooner are having regarding the negative bitrate error. I have been doing several tests on the men in black II disc where the problem has been happening and no matter what I do it keeps on happening. I've actually encoded the disc with BDRebuilder using very fast one pass ABR settings in which the error didn't happen but the output BDRebuilder video is garbled and doesn't display anything related to the source. Another interesting thing is that the original video size is 119MB but the garbled encode that worked once in the single pass ABR turned out to be 1.61MB. The two videos that it's gettings stuck on are anti-piracy video information for belgium and I think belgie. Both videos are pretty much identical and don't seem like anything special from what I'm seeing using mediainfo. Same time and background. The only thing different is the text displayed ontop of the video which is formatted for that country. Since I saw what the video was I figured that my bluray player would ignore it due to region settings and sure enough it did and plays perfectly fine. I can't get that video to play anywhere on my bluray player.

This is what I've done to try and test it for you:

1. I had a suspicion that I had a bad memory stick. Sure enough I did. I removed it from the equation and BDRebuilder still failed.
2. Tried disabling/enabline LAVF in the settings. No Change.
3. Uninstalled everything and reinstalled it. No Change.
4. Deleted BDREBUILDER.INI and reset to default. No Change.


Tonight, I'm going to use an older version just for kicks to see what happens. I'll keep you apprised of the situation.


P.S. Any new info regarding my mummy encodes from here (http://forum.doom9.org/showthread.php?p=1574683#post1574683)?

[jdobbs]

jdobbs, regarding my post here (http://forum.doom9.org/showthread.php?p=1575401#post1575401) that I and dfsooner are having regarding the negative bitrate error. I have been doing several tests on the men in black II disc where the problem has been happening and no matter what I do it keeps on happening. I've actually encoded the disc with BDRebuilder using very fast one pass ABR settings in which the error didn't happen but the output BDRebuilder video is garbled and doesn't display anything related to the source. Another interesting thing is that the original video size is 119MB but the garbled encode that worked once in the single pass ABR turned out to be 1.61MB. The two videos that it's gettings stuck on are anti-piracy video information for belgium and I think belgie. Both videos are pretty much identical and don't seem like anything special from what I'm seeing using mediainfo. Same time and background. The only thing different is the text displayed ontop of the video which is formatted for that country. Since I saw what the video was I figured that my bluray player would ignore it due to region settings and sure enough it did and plays perfectly fine. I can't get that video to play anywhere on my bluray player.

This is what I've done to try and test it for you:

1. I had a suspicion that I had a bad memory stick. Sure enough I did. I removed it from the equation and BDRebuilder still failed.
2. Tried disabling/enabline LAVF in the settings. No Change.
3. Uninstalled everything and reinstalled it. No Change.
4. Deleted BDREBUILDER.INI and reset to default. No Change.


Tonight, I'm going to use an older version just for kicks to see what happens. I'll keep you apprised of the situation.


P.S. Any new info regarding my mummy encodes from here (http://forum.doom9.org/showthread.php?p=1574683#post1574683)? I fixed that one for the next release. I was able to repeat it on "The Sopranos, S1D5". It just happened that in that M2TS the audio was much longer than the video -- so when BD-RB tried to calculate the maximum bitrate allowable (after accounting for the audio size), it resulted in a negative value. The reason I didn't see it originally is because I wasn't keeping the original audio intact.

You should see a release with the fix soon.

[jdobbs]

Wondering if I'm the only one seeing this, but it seems that the latest release runs much hotter, >10 ºC hotter than I've ever seen before? No other application is showing unusually hotter temperatures. You're probably seeing the result of higher ambient temperatures -- because it's getting warmer in the northern hemisphere. It's also possible that your heatsink is collecting dust. But I don't think the temperature is related to any changes in BD-RB or its helper apps.

[Audiophile1178]

I fixed that one for the next release. I was able to repeat it on "The Sopranos, S1D5". It just happened that in that M2TS the audio was much longer than the video -- so when BD-RB tried to calculate the maximum bitrate allowable (after accounting for the audio size), it resulted in a negative value. The reason I didn't see it originally is because I wasn't keeping the original audio intact.

You should see a release with the fix soon.

Great to hear that you were able to duplicate it! I was starting to wonder if it was something to do with my system.

I have three questions for you:

First, I don't know if you saw my P.S. but did you have any idea what's happening with the mummy movies 480p~~>480i? I don't know if that'll cause any issues with pip when the original video is 1080p?

Second, if i'm experiencing no sound on the dts express on the mummy movies does that also mean that any other movie with pip such as watchman i'd experience the same issues?

Third, if hidden options are still experimental then would blanking be better off not being used? I just saw that it was there and how to enable it but haven't used it yet and don't know if there's any side effects to using it yet.


Thank you for your help on this and for making such a great program that one of a kind!

[jdobbs]

1. I still haven't looked at that one. But I've done many, many discs with 480p PiP and have never had that issue -- BD-RB gets the format from the source. I can't be positive, but my guess would be that 480i wouldn't work correctly with a 1080p base.

2. If you are not getting the sound then your player isn't recognizing it -- that makes it likely no other backed-up DTS Express source will work on that player either. I'm working that issue, but so far with no idea what it could be.

3. Not all hidden options are experimental. Blanking is experimental -- but not because it doesn't work correctly. I just haven't found a foolproof way to determine what should and should not be blanked in automatic selection modes (like Movie-and-Menus).

[hifreak]

????

This is what you posted: I assumed that if you have this in your INI, you are using them... if not, where did they come from? BD-RB certainly didn't add those lines to your INI.

Hi again actually it was my friend who installed those tweaks long time ago, I just forgot that :D Anyway It is a little faster now, so the tweaks was probably the reason. I will try not to use those tweaks. Thanks for the feedback.

[AmigaFuture]

Seems there's a bug with Loading and Saving projects. I edited 2 disks, manual blanking and saved the project for another moment. Then edited another disk. I saved that project. Quit BD-RB. Shut off Windows. The next time I used Windows, I ran BD-RB, and loaded 1 of the disk projects. I noticed the edits weren't there. I loaded the other project, edits weren't there for it either. I figured...perhaps they Are there just not reflected via GUI. So I ran the backup process. I just checked the rendered, yep...edits were not kept. They may have been saved by BD-RB, but not reloaded?

This applies for Full Backup. Option Auto-Blanking Extras seems to retain edits, but not customized editing; unchecking "Blank this item" then saving the project.

[jdobbs]

Seems there's a bug with Loading and Saving projects. I edited 2 disks, manual blanking and saved the project for another moment. Then edited another disk. I saved that project. Quit BD-RB. Shut off Windows. The next time I used Windows, I ran BD-RB, and loaded 1 of the disk projects. I noticed the edits weren't there. I loaded the other project, edits weren't there for it either. I figured...perhaps they Are there just not reflected via GUI. So I ran the backup process. I just checked the rendered, yep...edits were not kept. They may have been saved by BD-RB, but not reloaded?

This applies for Full Backup. Option Auto-Blanking Extras seems to retain edits, but not customized editing; unchecking "Blank this item" then saving the project. So by "edits" you mean specifically custom blanking/unblanking? Anything else not coming through?

[gg72]

@jdobbs, I found a bug when using x264's internal LAVF for decoding that causes undersized output and (potentially) out of specs streams, basically the demuxed original video is identify by LAVF as 25 fps regardless of the original framerate (23.976) /.../

I have the same problem: when I use the internal LAVF for decoding, the output has a different fps as the original.

The original has 29.970 fps, but it was identified by LAVF as 25 fps. The result: audio delay. The source was a concert movie with 1080i and 29.970 fps.

With film material and external serving (DirectShow) I havent any trouble yet.

Is there an explanation of it?

[AmigaFuture]

So by "edits" you mean specifically custom blanking/unblanking? Anything else not coming through?

Yes, custom un/blanking. I've checked 2 movies, and they look/sound good. SUPs are showing, audio sync in place.. More movies to check.. :)

Also...Even if I exit BD-RB, set unblank on 1 or 2 streams (containing audio/video, not SUPs) from what Auto-Blank Extras set to be blanked, and exit..then rerun BD-RB, the all extras are set to be blanked again.

Also, with respect to your comment about video encoding quality, I appreciate Highest (Very Slow) being there. I don't use it every time, but it's sweet to have it. Most may not notice, but for those of us who Do. 2 thumbs Up.

[Cela]

...
Still missing an _explanation_ ...
SourceCheck() 00006 2501 (for test BD 1)
SourceCheck() 00055 2501 (for test BD 2)
...
I bought a new BD drive (LG BE12LU38), but BD-RB V04009 still refuses to accept that BD with same messages as almost a month ago:
SourceCheck() 00055 2501
Illegal Source
Selected source is not BD format.
I get these messages even when I let BDRB open the original disk directly from the BD drive. This slows down BDRB processing, but makes it possible to get some impression of what BDRB is doing after browsing to the Source Path. Normally it takes ~ 10 seconds to check the streams and opens the source path.
But for this BD, which Slysoft support claims to open correctly, it does not take BDRB a second to refuse it without even inspecting the streams.

It should be possible to tell exactly from the error message what BDRB is expecting when it issues that message, else the message is completely useless if it does not provide a relevant clue.

So, I ask again, what is it that BDRB, after next to no investigation, decides
SourceCheck() 00055 2501
Illegal Source
Selected source is not BD format. ???
What does SourceCheck() 00055 2501 really mean?
Why can multiAVCHD repair this alleged Illegal Source? Why can't BDRB? What exactly is 'illegal'?

Edit:
ErrLog.txt
05.31.12 [12:44:42] SourceCheck() 00006 2501
05.31.12 [12:45:16] SourceCheck() 00055 2501
Remark: 1st message automatically during startup of BDRB,
2nd message at first user attempt (retry) to open BD drive.

[RobertM]

I bought a new BD drive (LG BE12LU38), but BD-RB V04009 still refuses to accept that BD with same messages as almost a month ago:
SourceCheck() 00055 2501
Illegal Source
Selected source is not BD format.

Disc that are formatted as BD require a specific format. You will see specific folder names ("BDMV", "CERTIFICATE", "STREAM", etc.) and some of those folders will be required to have specific content. If BDRB does not find the required formats it will throw that error. This has nothing to do with the optical drive, as long as the drive is working properly.

I get these messages even when I let BDRB open the original disk directly from the BD drive. This slows down BDRB processing, but makes it possible to get some impression of what BDRB is doing after browsing to the Source Path.
BDRB doesn't care where the information is -- just what the format is. It is recommended that you rip to HDD first simply because this speeds up the data reading process. The response time of the optical drive is slower, so it might be possible that you could run into trouble if the re-encoding process is starved for input data.

Normally it takes ~ 10 seconds to check the streams and opens the source path. But for this BD, which Slysoft support claims to open correctly, it does not take BDRB a second to refuse it without even inspecting the streams.
BDRB isn't scanning the files themselves. It has taken a look at the file structure and doesn't like what it sees. This doesn't take much time. Just because AnyDVD hasn't given you an error message doesn't mean that it has successfully decoded the disc. If it has been presented with an encryption scheme that it is not familiar with then it might fail silently. Are you using the latest version of AnyDVD?

After AnyDVD finishes its decryption, and before you even bother to run BDRB, what does the decrypted file structure look like to you? Does it look like other BD discs, especially the ones that have backed-up successfully for you in the past? Is there actual content in the "Stream" folder?

It should be possible to tell exactly from the error message what BDRB is expecting when it issues that message
"Selected source is not BD format" seems to be a pretty clear message to me.

What BD disc are you you trying to backup?

[jdobbs]

@cela

It's possible that something is corrupt in one of the MPLS files. They are scanned for legal references and chapter information when checking the source. Can you look and tell me how many MPLS files exist on that disc? They are found in the \BDMV\PLAYLIST folder. They're usually pretty small. Can you put them into a zip file and send them to me? Email to: dvd-rb@jdobbs.net

Other than the MPLS files, pretty much the only thing that is done in that section of code is checking to ensure the correct folders exist for BD compliance.

[Cela]

@jdobbs
Thanks for your willingness to investigate. You've got mail.
It's an exciting puzzle. I sincerely hope there will be a good solution.

[jdobbs]

@jdobbs
Thanks for your willingness to investigate. You've got mail.
It's an exciting puzzle. I sincerely hope there will be a good solution.

Got the files and was able to repeat the issue. It'll be fixed for the next release. Look for it in the next day or two.

[Cela]

...It'll be fixed for the next release. Look for it in the next day or two.I am very happy and grateful that you will be able to fix the flaws of my problem disk! Thank you so much! :) :thanks::

Disc that are formatted as BD require a specific format. ...
"Selected source is not BD format" seems to be a pretty clear message to me... I agree with you, its a clear message, but it is a verdict, a conclusion. It does let me understand the _reasons_ for the conclusion, _what shortcoming_ triggered the conclusion, what I should do better. In the discussion since posting #14921 on page 747 I tried to find out _what_ to do better, i.e. what exactly was wrong. Was it the physical disk? A vulneration of the required format? If so, then _what_ format item? Or, was it the drive? Or, was it that AnyDVD had missed something? Etc.

I am very happy now that jdobbs has found a solution for whatever was wrong with my disk and will implement it in the next release. :)

[jdobbs]

I am very happy now that jdobbs has found a solution for whatever was wrong with my disk and will implement it in the next release. :) The truth is that your disc wasn't "illegal" or "wrong". As it turns out, a part of one of the MPLS files was just exceptionally odd. So the issue was in BD-RB in that it wasn't robust enough to handle that odd (but legal) circumstance.

[RobertM]

In the discussion since posting #14921 on page 747 I tried to find out _what_ to do better, i.e. what exactly was wrong. Was it the physical disk? A vulneration of the required format? If so, then _what_ format item? Or, was it the drive? Or, was it that AnyDVD had missed something? Etc.

You are right that, everything else being equal, it would be better if the error messages were more meaningful to the end user, but it would take some effort on JDobbs' part to provide all those additional messages. The errors have to be reported to JDobbs for resolution anyway, and he already knows what the error codes mean.

I'm just so used to BDRebuilder NOT being the problem -- almost always it is a bad rip, bad decode, pre-processing, faulty drive, overheating processor, etc.

[jdobbs]

You are right that, everything else being equal, it would be better if the error messages were more meaningful to the end user, but it would take some effort on JDobbs' part to provide all those additional messages. The errors have to be reported to JDobbs for resolution anyway, and he already knows what the error codes mean.

I'm just so used to BDRebuilder NOT being the problem -- almost always it is a bad rip, bad decode, pre-processing, faulty drive, overheating processor, etc. You're right. The problem is that there are thousands of possible errors that could happen in a standard as complex as blu-ray. If I tried to create an error message for every one I'd do nothing but type error messages for the next 2 years. The messages aren't meant for the end-user. They are meant to point me to the right place so I can fix it.

[dfsooner]

I got the error shown below last night. Got the same error selecting BD-9.

I couldn't find any setting in .ini or in hidden options that would seem relevant. Any suggestions?


[05:29:32] Source: SOPRANOS_S6D3
- Input BD size: 30.20 GB
- Approximate total content: [02:45:23.997]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: High-Speed Option (BD-25), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[05:29:33] PHASE ONE, Encoding
- [05:29:33] Processing: VID_00002 (1 of 3)
- [05:29:33] Extracting A/V streams [VID_00002]
- [05:36:48] Reencoding video [VID_00002]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 77,835 frames
- Bitrate: 12,826 Kbs
- [05:36:48] Reencoding: VID_00002, Pass 1 of 2
- [05:36:49] Reencoding: VID_00002, Pass 2 of 2
- [06:14:08] Video Encode complete
- [06:14:08] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (spa): Keeping original audio
- [06:14:08] Multiplexing M2TS
- [06:18:45] Processing: VID_00004 (2 of 3)
- [06:18:45] Extracting A/V streams [VID_00004]
- Error in attempt to extract audio/subs.
- AV frame too large (65532 bytes). Increase AV buffer.
[06:21:46] - Failed to retrieve audio, aborted


[Status]
LABEL=SOPRANOS_S6D3
VERSION=v0.40.09 (beta)
SOURCE_SIZE=32428507588
SOURCE_VIDEO_SIZE=31940352000
TARGET_SIZE=24641536000
REDUCTION=.756202699707254
RESIZE_1080=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
[00002]
AUDIO=11
PGS=1111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=7999935971
RATE=12826
SPLITS=1
NSTART=27000000
NEND=173086560
NSIZE=7537858560
FLINK=0
MLINK=0
[00004]
AUDIO=111
PGS=11111

[RobertM]

- AV frame too large (65532 bytes). Increase AV buffer.


I've had this error before -- it was a bad rip.

[dfsooner]

I've had this error before -- it was a bad rip.

I suppose that's possible but it plays fine with TMT. How do you increase AV buffer?

[jdobbs]

I suppose that's possible but it plays fine with TMT. How do you increase AV buffer?

It's a bad rip.

Never confuse "playing" with "decoding and reencoding" -- playing can ignore errors, decoding/reencoding can't.

The error comes from TSMUXER. The AV buffer isn't really the issue. That's just where the corrupt source showed itself. You'd probably get it no matter how big you made the buffer.

[Revgen]

I was able to solve the run-time error I reported earlier. I found out about a program called "process explorer". So I ran BD Rebuilder and processexplorer told me that one of the places BD Rebuilder first goes to when it's opened is the Application Data folder in Documents and Settings. I went there and found that most of the folders are hidden, including the BD Rebuilder folder. So I decided to unhide them all and see what happens. Now it starts without a hitch. No errors. I rehid the Application Data\BDREBUILDER folder again, and I got the error again. Apparently BDRebuilder doesn't like hidden files or folders.

[jdobbs]

I was able to solve the run-time error I reported earlier. I found out about a program called "process explorer". So I ran BD Rebuilder and processexplorer told me that one of the places BD Rebuilder first goes to when it's opened is the Application Data folder in Documents and Settings. I went there and found that most of the folders are hidden, including the BD Rebuilder folder. So I decided to unhide them all and see what happens. Now it starts without a hitch. No errors. I rehid the Application Data\BDREBUILDER folder again, and I got the error again. Apparently BDRebuilder doesn't like hidden files or folders. It's your O/S that is in error. BD-Rebuilder doesn't access those specifically -- it is the redirection of your O/S that does it. Apps are supposed to have access to the application data folders. In other words, something is misconfigured in your system.

[Revgen]

It's your O/S that is in error. BD-Rebuilder doesn't access those specifically -- it is the redirection of your O/S that does it. Apps are supposed to have access to the application data folders. In other words, something is misconfigured in your system.

Hmm...interesting. Unfortunately I can't begin to fathom where the misconfiguration is.

I'm just glad it's working now.

[ceet12]

hi jdobbs, quick question not used bd rebuilder for a while as bd drive broke and i have since bought a new one,

when trying to set up the codecs as described on the first page, i think i set up some wrong, or couldn't find the exact setting, as i right clicked inspect, and opened the program, and it seemed to correct everything for me automatically as since clicking inspect again everything is set to ok?, im assuming that it should work correct as inspect has set it for me, or do i need to go back into ffshow and rest manually?

also im recently trying to rip a backup blu ray with ipbot and its asking me to update my ffdshow to rev 4400 or newer, if i update, would this break the bd rebuilder settings?

Hope you can help, thanks again

[jdobbs]

hi jdobbs, quick question not used bd rebuilder for a while as bd drive broke and i have since bought a new one,

when trying to set up the codecs as described on the first page, i think i set up some wrong, or couldn't find the exact setting, as i right clicked inspect, and opened the program, and it seemed to correct everything for me automatically as since clicking inspect again everything is set to ok?, im assuming that it should work correct as inspect has set it for me, or do i need to go back into ffshow and rest manually?

also im recently trying to rip a backup blu ray with ipbot and its asking me to update my ffdshow to rev 4400 or newer, if i update, would this break the bd rebuilder settings?

Hope you can help, thanks again BD-RB will set the CODECs for you if you right-click and "Run as Administrator"... but INSPECT doesn't do so.

As for FFDSHOW, it depends on the version used and any bugs in it. I haven't tested any of the newer versions, the last one I've tested is 4052. It should be ok to upgrade -- but if you run into any problems, revert to one of the recommended releases before reporting anything as a bug in BD-RB.

[Ch3vr0n]

if everything is set as ok, then you should be good to go unless you're using any kind of codec pack like klite etc. If you do, remove em. They usually interfere with BDRB's operations. Do NOT update to 4400 or newer. It has not been tested to work correctly with BDRB. If you do update, you do so at your own risc for multiple reasons. 1) The latest versions are not tried & tested and probably do not work correctly like BDRB wants them too and 2) jdobbs does not accept any kind of bug report from versions that do not match the ones in the first post

[Atak_Snajpera]

if latest ffdshow works in ripbot so it has to also work in bdrb.

[AmigaFuture]

Hmm...interesting. Unfortunately I can't begin to fathom where the misconfiguration is.

I'm just glad it's working now.

That's why I suggested using MSConfig. It's _a_ step to answering the question "Why?". That's still my suggestion while you're now enjoying using BD-RB. :D

[Revgen]

That's why I suggested using MSConfig. It's _a_ step to answering the question "Why?". That's still my suggestion while you're now enjoying using BD-RB. :D

I tried MSConfig with "diagnostic startup" before I unhid the application data. The problem was still present. So it's a fairly specific issue that's deeply rooted.

[HiQ123]

A question to jdoobs:

I read in the Frequently Asked Questions thread about AUTO_BIAS=n the following:

"You replace the "n" with one of 3 values: 0, 1, or 2. "0" tells the quality selection to have a bias toward speed, "1" (the default) balances speed and quality, and "2" tells the quality selection algorithim to have a bias toward higher quality."

But in the HIDDENOPTS file it says: n = 0-3 - Def=1, Auto Qual bias, 0=high speed, 1=normal, 2=high quality, 3=highest qual

Can I use 3? What is the difference between 2 and 3 (quality and speed)?