MLB

Thanks so much both! I appreciate it

But if I uninstall it I wouldn't be able to use EastWest, I suppose. Or do you mean uninstalling to then re-install it? Thanks for your help.

And this might seem like a very basic question, but how do I delete the PLAY component? And is there a risk that my sessions might corrupt if I do?

Thanks David, I thought that might be the case. In fact, this is happening to me on sessions in which I am using PLAY.

I'm having this same issue. @thesecession what do you mean by the PLAY component? Thanks!

Unfortunately not. It's frustrating, isn't it?

'Selection as MIDI file' Actually the file I attached last night works fine when open in Sibelius because it hasn't been exported from my computer, but let me attach one here that has been exported form my Logic. To clarify, they are both fine when opened in Logic, but if you open them in Sibelius, the one I've attached in this post is 2001 bars long, because it's been exported form my Logic, the other is like 60 bars which is what it should be. I wonder what it is, maybe something in settings? midi test 2 28.04.20.mid

I've been asking around and nobody knows the answer. It seems to only happen when exporting the midi from my Logic in my computer. I've attached a MIDI file in here, you should be able to open the project by right clicking on it and selecting open with Logic. This is driving me crazy!!! I can't find the solution... THANK YOU MIDI TEST MLB.mid

Hi, I've been having this issue on a specific Logic session where I export a midi file with 'export from selection' from a couple of instrument tracks, having activated cycle (loop) and having set the end of the project to 40 (for example)... If I open the exported midi file on Logic everything is fine. But when I open it on Sibelius the project has 2001 bars in total. I've tried all the obvious things, checking midi events, markers, tempo changes, automation, opening a new session in Logic and importing the project again, changing settings in Sibelius, etc. I think it's a Logic issue, and not Sibelius, because when I open a new project from scratch and export a midi file it works fine. It's worth saying that the problematic session has a movie file, but it continues behaving that way even when the movie file has been deleted, and the audio. To be honest, at this stage I just want to get to the heart of the problem to understand what's happening and prevent it from happening in future projects. Thanks for your help!!

Good point! I'll look into it

For me it's a way of manipulating sound, a way of getting to an interesting result by changing the tempo of an instrument (or equivalent) drastically. For that reason, the wider the range of tempo, the better for me.

Aw... That's a huge limitation... What tool would you use to manipulate the speed of the recorded material live?

Is there a way to go higher than 177bpm or lower than 50bpm when controlling the tempo fader then? Any tricks?

Thanks! I'll get back to you once I've looked into and tried your suggestions.

What would that be? Also, I couldn't find any manual about the FX version of Maschine's plugin. Does anybody know where to find some info about it?