Well, I figured I could at least do a quick test using scaling with the driver I have installed (6194), to compare to the 6519 driver.
I added it to the table.
It came in at 493fps (6194) instead of 219fps with the latest driver (6519).
Search found 43 matches
- Sun Feb 17, 2019 10:38 pm
- Forum: Windows
- Topic: Kaby Lake - H.265 (Intel QSV) options vanished/missing
- Replies: 12
- Views: 2601
- Sun Feb 17, 2019 10:29 pm
- Forum: Windows
- Topic: Kaby Lake - H.265 (Intel QSV) options vanished/missing
- Replies: 12
- Views: 2601
Re: Kaby Lake - H.265 (Intel QSV) options vanished/missing
You're right, there was a 720 -> 716 auto-scale that was inadvertent. Since it appears to be resolved in the nightly, I guess it's debatable whether it's worth the effort to repeat the test(s). Since I'd done the testing, I just thought I'd share in case it might indicate something to someone more k...
- Sat Feb 16, 2019 7:28 pm
- Forum: Windows
- Topic: Kaby Lake - H.265 (Intel QSV) options vanished/missing
- Replies: 12
- Views: 2601
Re: Kaby Lake - H.265 (Intel QSV) options vanished/missing
@rollin_eng - each of those pastebin links is an activity log
- Sat Feb 16, 2019 6:23 am
- Forum: Windows
- Topic: Kaby Lake - H.265 (Intel QSV) options vanished/missing
- Replies: 12
- Views: 2601
Re: Kaby Lake - H.265 (Intel QSV) options vanished/missing
Mea culpa --- I made a mistake. Either I mixed things up or I just can't reproduce it. The H.265 QSV option actually does disappear in HB as of driver 6291 (the first problematic version) and isn't available with any driver version up through the current version, 6519. (Scratch what I said earlier.)...
- Sun Feb 10, 2019 8:40 am
- Forum: Windows
- Topic: Kaby Lake - H.265 (Intel QSV) options vanished/missing
- Replies: 12
- Views: 2601
Re: Kaby Lake - H.265 (Intel QSV) options vanished/missing
I've noticed that QSV H.265 disappears from HandBrake as of Intel GPU driver v25.20.100.6471, but driver versions prior to that also started dramatically slowing performance, before the QSV H.265 option completely disappeared from HandBrake. Encodes that would typically be 600fps were suddenly encod...
- Thu Dec 24, 2009 6:07 am
- Forum: Development
- Topic: [Patch][WinGUI] AppData for Queue recovery; GUI Version
- Replies: 2
- Views: 755
Re: [Patch][WinGUI] AppData for Queue recovery; GUI Version
There isn't any need for that backwards compatibility code. You don't really want to recover a queue between versions. If you did that between 0.9.3 and 0.9.4 for example, you would probably run into problems. Users can always copy/paste the file if they are feeling dangerous. I wrote the backwards...
- Wed Dec 09, 2009 8:41 pm
- Forum: Development
- Topic: [Patch][WinGUI] AppData for Queue recovery; GUI Version
- Replies: 2
- Views: 755
[Patch][WinGUI] AppData for Queue recovery; GUI Version
1. If Queue recovery is meant to be reliable over time, then using the user's temp folder is risky. The Temp folder can be emptied at any time, and it should not contain data needed over time/reboots. I've created a patch that moves the Queue recovery file from the user's Temp folder to the Applicat...
- Thu Sep 10, 2009 3:12 am
- Forum: Development
- Topic: [Patch] WinGUI - Yet more AutoName fixes
- Replies: 2
- Views: 786
Re: [Patch] WinGUI - Yet more AutoName fixes
The other thought I had after looking at it again is that it would only execute the source scan if (1 <= type <= 3). Is that desirable?
- Wed Sep 09, 2009 7:58 am
- Forum: Development
- Topic: [Patch] WinGUI - Yet more AutoName fixes
- Replies: 2
- Views: 786
[Patch] WinGUI - Yet more AutoName fixes
Patch: http://handbrake.fr/pastebin/pastebin.php?show=852 I encountered a strange scenario where the output file extension would get set to ".". The bottom line is that Main.autoName() shouldn't try to add an extension if there isn't one to add, and frmMain.SetExtension() should change the...
- Wed Sep 09, 2009 5:25 am
- Forum: Development
- Topic: [Patch] WinGUI - CLI output, custom DAR, Queue, Window size
- Replies: 3
- Views: 1128
Re: [Patch] WinGUI - CLI output, custom DAR, Queue, Window size
Brilliant, thank you. One note - It appears on the minimum GUI size the text of the error string wasn't updated to reflect the new 620 height requirement. I realize you could just change the value, but I made a quick patch so as to reformat the string in preferred .NET syntax. Side question - do you...
- Wed Sep 02, 2009 7:18 am
- Forum: Development
- Topic: [PATCH] Fixed width calculation after scan when KeepAR is on
- Replies: 1
- Views: 503
Re: [PATCH] Fixed width calculation after scan when KeepAR is on
I was working on a fix for this, as well as a number of others (see http://forum.handbrake.fr/viewtopic.php?f=4&t=12119), as you posted this. Missed it. I see you calculate the width with CalculateAnamorphicSizes(), then the DAR from that width and the source height, whereas I originally used th...
- Wed Sep 02, 2009 6:19 am
- Forum: Development
- Topic: [Patch] WinGUI - CLI output, custom DAR, Queue, Window size
- Replies: 3
- Views: 1128
[Patch] WinGUI - CLI output, custom DAR, Queue, Window size
Sorry, it's been a while, so not sure if we're using one thread or many these days for WinGUI patches. CLI Output I haven't seen it discussed, but I assume backwards compatibility between the current WinGUI and the 0.9.3 version of the CLI is a low or nonexistent priority, but I thought, at least in...
- Tue Apr 14, 2009 4:33 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
Re: [PATCH] WinGUI Patches
http://handbrake.fr/pastebin/pastebin.php?show=529 A few fixes for destination filenames: Separated the filename from the initial directory before showing the save dialog. This way, even if there is bad or no directory info, the filename is preserved. Changed the check for the destination path. With...
- Mon Mar 30, 2009 9:59 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
Re: [PATCH] WinGUI Patches
http://handbrake.fr/pastebin/pastebin.php?show=508
The default psy-rd value is 1.0. This patch sets the GUI slider to the default (10 for the slider) so it matches the text display when no psy-rd value is specified.
The default psy-rd value is 1.0. This patch sets the GUI slider to the default (10 for the slider) so it matches the text display when no psy-rd value is specified.
- Tue Mar 17, 2009 12:07 am
- Forum: Feature Requests
- Topic: Accurate target bitrates
- Replies: 6
- Views: 1477
Re: Accurate target bitrates
Regardless of what I want, it seems logical that everyone involved in the project would like the software to be useful beyond for themselves, for as many people as possible. This is a patch that increases HB's utility for a much wider audience. Regardless of what I say, I'm hoping that fact influen...
- Sun Mar 15, 2009 11:25 pm
- Forum: Feature Requests
- Topic: Accurate target bitrates
- Replies: 6
- Views: 1477
Re: Accurate target bitrates
I started another thread because you seemed like you had something to say and didn't want to derail the other thread. You said the patch hasn't gone in because you hadn't gotten around to it, because HB is going in a different direction. I have no idea when or if that means the patch will be impleme...
- Sun Mar 15, 2009 1:46 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
Re: WinGui: Small icon for Queue window Re-Add Current Job
Absolutely, I will bundle the small stuff in future. I tried to bundle the related matters, and this probably should have gone in my other thread. Some development communities prefer to keep separate issues, no matter how small, completely separate, and others want to keep the proliferation of threa...
- Sun Mar 15, 2009 1:38 am
- Forum: Feature Requests
- Topic: Accurate target bitrates
- Replies: 6
- Views: 1477
Re: Accurate target bitrates
I totally understand - I mention in my post that it is simply a matter of appreciation for anything that can be done. I'm new here, so I don't know what the motivation is for HB to move toward CRF encodes, as jbrbrake mentioned. Since I was inadvertently hijacking the other thread, when it seemed jb...
- Sun Mar 15, 2009 1:31 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
WinGui: Small icon for Queue window Re-Add Current Job
Since 'Re-Add Current Job' in the Queue window was moved from a button to a menu item (a good change, IMO) I created a 16x16 version of the 'Add to Queue' icon to include on the menu. http://i63.photobucket.com/albums/h145/exdeus/HB/AddToQueue_small.png s55, is it something you could add to the Reso...
- Sun Mar 15, 2009 1:24 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
[PATCH] WinGui: Prompt to confirm GUI closing
I wrote a patch to prompt the user to confirm closing the GUI if the queue is processing jobs. http://handbrake.fr/pastebin/pastebin.php?show=496 I got so used to closing the Queue window without consequences, that sometimes I close the HB GUI when I want it to remain open to continue processing the...
- Sun Mar 15, 2009 1:12 am
- Forum: Development
- Topic: [PATCH] WinGUI Patches
- Replies: 35
- Views: 4065
[PATCH] WinGui: Correct destination filename & other cleanup
Three changes included. I've bundled them because really only #2 is a material change. http://handbrake.fr/pastebin/pastebin.php?show=495 As ordered in the diff: 1. Remove a duplicate call to setQueue() before showing the Queue window - this is now done in frmQueue.Show(). 2. Rather than taking the ...
- Sun Mar 15, 2009 1:01 am
- Forum: Feature Requests
- Topic: Accurate target bitrates
- Replies: 6
- Views: 1477
Accurate target bitrates
To not hijack another's topic, I'm breaking this off from another thread . http://forum.handbrake.fr/viewtopic.php?p=52290#p52290 As far as the bitrate thing....you're using same as source fps and detelecine. When fps varies you of course can't accurately predict the framerate before you start, so t...
- Sun Mar 15, 2009 12:15 am
- Forum: Windows
- Topic: Encoding To MKV: Not exact size, and only 1 audio track?
- Replies: 9
- Views: 2250
Re: Encoding To MKV: Not exact size, and only 1 audio track?
There is no way you can seriously tell me you *know* your source actually is going to come out at 23.976 short of encoding it. Allowing VFR is a valid point - on a set of encodes, I know the average framerate will turn out to be ~23.976fps, but that wouldn't allow for VFR. I'm not going to take you...
- Fri Mar 13, 2009 10:50 pm
- Forum: Windows
- Topic: Encoding To MKV: Not exact size, and only 1 audio track?
- Replies: 9
- Views: 2250
Re: Encoding To MKV: Not exact size, and only 1 audio track?
As far as the bitrate thing....you're using same as source fps and detelecine. When fps varies you of course can't accurately predict the framerate before you start, so the FPS handed off to x264 is an estimate. In this same scenario, if I know my content will be IVTC'ed to 23.97fps, does selecting...
- Thu Mar 12, 2009 6:19 am
- Forum: General Questions
- Topic: HandBrake equivalent to AviSynth FieldDeinterlace()
- Replies: 14
- Views: 2665
Re: HandBrake equivalent to AviSynth FieldDeinterlace()
Doing frame by frame comparisons of your test encodes, I think you're seeing some container-induced jerkiness from MKV. I will try out an MP4 in one of players you suggested. Just testing MPC-HC already makes a difference. I think playback is smoother. I should've tested other players earlier. One ...