StaxRip

[stax76]

About

StaxRip is a video encoding GUI for Windows, it executes and controls console apps like x265, NVEnc, mkvmerge or ffmpeg and uses the scripting based frame servers AviSynth and VapourSynth for video processing.


Website

https://github.com/staxrip/staxrip

[Groucho2004]

Originally Posted by stax76

• All AviSynth plugins except ffms2 and l-smash are gone

Why? There are quite a number of working 64 Bit plugs, see here for example.

Originally Posted by stax76

The latest AviSynth+ binary build is here:
http://forum.doom9.org/showthread.ph...70#post1711770

Nope, the latest builds are here.

[stax76]

I've not known this links so thanks again, did you notice AVSMeter x64 is included (Tools/Advanced/AVSMeter)?

[Groucho2004]

Originally Posted by stax76

I've not known this links so thanks, did you notice AVSMeter x64 is included (Tools/Advanced/AVSMeter)?

I don't use GUIs so I did not download it. However, quite a number of people seem to be using staxrip and this way 64 Bit AVS+ will get a lot more testing.

[NikosD]

Frank, I have sent you an email regarding DSS2 mod which I think it works with x64

[stax76]

Thanks, it works! Next version will have ffms2, l-smash, DSS2, SangNom2, checkmate, RgTools, DGDecNV works and DGDecIM will be integrated shortly.

[NikosD]

Great!

Have you contacted Rigaya for the HW encoders not being able to use AVS with x64 versions ?

[stax76]

I mailed him 22 hours so hope he replies soon otherwise I might have to use piping with ffmpeg meanwhile.

[NikosD]

From your first posts I can see that maybe your decision of abandoning completely the x86 version of a program that is based so much upon Avisynth, is probably rushed.

I think the release of madVR x64 and the obvious weakness of LAV HEVC x86 decoder, have created a "madness" with 64bit version for everything, but that seems to not working so good at the moment.

I suggest to reconsider the maintenance of x86 version, at least on fixing latest bugs and then updating components (apps, filters etc) in the future without adding new features.

At least until StaxRip x64 reaches the functionality of StaxRip x86

[stax76]

For madvr, Firefox and StaxRip this is the year of x64. I'll probably make some 32-Bit maintenance releases.

[huhn]

did your old version used the x265 build with 8 bpp?

[NikosD]

The x86 version had both executables (8bit and 10bit) for both encoders (x264 and x265) and you could select whatever you want for each encoder.

I don't know why Frank decided to include only one executable for each encoder and not both in x64 version.

[huhn]

i was asking about 16bpp or 8bpp. while 10 bit should always be 16bpp you could choice it for 8 bit and the 8bpp version is pretty bad.

[stax76]

The download size and hard drive space is huge, I added new plugins and might be able to restore old plugins because I found 64 bit versions, I've also added xvid encraw and DivX265, AviSynth+ is gonna be 18 MB, so altogether it's 70 MB now. The source is on github now, probably I should give up sourceforge completely, I don't know if github allows that much traffic, many people here use mediafire, mkvtoolnix uses fosshub, maybe BitTorrent could be a way.

What I'll much likely do is allow tools not used being deleted, I added xvid encraw only because it was requested at least once a week so still used by many people, if people request separate 8-Bit and 10-Bit frequently I have to put it back, the poll showed there are x264 10-Bit users, if I add this people might enable it not even knowing it has little to no hardware support (right?) so I would have to add a warning at least. It's not looking there are many people using x265 8-Bit, HEVC is all about 10-Bit, right?

[huhn]

Originally Posted by stax76

What I'll much likely do is allow tools not used being deleted, I added xvid encraw only because it was requested at least once a week so still used by many people, if people request separate 8-Bit and 10-Bit frequently I have to put it back, the poll showed there are x264 10-Bit users, if I add this people might enable it not even knowing it has little to no hardware support (right?) so I would have to add a warning at least. It's not looking there are many people using x265 8-Bit, HEVC is all about 10-Bit, right?

yes there is liberally no h264 10 bit hardware support,

but nearly all hardware decoder can't decode 16 ref frames so do you have a warning for this too?
just add a (if you didn't already have) presets for devices like megui did. there are multiply settings you can't use for some hardware devices using x264 8 bit.

if someone is changing settings he has to deal with the result no need to hold there hands.

10 bit x264 is used quiet a lot.

some/most decoder can't decode 10 bit HEVC like lentoid or UHDcode. so there is a reason to use 8 bit HEVC but please use the 16 bpp version.

do you think about adding AMD VCE to your hardware decoder list? the people on the OBs forum liked it and i wouldn't be shocked if AMD VCE 2.0 is better than NVenc kampler and haswell.

[NikosD]

Do you know any tool in CLI form that supports VCE ?

[huhn]

Originally Posted by NikosD

Do you know any tool in CLI form that supports VCE ?

sadly no.

but OBS has a version with VCE support and it's open source and the used "encoder" there should be usable for things like staxrip.

using the SDK should be possible too.
http://developer.amd.com/community/b...ng-engine-vce/

[NikosD]

The developer of QSVEncC and NVEncC (rigaya) hasn't built a CLI tool for VCE but only an aviutil plugin - VCEnc.

[burfadel]

What about deinterlacing filters like YADIF, and IVTC processing?

[stax76]

@huhn

There is devices support applying some restrictions, I try to add at least some tooltips and help. I like adding new encoders even with GUI, my design makes this a very very easy task, I'm not really C++ programming (future maybe...) so no AMD support until there is a tool (which I didn't search hard for).

What about deinterlacing filters like YADIF, and IVTC processing?

There is a good chance most comes back in the next release.