Ddon’t know if it can be seen as the same or not but i use a Nas synology 414J, plugged in Samba on my pc, I often use VEAI with it, and never got this problem.
I was a beta tester last year for VEAI, but gave up @ 1.5.0, because it was too slow and buggy with my system setup which is a i5 9400F with 8Gb of ram and a GTX-1650. When fast forward to 2021 and version 2.6.0 later, I upgraded my system to 32Gb ram and with the same GTX-1650, I got impressive results. What I used to get from Artemis MQ from 480p-720p was 0.88 to 1sec/frame and 480p-1080p was 1.56sec/frame. With 2.6.0 and with the same GTX-1650, Artemis MQ on 2.6.0 delivers 480p-720p in 0.36sec/frame, 480p-1080p also in 0.36sec/frame and 480p-4K in 0.88sec/frame. All of this in sub 1sec/frame territory. So there’s great improvement between 1.5.0 and 2.6.0 and I think it’s using the GPU more. What I try to wrap my head around is that; at what point will the return become more incremental rather a bigger leap?
If I remember correctly, the only “big” speed improvement (Windows) is
around V1.7.1, where they switch fp32 model to fp16 model.
For GTX1650, FP16 performance: 5.967 TFLOPS , FP32 performance 2.984 TFLOPS.
That is why you get 2x speed improvement.
Other than that, most version update speed improvement is pretty minimal.
2 Likes
Probably when the major bug issues are no longer, the audio is sorted out, and when a more normal selection of output formats with a bit of standard customization is allowed from the GUI. In other words when the developers are no longer speeding time with the basic mechanics of the software and can devote most of their time to the models. The models will be what they are, slow learners like we are, haha.
As time goes on a new model may pop up that will be a big difference like with Proteus. Early we had Gaia HQ, than Artemis MQ and now Proteus V3. We also have what I think of as the specialty models Dione and Chronos. My thinking is those models will give way to being included with a switch in the standard models somewhere in the future.
1 Like
Yeah this was odd because I wasn’t sharing the drive. This happened on 2 computers with NTFS formatted EVO 970 Plus NVMe drives on the C Drive. I copied the folder to each computer and there were 18 identical files on each computer. I was doing some comparison tests as one computers has an EVGA 3060 XC Gaming GPU and the other has an EVGA 3060Ti XC Gaming GPU. I have some upscaling jobs coming up where I would like to plan the processing time for each computer and doing this test was going to help.
Like I said all I did to fix the problem was rename the folder on both computers. I don’t know if it is a Windows 11 problem or VEAI problem in this case. Microsoft did release either in the latest update or the one just before this one a fix where special characters were not being allowed in the registry. I checked that and it is being allowed but is there something else happening at a more deeper level with Windows. Or is this some strange one off thing.
I’ve never had an issue with 2.6.0 using an external drive or shared drives across the network as the working drive.
Ah yes, I am remembered this now when Topaz said they would. Thank you for the reminder.
When I was using 1.5.0, Dione and Proteus weren’t available and today, the new models are better in 2.6.0. Did they ever include features like support on the Tensor cores on the RTX models when they are planning to prior to 1.5.0?
My next upgrade will be getting the RTX 2060 card to replace the GTX-1650, when the chip shortage sorted themselves out and wonder if the RTX model would provide any more substantial gains in upscaling speed?
I’m not sure but I would think so. I made the jump from GTX-1660 Super to a RTX 3060 non Ti and it was a huge leap. The memory usage was about the same but the speed was a major jump. Than I picked up a 3060Ti which was a good jump from the 3060. Again no real change in memory usage but triple the speed or better of the 1660s. I was very fortunate as the 30 series cards are both EVGA. One the RTX 3060 Xc Gaming and the RTX 3060Ti Xc Gaming. I got them through the EVGA queue system and only paid MSRP so both for roughly the price of a 3060 on Amazon right now.
One thing that has made using VEAI so nice is having good CPU’s with these 3060’s. One machine has a Ryzen 5600x and 3060 and the other has a Ryzen 3900x and the 3060Ti. Both have 32GB of ram. This allows me to run 2 instances of VEAI on both machines and still have head room to do other things, even light gaming on the 3900x system. Both have 970 Evo Plus NVMe drives and both are running Windows 11 and have been since July.
2 Likes
Thank you very much for the feedback on the RTX 3060. I’ll keep that as an option when I execute my upgrade plan in the new year.
My VEAI machine hasn’t upgraded to W11 yet, and the problem with the rejected paths came immediately after lifting VEAI from 2.4 to 2.6 which is why I don’t think the problem is Windows related. The network (RDP) path I tried to save to is a simple as it gets, 7 letters (no number or special character) right above the drive letter. I haven’t tried saving to an external drive attached to the VEAI machine (makes no sense as to my workflow), nor have I used a genuine network drive because I don’t have one. All I can say is that 2.4 used to save to the remote PC’s drive without a problem whereas 2.6 doesn’t. It seems that 2.6 adds a slash to the drive path in some (all?) cases which is also written into the registry but local paths on my VEAI machine get accepted inrespective of the additional slash. I haven’t yet figured out what the trigger for the actual problem is. However, I still have hope that the devs eventually will:grin:
I’m also experiencing this problem. Moving the app into the foreground and the speed jumps back up.
I’m getting a glitched line at the bottom of all the videos now with 2.6. I’m running the latest Windows 10 build, 2080Ti with driver 496.76 (updated it from .19) and compared to 2.4, there is this glitched pixelated line. I tried with GPU, CPU mode, and a fresh reinstall of 2.6 (removed all folders and registry entries) and still there. Anyone seeing this?
No i’m not. I tried Cpu and Gpu / both drivers, game and studio driver one. 1050ti here with latest studo driver.
I’m still doing testing. With nothing else changing, 2.4 is ok, 2.6 has the line at the bottom of frames.
Examples of what I mean. Look at the bottom of the frame. However I’m about to do a clean graphics driver reinstall. I’ll report back after.
Looks like maybe the original video might have an odd resolution size causing the aspect ratio to be nonstandard.
Well, just tried the 2.6.1b…and it’s fixed. I’m not sure what caused this (clean driver install, clean 2.6 install) but 2.6.1b is fine. So. I guess all good on this end now for this!
2 Likes
I’m just testing 2.6.1.0bBeta, upscaling from an old camcorder video 480x756 25FPS by Dione Interlaced DV :HD into 1920x1080 50FPS.
The result images are ok, but I miss audio, and would prefer to stay with 25FPS.
Can this be fixed in further VEAI development, please.
Well, I tried again exploting several models, and all of a sudden again with Dione Interlaced DV into 768x576 I got 25FPS and audio
You do not want the audio from VEAI. It gets dropped to a very low bitrate.
