Page 4 of 15

Re: CUDASynth

Posted: Tue Oct 23, 2018 8:27 pm
by admin
Will do. IIRC I have an 800W supply in there. I'm going to install tomorrow morning.

Re: CUDASynth

Posted: Wed Oct 24, 2018 11:12 am
by admin
LOL, it's 850W.

The 2080 Ti install went smoothly. DG tools still working fine. The List GPU dialog shows some weird things, like 0 CUDA cores. I'll have to investigate that. Maybe things need to be rebuilt with a later CUDA toolkit. Will get some preliminary performance numbers shortly.

Re: CUDASynth

Posted: Wed Oct 24, 2018 11:26 am
by admin
Testing 3840x2160 HDR -> SDR script with pipeline:

1080 Ti runs at 180 fps.
2080 Ti runs at 321 fps. 338 fps with moderate overclocking.

That is a hefty performance boost. :wow:

It seems they did some great work on the video engine.

Now I have to decide whether to keep the 1080 TI in this machine as well, or upgrade my backup PC. Putting it in this machine will allow more fun things to play with, such as encoding on the second card, etc.

Christmas came early. ;)

Re: CUDASynth

Posted: Wed Oct 24, 2018 3:41 pm
by Guest
Could you check the encoding features for HEVC (such as B frames) on the RTX 2080ti, please?
And you are right, those are some significant numbers on the fps
Question
If you did keep the GTX 1080ti and the RTX 2080ti in the same system which one would you use for frame serving and which one for encoding

Re: CUDASynth

Posted: Wed Oct 24, 2018 5:23 pm
by admin
I'll look into encoding. I never worked with it but this is a good time to start.

If I keep them both in I can try it both ways for decoding and encoding.

Re: CUDASynth

Posted: Wed Oct 24, 2018 10:46 pm
by admin
After further testing it appears that the large gain is due to the very fast memory on the 2080 Ti and not due to the video engine. The large gain is seen only for the pipeline and not when the frames are always transferred back to the CPU. So the faster memory copies to/from the GPU pipeline buffers must be the relevant factor.

Re: CUDASynth

Posted: Sun Nov 11, 2018 5:29 pm
by Guest
Some new info, for me anyways, on the RTX 2080ti's capabilities
https://developer.nvidia.com/video-enco ... ort-matrix
Please note the new capabilities in the Decode section
Will require a new SDK which hasn't been released yet

Re: CUDASynth

Posted: Sun Nov 11, 2018 6:47 pm
by admin
Interesting, thanks for the link!

Avisynth Neo

Posted: Fri Dec 14, 2018 5:35 am
by Guest 2
I've just seen this: https://github.com/nekopanda/AviSynthPl ... isynth-Neo.

What do you think about it?

Re: CUDASynth

Posted: Fri Dec 14, 2018 6:32 am
by admin
I can't read Japanese so can't make much out of it.

Re: CUDASynth

Posted: Fri Dec 14, 2018 6:40 am
by Guest 2
admin wrote:
Fri Dec 14, 2018 6:32 am
I can't read Japanese so can't make much out of it.
It's a fork of AviSynth+ with CUDA support. I read it thru Google Translate service.

Re: CUDASynth

Posted: Fri Dec 14, 2018 11:02 am
by admin
OK, but what does "with CUDA support" actually mean?

Re: CUDASynth

Posted: Wed Mar 06, 2019 2:31 am
by hydra3333
OK, now I'm an old guy who is officially lost and asking for directions.

I'm looking for latest CUDAsynth downloads and I guess AvsCompat.dll as well, per these,
viewtopic.php?f=14&t=506&p=9119&hilit=AvsCompat#p9119
gonca wrote:
Thu Nov 08, 2018 4:49 am
hydra3333 wrote:
Wed Nov 07, 2018 11:30 pm
I seem to recall something about a custom avscompat.dll for vapoursynth ... is one needed ?
For the normal DGIndexNV and DGDecodeNV no
For the CudaSynth versions one will be needed
admin wrote:
Wed Oct 17, 2018 4:43 pm
Meanwhile, on the CUDASynth front, I have discovered some very interesting things focused around what Prefetch() does in Avisynth+, and what the PREFETCH macro does in Vapoursynth, and how they interact with CUDASynth. It opens a possible avenue for further performance gains. I'll write a post about it when I get an energy burst.
A (vapoursynth) patch would likely not be accepted as similar ideas have been rejected. No problem; it's easy to replace AvisynthCompat.dll.
This is the latest stuff I could find from circa 9/10/2018:
viewtopic.php?f=14&t=671&hilit=AvsCompat&start=60#p9016
http://rationalqm.us/misc/CUDASynth_0.2.rar
which had it's own (older?) DLL versions
DGDecodeNV
DGHDRtoSDR
DGPQtoHLG
DGSharpen

Other downloads ?which seem to not be "CUDASynth enabled"? include
dgdecnv2053.zip
http://rationalqm.us/hdr/DGHDRtoSDR_1.11.rar
http://rationalqm.us/misc/DGPQtoHLG_1.0.rar

Hence, may I enquire about the latest status and plans ?

Re: CUDASynth

Posted: Wed Mar 06, 2019 8:30 am
by admin
Thank you for your interest. I'll come back to this after dealing with a couple issues I have in DGDecNV.

Re: CUDASynth

Posted: Wed Mar 06, 2019 12:40 pm
by hydra3333
Sounds like a plan, first things first.

