Problems with tempo in imported midi

I am trying to export midi from Reaper and import into Dorico.
It ignores tempo changes and plays at a ridiculous speed.
I can see the tempo changes in to imported midi (in the midi editor). dorico plays back at q = 500. Marvelous!

It shows the tempo markings in the score too. Even if I delete these and add new markings they are still ignored.

There’s a little thing to open “Used in this flow“. These show what is visible in the midi view - but as a list.

So is it actually possible or will I have to transcribe the thing note by note?

Sounds like you’ve got Fixed Tempo mode on?

If you want the tempos in the score to be obeyed, make sure the tempo indicator is blue.

Thank you. There was an initial setting of q = 600 (in the midi) - with this present it didn’t matter about the tempo indicator being blue. Then I imported into cakewalk sonar, removed it and exported again. Dorico now plays back OK but where Reaper’s tempo “envelope” had a simple slope for a ritard in Dorico this awful mess appears. There’s probably a way of fixing it…

Hi @Paul_Ritchings, you can delete those tempi also from the Key Editor’s Tempo lane:

CleanShot 2026-03-12 at 22.42.08

No. When the initial setting of q = 600 was included anything tempo setting after that were ignored and it did not matter whether the tempo indicator was blue or not.

I’ve already said this.

Thanks. I’ve found that and the line tool for continuous changes.

Maybe just create a new flow with the same instrumentation then copy and paste the notation into the new flow. I find that this has solved the occasional issues that can arise with MIDI or musXML imports.

So the title was changed for me…

For information: I tried some more experimentation - thinking that perhaps the issue was with Reaper. I exported from both Sonar and Reaper with and without the q=600 tempo setting. Export from either without the setting and Dorico behaved as we should expect. With the setting Dorico did indeed ignore any subsequent tempo settings.

If I had found the problem was with Reaper I would have said so here and informed Cockos Inc.

This is a bug. I know about it now so it’s simple enough to avoid.