Hello,
Just pushed an update to address this issue. Let me know if this has been resolved for you !
2 Likes
14 hours feels too long. I am mostly using Proteus, and average about 5fps.*
I also use Process Lasso Pro, to set ffmpeg exclusively to P-Core affinity (as a defined Rule), and let TVAI itself run on the E-Cores. I found that throwing the E-Cores into the mix, for ffmpeg, only slows things down.
** Things slow significantly down on cropping (see a post above). Like with a 1920x800 movie, suddenly fps is cut in half.
3 Likes
Hello.
I really do not understand why some users âcropâ their BluRay content.
Today, all modern media players⊠e.g. JellyFin, Plex⊠has this feature.
When we had TVAi, just for giggles, we sampled a cropped video and noticed that it modifies (cut out) parts of a scene(s) and important details.
I understand that some users like the idea that their processing time could be shorter, the awful black bars are reduced or removed⊠but at the cost of diluting your purchased content that cost ~20 to 40 (a lot more if you factor in UHD Steelbooks, Collection sets, & UHD TV Shows) bucks a pop per content?! I donât know.
If I have blu-ray content thatâs a 1440x1080 image in a 1920x1080 frame, Iâll crop the black bars on the sides to reduce the processing time (I donât have a tremendously powerful system so every little helps!). Iâve never lost any part of the picture doing this, since Iâm only excising the empty areas. You do have to be sure to set the cropping parameters exactly, but as long as you do I find it an excellent way to accelerate my workflow with no downsides.
1 Like
I think mediaInfo reads Containerdata, but for example you can export just one Image with Avidemux or VirtualDub from the video should gives you exact size
I also like 4:3 content without black side bars, enhance processing is faster and file size shrinks (without losses) so I cut it away, but have take care at the end video is flaged als 4:3 for playing.
Some of my denoised blu-rays are almost 20 years old. 
At the time, it briefly felt like a good idea to crop black bars off, as it shortened re-encoding time (on my then 6700K quad core, iirc). I no longer do that (even though I still crop the bars off, in VapourSynth, but then do an addborders at the end, so as to get pure black bars), I had a Sony TV that would show odd fringes at the edge of 800p, for instance. Besides, and especially with UHD/HDR, itâs always best to keep the official resolution, lest the player wonât even properly recognize the HDR as such (let alone DV).
Yes that s what I did. The size was totally wrong indeed.
Guys, pls support with vote my idea Topaz AI Trainer - Empower Users to Train Their Own Models
Thanks for the info, I tested this out today with turning off e-cores for ffmpeg and only using them for Video AI exe but didnât see any improvement using only p-cores and setting priority to high and even tried realtime.
The only thing I noticed when exporting is the fps timings didnât stutter as much as wore consistent.
Hopefully the next gen GPUs will speed things up, not long now.
Cropping save not only space and compressing ressource but also allows displayer to adjust perfectly to diffuser using metadatas Mastering Display, coded_width, coded_width, displayed_width, displayed_height
Also leaving 2 to 5 pixels borders help a lot with models that scale up or down the image, so that you can crop them into final displaying, using coded_x
You avoid some borders ringings like this
Is anyone having the issue where they cant use the software at all? Topaz isnât importing any media at all on both Mac and PC.
Can someone explain to me why when I upscale a videofile from 720x576 4:3 to 1920x1080P 16:9 the render output file is 1.942 instead of 16:9??
Settings is:
Codec settings output
QuickTime V210
Profile Uncompressed YUV 10-bit
Container .MOV
Output resolution
1920x1080 FHD
Pixel type Original type
Crop setting Letterbox/Pillarbox
Video type
Progressive
AI Model
Proteus
Framerate 25fps
MediaInfo
Width : 1 920 pixels
Clean aperture width : 1 920 pixels
Height : 1 080 pixels
Clean aperture height : 1 080 pixels
Display aspect ratio : 1.942 ??
Clean aperture display aspe : 1.942 ??
VEAI 5.3.6 has a little regression bug with zooming/panning the video Iâve reported before, v5.3.5 was fine. It might be not important anymore though, as mpv is going to be in charge of the playback soon in the beta, then in release, I hope.
1 Like
No because itâs no where as simple as you think.
And itâs not a competition on here to get votes.
2 Likes
Weird. At 1920x1080, Display Aspect Ratio should be 16:9, of course (1.77)
This sounds to be a bad use of DAR and SAR
MediaInfo works with internal tables to ensure an âalwaysâ result
If meta are missing, this can lead to incorrect aspect ratio, but will not lead to unplayable file because displayed_width and displayed_height are searched ahead.
Keep in mind that TVAI use not only tweaked ffmpeg but also return incomplete metadatas.
1 Like
Hello.
That is one thing we had noticed when we had TVAi.
We didnât spend enough time to troubleshoot but mediainfo showed a TVAi processed HDR project with no HDR metadata but it did show the REC.2020 info.
I recall (somewhere on here) that TVAi supports HDR processes but it doesnât show up in mediainfo correctly. 
Why do you work only with UI for years? No models acceleration at all. It is pretty ridiculous when it runs with 5-8 FPS (nyx, artemis) by upscaling 1080 to 4k with RTX 4080, it takes half of a day to workâŠ
2 Likes
It always did thatâŠ
