DOWNLOAD > DATV-Easy V2.12

[M0DTS]

I had to update my Nvidia drivers to get the Nvidia encoding to work too.
I was on an old version 476, now on version 527.

Rob

[M0SKM]

My laptop an i7 Gen11 was OK on Nvidea and Intel; although I have since found driver updates for both. My problem is with the standalone C920 option, I understand that Arthur G4CPE has exactly the same issue. We have tried every option and after two or three seconds of running the power pulses on/off continually. At present we have no solution, has anyone else experienced the same?

Steve

[G4KLB]

Hi Clive,

My drivers weren't very old, I used GeForce Experience to update them.

[PE5PVB]

I tested 4k, but output resolution still is at 1920x1080 and no video.

[g0mjw]

Note you can't generate 4k unless you have a 4k input and that means setting that up in OBS or VMIX.

A 4k capability is not mentioned in the manual, but then neither is HD or 720p. In any case, trying to squeeze 4k into 333ks is in my experience not particularly pretty for moving images and it needs 1Mb/s or more to look good and quite a lot of processing power, ideally a recent GPU. At lower SRs, although the resolution is high, so are the artefacts, unless you are sending a talking head type image and sit still, but that then shows signs of aging better which might not be what we want. Lower resolutions, HD or even 720p when sourced from a good camera and lens usually look better than 4k with a standard camera and are easier to encode.

Sending over 1Ms to the Pluto is a bit suspect, the limits of the USB connection. The Lime is OK. At the moment 4k is fun for the more advanced operators to play with, but I know what will happen. Those who don't have the technical knowledge yet will try it because it is there and sounds cool, and then get frustrated when it doesn't work very well for them. It might be better to consider separately a "DATV-A-little-bit-more-difficult" experimental branch.

Mike

[K0ZAK]

I have decided to give DATV-Easy V2.12 a try, but I'm having a strange issue with it. When I first load the program, I have both DVB-S & DVB-T options in the mode list. I set it up for DVB-T QPSK and when I try connecting to my Adalm-Pluto with Pluto F5OEO 0201 loaded, LEDs go green momentairily then red again. At that point all the DVB-T modes disappear from the Mode box and will not come back till I delete & reload the program. I've also tried loading earlier versions, V2.08, V2.09 and the same thing happens. My Pluto behaves fine using DATV Express and controlled directly from OBS, so I'm not sure what is going on with DATV-Easy.

I've read all the docs I can find for the different versions of DATV-Easy but can't figure out what I am doing wrong. Figured I'd ask before I strat loading different firmware on the pluto.

John

[PE5PVB]

Ofcourse I set OBS to 4k resolution. Our local repeater has a 2Ms/s input which is capable of 16AFSK, so BW is no problem. I use this often at max bitrate with my LimeSDR in HD.

Note you can't generate 4k unless you have a 4k input and that means setting that up in OBS or VMIX.

A 4k capability is not mentioned in the manual, but then neither is HD or 720p. In any case, trying to squeeze 4k into 333ks is in my experience not particularly pretty for moving images and it needs 1Mb/s or more to look good and quite a lot of processing power, ideally a recent GPU. At lower SRs, although the resolution is high, so are the artefacts, unless you are sending a talking head type image and sit still, but that then shows signs of aging better which might not be what we want. Lower resolutions, HD or even 720p when sourced from a good camera and lens usually look better than 4k with a standard camera and are easier to encode.

Sending over 1Ms to the Pluto is a bit suspect, the limits of the USB connection. The Lime is OK. At the moment 4k is fun for the more advanced operators to play with, but I know what will happen. Those who don't have the technical knowledge yet will try it because it is there and sounds cool, and then get frustrated when it doesn't work very well for them. It might be better to consider separately a "DATV-A-little-bit-more-difficult" experimental branch.

Mike

[Hotscam]

I used Easy 2.08 with NVIDIA and Pluto successfully up to today. Wonderful package.

Today I upgraded to Easy 2.12 and I have problems.

The LEDS do no longer come on in NVIDIA mode.
When I switch to SOFT coding all back to normal, so I suspect a NVIDEA upgrade problem as various people reported

Upgraded to version 3.26.0.160 but no change, while Geforce diagnose reports optimal operation with OBS.

I hear there could be a relation to a newer version ffmpeg 5 used now, which may also explain that V2.08 also shows the same problems now.

Erased and reinstalled the complete 2.12 package to make sure but no luck

Any ideas ?

Jack
PA3AXO

[Hotscam]

Found the problem !!

Besides geforce version update I also had to update the game drivers from V 516 to 527. Working great now

Older Easy versions 2.08 and 2.10 only seem to work with ffmpeg 4.3
2.12 only works with ffmpeg 4.4

took almost a day but happy again

Jack
PA3AXO

[M0SKM]

Running in Win 11 no problem of that kind here.
Steve