If there isn't a option then it's not supported, StaxRip supports 100% of all available switches of x265, NVEncC and QSVEncC.Hi everyone! I'm trying to convert a h264 mkv video to h265 mkv, i'm using last build StaxRip and nvenc with my gtx 970. I want to encode to main 10 profile 10 bits, but i don't find where set this...
It's not available for x64 so can't be used in StaxRip.Anyone knows how to add a filter called "asharp" to StaxRip!?
+ Reply to Thread
Results 121 to 141 of 141
Staxrip supports 10bit x264 and bit x265.
But for somereason its in a different menu then the usuall codec one.
Its also not in the staxrip itself preference.
I know its true but cant say where exactly.
To my nusance I forgot and then postponed my converting.
The option really does seem to be hidden for god knows why.
Also, over at handbrake they release a x265 bit 12 dll file wich only works with handbrake nightly.
Sadly on for 64bit as 32 bit has a memory problem.
Also I read ffdshow is 12bit capable both reading and writing. Encoding did have low amount of parameters....
x264 10-Bit is rather new so you might need the latest test build.
It's for both codecs in the exact same location:
x264 options > Basic tab > Depth
x265 options > Basic tab > Depth
My support refers always to the last test build.
Last release had too many and big issues so I made a new release hoping for more luck:
- added new QSVEncC switches
- added support to use network drive as temp folder
- added yadifmod for VapourSynth. Due to popular request I didn't reset the filter profiles, to make the default filter profile for yadifmod available the filter profiles must be manually reset in the filter profile editor.
- added new command SaveJpgByPath to preview dialog which can be used to customize the menu to save a jpg file to a fixed path without the file browser showing, the path can contain macros.
- added taskbar progress support
- fixed the check for enough free space on the disk of the target file, instead of three times the source file one time is now enough
- fixed crash StaxRip checking for enough free space in file batch mode and if target directory is network share
- fixed Umlaute don't work on Windows 7
- fixed many avs/vs scripts are created when the target file name is changed by typing
- fixed feature to run jobs in new instance and changed the behaviour of this feature in that when the jobs complete the instance exits without overwriting the settings
- QSVEncC 2.51
- yadifmod (VapourSynth) r9
Is there any trick how to start StaxRip 1.3.7. other than unpack and run?
Starting with version 1.3.4. it does not work on my Win7 Pro x64 any more.
Is there any cure or do I need to install some libraries here?
1.1.9, 1.3.1 and 1.3.2. all work no problems.
List of files in "root" folder of the archive contains several DLLs now - that was not the case in the past with Stable archives.
Also there is a LICENSE.TXT file with profanities, something that did not exist in earlier versions of StaxRip.
Thanks for considering this question and let me know do I need to upload certain log files etc for your reference.
The stack trace was enough to tell me what's wrong, the root problem is the settings file deserialization (loading) fails, there is exception handling implemented which is supposed to load the default settings but it's buggy due to .NET unable to call TaskDialog from the main form constructor. You have to delete the settings file or wait for the next build which will reset the settings to defaults. I cannot tell you why the file don't load, maybe it's corrupted, according to missing reports and personal experience it's something that happens extremely rarely.
Has anyone got even close to X265 CPU Encoding using X265 NVEnc? I use 10bit X265CPU Encoding with Stax and get fantastic quality & small filesize (to me the whole point of X265) but with NVEnc I find I have to more than double the bitrate to get similar results which also results in a much larger filesize. My frustration is that I have a GTX 1060 Extreme which can plough through at 800 Frames Per Minute on NVenc and an I7 at 10 Frames Per Minute, it would seem that there is no middle ground that can be reached? I see that 10bit is now available with NVEnc but cannot find that option in Stax? Just after everyone's personal opinion/experience on this?
I'm still breaking, trying to learn dancing and flying, trying to learn to read and write real and differ rent code and mails, Big ups to the VideoHelp and doom9 community helping to evolve our tools and the things we love.
126.96.36.199 unstable test build:
nnedi3 (avs) 0.9.4.31
VC++ Runtime 2015
L-Smash-Works (avs/vs) 911
yadifmod2 (avs) 0.0.4-1
KNLMeansCL (avs/vs) 0.7.7
nnedi3 (vs) 10
mvtools2 (avs) 188.8.131.52
MP4Box 0.6.2 current snapshot
I've been using StaxRip for a while now to convert my video library to HEVC using the NvEnc video encoder and think it's great.
However, I'm stuck on something. Hopefully the answer is easy (?) - I would like to use the tool to point at folders of videos of varying bitrates and say, "convert these to HEVC using VBR2, set bitrate to 50% of source bitrate". I see menu items like "50% / 60%" under Size in the GUI, but they're always greyed out, even for CBR and CQP? I've given up on that.
Now I'm looking at adding a CSX script to just jam the bitrate onto to the encoder command-line using app.ImportVideoEncoderCommandLine("--vbr2 NNNN"); But somehow I need to read in the source video bitrate before I can format the string NNNN to. I think I see how GlobalClass & GlobalCommands are mapped to the Scripting.App object, but can't find a method to read the video bitrate so that I can do some math on it, etc.
Am I going about this wrong? Are there any more extensive examples available somewhere? Is there an easier way?
Thanks to anyone who can help and thanks for creating this nice tool, Stax76.
Doesn't %video_bitrate% macro in Filter Profiles do what you wish ?
Ideally I'd get this as a parsed native integer ready for math and not a "15 MB" or other MediaInfo display string that I'd have to evaluate. (?)
Perhaps you could extract it from the Staxrip_log that is created for each new source, which contains a field such as
Bit rate : 3 237 Kbps
StaxRip a bit and %media_info_video:BitRate% should work but doesn't. My guess is that this is because macros resolve before the file is loaded. However this doesn't make sense since it would make the whole %media_info_% set of macros useless.
@Stax, any suggestions?
EDIT: Ok, I figured this part out. The first parameter to Scripting.App.WriteLog() is a header field, which doesn't get macro processing. Calling Scripting.App.WriteLog("BitRate", "Video BitRate = %media_info_video:BitRate%"); returns a nice, easily parsible string. Also only triggering the script on event 'Before Project Encoding' helps too
UPDATE: Ok, this is really weird. The following script:
dynamic app = Scripting.App; string bitRate = "%media_info_video:BitRate%"; app.WriteLog("BitRate", "input rate=" + bitRate); for (int i = 0; i < bitRate.Length; i++) app.WriteLog("BitRate", "i=" + i + " = " + bitRate[i]); int rate; bool result = System.Int32.TryParse(bitRate, out rate); app.WriteLog("BitRate", result ? "success" : "fail"); app.WriteLog("BitRate", "parsed rate=" + rate); rate = rate / 2; app.WriteLog("BitRate", "new rate = " + rate.ToString());
[...] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Process Event Command 'BitRate' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Event: Before Project Encoding Command: ExecuteScriptFile Parameter File Path: C:\Users\Dave.GEISEFAMILY\Desktop\BitRate.csx -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- BitRate -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- input rate=4572688 i=0 = % i=1 = m i=2 = e i=3 = d i=4 = i i=5 = a i=6 = _ i=7 = i i=8 = n i=9 = f i=10 = o i=11 = _ i=12 = v i=13 = i i=14 = d i=15 = e i=16 = o i=17 = : i=18 = B i=19 = i i=20 = t i=21 = R i=22 = a i=23 = t i=24 = e i=25 = % fail parsed rate=0 new rate = 0 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Script -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- [...]
Last edited by Encoder; 23rd Nov 2016 at 23:03.
I'm trying to use the 184.108.40.206 unstable test build with VapourSynth. I clicked download in StaxRip and it had me download VapourSynth 35. After installing VS, StaxRip said that the VapourSynth dll had to be in \core64 but there is only a \core32 folder.
Then I see that VapourSynth 34 is bolded in the release notes, so I downloaded 34. It too only has a \core32 folder and not a \core64 folder.
Brilliant software and thank you for keeping it up to date, used a few times now with no issues at all