With that what you are describing and looking at your Dorico log files, I actually am totally puzzled and have no explanation for the behaviour you describe.
I guess @dspreadbury also has no none. I’ll forward the data I received from Roeeli, so please also have a look.
At least not at the moment. Our current logging does not give us enough information, therefore we need to add more logging. Dorico 6.1 will become a free update for 6.0 customers, so please wait until 6.1 is available.
MIDI toggled itself on, a few minutes after installing 6.1 - will the logging now give you more information as to why it keeps doing that? If so, please tell me where to send the files - they are to large to send here
Next time it happens, do Help > Create Diagnostic Report immediately and make a note of the time at which this happened, then attach the resulting zip file here.
Thanks! The files are too large to send here - where else can I send them?
And while we’re at it (I guess it might be related) - lately, a few times a day, Dorico suddenly stops receiving MIDI input. Other apps still receive MIDI, so it’s a Dorico issue, and not system MIDI issue. I need to restart Dorico to have it work again. I think it usually happens after I switch to another MIDI app and back. Is this a known problem?
This is how the folder looks - the Zipped folder is 6.5MB
Also - it seems that creating diagnostics file to the desktop now overwrites the previous one - I saved two different diagnostics files today for you to look at, but only one survived. This wasn’t the case in previous Dorico versions as far as I can tell (they were named differently) - might this be a version 6.1 bug?
No, there’s been no change in how the zip files for diagnostics are named.
For the time being, please remove all but the most recent files from the Dorico 6 AudioEngine/logs folder. I don’t need any historical logs, only the logs that are relevant to the specific time at which the problem occurred.
Be sure to tell me the precise (or as precise as you can manage) timestamp at which MIDI thru unexpectedly became enabled.
Thanks, I will as soon as I create a new diagnostics file that captures the problem.
As for the diagnostics rewrite issue - here’s a screen capture of me creating a Diagnostics report, the Desktop window is below - you can see that when I save a report it rewrites over the existing one from 2 minutes before without warning. Previously, a new Diagnostics file was created, with a number added to the name.
I’m assuming this might be related - at (or very close to) 6.17pm, Dorico stops receiving any MIDI information from USB controllers. A reboot of Dorico is needed for note input to work again. No other MIDI related apps are affected, so apparently it’s a Dorico issue. (This happens to me very frequently lately)
All the files in the log have the exact same “last modified” and “time created” time stamps (the time the diagnostic report was created) - how do I know which files I can delete before sending…?
Here is a log file created right after MIDI Thru toggles itself on again. Since it’s too big to send here and I have no way to know which are the newest Audio Engine Logs that you need to see (all files have the same creation time stamp), I’m sending the compressed “Activation Manager” and “AudioEngine” folders separately.
I noticed the problem at 3:39 pm - it might have happened a little sooner.
Hi @roeeli, Daniel built some additional logging into Dorico 6.1.10. According to the latest logs that we have from you, you are still on 6.1.0, so one before the latest release.
Please do an update to the latest, unless you have a very good reason not to do it. Of course, 6.1.10 will not solve your problem, but give us more insights into what is happening with you. So please send me a new diagnostic report when you get into that situation again.