Like, I thought I'd retired but now I'm back at work for a while ... one does what one has to ;) :? :wow: :o :shock: :facepalm:

Re: CUDASynth

Posted: Wed Mar 06, 2019 12:47 pm
by admin
hydra3333 wrote:
Wed Mar 06, 2019 12:40 pm
one does what one has to
Definition of a responsible person. Congratulations!

Re: CUDASynth

Posted: Wed May 15, 2019 10:56 pm
by hydra3333
:) Just wondering, is there perhaps enough customer interest in CUDAsynth to consider taking it further ?

Re: CUDASynth

Posted: Thu May 16, 2019 5:29 am
by Guest
hydra3333 wrote:
Wed May 15, 2019 10:56 pm
:) Just wondering, is there perhaps enough customer interest in CUDAsynth to consider taking it further ?
+1

Re: CUDASynth

Posted: Thu May 16, 2019 8:48 pm
by admin
"customer"? Don't you mean "donor"? ;)

Not too much traction for the idea, I'm afraid. Nobody cares about performance anymore?

I'll come back to it, but right now I have a physics paper in the works.

Speaking of traction, see here. I've been cited in an influential place. Arthur Fine is a monumental figure in quantum foundations.

https://plato.stanford.edu/entries/qt-epr/

Re: CUDASynth

Posted: Thu May 16, 2019 10:04 pm
by admin
Bullwinkle fell asleep. Everyone needs a rest. Wheee!

Re: CUDASynth

Posted: Tue May 21, 2019 10:00 pm
by hydra3333
Graft, D. A., 2016, “ Clauser-Horne/Eberhard inequality violation by a local model”, Advanced Science, Engineering and Medicine, 8: 496–502.
Nice work, Sir.
(I cited without reading, on the basis of not smart enough to comprehend it :))

Re: CUDASynth

Posted: Tue May 21, 2019 10:49 pm
by admin
I'm sure you're smart enough; it's just a matter of studying the field first to avoid common errors.

That paper is probably my favorite. The idea hit me in the middle of coaching a swimming workout, and I developed the math on the back of the whiteboard while people were swimming a set. They asked me why I was suddenly in such a good mood! Just refuted a large number of experiments purporting to prove quantum nonlocality.

I'm going to do something about TrueHD demuxing then I will come back to CUDASynth. I can do it in parallel with my current physics paper. It's about EPR steering and Luders projection. Whee!

Re: CUDASynth

Posted: Sat Aug 03, 2019 12:55 pm
by admin
I'm back to CUDASynth for a while. I had to update everything because the CUDASynth DGDecodeNV was at 253.0.0.158 and current DGDecNV is 2053.0.0.179. Note that the DGHDRtoSDR used below is 1.11 and needs to be upgraded to 1.12.

Here is a test script:

loadplugin("D:\Don\Programming\C++\Avisynth filters\CUDASynth\DGDecodeNV\x64\release\dgdecodenv.dll")
loadplugin("d:\don\Programming\C++\avisynth filters\CUDASynth\DGHDRtoSDR\x64\release\dghdrtosdr.dll")
dgsource("LG Chess 4K Demo.dgi",fulldepth=true,fdst="gpu0")
dghdrtosdr(impl="255",light=250,fsrc="gpu0",fdst="gpu1",fulldepth=true)
dgdenoise(fsrc="gpu1",fdst="gpu0",chroma=true)
dgsharpen(fsrc="gpu0")
trim(0,999)

For non-CUDASynth operation all fsrc and fdst are replaced with "cpu".

Here are the test results showing a very healthy FPS improvement of x3.6 , enough to make the difference between non-real-time and real-time playback:

-----
D:\Don\Programming\C++\Avisynth filters\CUDASynth\CUDASynth Test 1>avsmeter64 "LG Chess 4K Demo - No CudaSynth.avs"

AviSynth+ 0.1 (r2728, MT, x86_64) (0.1.0.0)

Number of frames: 1000
Length (hh:mm:ss.ms): 00:00:16.683
Frame width: 3840
Frame height: 2160
Framerate: 59.940 (60000/1001)
Colorspace: YUV420P16

Frames processed: 1000 (0 - 999)
FPS (min | max | average): 8.496 | 30.45 | 27.05
Memory usage (phys | virt): 316 | 1362 MiB
Thread count: 19
CPU usage (average): 12%

Time (elapsed): 00:00:36.974

D:\Don\Programming\C++\Avisynth filters\CUDASynth\CUDASynth Test 1>avsmeter64 "LG Chess 4K Demo.avs"

AviSynth+ 0.1 (r2728, MT, x86_64) (0.1.0.0)

Number of frames: 1000
Length (hh:mm:ss.ms): 00:00:16.683
Frame width: 3840
Frame height: 2160
Framerate: 59.940 (60000/1001)
Colorspace: YUV420P16

Frames processed: 1000 (0 - 999)
FPS (min | max | average): 54.09 | 103.0 | 97.40
Memory usage (phys | virt): 316 | 1356 MiB
Thread count: 19
CPU usage (average): 12%

Time (elapsed): 00:00:10.267
-----

Re: CUDASynth

Posted: Sat Aug 03, 2019 3:12 pm
by Guest
Do you still have your 1080ti lying around?
Would be interesting to see two card performance if possible

Re: CUDASynth

Posted: Sun Aug 04, 2019 5:53 am
by admin
I don't have a system that properly supports two cards.