When I change the level on the send, the level changes on Fx 1 as expected
I turn off send to Fx 1 - no sound is sent to Fx 1 as expected
What could cause channels to send to Fx 1 by default? As far as I’m aware, audio from an instrument channel can only go to Output, optionally also to actively selected sends, so I’m not sure if I’ve done something here or if I’m observing a bug.
Dorico 6.0.22.6052
Edit: Please note that before this observation, the Glockenspiel had not previously been sent to Fx 1. So the send was in its default off state when I noticed this.
Ok, I might be misremembering with regards to the last edit and therefore the premise of the initial title and conclusion. I say that because after observing the above I closed my session and opened again.
I have now successfully reproduced this issue several times and have boiled it down to the bare minimum. It seems like a UI bug where send values are not correctly displayed in the UI.
@dspreadbury I can supply video where I reproduce the issue and also Dorico project in private if you’d be inclined to have a look?
I’m experiencing that Dorico is not initializing the Play page correctly when opening a project. The sends work but are not represented in the UI, it is very frustrating.
I have ruled out most complexities I can think of, down to just opening an empty project, importing a flow and applying a playback template. It is consistently occurring when I reopen the project.
Hi @christerdk , could you please also provide me the video and possibly the corresponding project file in order for us being able to reproduce your issue? Thanks a lot
Hi and sorry for the bit late reply.
Maybe it is due to the missing sound libraries (You use libraries that I don’t have), but I could not find a way to reproduce your issue. I will hand over the case to our tester, maybe he can find out something. Let’s see…
I’m also unable to reproduce the problem. @christerdk, if you start a new project from one of Dorico’s factory templates, and use a factory playback template, are you able to reproduce the problem?
It sounds as if the steps should be something like:
Remove the default Reverb FX channel.
Add a new FX channel, which appears as FX1.
Enable the send to FX1 for one Mixer channel, and set the level.
Save, close, and reopen the project.
However, I find that Dorico always correctly shows the expected send level when I reopen the project. What am I missing?
That is indeed a good question. After reading your response, I tested creating a new project and add the three fx channels for my need, as a baseline test. And of course, it works perfectly fine
So I thought maybe it has something with the scale of use. Maybe I had just reached some limit specifically in the Play screen with my workhorse instruments, as they do take up more CPU while initializing and ram for samples. So I removed half of the instruments, saved and reopened the project. The project loaded faster but the issue still persisted.
So I decided to take the long road (I’ve done my fair share of software testing before) and actually build up a project from scratch. I screen recorded the whole process.
TLDR: I was able to reproduce the issue.
I create a new project based on template Empty
I import a flow from a different Dorico project
I add three FX channels
I add a reverb to each of the fx channels
I add random sends to the first 9
I start adding VSTs one-by-one.
I then reroute the first 9 tracks to the new VSTs.
Note: The instrument is removed from it’s current position and added to the end of the mixer and the send levels are no longer present on these instruments. I assume that’s a result of the re-routing process. Fair enough.
I add send levels for these instruments again
I then add some random send to other instruments (Horns 1+2, Trumpet 1), but I don’t replace the instruments
I save the project
I open the project again
Result:
The sends levels I set in step 9 are not visually shown in the mixer
The sends levels I set in step 10 are shown
While the send is state = Off for the Step 9 instruments, the track / instrument is actually sending to the FX channel. I show this by playing a flute instrument and you’ll see the meters indicate audio on the track channel and the fx channel.
The video is quite long and while it may contain relevant context information for you to uncover the issue, Step 9 starts at timestamp 14:30.
I’ll send the video to @Ulf as I have his email address.
I decided to make another test in an effort to figure out what is the minimum to trigger what I’ve observed.
In the new video, “simple build”, I create an empty score, manually add three instruments (no flow import) and three fx channels (no reverbs added) and replace one instrument in Play. I add send levels, save and reopen.
That’s golden, Daniel. I hope it’s not too much of a headache.
I just observed another thing with the mixer and created a new post. It might be related this issue but I wasn’t sure, so didn’t want to sidetrack this thread more than providing this heads up. The new observation is here.
I’m looking at a collection of projects that would need to have their sends values nudged and dialed in better.
Unfortunately, they all suffer from having their send values displayed in this way, which means nudging isn’t practically possible.
Under the assumption you might have found and solved the issue and that it’s a UI state issue (I assume that because the sends work), I would be happy to give any beta version you have a go.
Is there any update on this? I ask because I just experienced what I think is a related issue: I added a new player to an existing score and thus a new track. All instruments that had working reverb send but invalid visual send state (per the above) all got the sends reset. The result was that all these instrument became dry.
The few instruments that had a visually valid state kept their reverb assignment.
Also, I only have to switch between Play and Write a couple of times and then the reverb setting state is visually incorrect again.
So while I can assign all the sends again, it seems it’s just a matter of time before they get reset to dry again.
Dorico Pro 6.1.10 / Windows 11
PS. I’m open to a screen share session if you’d like to dig deeper in the state of my project.
Absolutely, it’s on the way to your inbox now! Hopefully you’d be able to attach a debugger and see what goes on underneath the hood.
Instruments are primarily Acoustic Samples (UVI Workstation,p retty light in terms of memory footprint) and AudioBro MSS / MSB (Kontakt, potentially quite large footprint, but I purge regularly). But I’m not sure that the specific instruments are part of the core problem, as the observed problems occur on any type of instrument, seemingly at random.
What I’m really curious about is what happens in Dorico that makes it evaluate and seemingly reset the endpoint config on unrelated instruments? The instruments are not bundled in any way, not intentionally, at least.
@Ulf I searched more and based on what I found I have a follow up question: when creating a new player + instrument of a type (in my case a Flute) that was configured in the (far back ) originating playback template for the project, could it be so that Dorico potentially wipes the mixer settings and re-applies the playback template to all instances of instruments included in the playback template? If so, that could explain why I saw all the sends return to off and reset the send value.
If that’s the case, at least there’s an explanation for that part - although that makes it quite tricky to add new players. From what I read, the solution could be to delete the referenced playback template, to cut the connection with the playback template?
If that rings a bell with you I think we can park that observation for now - the invalid UI state in the mixer is unfortunately still happening.
