Page 1 of 1

Posted: Sun Jun 05, 2005 2:45 pm
by Casper
<a name="planetz-file"></a><a href="http://www.planetz.com/Pulsar/files/dev ... .zip"><img src="/forums/images/file_icon.gif" border="0" alt=" File"> File</a><BR> <a name="planetz-file"></a><a href="http://www.planetz.com/Pulsar/files/dev ... .txt"><img src="/forums/images/notes_icon.gif" border="0" alt=" Notes"> Notes</a><BR> <a name="planetz-tag"></a>Price ($USD): 0<BR> <a name="planetz-tag"></a>Type: Utility<BR> _____________________________________<BR><BR>
On 2005-06-05 09:11, ChristianB wrote:
Great Casper !!!
The midi ctl working fine
but....
the transpose button on the lower split does'nt go to minus 64 anymore....it is making impossible to cover a large range of the notes. Ex.: I have a 25 notes keyboard and I want to be able to do note 0 to 12 on the lower split and notes 84 to 96 on the high split. The way to do that is to put the keyboard on center note 60 and transpose the lower split to minus and the high split to plus.

Also a good upgrade from the original key splitter from scope would be to :
1- transpose buttons going by octave instead of cent = Modify the one in place or add a second transpose button that goes by octave.
2-Make the transpose buttons so they don't cut the note playing as you change the transpose and also not transpose the note that is actualy playing (it is not a problem for now but....)
Thanks a lot Casper!

Cb)

Update: V5! Presets Functionality
Update: FinalVersion (Screenset saveability)

Idea : ChristianB
Technical Help :John Bowen

cheers,

Casper



<font size=-1>[ This Message was edited by: casper on 2005-06-08 06:38 ]</font><BR><BR><a name="planetz-fileimage"></a><IMG SRC="http://www.planetz.com/Pulsar/files/dev ... plitV5.gif" BORDER="0">

Posted: Sun Jun 05, 2005 5:39 pm
by ChristianB
I just realized that the low transpose button does not transpose in the minus at all (the original too).
So the only way to reach the note zero is to put my controller on the lowest octave range but then the highest note in the upper split begin at 73, that is not enough.
In your last modification the low trans button is going to -64 to +128, if you do the same with hi trans button things will be all right...
I notice that the hi trans button does transpose in the minus ???
Are you planning on a per octave transpose button???

Cb)

Posted: Mon Jun 06, 2005 2:40 am
by Casper
Version 4.

I think i t's better to just add the updates in this post. Instead of creating a whole new post..?

So here is another update
http://student-kmt.hku.nl/~casper0/

Octave knobs added.
Transpose knob (high split) wider range.
I've just set it to [-128,128]
You will hit the ceiling of the internal calculation when setting the low/high notes too low/high.

cheers,

Casper B

Posted: Mon Jun 06, 2005 6:03 am
by ChristianB
The per octave knob is fantastic ! thanks

Regarding my previous post here, I was wrong to say that the Low transpose button is not transposing in the minus....I just misunderstood the low and high zone...every thing is fine now ! I think that trans. ( -72 to +72) would be perfect.

I found that the device does not save is position in the project, it always go back to the bottom-right.

Cb)

Posted: Mon Jun 06, 2005 7:51 am
by Casper
Yes, I noticed it too. But I don't know how to fix that.

Maybe some SDK-user can mention this?

cheers,
Casper

Posted: Tue Jun 07, 2005 1:51 am
by Casper
V5 done! Changes: Presets are ok now.

cheers,

Casper

Posted: Sat Jun 11, 2005 10:34 am
by johnbowen
Casper,

You might want to look at one of the example devices in there (I don't know what the new SDK comes with), and compare what is marked in the check boxes with what you have for your device.

For example, any of the Show surface pads don't need to be stored in the preset list, etc. You will find also the position of the preset list for screensets is saved as well as the main surface, etc.

cheers,

Posted: Sun Jun 12, 2005 1:51 am
by Casper
Thanks John ,ofcourse i've looked at all of those examples. But sometimes things I do could (without me knowing) result in missing that 2 pads. Starting with a clean and empty module should be possible too (and is).

Thanks again for your help John.

cheers to you,

Casper