Also, I will check, when the problem occurs, if something changed within the patch. I dont know if Logic transmits some sysex that could change something, but that sounds a bit far-fetched doesnt it?
-
Rasmus, Any time I've had really strange playback problems like this (not exactly your problem, but you get the idea) it's generally been the result of an errant controller somewhere. That is, a controller value is being sent to something in the VI that I was not expecting. Double-check your controller assignments in the VI, just to make sure they're not being accidentally altered by something coming from Logic. Just a thought. --- J.
-
Yes! That's it. I have it on every project after a few hours. Especially with legato and sustain patches. Bloody irritating when one's trying to earn some money with it.
But it's to be solved by emtying the cache and reload the patch? What does emtying the cache mean?
-
I knew Logic was doing harm to VI, but I just didn't figure out how to resolve it... What specific controller assignments are doing this exactly. Until now I didn't know what to search for...
-
Hi all. I doubt whether Logic would transmit sys-ex data of its own accord, but you can check the contents of a sequence in the Event List ('Apple 2') - scroll down and you'll see each individual piece of MIDI data. If a sequence happened to contain spurious MIDI information such as unwanted aftertouch or controller information, it would most likely have been generated by the master keyboard. If that's the case you can filter the unwanted data out on input (File -> Song Settings -> MIDI -> Input Filter. Tick the boxes for the stuff you don't want to record.)
-
I get it sometimes. WindowsPC/Cubase4 here.
It's really not the end of the world, though, for me. It in fact doesn't "come and go", I've found that it has to do with relying on the legato patches to do your note transitions, and ending with two notes actually held down. It seems to confuse it. Even letting off the oldest first...it seems to still trigger the older note's release sample after the end of the final note. If I play it cleanly, or edit the part to a closer overlap, it goes away.
you might try that.
-
The same to me with Sonar and VI solo-strings when I use legato and the value of a note is long. So it happens often on the last note played of a musical phrase.
Sergino
-
This cannot be the problem with my setup since when the problem occurs the strange tones are sort of random, so there are also notes that I didn't use in my project. When I stop playback and play some notes on my keyboard they sound like a rythmic loop. Only when I start playback from another point, it plays correct again, but when I start playback from the beginning it's there again. Help...!@popmann said:
I get it sometimes. WindowsPC/Cubase4 here.
It's really not the end of the world, though, for me. It in fact doesn't "come and go", I've found that it has to do with relying on the legato patches to do your note transitions, and ending with two notes actually held down. It seems to confuse it. Even letting off the oldest first...it seems to still trigger the older note's release sample after the end of the final note. If I play it cleanly, or edit the part to a closer overlap, it goes away.
you might try that.
-
I'm still getting this same error... Even with "Play Release" switched off in the "perform" screen, and note-off velocity at zero. Have there been any developments? It's getting a bit boring.