AIR Iona vst VS Reaper DAW

[ghostwhistler]

I am serioyusly beginning to regret my purchase of this vst tbh. Installation was the worst experience installing any plug in. It sounds great, but midi learn can only be done in the DAW and is highly idiosyncratic.

Now I find, using reaper, that it won't record the midi data from assigned controller.

I have a NektarlX25 mk3 and I have assigned a couple of knobs to decay and filter envelope mod. These work fine (eventually). But when I go to record a take using those knobs (as midi overdub), it doesn't seem to playback the data. I think it has recorded it, if I look in the CC data it seems to be there. But it's as if the controller setting overrides the playback. That is, where I left the knob after recording, overrides the recorded data.

I have no idea why this is.

[Cuauhtli]

Reaper records midi overdubs with other vsti(s) using that controller I gather? Open the midi take and click on the {Velocity} tab at the bottom. The top option on the list that opens should be: Lanes with Events. Open those and it will show you if the midi overdub is indeed recorded or not. If it is recorded, then yeah, it's probably a vsti issue.

I remember having some issue way back when with Reaper where it would mess up my midi after I stopped recording (maybe zeroing it, I don't recall). I guess try clicking on the arm/disarm button to disarm the controller before moving anything and see if that saves it.

How is the AIR installation process btw? I have that tape feebie and Riser plugin that I got free but haven't tried installing them. Not sure I have a use for them, or that they're worth trying out.

[HOTF]

The few experiences I had with AIR products were bad so I just ignore their products right now no matter how good they might look Sorry if that's not what you want to hear - I hope they fix your issue

[ghostwhistler]

Reaper records midi overdubs with other vsti(s) using that controller I gather? Open the midi take and click on the {Velocity} tab at the bottom. The top option on the list that opens should be: Lanes with Events. Open those and it will show you if the midi overdub is indeed recorded or not. If it is recorded, then yeah, it's probably a vsti issue.

I remember having some issue way back when with Reaper where it would mess up my midi after I stopped recording (maybe zeroing it, I don't recall). I guess try clicking on the arm/disarm button to disarm the controller before moving anything and see if that saves it.

How is the AIR installation process btw? I have that tape feebie and Riser plugin that I got free but haven't tried installing them. Not sure I have a use for them, or that they're worth trying out.

THe installation was the worst experience i've had with a vst. I had to get them to help. You need to use their download manager (because of course you do) and it didn't read the file properly. It was easily fixed, but shoudl not have happened. Can't recommend.

Other vst's are fine.

In fact Iona reads and plays back modwheel and pb data just fine.

In fact the midi data is visible in the editor on the pertinent cc channel. But it won't play back. Doesn't even matter if i draw that data in directly.

I have no idea why this is. I don't have another DAW and don't intend to, to compare.

I can only assume it's intentional on the part of AIR, and having raised the issue, I shall be pushing for a refund. We'll see what happens.

The few experiences I had with AIR products were bad so I just ignore their products right now no matter how good they might look Sorry if that's not what you want to hear - I hope they fix your issue

Lessons learned. I certainly won't be recommending this if they can't fix this.

Fortunately it was cheap, but it's a shame because it sounds spectacular.

[ghostwhistler]

EDIT!

I have found a workaround.

Open the relevant parameter as an automation envelope. Then use the function there to assign the parameter to the relevent cc midi number.

An utter ballache. totally not the most expedient way of doing things and goes no way to explaining why the recorded cc data doesn't play. But it seems to work.

I'll still be pushing for a refund. This whole experience has been sour and I can't recommend this over something like TAL Bassline 101.

[digitalboytn]

I am serioyusly beginning to regret my purchase of this vst tbh. Installation was the worst experience installing any plug in. It sounds great, but midi learn can only be done in the DAW and is highly idiosyncratic.

Now I find, using reaper, that it won't record the midi data from assigned controller.

I have a NektarlX25 mk3 and I have assigned a couple of knobs to decay and filter envelope mod. These work fine (eventually). But when I go to record a take using those knobs (as midi overdub), it doesn't seem to playback the data. I think it has recorded it, if I look in the CC data it seems to be there. But it's as if the controller setting overrides the playback. That is, where I left the knob after recording, overrides the recorded data.

I have no idea why this is.

I have a very clear idea of what is going on...

It is called "user error"...

Don't blame the product when you have no idea how to drive the bus

Spend some time with it,RTFM and you will build up a working relationship with what is arguably the best DAW on the planet

[ghostwhistler]

I am serioyusly beginning to regret my purchase of this vst tbh. Installation was the worst experience installing any plug in. It sounds great, but midi learn can only be done in the DAW and is highly idiosyncratic.

Now I find, using reaper, that it won't record the midi data from assigned controller.

I have a NektarlX25 mk3 and I have assigned a couple of knobs to decay and filter envelope mod. These work fine (eventually). But when I go to record a take using those knobs (as midi overdub), it doesn't seem to playback the data. I think it has recorded it, if I look in the CC data it seems to be there. But it's as if the controller setting overrides the playback. That is, where I left the knob after recording, overrides the recorded data.

I have no idea why this is.

I have a very clear idea of what is going on...

It is called "user error"...

Don't blame the product when you have no idea how to drive the bus

Spend some time with it,RTFM and you will build up a working relationship with what is arguably the best DAW on the planet

My goodness.

This forum is amazing. For every genuinely helpful and productive rresponse, there's always five more like this. Utterly devoid of content, ego driven, nonsense.

Clearly you don't understand. You are not familiar with the VST at all. If you were you'd know that the manual does not include midi learn instructions at all. Iona doesn't have any. It has to be done in the daw.

You also don't understand reaper. If you did, you'd have provided something instructive and not this rubbish. You could , for example, have explained why Iona (and no other vst I own) records the midi data from the controller input but doesn't play it back. But you didn't.

What's worst about people like you is that in pointing this out I will be characterised as being ungrateful. Sorry, bullshit. If you came here to post something productive, then by all means. But I doubt that, because what Im responding to is at best mere condescension.

[digitalboytn]

Everyone is welcome to their point of view

[ghostwhistler]

Everyone is welcome to their point of view

It's not a point of view. This happens so often on here that the signal to noise ratio makes discussion almost impossible. I'm more than happy to hear people offer constructive advice or critiism. Telling me that it's "user error" when you understand none of what I'm talking about is extremely condescending and completely unhelpful. How do you not see this?

[Cuauhtli]

That is weird. I guess maybe try assigning a specific Midi channel instead of omni, or whatever Reaper calls it, and see if that works. Or you might set it up the way you got it to work and save it as a blank project/template and load in the future. I don't know if you can save a track template so you can import it into other projects, would be handy if you can.

[ghostwhistler]

I had contacted Air directly. A support representative asked me some questions. I replied. My support ticket was then cancelled without warning.

Conclusion: avoid these people. I certainly can't recommend buying from them. The whole experience hasn't been positive.

[mabian]

I had contacted Air directly. A support representative asked me some questions. I replied. My support ticket was then cancelled without warning.

Conclusion: avoid these people. I certainly can't recommend buying from them. The whole experience hasn't been positive.

Welcome to the club, and add broken promises to update their valuables old plugins to new resizable and modern GUIs. Never done. I dismissed them all.

[Andreya_Autumn]

You could, for example, have explained why Iona (and no other vst I own) records the midi data from the controller input but doesn't play it back. But you didn't.

I know Reaper well and could try to help you. I *think* this might be the information you need:

There's two ways to get MIDI CC's through to VST's in Reaper: A) via the MIDI input on the track, B) the control path. When you enable a MIDI controller in Settings - MIDI Inputs you will see (assuming Reaper 7 there's a few columns (Input - All - Control), where the last one enables the controller for the Control path.

The Control path is a global and always active path, which you can use for things like MIDI learn. When you use Reapers MIDI learn on a control, it will listen to the control path. Which is useful if you want MIDI learn to work without having to worry about setting up the MIDI input on the track etc etc. Or if you want rour MIDI learned parameters to work without the track being record armed, etc etc.

It's hard to know for sure, but *probably* what has happened is:
You set up MIDI learn from your keyboard to the Iona VST, incorrectly assumed that the MIDI learn data comes from the track path and thus you expect that *recorded* MIDI CC's from MIDI clips on the timeline should work on the learned params. But the params don't listen on the track path, they listen on the control path. Which is global and doesn't receive the data from your recorded clips.

Some VST's have *their own* internal MIDI learn. Which (of course) doesn't known anything about the separate control path Reaper has, but only listen to the VST MIDI input. Probably the other VST's that worked for you before, you used their internal MIDI learn, not Reapers external one. Note that some plugins can integrate the Right-Click menus so that if you right click a param, you see both the plugins own options and those of the host. In Surge VST3 for example you right click a param you will see "learn" twice, one is Surge's internal MIDI learn, one is Reapers.

So: Go to Settings-MIDI inputs and disable the "control" column for your keyboard. If your MIDI learn now stops working entirely, you have confirmation that this is your problem. Lemme know if that is the case, and I'll show you what to do about it ok?

[Dirk Diggler]

Also worth looking into ReaMidiControl, and of course you have to enable the lanes as mentioned above.

I don't have the plugin you're having issues with, but it seems to me it's pretty specific to the app and it's midi handling and not the DAW. I record full automation in Reaper all the time, including MPE.

I think Andreya has some great suggestions.

Also keep in mind most folks are actually trying to be helpful, but drive by quick advice without full reading comprehension, will always cause angst.
No need to scold folks for trying, if you think the advice is bad, just move on to the next post.

Good luck.

[Andreya_Autumn]

ReaControlMIDI is indeed the solution if the problem is what I suspect. But yeah, start by verifying that it is.