I understand your frustration, and I used to think the same as you did initially long time ago.
But topaz did not invent anything here. it is a common practice in the retail software industry that “beta” program is an option for licensed users that “voluntarily” want to help, it is not a jail-out free pass.
I am on Beta program/tester for other software as well, Microsoft (MSFS), Laminar Research, and others and all are “optional” for those who are licensed that want to take the extra mile “voluntarily” and contribute without any expectation for return or free software, even if it’s in a Beta state (still, it’s a fully functional software after all).
It seems the “live preview” option might be causing some issues.
I uploaded an old video and it gave me an error in the live preview section in “export”.
Even when I toggle live preview off, it still gives me an error when I’m previewing it.
I tried to upload the video onto the (not beta) Topaz Video AI 3.3.2 and it works totally fine.
I’m also wondering what this feature is for and why it makes 2X storage space. Is the 2X storage space temporary?
The weird morphing artifacts don’t still there. I skipped a version as confirmation received it was known and working and I didn’t see a mention if resolved yet, but this confirms not yet.
You have changed something on the extract. I still need to put somethign in the name field, instead of it just exporting, but now you start at frame 1 instead of frame 0. Given the input starts at frame 0 which is normal for an image input sequence, this effectively guarantees the output sequence is always off by one frame. Was this somehow an attempt to correct the issues with frame numbers? If it is, maybe step in right direction (?) but unfortunately causes more issues than it might solve, ie:
– The input target frame is being identified by the input frame number not the export, so do you guess and cut the sequence a frame early or late to try to make the export match?
– Frame targeting is still off by default. You select 11900 and it starts export at 11899 which means the offset of one counteracts this attempt to rename and you still end up with the wrongly name frames, eg https://i.imgur.com/JjFHJQ4.png this has the input section on left and the output frames on the right. Scene change still on the wrong frame number.
I am not going to do much testing on output quality - its hard to do that when the image moves around like ants, but on a very quick test that I did to confirm that issue, just using Auto, I can see Auto on current Iris is still too soft by default. IE such as this which compares manual settings on last good Iris model to Auto on the current version - Comparisons - Imgsli
Or as an alternative comparison, the same Manual settings in Iris in 3.2.9 and current Beta Comparisons - Imgsli showing that putting aside the werid morphing going on, the newer model is still too soft even manually adjusted +50 sharpen +50 Anti deblur and +60 Details.
I thought maybe this was the new Original Details slider - which was default to 0 - so I tried again at 50% and it made no difference at all, suggesting the slider bar doesn’t really do anything currently. I forgot to name the last image, so its still the frame number, but this comparison is the same as teh last - manual settings identical Iris between 3.2.9 and current, but the named image is 0% Original details the frame number is 50% Original details - More Comparisons - Imgsli if there is genuinely a difference, I cannot see it.
I thought I made a mistake - which is always possible - so I tried again being careful to explicitly separate the images and I THINK I can now see a very small change - Recover Original Details - Imgsli - though it still has lost far too much detail.
To gather logs, please select Help > Logging and make sure that there is a check mark next to Logging. Next, recreate the issue and then return to the Help menu and select > Get Logs for Support and attach the zip file to your reply.
Here is the System Report. Mac mini.spx (6.0 MB)
Here is the logs for support. logsForSupport.tar.gz (287.7 KB)
Here is a screen shot of the warning in the panel.
this is not a bug / issue.
mp4 cannot contain PCM audio track, only mov, mkv or avi can.
your video probably contains PCM audio track and you selected “copy” and export it as mp4 or you decided to transcode (“convert”) to PCM into mp4 file/container
edit : seems that the issue is related to activating the text cursor display and make it bigger in Windows accessibility Parameters.
when turned off, the issue and the jerky playback are gone. Seems it was reproductible in an another software (vegas pro 19) but can’t really be sure, the project I tested is big already and slow down is “espected”. but when i de activated this, the jerky playback in VideoAi was gone immediatly.
don’t know if it’s an issue with Windows 11 (insider preview beta last build) or maybe VideoAi ? anyway, i sent a comment via the windows insider issue report about it.
