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.

 

Go Back   Doom9's Forum > (HD) DVD, Blu-ray & (S)VCD > DVD & BD Rebuilder

Reply
 
Thread Tools Search this Thread Display Modes
Old 19th April 2017, 11:49   #25841  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 948
@Lathe
Quote:
Mr. Anal,... cracks
You are trying to make it easy
gonca is offline   Reply With Quote
Old 19th April 2017, 16:20   #25842  |  Link
Denner
Registered User
 
Join Date: Feb 2008
Posts: 64
Quote:
Originally Posted by Taurus View Post
@ Denner:
Please share your insight.
I'm about to buy a Ryzen and everything cleared beforehand
is stopping me from wasting time on experiments.
Thank you.
I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it

You can find the version here:https://www.videohelp.com/software/B...r/old-versions
Denner is offline   Reply With Quote
Old 19th April 2017, 16:23   #25843  |  Link
Denner
Registered User
 
Join Date: Feb 2008
Posts: 64
Quote:
Originally Posted by Lathe View Post
Wow, dude that REALLY is fast! Getting that speed using the ridiculously ultra-slow setting is bloody amazing! I just use the 'High' setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, granted, with a couple of x264 'tweaks' on the 2nd pass I MIGHT get like 5 or 6 fps, usually slower... I guess that's what 8 frigg'n smok'n cores will do for you

Yup the power of a Ryzen 1700 overclocked to 3.8 GHz, love this CPU, easiest overclock I ever did
Denner is offline   Reply With Quote
Old 19th April 2017, 19:26   #25844  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 567
Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?
mparade is offline   Reply With Quote
Old 19th April 2017, 19:43   #25845  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,394
Quote:
Originally Posted by mparade View Post
Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?
Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 19th April 2017, 20:00   #25846  |  Link
mparade
Registered User
 
Join Date: Nov 2013
Posts: 567
Quote:
Originally Posted by jdobbs View Post
Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.
Sorry...I left IVTC turned on in the setup dialog. I thought it had no effect on pure progressive content at all. But now, I see.
mparade is offline   Reply With Quote
Old 19th April 2017, 21:43   #25847  |  Link
Yordan5
Registered User
 
Join Date: Aug 2010
Posts: 72
Quote:
Originally Posted by Denner View Post
I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it

You can find the version here:https://www.videohelp.com/software/B...r/old-versions
Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.

Last edited by Yordan5; 20th April 2017 at 07:36.
Yordan5 is offline   Reply With Quote
Old 20th April 2017, 08:26   #25848  |  Link
Lathe
Registered User
 
Lathe's Avatar
 
Join Date: Aug 2005
Posts: 984
Quote:
Originally Posted by gonca View Post
@Lathe

Quote:
Mr. Anal,... cracks

You are trying to make it easy
You ask, you plead, you beg, and this is what you get...


Lathe is offline   Reply With Quote
Old 20th April 2017, 08:37   #25849  |  Link
Lathe
Registered User
 
Lathe's Avatar
 
Join Date: Aug 2005
Posts: 984
Quote:
Originally Posted by Yordan5 View Post
Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.
That's about what mine runs at the same setting. If I add a couple of x264 'tweaks', it might take a bit longer.

JD, do YOU recommend replacing the current BDRB version with this particular version of x264 (BDRB 5011) and renaming it as suggested above?
Lathe is offline   Reply With Quote
Old 21st April 2017, 19:59   #25850  |  Link
Thaddäus
Registered User
 
Join Date: Jun 2016
Posts: 8
I've been using BD Rebuilder for many discs during the last months and recognized that there's always more than 1 GB space left on a BD25 when I'm using the BD25 target size-preset. Sometimes there's even more left - last week I tried a backup of "Deepwater Horizon" and the output-size was only 20,9 GB so 10% of the disc space (should be around 23,1 GB) is still free.

Has someone tested BD Rebuilder with a custom-target size to use the whole capacity of a BD25? I'm using the highest quality-settings and two pass-encoding, so BD Rebuilder should be able to calculate the optimal bitrate and make the most of the availiable space. I'm only keeping the German and English audio-tracks in HD (if availiable) and do a backup of the full disc with all bonus features. I read about the problem in other boards and they were discussing that deleting some audio tracks can result in miscalculation of the target size. But in the case of "Deepwater Horizon" those two were the only audio-tracks availiable, so that can't be the reason for that big miscalculation BD Rebuilder did. Did someone recognize similar problems and is there a workaround for this (maybe a certain custom target size) to get the best results possible?

