Continuos mono mode.

[cuckoo]

Wow! It sounds so great! I just played around with it for an hour or so after a happy purchase. This will make the base of my next album

Since I'll most probably gonna use this live, and play on a tiny midi keyboard it's important for me that it performs well live. Therefore I'd need a continuos monophonic mode. You know, when I press a key, it plays, then press a second key while key 1 remains pressed it plays the second note. THEN when key number 2 is released it should go back to playing key 1 that is still being pressed. (Instead of just going silent, having to repress key 1).
Playing live on small keyboards means a lot of mis-hits and double-presses and thus making the sound go silent by mistake in its current state.

This could potentially have two modes.
1- ReTrigger mode. A new Note-On is triggered each time. (Simple to implement without big changes in your system)
2- Legato mode. A new Note-On is only triggered after the continuos tone has been released properly. (Possible messes some things up, (multisamples?) but would be a beautiful option)

[davidv]

Hi!

Yes full legato modes are high on the todo list indeed.
And yes it depends a lot on the current polyphony settings.

I guess this option should be available as a drop down right beside the polyphony setting in the mixer.

Thanks and can't wait to hear the tracks!

[cuckoo]

Thanks, tried it out more now and put it up on youtube. It's fantastic!
http://www.plogue.com/phpBB2/viewtopic. ... 4897#24897

[davidv]

Thanks, tried it out more now and put it up on youtube. It's fantastic!
http://www.plogue.com/phpBB2/viewtopic. ... 4897#24897

Thanks Im really curious about the crash log.

[cuckoo]

Thanks Im really curious about the crash log.

Hey again. I think we agreed on Live was to blame.. but there is something funky to it. I experience a lot of crashes with chipsounds in Live. (Like 4-6 every time I use it for a few hours). Especially when I'm recording audio and using Chipsounds at the same time. Live has been very solid for me before, so my hunch is CS might have something to do with it.

My setup involves:
A nanoKONTROL that sends CC messages (almost all supported CC messsages) to channel 1-4. And I knob them around all the time. Sometimes I might be sending CC messages to several channels/ chips at once. Maybe I accidently send an unsupported CC message to a chip that lacks that feature. For instance cutoff-change CC74 to an RP2A07 chip.
Are there illegal values that can cause a chip to freak out?

I'm using 4 midi tracks in Live that all receive their input from one keyboard and the nanoKONTROL. I route these midi tracks to channel 1-4 on the ChipSounds-track. Switch on and off these 4 midi tracks..

Any of this that seems alarming?

[davidv]

hi

pm sent,

dont think ccs can kill any chip.

would love to see all your logs tough.

thanx

[kaptainkaffeine]

I know this is from a while back, but I'd like to bump this to say that as much as I love chipsounds, this is a very serious drawback for me. Playing leads and basses both suffer from needing to press every note. It becomes difficult to record parts and with no simple way to program legatos (Ableton Live...), it's a major hiccup in my workflow no matter how much I want to use it. This is absolutely the number one thing that I would change about chipsounds.

[davidv]

This is well noted. As i said, it might be in a future update. No word on dates though.
regards