Hi,
Does anyone experience Dorico not saving presets loaded to Frequency as a plugin? Looks like it is particular for Frequency, other plugins, also non-Steinberg load their presets on project opening correctly.
Witold
A very quick test on my Win machine showed no problem
Maybe you could give a step by step recipe? Thanks
Hi Ulf,
Actually that is very simple. I loaded Frequency as an insert into Stereo Out channel. Then I loaded one of my EQ presets to Frequency, saved the project and closed it. When I opened the project Frequency was loaded, the Frequency preset name could be seen but the settings (EQ curve points) were not there, the EQ curve was a flat line like in the “default” setup. All other plugins like compressor, Altiverb, limiter and Curve EQ were loaded with their respective presets. What is the most interesting is that Frequency recognizes the presets, opens them (displays their names), but does not load the data.
It is not a critical bug, I replaced Frequency by Curve EQ and put the original problem aside, but thought that those of us who do not have other EQ of an equal class as Frequency may not be aware of such situation and be surprised when their manicured scores suddenly don’t sound as they sounded “yesterday”.
Should this happen - go and check what is loaded (or not loaded) into Frequency.
Witold
PS I work on Mac Pro 2020 with macOS Ventura
Hi Witold, first of all thank you for the details, but I tried again with the same result, I reopen the project and the Frequency plug-in shows the preset name as well as the correct curve. So I really wonder what is the difference with you?
Are you on the latest Dorico 5.1.30? And Frequency 12.5.50?
Hi Ulf,
Yes, Dorico 5.1.30, Frequency 12.5.50.76. I do not want to make it complicated. Under Cubase I created a test preset, then opened Dorico project, loaded this preset and saved Dorico project without touching the preset. Then I reloaded Dorico project, opened Frequency and the name of the preset was there but setup was flat (see the photo). However I still could reload the preset and get the proper values. BUT if I saved this preset under Dorico all data would get deleted.
Witold
Hi Witold,
not exactly the same what you report, but in the end I think it is the same:
I start a new project and insert an EQ, apply a preset and save the project, then close the project and reopen, everything is fine.
But now comes the turn, I apply a different preset to the EQ and then I close the project => Normally Dorico should know that the preset has changed and therefore ask to save the changes, but it doesn’t, it just closes the project without saving. So when I open that project again, it has still the old EQ values.
And it doesn’t matter if it is Frequency or a different EQ plug-in.
Can you confirm this behaviour?
Consequently, just applying a preset does not set the dirty flag in the plug-ins and therefore changes get lost on closing a project.
1 Like
Hi Ulf,
In Frequency is as I described before, project loads the preset as it was saved with the project, but flat. Reloading the preset is still possible and loads correct values. Saving the preset from within Dorico zeroes all curve points but keeps the name. When opened under Cubase this preset is empty, only the name stays. This a delicate point, because if you had a very elaborate preset and did not make a copy your work gets lost.
Changing the preset and closing Dorico works exactly as you said, closes without asking for saving and reopening the project loads the old preset but in my case - FLAT.
Changing the plugin and trying to close Dorico activates the Save? window, so this is correct. Changing the preset in other EQ does not activate the Save? window, Dorico closes, on reopening the project the old preset is there, BUT all data are still there.
So here we are.
Witold
Hi Witold,
there is one bug on Dorico end where, as I said, the dirty state of a plug-in is not raised and therefore changes get lost. That what you describe as presets being “empty” I could not reproduced so far, but I will try to. I’m currently pretty busy, but hopefully will find the time to in between.
Rest assured though that we treat it as an important matter.
Hi Ulf,
I really appreciate your attention put to this problem. If I find a moment I will make a short video, perhaps it will be helpful for the developers in finding what exactly happens.
Thanks again
Witold
Indeed, a screencapture would be very helpful, because something must be different in your procedure to mine. I created a Frequency preset in Dorico and then opened that very same preset in Cubase and it worked correctly.
Thanks very much for your effort.
I have a (probably) similar problem with some of my waves plugins.
Some of them will always be reset to default when I reopen a project.
Could you please elaborate on this a little, Stephan?
Is it alway the same ones, does it have to do with presets? Maybe you have also a DAW, do those presets work there but not in Dorico?
Thanks for clarification
Hey Ulf,
it always happens for the same plugins, and on these plugins it happens all the time.
The plugins (or Dorico) seem to forget about the changes I did in the plugins every time I close the project.
It doesn’t matter if I save settings as a new personal preset or use factory presets.
When reopening, the plugins are reset es to default.
In Cubase these plugins work just fine and after closing and reopening a project I find anything just as I left it.
Best regards,
Stephan
When you make a change in the plug-in, make sure you then manually save the Dorico project afterwards. Dorico doesn’t get informed that the plug-in has been edited, so changing the plug-in settings won’t cause the project to be marked as “dirty” such that it will prompt you to save when you close the project. But if you manually save your project, then Dorico will save the state of the plug-ins at that point.
1 Like
Saving the project has no effect on the plugins…
Hey Daniel, thanks for chiming in.
Sadly the plugins appear deeply unimpressed by any saving activity.
Hi @StephanK1 , I entered this issue into our bug database and will further investigate on it.
Thank you Ulf,
I’m still waiting for any feedback about this from the waves support. If there will be anything helpful I will post it here.
1 Like
Hi Ulf,
It was a moment since we discussed this subject, but it is back and even worse, despite of the latest upgrade to 5.1.60.
What happens since upgrade to 5.1.50 is that Dorico crashes on closing after an EWQL Play or OT Sine was used. It continues crashing even if every player was removed and project was completely emptied until I restart the computer (Mac Pro 2020, macOS Sonoma up to date). I attach the latest reports about Dorico 5 and VST Audio engine crashes. What really is unfortunate is that a very important project I work on uses both of them.
PLUS the old trouble with loading Frequency presets. I did not use them for quite a while, so I did not notice that nothing changed, but now, when I had to quickly create a decent mockup I found that the problem is still there, almost 6 months later it is still there. Guys, please, do something. I attach a screenshot of what I get after opening the project.
About crashes by now Steinberg must be flooded with my crash reports. I open/close Dorico a few times a day and every opening begins with message about a recent crash and asking if I want to send it to Steinberg. And I mercilessly answer “YES”.
Witold
Dorico 5-2024-10-13-035130.ips (92.0 KB)
VSTAudioEngine5-2024-10-14-004653.ips (40.1 KB)
Hi @witold ,
I have to apologies deeply, because I lost track with the Frequency presets issue. I remember having discussed this with Daniel as I thought that it needs to be fixed on the Dorico side and not on audio engine side. But somehow it got forgotten and only can ask you to forgive me. I put it up on the agenda again.
The other issue with the crashes is new and to be honest, I have no clue why this suddenly happens. Contained in your diagnostics is a crash dump of the audio engine, and that shows that Play is crashing the audio engine during shutdown. If plugins are crashing our engine, then we normally say that we can’t do anything about it and that you have to contact the plug-in vendor.
Well, in this case you might say, sure, but it was working before and only with 5.1.60 this now happens, so it must be a fault on the audio engine side.
I need to have a look what has actually changed and if that can have such big impact.
However, since it also happens with OTSine, may I ask you to check that you have the latest versions of OTSine, Play and Opus installed?
And you know that Play is not maintained (or will not be maintained any more) by EastWest? Opus is the successor and only that one should be used.
Hi Ulf,
Thanks a lot for putting the Frequency issue on the first position of your list. My complaining about it is the result of Dorico being really good. When the presets are correctly loaded my basic production time may get shortened in more than half. What I would still need to happen is Dorico’s mixer having a group channel (like Cubase has). In such case my setup would have best of two worlds, classic music notation (which is my best tool of composing) from Dorico and technical detail management (controllers and FX) similar to Cubase. I will even be able to copy mixer setups from Cubase to Dorico. All together giving Cubase-like level of control with enormous flexibility and speed for music changes and modifications. That would be a great breakthrough for Dorico users.
About crashes. I use Play despite of its user unfriendliness and having Opus only because Play setup of the library I use is better. As for Sine, I checked, I did not have the latest version (we got used to update notification, but Sine seems to not be there yet), so I updated it and voilĂ , nothing changed. I even reinstalled Play, and Opus is up to date. A small detail that may be helpful for developers is that Dorico crashes first when closed after loading Play/Sine and the second time when closed after removing them. Only the third opening of Dorico is clean. So I attach 4 crash reports, Play load/remove and Sine load/remove, all named respectively. I hope it helps.
Witold
VSTAudioEngine5-2024-10-14-135255 (after loading SINE).ips (42.4 KB)
VSTAudioEngine5-2024-10-14-135454 (after removing SINE).ips (32.7 KB)
VSTAudioEngine5-2024-10-14-135706 (after loading PLay).ips (31.6 KB)
VSTAudioEngine5-2024-10-14-135825 (after removing Play).ips (29.7 KB)
UPDATE on 0ct 15 - Dorico latest crash report:
Dorico 5-2024-10-15-032025.ips (190.2 KB)