EDIT: Don't know if it's going to help but here's the logfile of my "Deepwater Horizon"-backup

Code:
----------------------
[04.16.17] BD Rebuilder v0.50.23
[12:28:07] Source:  DEEPWATER_HORIZON
  - Input BD size: 45,62 GB
  - Approximate total content: [04:20:30.916]
  - Target BD size: 22,95 GB
  - Windows Version: 6.2 [9200]
  - Quality: Highest (Very Slow), Two Pass
  - Decoding/Frame serving: DirectShow
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:28:07] PHASE ONE, Encoding
 - [12:28:07] Processing: VID_00005 (1 of 15)
 - [12:28:07] Extracting A/V streams [VID_00005]
 - [12:28:17] Reencoding video [VID_00005]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 24,000fps, 2.193 frames
   - Bitrate: 11.316 Kbs
 - [12:28:17] Reencoding: VID_00005, Pass 1 of 2
 - [12:28:41] Reencoding: VID_00005, Pass 2 of 2
 - [12:30:27] Video Encode complete
 - [12:30:27] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [12:30:27] Multiplexing M2TS
 - [12:30:33] Processing: VID_00006 (2 of 15)
 - [12:30:33] Extracting A/V streams [VID_00006]
 - [12:30:46] Reencoding video [VID_00006]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 24,000fps, 3.373 frames
   - Bitrate: 11.640 Kbs
 - [12:30:46] Reencoding: VID_00006, Pass 1 of 2
 - [12:31:23] Reencoding: VID_00006, Pass 2 of 2
 - [12:34:12] Video Encode complete
 - [12:34:12] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [12:34:12] Multiplexing M2TS
 - [12:34:17] Processing: VID_00007 (3 of 15)
 - [12:34:17] Extracting A/V streams [VID_00007]
 - [12:34:29] Reencoding video [VID_00007]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 24,000fps, 3.332 frames
   - Bitrate: 11.634 Kbs
 - [12:34:29] Reencoding: VID_00007, Pass 1 of 2
 - [12:35:03] Reencoding: VID_00007, Pass 2 of 2
 - [12:37:54] Video Encode complete
 - [12:37:54] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [12:37:54] Multiplexing M2TS
 - [12:38:00] Processing: VID_00021 (4 of 15)
 - [12:38:00] Extracting A/V streams [VID_00021]
 - [12:52:40] Reencoding video [VID_00021]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 24,000fps, 155.028 frames
   - Bitrate: 4.059 Kbs
 - [12:52:40] Reencoding: VID_00021, Pass 1 of 2
 - [13:21:01] Reencoding: VID_00021, Pass 2 of 2
 - [14:46:33] Video Encode complete
 - [14:46:33] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
   - Track 4353 (eng): Keeping original audio
 - [14:46:33] Multiplexing M2TS
 - [14:51:41] Processing: VID_00101 (5 of 15)
 - [14:51:41] Extracting A/V streams [VID_00101]
 - [14:53:50] Reencoding video [VID_00101]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 73.335 frames
   - Bitrate: 5.650 Kbs
 - [14:53:50] Reencoding: VID_00101, Pass 1 of 2
 - [15:05:52] Reencoding: VID_00101, Pass 2 of 2
 - [15:49:51] Video Encode complete
 - [15:49:52] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [15:49:52] Multiplexing M2TS
 - [15:50:21] Processing: VID_00102 (6 of 15)
 - [15:50:21] Extracting A/V streams [VID_00102]
 - [15:51:05] Reencoding video [VID_00102]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 26.229 frames
   - Bitrate: 6.615 Kbs
 - [15:51:05] Reencoding: VID_00102, Pass 1 of 2
 - [15:55:28] Reencoding: VID_00102, Pass 2 of 2
 - [16:12:39] Video Encode complete
 - [16:12:39] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [16:12:39] Multiplexing M2TS
 - [16:12:53] Processing: VID_00103 (7 of 15)
 - [16:12:53] Extracting A/V streams [VID_00103]
 - [16:13:40] Reencoding video [VID_00103]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 24.797 frames
   - Bitrate: 6.636 Kbs
 - [16:13:40] Reencoding: VID_00103, Pass 1 of 2
 - [16:17:45] Reencoding: VID_00103, Pass 2 of 2
 - [16:33:31] Video Encode complete
 - [16:33:31] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [16:33:31] Multiplexing M2TS
 - [16:33:46] Processing: VID_00104 (8 of 15)
 - [16:33:46] Extracting A/V streams [VID_00104]
 - [16:34:52] Reencoding video [VID_00104]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 39.288 frames
   - Bitrate: 5.650 Kbs
 - [16:34:52] Reencoding: VID_00104, Pass 1 of 2
 - [16:40:57] Reencoding: VID_00104, Pass 2 of 2
 - [17:03:25] Video Encode complete
 - [17:03:25] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [17:03:25] Multiplexing M2TS
 - [17:03:47] Processing: VID_00105 (9 of 15)
 - [17:03:47] Extracting A/V streams [VID_00105]
 - [17:04:27] Reencoding video [VID_00105]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 23.385 frames
   - Bitrate: 5.656 Kbs
 - [17:04:27] Reencoding: VID_00105, Pass 1 of 2
 - [17:07:52] Reencoding: VID_00105, Pass 2 of 2
 - [17:20:36] Video Encode complete
 - [17:20:37] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [17:20:37] Multiplexing M2TS
 - [17:20:51] Processing: VID_00106 (10 of 15)
 - [17:20:51] Extracting A/V streams [VID_00106]
 - [17:21:01] Reencoding video [VID_00106]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 24,000fps, 3.030 frames
   - Bitrate: 5.386 Kbs
 - [17:21:01] Reencoding: VID_00106, Pass 1 of 2
 - [17:21:33] Reencoding: VID_00106, Pass 2 of 2
 - [17:23:19] Video Encode complete
 - [17:23:19] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:23:19] Multiplexing M2TS
 - [17:23:24] Processing: VID_00401 (11 of 15)
 - [17:23:24] Extracting A/V streams [VID_00401]
 - [17:23:32] Reencoding video [VID_00401]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 25,000fps, 2.204 frames
   - Bitrate: 5.388 Kbs
 - [17:23:32] Reencoding: VID_00401, Pass 1 of 2
 - [17:23:55] Reencoding: VID_00401, Pass 2 of 2
 - [17:25:03] Video Encode complete
 - [17:25:03] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:25:03] Multiplexing M2TS
 - [17:25:08] Processing: VID_00402 (12 of 15)
 - [17:25:08] Extracting A/V streams [VID_00402]
 - [17:25:17] Reencoding video [VID_00402]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 25,000fps, 3.384 frames
   - Bitrate: 5.385 Kbs
 - [17:25:17] Reencoding: VID_00402, Pass 1 of 2
 - [17:25:57] Reencoding: VID_00402, Pass 2 of 2
 - [17:28:01] Video Encode complete
 - [17:28:01] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:28:01] Multiplexing M2TS
 - [17:28:07] Processing: VID_00403 (13 of 15)
 - [17:28:07] Extracting A/V streams [VID_00403]
 - [17:28:14] Reencoding video [VID_00403]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 25,000fps, 2.162 frames
   - Bitrate: 5.678 Kbs
 - [17:28:14] Reencoding: VID_00403, Pass 1 of 2
 - [17:28:38] Reencoding: VID_00403, Pass 2 of 2
 - [17:29:49] Video Encode complete
 - [17:29:49] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:29:49] Multiplexing M2TS
 - [17:29:54] Processing: VID_00404 (14 of 15)
 - [17:29:54] Extracting A/V streams [VID_00404]
 - [17:30:02] Reencoding video [VID_00404]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 25,000fps, 2.880 frames
   - Bitrate: 5.387 Kbs
 - [17:30:02] Reencoding: VID_00404, Pass 1 of 2
 - [17:30:30] Reencoding: VID_00404, Pass 2 of 2
 - [17:31:58] Video Encode complete
 - [17:31:58] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:31:58] Multiplexing M2TS
 - [17:32:03] Processing: VID_00405 (15 of 15)
 - [17:32:03] Extracting A/V streams [VID_00405]
 - [17:32:14] Reencoding video [VID_00405]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 3.480 frames
   - Bitrate: 6.341 Kbs
 - [17:32:14] Reencoding: VID_00405, Pass 1 of 2
 - [17:32:52] Reencoding: VID_00405, Pass 2 of 2
 - [17:35:22] Video Encode complete
 - [17:35:22] Processing audio tracks
   - Track 4352 (deu): Keeping original audio
 - [17:35:22] Multiplexing M2TS
