You have to start the dorico file, which then will open midipipe. Every time you open Dorico. I made a shortcut which first open midipipe and then dorico.
It doesn’t work either with regular chords or “one note chords”
Perhaps there’s a second MIDI translation issue. Someone who has this problem will need to provide a MIDI log.
@benwiggy
I assume you’re not talking about Diagnostic Report.
What is the way to extract MIDI log?
TIA
IB
P.S. Generally, I’d expect the company of Steinberg rank, being able to get that kind of data on their own. Is that unreasonable?
I’m talking about using a MIDI logging utility, like MIDI Monitor, as described above.
It seems to be only some MIDI keyboards that exhibit the problem, so I guess it depends whether you think it reasonable for them to have access to any and all MIDI peripherals that exist for their testing.
@benwiggy
Given the similarity of the problem, the root cause should be the same for the models mentioned in this thread.
For example, midi device is M-AUDIO Keystation 49
Also, one can only admire and envy many Dorico users for being savvy.
But I believe such problem should be solved by engineers, not by musicians.
People who have applied the “fix” say it works for everything except Chords, so there may be some other issue at play.
If anyone wants to help, then that would expedite a solution. If not, fine.
@IgorBorodin, we’re exceptionally fortunate to have many musicians here who are also expert Dorico users. They dedicate a great deal of their time to helping others, so while I understand your wish for a prompt response from the development team, there is probably little more that can be done until the next Dorico update. Daniel has already indicated that an update is not imminent.
As the release notes for each release (including the many interim updates) demonstrate, the development team is highly responsive to issues as they arise. I’m sure they will want to address any incompatibilities with macOS Golden Gate as soon as is practicable.
Alas! It hurts so much to see my fix in parentheses ![]()
But I suggest that @organ first does the search and if none is found reports this as a separate issue. Indeed, I found out how one should add a chord to a certain position using MIDI keyboard and I can verify that it does not work. With or without my “fix”. MacOS 27, Dorico 6.2.30- chord symbols do not appear in popover when I play them on MIDI kbd. I tested with VMK-188Plus that requires the fix and also with iRigKeys 37 that doesn’t. Same result. So the chord issue deserves another thread (if that is not already opened).
I cannot tell if this was broken with OS27 update because it was my first time to enter chords in Dorico.
@Ulf , I also have a bug to report. The chord issue that @organ mentioned has a nasty addition here, 100% reproduceable (so far):
If I open a chord popup and close it without touching a MIDI keyboard, it is ok. BUT when I try to enter a chord in chord popup using MIDI then in addition to chord not appearing no furher pitch info comes from my keyboard to dorico. Midi thru keeps working but I cannot enter pitches. The only solution I have found is quit Dorico (and VST engine with it) and open it again.
I am lucky that I do not need to enter any chords to do my work.
Hi @composerkaumann , I have a fix version here where notes don’t stick any more and also chord input works. Can you describe once more in greater detail what you do in your case, so I can cross check here? Thanks
A short list of steps:
- select a note in score
- activate chord popover
- try to play chord (or chords, or anything) on MIDI kbd
- close popover with no chord appearing
That is it. After that MIDI Thru keeps working but I cannot enter pitches, the caret does show only pauses in note entry mode.
I can’t confirm your behaviour in the old, broken version.
I press shift Q for the chord symbol pop-over and play on the keyboard and I can hear long sounding notes, but no chord symbols get entered. Then I escape from the pop-over and no notes get entered any more, but then when I click the mouse somewhere on the stave note input continues (and also chord input works for me, i.e. stacked notes appear, not chord symbols) This is what happens in the old broken Dorico.
My fix version behaves as expected in that situation.
And by the way, we will try to get out a hotfix version as soon as we can.
I retried after reading this and I am puzzled. After trying to use Chord Popup no notes appear any more. MIDI Thru works, sounds change as I move between instruments but no pitch entry. Clicked and tried with several variations.
I’ve tried the MIDI Pipe suggested solution, and followed everything to the letter, including allowing MIDI Pipe to run. But when I click on the MIDI Pipe icon, it just sits there, bouncing up and down and doing nothing/ Is there a solution for this?
Thank you, Ulf!
Can’t wait for Dorico release with that fix.
Meanwhile, for Dorico users who are not willing or comfortable using the fix suggested by @composerkaumann (sincere accolades to you), I came up with an alternative trick.
Piano does not exhibit that ‘stuck’ note effect; just a short reverb.
So, I added to the score a temp piano stave and entered the notes for violin part there as usual. Then simply copied the music to violin stave and removed the temp piano stave.
Yes, it’s utterly primitive, but until we get Ulf’s fix, it may help some users.
IB
Sometimes simple solutions are good. I considered having Pianoteq app open and Dorico’s Midi thru off, no overall sustain in this case, just piano sound but I was too curious to find out why all this happened.
Great solution! Many thanks for this. Now I can get back to getting work done!
I am truly impressed by the speed Steinberg addressed this.