‘Crop to Fill’ is still done in an abysmal manner. Take a 1920x800, 16:9 source (and movie I had once cropped myself). Now, the proper way to get rid of the letterbox, is to FIRST crop, as follows (in VapourSynth syntax):
vid = core.std.CropRel (clip=vid, left=248, right=248, top=0, bottom=0)
(248 = 140 x 1.77) Then, and only then, do you ‘stretch’ (upscale) to 2160p. What TVAI apparently does, however, is first upscale the frame x1.35 (to reach 1080p, from 800p), and then you wind up effectively upscaling a 2592x1080 image to 4k (that is then cropped to the sides later).
The result is a dismal drop in fps (like to 2.5fps on my RTX 4090), a slowdown consistent with the totally unnecessary pre-upscaling.
Have you check “Encoded Size” and “Displayed Size” ?
Encoded is what is hard encoded and me be used with 3rd party software.
Displayed is what id truely sent to → Displayer
Once again: Topaz Topaz does not have an Apple license for Prores and therefore does not encode in Prores but in a kind of (free) homebrew version of something that looks like Prores. Adobe and other companies are really not going to adapt their software to that kind of junk ‘ProRes’ video.
Apple checks extremely carefully whether the licensees implement the Prores standard correctly in their software. That is why many video producers ask for Prores files for a complicated workflow, because technically they can be read and edited by everyone.
That is why sending a Topaz ‘Prores’ video file to a video producer as a paid professional is a very, very bad idea.
That’s a shame, did you try to import the Topaz exported file in ME as well?
I am unaware of any issues due to “a kind of (free) home-brew version of ProRes” included in the Topaz version. Good to rule that out simply by asking the Topaz Team. I think there is a list somewhere on the Apple website showing all licenses.
Is the other commentator also on a Mac system or using a Microsoft system?
That said. It’s strange my system handles all Topaz ProRes files without any issues. Do not share that many ProRes files, but never had any complaints on sharing the some that I did, by the way. That must be more than mere luck or based on the fact that I am a nice guy. Furthermore, I recall you saying that Quicktime handles it “ok” as does DaVince Resolve. So strange it is.
If you’re able to open the file in QuickTime (finder uses QuickTime right?) what if you were to “save as” the file and then try to load the result In PP or AE.
One option left:
Contact Adobe. Send them a small portion of the file to see why it jams. This has taken too long.
I tried this, for lulz, on a regular bluy-ray, with many compression artifacts (Brazil), and the result is ridiculously good! Not sure how that’s possible, frankly, as, indeed, I turned Fix Compression all the way down; yet, the output is clean as a whistle!
Oh, and Iris V1 runs much faster than Proteus, to boot.
I’m a PP editor dating back to 6.0. I had a bit of trouble with playback on one PR 422HQ file exported from 5.3.5. the first time I’ve had an issue. It would play but I would get audio overload notifications. I exported the audio as a .wav file, reimported it, and replaced the original audio with it in the sequence and now everything is Kosher. The main thing I notice with Topaz PR exports is the extremely high bit rates, sometimes over a 1000, you get with each file. But other than that they play fine for me. MBP M3M OS 14.7
It’s not just you. Going on a small mini rant here:
Why can you guys not get Preview to work?! It’s not higher math, you know. You have a bit of the original on the left, then play the segment, in the adjacent window pane, only processed. This is child’s play – or should be, rather. And remember 2.6.4, where you could even do something as radical as click back in the processed timeline, and see the result? (= very useful, to see whether you’ve chosen the right settings for your video, by checking various processed sections). And don’t give me ‘difficult.’ It was possible in 2.6.4 just fine. So, whoever you let do the Preview in 2.6.4, hire him back, and let them fix the current incarnations of your software. Because currently Preview is severely broken: half the time it just shows the original; and where the original is supposed to be, it says 3840x2160 as well (although that’s just cosmetic), The other half of the time Preview shows something (but never back on the timeline), or TVAI just outright hangs when the clip ends. /rant
I cannot stress enough how important a working, side-by-side, Preview is; and one where you can ‘preview’ the processed results earlier in the timeline too. All new fancy models are cute and all, but of little use to me if I can’t do easy Preview tests (and, again, see earlier processed data too). Even on my i9 12900k + RTX 4090, processing a full blu-ray can take up to 8 hours. Preview is essential: if not for my own sanity, then for my electric bill.
How are you getting a blu ray movie upscaled to 4K in 8 hours with a 12900k+4090?
I have the same CPU paired with a 4080 and judging by the benchmarks I’ve looked at, there is only 3% performance difference between the GPUs since Topaz doesn’t optimise the full power of the 4090.
A 2hr movie from 1080p to 4K takes 14-15hrs for me.
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.
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.
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).
Not sure how that’s possible, frankly, as, indeed, I turned Fix Compression all the way down; yet, the output is clean as a whistle!