[17:35:27]PHASE ONE complete
[17:35:27]PHASE TWO - Rebuild Started
 - [17:35:27] Rebuilding BD file Structure
[17:35:37] - Encode and Rebuild complete
[17:35:37] JOB: DEEPWATER_HORIZON finished.

Last edited by jdobbs; 21st April 2017 at 20:24.
Thaddäus is offline   Reply With Quote
Old 21st April 2017, 20:29   #25851  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,394
I haven't had any issues with sizing. But, then again, I never use the "Highest (Very Slow)" setting for encoding. I'm guessing that is the source of the sizing impact. No matter what setting you choose BD-RB will calculate a set of bitrates that is required to fill the target size. It's possible, though, that if you set a higher quality setting, the encoder might reach its maximum quality level and not output at a size that matches the specified bitrate.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 21st April 2017, 20:44   #25852  |  Link
Thaddäus
Registered User
 
Join Date: Jun 2016
Posts: 8
Thanks for your reply!
As you can see it took around 5 hours to do the backup of that disc which had 4:20 h of material on it - so I can't complain about slow encoding even with the "Highest (Very Slow)"-settings.
I just did a scan of the main movie's video bitrate with Bitrate Viewer - and it says the average bitrate is 4.058 kbps which exactly matches BD Rebuilder's calculated bitrate from the logfile. Maybe I'm trying it again with a custom target size of 24500 MB and see what happens.

