Solved - This should be an easy midi connection, but not.

[Curtis]

I'm trying to send the midi output of Muse score to reaper. Muse score sees loopback midi, reaper also sees loopback midi. So I tried to use it to communicate from Muse score to Reaper. But it does not work, I guess there is something else I should also do but don't have a clue what.
I looked in manual for reaper that was no help.

[LowlyOP]

Eliminate some variables:

1. Have you had any previous success with similar arrangements?

In other words; are you able to establish a connection between (Ableton, Maschine, MPC Studio, or any of many other examples) standalone midi capable software besides MUSE) and Reaper, using loopback?

2. Have you tried loopMIDI? Bome's MIDI translator?

[Curtis]

I no longer have Ableton, I quit using it three years ago. Never buy machine or things by that company, always see problems with there products on the forum.
The only thing I have used loopback midi either is reaper.

[mschnell]

AFAIK, both Reaper and MuseScore support Music XML, So maybe it it might be a better idea to load the notes to appropriate tracks instead of trying to run both in parallel in realtime.

-Michael

[Curtis]

My intent was to avoid using reapers notation, because it is not as friendly as
Muse, I'm sure there will be ones that dispute that and at the same time have never used Muse.

[mschnell]

Yep I thought that this would be your intent.

Hence do the notation in MuseScore -> write XML file -> import in a Reaper track -> playback by Reaper.
-Michael

[Curtis]

I have the connection between Reaper and Musescore resolved evidently bus17 is not compatible with Reaper.
Everything is working as it should.

[mschnell]

Thanks for letting us know !

Just wondering: what is "bus17" ?

-Michael

[Curtis]

Originally Posted by mschnell

Thanks for letting us know !

Just wondering: what is "bus17" ?

-Michael

That is the buses reaper supports, I'm using loopmidi that gives additional midi resources.
Reapers supports up to bus16, also note Reaper uses bus01 for it's midi channels.

[mschnell]

Originally Posted by Curtis

That is the buses reaper supports, I'm using loopmidi that gives additional midi resources.
Reapers supports up to bus16,

Ahh, This issue did come up by yourself some weeks ago. -> https://forum.cockos.com/showthread....light=loopmidi

LoopMidi is the culprit here !
It by default assigns the names similar to "Loopmidi Port 1" Loopmidi Port 2" ... to the Midi devices (not officially to be called "Ports" or "Buses") it creates, but in fact you can name them in any way you like.

This has nothing to do with the "Midi Buses" 1 .. 16, Reaper internally provides. Just a coincidence of names.

Why did you ignore the answers to your question at 6/2/19 ?

Originally Posted by Curtis

also note Reaper uses bus01 for it's midi channels.

As explained in the other thread, Reaper internally handles 16 Midi "buses" (Reaper speak), each comes with 16 Midi "channels" (official speak), making a sum of 256 "virtual midi channels" (my speak).

-Michael

[Curtis]

This has nothing to do with some post of several weeks ago.

[Curtis]

To whom ever asked regarding responding to a post when the rest of the forum gets to 100% of answering post at that time I will follow.

[mschnell]

Originally Posted by Curtis

This has nothing to do with some post of several weeks ago.

That thread was about Midi Buses in Reaper, and the misconception introduced by LoopMidi, by default not calling the multiple devices it creates "devices", making you confuse them with Reaper's internal Midi "Buses".

But OK. Then I fail to see why you were searching for a "bus17". Maybe I am missing some important point.

-Michael