SUU-Design Forum

Hello

I have found a weird bug (or perhaps I am making a mistake).
I am trying to use Hardcode Times in VTM (first 10 seconds of any file), with a simple matrix of one large picture, and Animate as Single Frame.
If I then run Videonizer and Generate a Screenlist with Always refer to current options/current VTM settings it works fine.

However if I export the Settings, and save the Options then the Hardcode Times are ignored when using the 'Use VTM Options/Settings' from a .vtm/x file' if I try again to Generate a Screenlist within Videonizer.

Is this a bug or am I doing something wrong?

Thank you,

Sounds like a bug, will check.
Thank you for letting me know.

Could you please provide more details or/and even examples?

I have found an issue, but it is not related to Harcoded Times.

I can't reproduce your case for some reason.
Please specify what exactly is produced in your case.

here is the original file (it is just a funny video tiktok thing i found, but the error reproduces with every file i have tried):
https://www.dropbox.com/s/dfg6pcuhww809 ... q.mp4?dl=0

here is the resulting files generated within VTM, with first 10 sec hard coded animation:
https://www.dropbox.com/s/5zcx71astajuc ... q.jpg?dl=0
https://www.dropbox.com/s/pxey81i2wjxq9 ... q.vtx?dl=0
https://www.dropbox.com/s/wwh4iu975ulpz ... M.mp4?dl=0

i get the exact same results within Videonizer, if i choose the 'always refer to current settings'
https://www.dropbox.com/s/66ntl3jq6g0dj ... t.PNG?dl=0

however, if i save export options, and export environment settings for videonizer, then i get a different output files:
https://www.dropbox.com/s/fjdueam1scig2 ... q.jpg?dl=0
https://www.dropbox.com/s/ekvvziwa53ykv ... q.vtx?dl=0
https://www.dropbox.com/s/psu73ps3dvkj7 ... M.mp4?dl=0

here are my exported settings files, maybe that is where the error is coming in?
https://www.dropbox.com/s/8l79sxszybsgn ... s.vtm?dl=0
https://www.dropbox.com/s/20c70bxdtz285 ... s.vts?dl=0

Thank you for your post.
Now it is clear what is wrong. It is related to the issue I have found.
Will be fixed in the next release of VTM (because the issue is in VTM Options export).

great, glad i could help!

Fixed in VTM 19.0.0.0.