By the way: Although the bitrate of that backup was quite low BD Rebuilder did a fantastic job when it comes to the picture quality which is still quite good! Wasn't expecting that when I saw the calculated bitrate but that tool keeps still surprising me in a very positive way.
Thaddäus is offline   Reply With Quote
Old 21st April 2017, 23:47   #25853  |  Link
MrVideo
Registered User
 
MrVideo's Avatar
 
Join Date: May 2007
Location: Wisconsin
Posts: 1,590
Quote:
Originally Posted by Thaddäus View Post
By the way: Although the bitrate of that backup was quite low BD Rebuilder did a fantastic job when it comes to the picture quality which is still quite good!
The x264 encoder is a fantastic H.264 encoder, especially when used in two-pass mode.
MrVideo is offline   Reply With Quote
Old 22nd April 2017, 09:11   #25854  |  Link
Lathe
Registered User
 
Lathe's Avatar
 
Join Date: Aug 2005
Posts: 984
Quote:
Originally Posted by Thaddäus View Post
I've been using BD Rebuilder for many discs during the last months and recognized that there's always more than 1 GB space left on a BD25 when I'm using the BD25 target size-preset. Sometimes there's even more left - last week I tried a backup of "Deepwater Horizon" and the output-size was only 20,9 GB so 10% of the disc space (should be around 23,1 GB) is still free.

Has someone tested BD Rebuilder with a custom-target size to use the whole capacity of a BD25? I'm using the highest quality-settings and two pass-encoding, so BD Rebuilder should be able to calculate the optimal bitrate and make the most of the availiable space. I'm only keeping the German and English audio-tracks in HD (if availiable) and do a backup of the full disc with all bonus features. I read about the problem in other boards and they were discussing that deleting some audio tracks can result in miscalculation of the target size. But in the case of "Deepwater Horizon" those two were the only audio-tracks availiable, so that can't be the reason for that big miscalculation BD Rebuilder did. Did someone recognize similar problems and is there a workaround for this (maybe a certain custom target size) to get the best results possible?
Yeah, that is pretty much what most of mine come out to also. Generally if I choose the BD-25 output size, no matter whether I'm using 'Fast' 2 Pass or 'High' 2 Pass, invariably the resulting encodes will be 22.1-22.5, sometimes 22.9. If I am really trying to squeeze an encode where it BARELY will fit, I usually select a custom size of about 23,700. But, even with that, most times the size is still 1 or 1 1.5 Gigs less than a full disc. If it's REALLY pushing it, I will try to go a bit more, but one time I tried 23,800 and it came out just a tad too big.

Of course, I've never been accused of playing with a full disc anyway...
Lathe is offline   Reply With Quote
Old 22nd April 2017, 13:37   #25855  |  Link
gonca
Registered User
 
Join Date: Jul 2012
Location: Scarborough, Canada
Posts: 948
Quote:
playing with a full disc anyway.
yeah, yeah
gonca is offline   Reply With Quote
Old 22nd April 2017, 15:33   #25856  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,394
Quote:
Originally Posted by Lathe View Post
Yeah, that is pretty much what most of mine come out to also. Generally if I choose the BD-25 output size, no matter whether I'm using 'Fast' 2 Pass or 'High' 2 Pass, invariably the resulting encodes will be 22.1-22.5, sometimes 22.9. If I am really trying to squeeze an encode where it BARELY will fit, I usually select a custom size of about 23,700. But, even with that, most times the size is still 1 or 1 1.5 Gigs less than a full disc. If it's REALLY pushing it, I will try to go a bit more, but one time I tried 23,800 and it came out just a tad too big.

