Now that I'm pushing my system up[ around 90% I have been getting a stuck note on occasion. MIDI reset from controller will fix any Giga related notes, but in Scope dev.'s I use to just enter "0" in the polyphony section of the device in question and it would fix the problem. That is why I was interested in MIDI control of polyphony. Playing live I could just hit the MIDI CC and alter the polyphony remotely from my keyboard. Since this is not possible, I would do it manually. But since upgrading to Solaris 4.1 when I do this trick it will not allow me to re-enter the "8" and resume playing. I have to reboot the whole DAW, I can't even just do a simple restart. Any one have a work around where I wouldn't have to reboot, as this is unacceptable in live venue.
Bold But Bewildered,
DSP stuck notes?
Wolf Audio Design has a handy Midi Tool Box - 20 midi tools - that has a Panic Button mdl that sends an all notes off message. I connect it to the device or the midi source and keep it handy on my display.
There's a lot of other useful gadgets in this bundle - worth a look:
http://www.worldless.com/sfp/mtb.html
I don't know about polyphony control with CCs though.
/dave
There's a lot of other useful gadgets in this bundle - worth a look:
http://www.worldless.com/sfp/mtb.html
I don't know about polyphony control with CCs though.
/dave
Hi Jimmy,
Welcome aboard !
I observe this with my Halion too!
For me it is related to the system load and apparently most of the disk streaming software samplers seems to be subject to this phenomenom. I guess too much concurrent IO activities for the system as from my observation it is not related to average CPU load but rather to a race condition. I don't think there is a solution for this problem and the only tweak candidate which come to my mind would be to raise the sampler buffering and remove memory caching in order to reduce IOs.
Maybe AndreD could enlighten us and give us some more insight?
Cheers
Welcome aboard !
I observe this with my Halion too!
For me it is related to the system load and apparently most of the disk streaming software samplers seems to be subject to this phenomenom. I guess too much concurrent IO activities for the system as from my observation it is not related to average CPU load but rather to a race condition. I don't think there is a solution for this problem and the only tweak candidate which come to my mind would be to raise the sampler buffering and remove memory caching in order to reduce IOs.
Maybe AndreD could enlighten us and give us some more insight?
Cheers
-
irrelevance
I'm wondering if this only happens when your project is fully loaded? I've had this midi note sustaining problem before but with plenty of DSP left so in my case I could rule out high load probs. Have you tried setting poly on solaris itself or in the live bar? I find the live bar better for such things, except some of the older devices that choose to ignore it.
Thank You Gents,
Sampling and CPU are running hot but fine. This a DSP phenomenon. I think that the Wolf MIDI Tool Box sounds like the ticket. I wish that there was a forum as GOOD as this one for Gigastudio. Thanks to you guys for answering, and thanks to John Cooper for having run the absolute best forum for us. I was going to contribute 20 USD for a donation/celebration of the great John Bowen B-Day party in announcements on the 10th of May, 2006. The four tips I learned in the last week on this forum were worth more than the meagher 20 USD that I'm donating tomorrow.
To Us, And Those Like Us,
_________________
Jimmy V.
<font size=-1>[ This Message was edited by: scope4live on 2006-05-09 12:41 ]</font>
Sampling and CPU are running hot but fine. This a DSP phenomenon. I think that the Wolf MIDI Tool Box sounds like the ticket. I wish that there was a forum as GOOD as this one for Gigastudio. Thanks to you guys for answering, and thanks to John Cooper for having run the absolute best forum for us. I was going to contribute 20 USD for a donation/celebration of the great John Bowen B-Day party in announcements on the 10th of May, 2006. The four tips I learned in the last week on this forum were worth more than the meagher 20 USD that I'm donating tomorrow.
To Us, And Those Like Us,
_________________
Jimmy V.
<font size=-1>[ This Message was edited by: scope4live on 2006-05-09 12:41 ]</font>
hi Jimmy,On 2006-05-09 11:30, scope4live wrote:
... MIDI reset from controller will fix any Giga related notes, but in Scope dev.'s I use to just enter "0" in the polyphony section of the device in question and it would fix the problem. That is why I was interested in MIDI control of polyphony. ...
the 'hanging notes' in Giga and Scope may have different reasons.
In Giga it seems entirely midi related, but in Scope it could as well be the complete synth hanging (from executing some nonsense under high load) and the note is just one symptom among others.
Setting poly to zero is a convenient way to re-initialize the DSP code of the device - it works similiar (but not as drastic) as changing the sample rate, which would reset the whole project.
For a true hanging midi note (in Scope) I'd expect any 'all notes off' should work, regardless of from sequencer source (giga) or an external device.
cheers, tom
Astro,
As usual I look forward to any comments from you. I knew my poly "0" trick worked, but didn't know why. Thanks for the explanation. I have since dropped poly to "1" voice and it worked. It didn't force me to re-boot. Whew!! That's good news. I still must get the MIDI Tool Box for all of it's little tricks though. It is so refreshing just buying new devices instead of new hardware.
Long Live Creamware,
As usual I look forward to any comments from you. I knew my poly "0" trick worked, but didn't know why. Thanks for the explanation. I have since dropped poly to "1" voice and it worked. It didn't force me to re-boot. Whew!! That's good news. I still must get the MIDI Tool Box for all of it's little tricks though. It is so refreshing just buying new devices instead of new hardware.
Long Live Creamware,