I really appreciate the effort to solve the VBR problem through CFR, but if this tries to solve one problem by causing others, I don’t know if it is a right solution. Relase 4.2.2 has none of these problems.
I’m still using 4.2.2 even though I renewed my upgrade license a month before v5 but refused to update due to the ruined UI change and new bugs, I thought I’ll hold off until the bugs are gone but seems almost a year later that the bugs are still there, judging by the forums nothing has improved by much since the launch of v5. So unlikely I’ll renew again once my upgrades expires in march. Until the software is more stable with bare minimum bugs then I’ll pay again but no point paying for new features on broken software. Really wished they prioritised fixing the software rather than focusing on features.
Does anybody know under which circumstances that VFR Problem happen ?
Does it happen with any Type of Input ?
Does it just happen if some specific Codec is set ?
Does it just happen with Interlaced stuff ?
Does it just happen if Audio is processed to ?
etc etc
I sent sample files, logs, and indicated the models in which the problem was occurring.
Keeping in mind the old versions (4.2.2) where the problem did not occur, I assume someone on the technical staff should be able to investigate the problem.
Thanks to you i looked at the 4.2.2 Topic and saw that Topaz used a normal List for Previews, and not that annoying clustered Tree List from V5 (that annoying Tree List was still better, as no List at all xD )
If it’s possible to install 4.2.2 (without removing V5) i will keep it.
Until V6 has a Plain an Simple Preview List (with Sort Function), like V4.
I’ve noticed a small issue - with real-time previewing (of short videos at least) the process doesn’t seem to finish up the last couple of frames, and just ‘turns the processing wheel’. I have to press the ‘wheel’ manually to stop the previewing (I’d like to see it finish and play the video looped, as it’s in 6.0.0).
It seems ffmpeg.exe crashes at the end of the video with ACCESS_VIOLATION c0000005 exception in opencv_world456.dll library. The crash seems to be connected to the frame interpolation part, where the app somehow can’t “guess, when to stop processing” and goes out of video bounds.
Since it doesn’t happen on every video, I’ll include the example from the screenshots (crash happens intermittently, but the preview-processed playback doesn’t seem to loop on this one): 672f1e3129924a76434cf0acec40620398ca2c18.zip (961.8 KB)
TEMP wipe bug is FIXED once again - thank you.
On the side, there’s (probably) known issue with Rhea XL v1 model - the ‘static’ elements of the video frame, the ‘repetitive’ ones (even if it’s zooming in/out or panning slightly) receive these artifacts pretty soon all over themselves:
Sorry, but this is totally unacceptable and beyond my imagination why such an option is even needed to get the job done in the usual way. Imagine your car got a “hold tire pressure” option to prevent flat tires every morning!.
In other words, you solved nothing? Way I read you, is you are still mysteriously stuck with a VFR output, which you can bluntly mask forcing CFR at at the end (meaning you will be padding skipped frames and such, like an AssumeFPS in AviSynth would do).
Seems I was right canceling my subscription for 2025.
I updated the VAI from version 5.3.4 to version 6.0.1, but I received the following message during the update installation.
“The specified account already exists”
And the update failed.
What should I do?