A here we go again. Been using Mac’s since the early 90s. Never experienced any issues like you describe. Impossible. These fine machines are protected against overheating unless you do not use them according to the rules - f.e. giving air to breath. That’s not marketing. “Dust fell out”…perhaps you should have kept it in a more clean environment?
No worries. There is no right or wrong in this. I left the Bill Gates surroundings when they’re at "C:" and never looked back. I think they still use that BTW. AS is a major step where it comes to speed and efficiency. Next to that: I just like the Mac OS-environment in which I can intuitively find my way and have hardly any worries about installing the latest drivers or other mysterious issues that involve incompatibly. Is it flawless? No. Can it be better? Yes. But to me less hassle means more time to do work. And most of the time to me the limitations are in the software. That’s why I’m still on 5.3.6.
Speaking of software. Wondering when we get an update on that 2025 roadmap?
Hello to topaz
why is 23 to 25 Frame conversion with AION making to short clips. in the original is visible contend not in the final clip.
if I refine with Artemis or other the clip is getting longer. that’s 100% unprofessional and only usable before the edit. this should be pointed out before selling.
So the consensus is, upscaling with Proteus or Iris will still cause the stutter or jittery output of the video. As long as you don’t upscale it’s all fine. I think. lol Anyways stick with 5.3.6 for now then.
it likely won’t perform much better. Testers have already pointed out “AI” was a misnomer. It is good “at faking frames so kids get happy looking at their FPS counter in their vidyagames”. When it needs to process existing data without anything to spoof it is slower than 40-series.
if I understand Topaz’s functions correctly the timeconsuming part is rendering the images it has drawn into a video. At that point the card has to follow instructions and insert each frame it has been handed. The 5090 AI is good at inventing things, and even though we’re working with AI content the video put-together-ing is straightforward directions as far as the card is concerned meaning its not able to take creative liberties unlike videogames where it’s making new frames but IT is MAKING the new frames not being handed new frames.
I wasn’t sure but I figured laying it out for the average “I need 3digitFPS or ill never win Worlds!!!11!1!11!” uberleet basementdwelling gamer to be able to understand wouldn’t hurt for when they stumble across the post
I have an SD video that is slightly wider than 16:9, which would have a tiny black bar top and bottom if upscaled to 1920x1080.
If I try to crop it to 16:9, the crop frame is locked hard left, not centered. It cannot be dragged to center (there really needs to be a pair of centering buttons, BTW).
If I use the X field to center the crop numerically, the area of the crop frame unexpectedly shrinks rather than just moving horizontally with the same height. If I use the height/width controls to numerically undo the shrinking, the crop frame locks hard left again. So, I cannot crop off the sides evenly without taking away a good part of the top and bottom as well (an unnecessary and objectionable loss).
16:9 and 21:9 are the only aspect ratios affected by the forced left off-center crop problem.
Although there is another odd problem: as I pan down the aspect ratio list, the crop area gets smaller and smaller. Each new crop selection is not based on the original video frame (it might be based on the area of the last crop selection instead).
To clarify the centering problem: all aspect ratios selected after clicking the crop reset button fill the entire height of the frame and are centered and movable, except for 16:9 and 21:9 which are always left aligned by default. and cannot be centered.
I was wondering where the loop preview has gone. It is now trying to generate another n frames of preview just ahead of the cursor while playing the preview, which causes stutters.
Yes SD 16:9 is not funny, 480 x 16/9 = 853.333… or some are 854 or 856, whichs gives not exactly 16:9 and procudes floating points
For example you can use VirtualbDub2, leave it unscaled and add Letterbox arround the size matchs 864 x 486, which is exactly 16:9. Upscale the 864 x 486 one and crop the the few pixel letterbox away on the final upscaled one.
The ffmpeg used by Topaz has been modified by their devs. However, there is still a lot of potential for using the standard ffmpeg for the final stage for codec / compression / container. I’ve previously given an example where one can make use of x264/5 libraries** for lossless compression by piping the raw output from the Topaz ffmpeg to the standard ffmpeg. However, all this has to be done via the CLI which is not particularly user friendly. So an option to use the standard ffmpeg (for the final stage), if the user already has it, would be a nice addition to the UI. Perhaps you should add it to the “Ideas” section?
Andy
** these can’t be used in the TVAI ffmpeg for licensing reasons
I decided to try this new build. I’ve done 2 DVD already. Proteus 1st Pass then Iris Med Q 2nd pass. It’s processing at 11fps! 5.3.6 was doing this at 5fps. Codes is ProRes Standard. Also no stutter or jitter after it’s done. The files are good.
iMac Hardware Overview:
Model Name: iMac
Model Identifier: Mac15,5
Model Number: Z19E000ZFLL/A
Chip: Apple M3
Total Number of Cores: 8 (4 performance and 4 efficiency)
Total Number of Cores GPU: 10
Total Number of Cores Neural Engine: 16
Memory: 24 GB
System Firmware Version: 11881.61.3
OS Loader Version: 11881.61.3
Mac OS: 15.2 (24C101)
Instead of pushing updates that don’t fix core issues (VFR/dropped frames bug that produces stuttering output upscales) which are software-breaking, Topaz should be warning its users not to download updates and to stick to v.5.3.6 until they fix a problem which has been known since at least August 2024.
) happy?