This isn’t the answer to your question, but we use 2021_2_2 with UHD 2160P 16 bit EXR PIZ with excellent performance on a variety of Linux workstations.
We also have many shows that are the same resolution but DPX with excellent playback performance.
Yeah i think im going ro suggest reverting back to 2021
I would suggest one project per episode, not one episode per library. If you have a database corruption, you’re only down one episode not many.
I’d find this really slow and annoying as you often want to copy things between episodes when working.
It’s a whole world of pain when a simple backup regime removes any issues of project corruption.
I use one workspace per episode and the shared libraries for anything like kit of parts etc
Same. Works a treat!
Can i suggest something here, i use loads of machines in facilities that do a pause in those same intervals. It MAY not have something to do with playback but something the machine or flame is doing… like a log dump or a backburner something or another - some background task or server hit that affects the machine. Ive seen this butr never understood why some facilities never have it while others its rampant. All down to how its setup etc. maybe look elsewhere for what the machine or OS is doing in the background. sorry i cant be more specific! just a suggestion
in General preferences make sure Protect Playback is enabled.
I thought that too but we have protect player enabled so in theory that should rule it out.
When in doubt, launch from the command line with " -d" trailing the start script.
Had anybody tested longform on 2024? Autodesk dont seem to have a clue what is causing these issues.
It has been like a decade now they still haven’t fixed the intermittent 1 minute delay when pressing Play. Flame is really trending towards the solo macOS rider.
No worry, we are investigating the issue but it is not clear yet that you have all the same problem. Thanks to the ones in the thread who reported the issue to our Support team so they can get as much information as needed to investigate the root cause. We will keep you updated about our findings.
Thank you but i think it must be pretty obvious we all have the same issue. I work in London and this happens at every facility where i have spoke to somebody on various different workstations.
Sounds like this should be easily reproducible by Autodesk. It’s great to have customer debugs, but it should be in addition to what ADSK have already identified as a defect by now.
Hard to do when everyone is WFH.
Any update on this?
Our Support team will keep you updated when we have a solution for this issue.
Has anbody had improved playback? I dont feel there is any difference.
Have you installed the service pack with the fix for this issue?