Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
21st September 2009, 01:41 | #5301 | Link | |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
|
|
21st September 2009, 05:47 | #5303 | Link | |
Registered User
Join Date: Dec 2008
Posts: 23
|
Quote:
That may have explained the problem, I upgraded to the latest version after I already did the rip. AnyDVD HD did ask me to download an update before the rip so I though that would have been enough. I try rip it again with the latest version see if the same problem occur. Thanks for the tip. |
|
21st September 2009, 10:07 | #5304 | Link | |
Registered User
Join Date: Aug 2003
Posts: 95
|
Quote:
Well, my BD-Player (LG BD390) supports 'real' blu-ray BD9s without a problem. Would there be *any* disadvantage for me if I continue to use "--avchd"? Or is it better to use FORCE_BLURAY=1 in my case? Some disc navigation advantages maybe? And would you please be so kind and share your thoughts on that "double AC3" problem I'm having again: http://forum.doom9.org/showthread.ph...46#post1327346 It's driving me nuts.. Thanks alot for your time. Last edited by samtroy; 21st September 2009 at 11:19. |
|
21st September 2009, 14:33 | #5305 | Link | |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
2. No. AVCHD is the output file format and isn't related at all to what HDDVD_Compliant does. |
|
21st September 2009, 14:36 | #5306 | Link | |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
There are no advantages I can think of for changing it... I just put the option in to maintain backward compatibility and "just in case". I've gone through the code over-and-over and I can't see any way that an AC3 would be generated unless it is chosen to do so. As for the two instances of each -- that's perfectly normal. If you have selected to reencode AC3 you will have the original (demuxed) and the reencode (@ either 640Kbs or 448Kbs). The reason that is done (e.g. from 640Kbs to 640Kbs) is so other adjustments can be made (filtering, normalization, etc.) in future versions. Today the only adjustment is "AUDIO_AMPLIFY=" which can increase reencoded volume levels. I've added an entry to the log that shows the audio settings at the start of the backup. That way, when I get a report of this type I can see absolutely what the settings are. Right now, until I can find a way it could happen, I have to assume the settings weren't what was thought at the time the job was started. Sometimes (especially in batch mode) the settings used for encoding aren't the ones you have in your INI file. They are what was there at the time the job was added to the queue. Last edited by jdobbs; 21st September 2009 at 14:50. |
|
21st September 2009, 15:31 | #5307 | Link |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
BD Rebuilder v0.29.05 (beta)
I've updated the first post of this thread with a link to a new version of BD-RB (v0.29.05). Changes for this version are:
Code:
- Corrected an issue in which, while the new audio delay routine in v0.29.04 was finding the delays correctly, they weren't being properly applied at remux. It should work correctly now. - Corrected an error in BATCH mode that could result in "RebuildFiles() 00075 2202" when output folder already exists. - Corrected an error in which small files that are a part of a multi-part movie-only encode could cause a "Can't open file: ...\VID_XXX.AVS.264" - Added code to adjust initial value when using CRF while resizing to 720p. Should reduce prediction passes. - Fixed an error in which sometimes (when PiP exists) the selection of 720p resizing was not following through in the encode. - Made changes to ensure that all 720p encodes held to BD specs -- especially when converting 29.97 or 25fps sources (requires framerate doubling). - Added "AssumeFPS()" to the AVS file when appropriate to make frame timing more exact. - Corrected an error in which resizing would not occur when destination space would not require encoding. - Added a new setting to the SETUP dialog that will convert standard definition (SD) sources (480/576) to 720p. This mode is useful for SAPs that always output in wide screen mode giving a "stretched" appearance to SD sources. It may also improve picture quality on some sources. - Added "--qpmin=0" to all command lines. This should reduce the likelihood of undersizing on high bitrate encodes. - Updated X264.EXE in zip distribution package to the latest (r1159) version. - Other minor corrections and cosmetic fixes. |
21st September 2009, 16:43 | #5308 | Link |
Registered User
Join Date: Jun 2009
Posts: 182
|
redoing for the 3rd time braveheart, last night had the same problem with this:
Corrected an error in BATCH mode that could result in "RebuildFiles() 00075 2202" when output folder already exists. will let you know if it works! thx again jdobbs! |
21st September 2009, 19:30 | #5309 | Link | |
Registered User
Join Date: Aug 2003
Posts: 95
|
Quote:
Isn't this bad because reencoding the AC3 tracks will degrade the audio quality? Or is this "amplifying" done without really reencoding the audiodata? Can this be turned off by any chance? I'm sure some users would like to leave the AC3 tracks completely untouched.. Last edited by samtroy; 21st September 2009 at 19:33. |
|
21st September 2009, 21:31 | #5310 | Link | |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
Be careful, though, because deciding to keep anything other than standard AC3 at 640Kbs or below -- you are violating the AVCHD specification for movie-only reencodes. In most cases the reencode is not distinguishable from the original. |
|
21st September 2009, 23:46 | #5311 | Link | |
Registered User
Join Date: Aug 2003
Posts: 95
|
Quote:
I *always* select not to reencode the AC3 track because I want to keep the original, untouched 640kbs AC3 tracks (when available). But BD Rebuilder *always* does process the demuxed AC3 files anyway. They are written again to the workfolder with nicaudio.dlls amplify-settings applied. Which means they are now modified and not untouched anymore. Those new, modified AC3 files are also used at the end for the final muxing. Even if I have chosen not to re-encode AC3 tracks. I have checked with different movies. My question was if this (automatic) AC3 amplifying step can be turned off, maybe by some ini-setting? Or some clarification on how this amplifying is done by nicaudio.dll: By completely re-encoding or only by modifying some volume values in the AC3 file and keeping the core audiodata untouched? Last edited by samtroy; 22nd September 2009 at 00:28. |
|
22nd September 2009, 00:14 | #5312 | Link |
Registered User
Join Date: Aug 2003
Posts: 95
|
Strange VC-1 encoding error
Strange VC-1 encoding errors
I've noticed that with VC-1 sources there are strange picture distortions in certain scenes. The effect appears only in *very grainy scenes* (like the whole movie "300" is shot). The picture then has some kind of pulsating horizontal distortions. As soon as these grainy scenes are over the problem is completely gone. This problem is absolutely *not* there with AVC/H.264 movies! I've already tried different VC-1 de-coders: ffdshow's internal one and WMP9. But both show the same problem . So it's apparently not a decoding issue.. I suspect it has something to do with x264's encoding. As if x264 has problems to properly encode VC-1 movies with very grainy scenes in it. Maybe it doesn't distribute the bitrate correctly.. ?? Could BD Rebuilder's encoding settings for x264 have something to do with it? Or has anyone had similar problems like this with VC-1 movies? Latest BDR version, Win7 (also tried Vista), movie-only, BD9, no resizing, 2-pass high quality. Like I said, H.264 sources are perfectly OK. Thanks for any help! |
22nd September 2009, 01:42 | #5313 | Link | ||
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
Quote:
Last edited by jdobbs; 22nd September 2009 at 01:46. |
||
22nd September 2009, 10:34 | #5314 | Link | |
Registered User
Join Date: Aug 2003
Posts: 95
|
Quote:
I'm sending you the latest log/ini-files and more detailed info via private message. Last edited by samtroy; 22nd September 2009 at 12:10. |
|
22nd September 2009, 14:24 | #5315 | Link | |
Registered User
Join Date: Aug 2006
Posts: 696
|
Quote:
I think you might be forgetting that BDRB ALWAYS encodes AC3 audio no matter what - it doesn't mean that you will be using that recoded stream when muxing though. For proof load the m2ts in eac3to and check if "dialogue normalization" is present. If it is, that means it hasn't been touched since BDRB strips it when it re-encodes. |
|
22nd September 2009, 16:48 | #5316 | Link | |
Registered User
Join Date: Jul 2005
Posts: 1,995
|
I can also confirm on a movie only backup to BD5 that BD-RB does not reencode the AC3 and does remux this original demuxed AC3 back into the new reencoded .m2ts.
I have only one AC3 file in my WORKFILES folder. Quote:
M2TS, 1 video track, 1 audio track, 1 subtitle track, 2:23:46, 24p /1.001 1: h264/AVC 1080p24 /1.001 (16:9) 2: AC3, English 5.1 channels, 640kbps, 48khz, dialnorm: -27dB 3:Subtitle (PGS), English |
|
22nd September 2009, 17:47 | #5317 | Link | ||
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
Quote:
Last edited by jdobbs; 22nd September 2009 at 17:50. |
||
22nd September 2009, 23:59 | #5320 | Link | |
Moderator
Join Date: Oct 2001
Posts: 21,092
|
Quote:
In the version I posted yesterday I added an entry in the log that shows the settings at the time the encode is started. If you run into it with that one please post the log so I can tell whether the setting is being read properly from the INI. Where did you install BD Rebuilder (the path)? I worry that Win7 may have some of the quirks that were there with Vista when it was first released -- and when the INI is being read, it is from a virtual location rather than the true one. If you installed in the "Program Files" directory that may be the case. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|