Yeah looks like a bug because even if you set the default prefs to use reactor, a “create BFX” renders in FG
@fredwarren Is this known?
1 Like
@taylaner @johnag This is a scenario we forgot to consider. Can one of you please submit a request at flamefeedback.autodesk.com for it.
Thanks
1 Like
Done @fredwarren
2 Likes
We just upgraded from Rocky 8.5 to 8.10 and from Flame 2023.2 to Flame 2025.2. Playback is absolutely terrible. Running flame on a threadripper 5975wx CPU, 256 ram, A6000, 14tb nvme raid 10. Any ideas what would be causing playback to be so slow? I’ve been testing a 30 second prores 422 spot. This should be smoother than butter
…
No blackmagic or Aja video monitor connected ?
Looks like it might have something to do with pulse audio…
the playback issue is definitely do to pulse audio. If I remove audio and the audio track then it will playback. This is what I get in the terminal if anyone has any ideas as I wait for Autodesk support:
For me it is the relation between pulse audio et aja : Help
Hi, Flame can only handing 1 audio device at a time, If AJA is enabled, there cannot be a pulse audio or ALSA at the same time. if your Flame setup app has AJA as Audio and video device then you should be good with the kona 4.
can you provide more information on the issue…
What is the clip FPS & resolution?
Do the AJA preview settings in the preferences match the clip FPS ?
Can you enable the player debug mode and take a screenshot during the playback (w Audio) of the clip?
2 Likes
Aja is not enabled. Video preview is set to none in the flame setup utility and audio is set to pulse audio:
There’s no point in using the debug overlay as nothing will play back with audio but here it is
The file is a 1920x1080 HD Prores 422 file with standard 48khz stereo mix.
So you are correct, if playback does not start at all, its definitely an audio related config problem. With Pulse Audio setup its possible Flame will select default device on startup depending on what is available on the workstation & there are likely multiple compatible pulse devices. Can you check the Flame preferences / system / audio/ outputs, and see which device is enabled. There should be drop down list.
Do you get audio out when you play something on the desktop e.g. youtube in Firefox ?
A quick test is to:
- kill pulse (pulseaudio --kill)
- rename (mv) your ~/.config/pulse directory to e.g. ~/.config/pulse-012725.bk
- restart pulse (pulseaudio --start)
- check audio output by play youtube in web browser
- check audio output in flame.
1 Like
Ultimately we had to do a full wipe of the system drive and upgrade to rocky 9.3. Somehow the authorized autodesk rocky update scripts from rocky 8.5 to 8.10 caused issues and the pulse audio daemon kept crashing. Beau James saved us big time!
2 Likes