Of course, I've never been accused of playing with a full disc anyway...
22.1 to 22.5 would be within the range of correct sizing. As I've said before, that's purposeful because the outer edges of the disc are much more prone to failure/error. By keeping the disc in a smaller size range you are less likely to experience problems. It also keeps me from having to respond to people who think the failed burn is BD-RB's fault. But the 20.9 (as reported) would be outside what should be expected.

Just my opinion/advice, but a disc written to capacity will hold about 23.3GB and that last 1GB (about 4%) or so isn't going to get you a noticeable improvement in quality, especially considering the risk. Of course, as always, I've added the ability to change the target size for anyone who disagrees.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 23rd April 2017, 01:25   #25857  |  Link
nozuul
Registered User
 
Join Date: Apr 2008
Posts: 28
Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.
nozuul is offline   Reply With Quote
Old 23rd April 2017, 02:15   #25858  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,394
Quote:
Originally Posted by nozuul View Post
Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.
You can use the filter editor (see SETUP) to add the tweak filter. Example: Tweak(bright=20). That filter also lets you adjust other parameters such as contrast, hue, and saturation.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net
jdobbs is offline   Reply With Quote
Old 23rd April 2017, 07:46   #25859  |  Link
Lathe
Registered User
 
Lathe's Avatar
 
Join Date: Aug 2005
Posts: 984
Quote:
Originally Posted by jdobbs View Post
22.1 to 22.5 would be within the range of correct sizing. As I've said before, that's purposeful because the outer edges of the disc are much more prone to failure/error. By keeping the disc in a smaller size range you are less likely to experience problems. It also keeps me from having to respond to people who think the failed burn is BD-RB's fault. But the 20.9 (as reported) would be outside what should be expected.

Just my opinion/advice, but a disc written to capacity will hold about 23.3GB and that last 1GB (about 4%) or so isn't going to get you a noticeable improvement in quality, especially considering the risk. Of course, as always, I've added the ability to change the target size for anyone who disagrees.
Yes, I fully agree. It's best not to push it to the outer edges of the disc.
Lathe is offline   Reply With Quote
Old 23rd April 2017, 08:19   #25860  |  Link
Lathe
Registered User
 
Lathe's Avatar
 
Join Date: Aug 2005
Posts: 984
Quote:
Originally Posted by nozuul View Post
Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.
As JD mentions above, 'tweak' is a simple but excellent Avisynth filter to use. I use it a LOT for films where I feel that the contrast could be boosted a little, or the colours need a tad more saturation, etc. Many times if you want to boost the contrast, it naturally also gets brighter, so many times I will boost the contrast and lower the brightness at the same time. You probably already do this, but if you take a small snippet of the film and use an .avs script to preview it, you can tweak it a number of times and change the settings to see how it will look in the final encode. Here are some of the scripts I've used for certain films:

LADY IN THE WATER: (cont=1.2, Sat=1.2) This was one of my very first tries, so I probably overdid it a little But, for me, I just can't stand really washed out looking films and prefer a 'sharper' or more contrasted image. I KNOW videophiles will pale in horror, but that is just my personal taste with some films. I only usually go to the trouble to do it if the print REALLY bugs me.






Another film that was REALLY washed out was 'GODZILLA VS. BIOLLANTE' But, that was likely just due to the film stock used at the time. I used these settings on that print:

Sharpen(.8)
tweak(cont=1.20, bright=-12)

In this case, the film is already pretty bright, but I wanted more sharpness and delineation, so in boosting the contrast I had to lower the brightness. The Avisynth 'sharpness' setting is pretty primitive, so I only use it sparingly. Normally, just using contrast, brightness, and sometimes saturation is enough. Again, this is one of my very first tries at Avisynth; I've since found better 'sharpness' filters.

Other films where I've used Avisynth are 'FORTRESS' & 'THE THIRTEENTH FLOOR'. Both 'DRACULA' (1979) and 'SEA OF LOVE' were SO bloody dark and washed out, that I REALLY had to tweak those two a lot. These were the settings I used for them:

DRACULA: tweak(cont=1.40, bright=1, Sat=1.3, startHue=325, endHue=15, maxSat=75)

SEA OF LOVE: tweak(cont=1.5, bright=-4)

I've probably only done around 12-15 films total.

Last edited by Lathe; 23rd April 2017 at 08:26.
Lathe is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 12:43.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.