Export presets not being read on first export command

[Shebbe]

With all the mess that is the new export page there is one bit we actually do like about this update and that is a preset manager. However there seems to be a very annoying bug that when you export a sequence for the first time it doesn't read the preset eventhough the preset is selected. We removed all the default presets from the user list so it's clear for our editors which ones to pick but it looks like it's grabbing a random one from the full list instead...

The same is happening when the preset was already picked but someone else opens the project on another machine. I opened someones project and it had exported to prores previously. Mine also mentioned that same preset but the resolution is 720x480 and 29.98 framerate every time.

Below an image showing what happens. The preset selected there should have timecode overlay and match source for resolution and framerate.

It 'fixes' itself when you click the preset menu and select that same preset again.

[Kevin-Monahan]

Hello @Shebbe,

Thanks for the message. It’s been a long time since you filed this bug, and I apologize for the lack of a response. Are you still having this issue? If so, the team will need more information from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

I'll move your post to the Discussions board while we await your information.

Thanks,


Kevin

[Shebbe]

Hi @Kevin-Monahan,

Thanks for picking this up. Last time I checked this is still an issue for us. I believe we are on 24.1 now but I'm off this week so can't double check yet. We use Windows and Mac systems and it's the same on both.

I might be able to test for a reproducable next week but it should be in the lines of what I described in the original post. So removing all default favorite presets and adding a bunch of custom made ones. Then on a new project, new sequence, export it and it will not pick up the preset yet eventhough it'll be selected at first. Upon reselecting the already selected preset it'll update to actually use it. If it does work immediately you could try exporting the file and then save and open the project on a different machine that doesn't have the file path of the previous one. I think that's the best bet at finding this issue.

Hope you can already find the issue, otherwise I'll be back for more on this once back at the office.

[Kevin-Monahan]

I'm also out of the office. When we both get back in, let's revisit the issue. Have an excellent time, @Shebbe.

Thanks,
Kevin