I’ve cracked it.
The reason that you’re all checking and unchecking the boxes is that the setup app is going for a world record of box checking.
Forgive the pun but check this lovely story.
1 Like
This was not thoroughly tested, so proceed with caution, but if you want a simple workaround:
- In a shell, navigate to /opt/Autodesk/.flamefamily_version/cfg:
- Ex:
cd /opt/Autodesk/.flamefamily_2025.1.1/cfg/
- Ex:
- Backup current config:
sudo tar -czpf init.cfg.bak_$(date +%m%d%Y_%H%M).tgz init.cfg
- Replace 601sync and DTVsync w/ free sync
- For MacOS:
sudo sed -i '' -E 's/(DTVsync|601sync)$/freesync/g' init.cfg - For Rocky:
sudo sed -i -E 's/(DTVsync|601sync)$/freesync/g' init.cfg
- For MacOS:
4 Likes
Thank you, this is terrific!
1 Like
When you edit the init.cfg file to set your sync to Free Sync, the next time you will install a new Flame version the new init.cfg will be generated from the previous init.cfg so you would only need to modify the config file once.
Setting the default value to freesync would have a negative impact on the various studios and broadcasters using external sync since they would not get the window so all in all, set freesync then forget about it.
@GPM Media Export default format is not DPX but Alias IF since it is the fist option (the list if sorted in alphabetical order). If you wnt to have another format or preset displayed first then just save a preset and you will be good to go since presets are displayed first.
that is until you install the newest version of Flame and have to go through it all again. My freesync choices are never remembered when i update to a new major Flame iteration.
Do you uninstall Flame before upgrading to a new version? if not, then the latest init.cfg on your system should be used as the base for the new init.cfg file this no need to reconfigure your previews and sync.
no - i dont normally uninstall old versions. Perhaps its when tech support have been sorting issues out they occasionally remove older versions.
Maybe. But on my side when I upgrade a version I get the right data in the new init.cfg file so no need to edit anything. Next time you upgrade please let us know if you get the issue.
@Slabrie I do understand the point about the big studios you made, which would ‘break’ if free sync becomes the default.
However…
A big studio has IT folks that carefully coordinate the roll-out of the software, and I’m sure making all sorts of changes to the config to match their specific pipeline. Them running a script of configuring sync is just one in a long set of check boxes. For all we know they may already have a script to customize that config file.
On the other hand you have a lot of smaller shops and free lancers, not all of whom a ‘sed’ warriors by trade. It’s a much bigger lift for them.
Are we optimizing the right way here?
Of course the big studio customers are big and important fish. No doubt. And that carries weight. But you also get a lot of love and nutrition from us sardines here too.
1 Like
Like I wrote, if you set Freesync using the Setup application once then you are good to go for all following updates. This should not be a major issue.
For the dot releases yes. On the next major upgrade once a year on the Linux system I re-install with a new ISO. Doesn’t carry over there.
And the setup application requires too many clicks as there is no ‘select all’. So terminal and ‘sed’ it is.
All good. It is what it is. An annual reminder that I’m a sardine. Albeit a very happy one…
@Slabrie Is it not possible for the application to identify incoming sync and act accordingly?
There is no need to have an init.cfg per version. NO ONE ever needs to have different settings for Flame 2032 and Flame 2032.0.1.2.case352525245, or between products.
Make 1 global init.cfg and ZERO people will complain.
This scenario is important when doing a fresh machine install and multiple versions are installed at once. There is no previous init.cfg, so you must modify each one. Now muitply that by 3 for Flame, Flare, FlameAssist.
For us that generally means about 9 different init.cfg that all need to be modified.
Go global.
It totally is, as evidenced by the annoying error message popup when you start Flame.
In fact my proposal was to add an option which simply would tell Flame to automatically fall back on free sync if no sync is detected. That does not break the big studios, because their sync would be detected. The only thing they would not get is an error if someone accidentally pulled the cable out of the back of the machine.
So when big studios wipe the system and install a new version, they would simply have to change that default preference to ‘off’. I’m assuming that they’re already changing all sorts of preferences to their pipeline setup.
Sadly not.
The centralized configuration theme that we have introduced with Flame 2025 should enable these workflows in future updates.
Can you elaborate?
When I install Flame and start it, by default I always get an error message popup that says ‘Sync not detected’. One of the buttons is to select ‘Free Run’ and then life goes on, until the next time I start Flame or take a break and do 40 clicks in setup (or run Phil’s command line in a terminal).
Why can me clicking the ‘Free Run’ button in that popup not be automated?
The code behind that popup has both a trigger and action that exist already. All that is needed by a preference settings to allow this trigger to take that action immediately without user confirmation.
if(NoSyncDetected) {
if(preferences->SyncFallBack) {
broadcast->SetFreeRun();
} else {
ui->ShowDialog("Will you fix your setup already!!!");
}
}
1 Like
hahah this is gaining more traction than I thought.
I would just like to have a simple button to change all to FreeSync , clicking EACH RESOLUTION OPTION everytime - nope.
yes i will probably fix it with init.cfg shenaningans now… but still… ugh
1 Like
as Finn is saying, there is never a situation where you would want 1920x1080@24 to be FreeSync but 1920x1080@23976 to be House/DTV sync. GLOBALIZE the inti…I mean, the init.cfg
1 Like
Enough traction that @ALan posted at 5AM.
5 Likes