VEPRO does not react to Reaper MIDI Bus 17+ (FIXED)

[mathei]

No midi on 17/1+. "Map Reaper MIDI Buses to VST3 MIDI Buses" in I/O for both input and output is checked. VEPro7 Server is set to 48 midi ports per instance and VEPro VST3 plugin to 48 midi ports too. Using Reaper version 7.02 with 128 buses.

[GeneralMidi]

Can confirm. The 128 midi Busses certainly does not work. When sending out on bus 17 channel 1, vepro does not receive midi at all. No activity.

Using reacontrol, every message states "Channel 1". Does reacontrol need to be updated so users can see what midi channel is being sent out?

[asai]

Can confirm bus 17+ doesn't work in VEPro 7, hopefully devs will see this and make it a priority.

[GeneralMidi]

I don't think it will be a priority, but hopefully if enough users mention it, Justin or schwa might have an idea why it's not working. I downloaded midiox and tried to help out by seeing if I could work out what was going on, but I'm not experienced enough in the technical side of things.

[smandrap]

I remember several discussions about this. So yeah, I can confirm and hope it’s solved

[GeneralMidi]

If the devs could point me to how I can test this, I have midi ox and virtual midi ports set up, I just don't know what I'm looking for.

[asai]

That was one of the promoted features of Reaper 7, so hopefully they can have a look soon. I've also worked with MIDIox, but I'm not sure that you would see it in MIDIox. I tried looking with ReaControlMIDI, but that doesn't seem to show much either. Not sure what else might prove helpful...

[GeneralMidi]

Yes, it was promoted as a key feature. I tried in reacontrolmidi, but there are feature requests for that too as it is not clear.

[asai]

I've tried several other utilities over the last few days, but I'm thus far unable to see any traffic passing between the two applications, not sure if it's even possible.

[EvilDragon]

I bet it's the case that all 128 busses work for internal connections within Reaper, but devs forgot to expand the option to convert to VST3 MIDI busses to support more than 16.

[smandrap]

Originally Posted by EvilDragon

I bet it's the case that all 128 busses work for internal connections within Reaper

eggsactly

[asai]

Thanks E.D., yeah, that would make sense. Hopefully it's something that's fairly simple to fix. Wish I could just do it myself and send in a pull request... Reaper open source... probably would drive the devs crazy.

[EvilDragon]

Bump on this one. Devs, this seems to be a clear oversight when number of MIDI busses was increased in Reaper, so there's a mismatch on VST3 end as it stands...

[Vadium]

I updated to version 7 just in order to expand the number of buses/channels (to work with multiple MPE plugins), and this function does not work in the end.. Developers, please!

[asai]

Thanks for the bump. I was debating whether or not I should bump it. Would definitely like to see this addressed.

[smandrap]

Fixed in 7.13

[Vadium]

it still does not work in Reaper 7.13. on channel 16 it is sent to Vepro 7.3.3610 as VST3i, on channel 17 it does not work. What's wrong?

Update: after the computer restart only first bus works - even buses 2-16 aren't transmits midi to Vepro..

Check it please

[asai]

I just tested 7.13, and I can confirm that it still does not seem to be working with MIDI bus 17 and up.

[asai]

Tried this on 7.14 as well (on Windows 10), and still not working by following this procedure:

-- In VEPro 7.3.3610, set plugin MIDI channel to receive on Bus 17. (also called "port" 17 in VEPro lingo.)
-- In Reaper, set MIDI send on track to the appropriate VEPro VST instance (which is configured for 48 MIDI ports) and Reaper track MIDI receiving input on all channels, and sending to Bus 17 (all).

Expected result -> VEPro receives MIDI data

Actual result -> VEPro receives no MIDI data

[ivanduch]

I can also confirm it doesn't seem to be fixed in 7.14. Has anybody found a workaround?

[Justin]

Ahh, we fixed it for the REAPER-mapping bus-to-bus, but not the mode that maps REAPER-buses to VST3-buses, fixing that!

[asai]

Justin, you are a very generous man.

[ivanduch]

Originally Posted by Justin

Ahh, we fixed it for the REAPER-mapping bus-to-bus, but not the mode that maps REAPER-buses to VST3-buses, fixing that!

Thanks a lot Justin!

[ivanduch]

I see it's on the list for 7.15 but I still can't make it work with Vienna Ensemble Pro. Has anybody else tested it already?

[asai]

Dang. I hate to say it, but I can't get it to work either. Still no response on the VEPro side. Same procedure as I outlined above, and same result.

[Justin]

ah this is embarrassing, 7.16 will be the release that finally fixes it...

[Gryno19]

Originally Posted by Justin

ah this is embarrassing, 7.16 will be the release that finally fixes it...

No need to be embarrased who know if this thread wasn't started the devs wouldn't have known it's an issue worth fixing

[asai]

Thanks, Justin. You are a true gentleman.

[Justin]

(we should just get a copy of VE so we can actually test these things, lol)

[ivanduch]

Thanks again Justin! Count me in if you need any beta testing, I also imagine Vienna would send you a free copy for dev purposes if you ask.

[asai]

I downloaded and installed v7.15+dev0418 and still no response from VEPro.

I've made this Licecap to show what my settings are for some visuals (if Bus is changed to anything below 17, it does work.)

https://imgur.com/a/Seoxfgk

[Vadium]

Confirm, still not able to send MIDI to 17+ bus of VePro on Reaper 7.15

Originally Posted by Justin

(we should just get a copy of VE so we can actually test these things, lol)

Hi Justin, there is a 30days free demo of VePro on VSL website: https://www.vsl.co.at/en/Vienna_Soft...a_Ensemble_Pro

[Justin]

Originally Posted by asai

I downloaded and installed v7.15+dev0418 and still no response from VEPro.

I've made this Licecap to show what my settings are for some visuals (if Bus is changed to anything below 17, it does work.)

https://imgur.com/a/Seoxfgk

Thanks for the video. I assume the VE VST instance has the “map reaper midi buses to vst3 buses” option set too?

[ivanduch]

Originally Posted by Justin

Thanks for the video. I assume the VE VST instance has the “map reaper midi buses to vst3 buses” option set too?

At least in my case, I'm using that option but still doesn't route the midi to VEP in buses above 16.

[EvilDragon]

Originally Posted by Justin

(we should just get a copy of VE so we can actually test these things, lol)

Contact them, they are open to sharing NFRs for fellow host developers!

[Justin]

hah I think I found the last remaining problem, if it's not fixed in today's build I'll reach out to VE

(I'm also very lazy when it comes to installing various plug-ins...)

[ivanduch]

Originally Posted by Justin

hah I think I found the last remaining problem, if it's not fixed in today's build I'll reach out to VE

(I'm also very lazy when it comes to installing various plug-ins...)

Thanks Justin! Fingers crossed.

[asai]

Much appreciated, thanks for persisting in this. I'm a programmer myself, so I understand the process is often not straightforward.

Justin, you likely already know this, but one of the reasons this is helpful is that in VEPro there are "Instances" that allocate CPU resources to a group of VSTs. In those instances are instruments loaded that require an assigned MIDI bus. If I want to keep all related patches in a certain instance, then sometimes more than 16 buses are required. It helps with keeping things organized and logical.

[asai]

Running v7.15+dev0419 and can confirm buses 17 and up are indeed working now.

Cheers!

[ivanduch]

Originally Posted by asai

Running v7.15+dev0419 and can confirm buses 17 and up are indeed working now.

Cheers!

Where can I download the dev builds?