For some virtual instruments, when a note is repeated without any break between the stop of the first and start of the second, the second note plays no sound. This does not happen if the pitch changes, only when the same note is repeated. If the first note is instead ended just before the second begins, then both notes play fine.
Does anyone else experience this problem? If it's expected behavior, then is there a way to make it not happen? Going through and manually adjusting the end time of the first note everywhere it happens does not sound fun to me
Each MIDI note has a "note on" command at the start and a "note off" at the end. If two notes overlap a tiny bit, the note off from the first note can keep the second note from playing.
Quantizing the notes can help, assuming you can find a quantize setting that matches what you're trying to do.
I'm familiar with the midi format, and I have quantized both the start and end times of the instrument's track to 1/16th notes. I'm currently experiencing the issue with Spitfire Audio's recently released BBC Orchestra library, specifically with the strings. I have had a similar issue in the past with other sounds, I just can't recall which ones at the moment. I solved the issue then by forcing the note to end a fraction of a second before the next note was supposed to start, but this is really clunky and I've finally had enough of it...So now I'm here!
I'm a programmer myself, so feel free to get technical if necessary
I've noticed one other thing while putting together the project to send over, though, might be helpful. When I try mixing down the midi string part created with the Spitfire plugin, the .wav file has no sound. Additionally, the midi track no longer plays any sound until I reselect the midi instrument, but it still fails to play repeated notes.
I'll include all this in the support ticket as well, however it's super easy to replicate if you pick up the Spitfire library...I'm not sure whether that instrument set will survive the trip across the internet...
And no, it doesn't happen with any virtual instrument, the strings section provided with MC plays fine. It's currently a problem with instrument I use that's part of Spitfire Audio's recent free 'Discover" library, even percussion sounds.
did you analyse the midi events carefully to be sure that a midi off message is being sent? Depending on how you are entering your midi information all of the control messages may not be sent.
Another thing to check for is if the midi controller is sending the same exact midi note on multiple midi channels. For example, on the PX-5s piano/synth when I use it as a controller to enter midi notes, I have to be aware of what patch it's set to. Some patches can have multiple layers going to different midi channels and in effect sending the exact same note to a daw or instrument that is receiving omni or all channels. The result can be a weird phasing or an instrument not playing at all under certain circumstances because it can't resolve the simultaneous playing of the same note.
I'm not sure how to analyze the midi events inside MC to determine if the off message is sent, so a quick rundown on this might be helpful. But let me just describe a really simple workflow that creates the problem, and perhaps rules out some of the other controller/channel issues you suggest.
1. Create a blank project with one VI track
2. Create a clip
3. Change the instrument to one of the BBC Orchestra instruments
4. Place two notes back to back, ensuring that they're quantized appropriately so that one note ends at the same time as the next begins.
With this process, the first note in the clip will play, and it will end when it's supposed to end. However, the second note, as long as it's the same as the first note, will not make any sound.
Let me reiterate, at the moment, I'm ONLY experiencing the problem if I use an instrument that's part of Spitfire Audio's Discover VST plugin. If I come across another instrument which has the same problem and is not part of that plugin, I'll mention it here.
@Greg,
I believe they have their own proprietary "player" and a series of sample/instrument packages that load within, similar to a Kontakt etc. Configuration.
Full disclosure: I signed up for the recent offer of a free library, and discovered some other interesting stuff from them, but I havent had an opportunity to download/install/explore yet.
But it appears you can install a free player and a number of free sample packs.
On the other hand, they also offer some pretty high priced libraries as well.
I have not contacted Spitfire yet, something tells me they wouldn't release their software without making sure repeated notes could play. What Mark says seems accurate. I don't know the details about what makes a plugin different from a library or a VST, but I know that in their more expensive packages the instruments can do some pretty impressive realistic effects, things that would be quite complicated to do in a midi editor alone.
I'd be surprised if, as a DAW developer, they wouldn't give you access to their free package without the 14 day wait. To be honest, I'm surprised they didn't reach out to you (Acoustica in general) to make sure it worked with your software. I guess I probably just don't know the business well enough.
I was looking forward to using the BBC Orchestra stuff, but this is super annoying and keeping me from doing so.
