Midiworks wrote:Transport can not be set to zero.
But then jumps again to bar xxx using Chainer.Just go the arrangement and click on the bar number you want to go. I agree though that a zero button and manual bar number entry would be good as well and we have that on the list.
You should add a complete transport control.
Not everybody works like that... look at me !We get your point. At the same time we're trying to keep complexity down and the sequencer/host already has transport controls. We'll definitely chew on it though.
3.) Jamstix should not start to play by default only after hitting play.
Yes, good one !You know how many E-mails we'd get if we did that with the line "It don't play nothing! What's wrong!!"
How about we make it an option?
"Jam with audio", the slider sets itself to zero after some time and after a click on it jumps back to zero...
YesDo you mean it goes to zero even with audio signal present?
When there is NO audio/midi input Jamstix should also stop jamming after a few bars.
YesHow about we make that an option?
Options are always good.The timing slips more and more out of sync,
the longer Jamstix is running.
Untill it is totaly off time.
Chainer atm, but strange, now it does not slip since quite a while...Just tested again with Sonar 4. Free jam for 39 minutes without any timing problems. What host are you using?
It looks always like it is set to intern.
Actually that happends with all those swtches,
after changing pages they show 'up'.
First yes, later not anymore....That's an odd one. Can't duplicate it here. Do the labels next to the switches still show the correct highlighting?
maybe also the possibility to change the out going
midi note numbers, this should be possible to be set by the user.
Sorry I did not get the idea...Does the key mapping not suffice for that?
"Output", as I wrote before, your slider ranges are set quite badly.
I see that you already changed 'the brain',Got it. We're working on that.
but now it feels to me like a boaring drumer,
without personality.(school boy drumming)
To be honest, I miss that wild drummer feel from v99c.
That drummer was too wild but he had style.
Now the range is too limited, even with all 3 sliders full up, its still the school boy....
A kind of "midi-mixer", that globaly alows the user to adjust the velocity of every sound used,
would be very helpfull.
But now I miss some velo pre-sets, the draw is not so convinient. Pre-sets would help.That's what the velocity map in the mapping tab is for. Now I know it looks like too much work at first but hear me out: We found VSTis where the problem was not just the max velocity but the transform function across the whole spectrum of a sound. For instance, a hihat would be too loud but if you just multiplied a reduction factor you'd have it too low on the quieter beats.
The velocity map allows you to draw a free-hand response curve for the transform so you can have the normal response in the lower velocity section and the higher reduction in the upper section.
13.) "CPU", while ok when running external VSTi,
the CPU grows here up to 33% after hitting stop.
Plugsound Drums&Percussion VSTi,Can you tell me what VSTi that is and what CPU you have?
P4 2ghz 780mb
Great work so far, now get the fine tuning right.
I will !
We're on it. Just keep it coming
)