Vapoursynth - Page 247

Myrsloik · 3rd February 2025, 09:04

Quote:

Originally Posted by Selur

@Myrsloik: Would be nice if core.text.Text would also support RGBH in the future, atm. it gives:

Code:

vapoursynth.Error: Text: Input clip must be 8..16 bit integer or 32 bit float, passed RGBH

so I have to convert to RGS and back

It's on the todo list. The reason it hasn't happened yet is that only some compilers support half precision types natively (gcc/clang both have the _Float16 and __fp16 extensions at least) and visual studio doesn't.

Software fp16 support is pointless since then single precision would be faster for all processing anyway. At best it would become a performance trap. Internally x86 cpus need to convert everything to single precision anyway.

Myrsloik · 12th February 2025, 09:05

Does anyone still use the Python 3.8 support? Are the windows 7 fanatics still around? It's now been quite a few years since my last check.

_Al_ · 14th February 2025, 01:59

I use 3.8 because of using old opencv before opencv introduced a bug, reading wrong pixel information for a pixel (it is3/4 quadrant of pixel off), and they do not care to fix it. So forced to use older numpy, older python etc.
But do not mind me. Just saying, you do not have to be win7 fanatic to use older version. :-)

12th February 2025, 09:05	#4922 \| Link
Myrsloik Professional Code Monkey Join Date: Jun 2003 Location: Kinnarps Chair Posts: 2,606	Does anyone still use the Python 3.8 support? Are the windows 7 fanatics still around? It's now been quite a few years since my last check. __________________ VapourSynth - proving that scripting languages and video processing isn't dead yet

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

14th February 2025, 01:59	#4923 \| Link
_Al_ Registered User Join Date: May 2011 Posts: 368	I use 3.8 because of using old opencv before opencv introduced a bug, reading wrong pixel information for a pixel (it is3/4 quadrant of pixel off), and they do not care to fix it. So forced to use older numpy, older python etc. But do not mind me. Just saying, you do not have to be win7 fanatic to use older version. :-)