Short how-to guide

[Tijs]

Is it possible that you write a short how-to guide which programs you need and how to adjust the parameters based on an already made controller. Then people (who know how to read programs) can start creating the ctrlrs for their own devices and the list of available ctrlr can grow rapidly. It’ll also save you lotsof time as people also can help eachother for their devices.

I don’t wether it is possible to give a short overview or that the project is too complex for this. I think the biggest problem here is that you keep the core source updated all the time so when people start experimenting they could go out of sync when creating for their devices.

I can imagine you’ll need visual studio, jucer (has to be compiled in VS), Gekon and the edocontroller for the midi.

[atom]

yeah i’m preparing a tutorial, how to create a ctrlr from ground up. it’s very simple but there are a few gotchas. once i have some more time i’ll sit down a create a tutorial with some images and stuff.

[mamonu]

great idea. im a programmer in my day job and i would be willing to help as long as i know how ” title=”Smile” />

EDIT:

i will start getting some xmls ready for equipment i have based on the Hardware midi specs i see on the wiki…

[TonE]

"atom":2p6h8uub wrote:

yeah i’m preparing a tutorial, how to create a ctrlr from ground up.[/quote:2p6h8uub]
I am also waiting for this tutorial. I could see some of the Pulse Arpeggiator parameters do not work correctly, also I would like to play around with different variants for the Pulse GUI, especially to see all settings at any time, e.g. right now we can not see all modulation source and destinations without clicking on those tabs.

Regarding the Pulse arpeggiator parameters: Maybe we need to limit the CC range in some cases to smaller ranges or distinct values, rather than using the whole range 0..127.

[atom]

Witch parameters are not working ?

[TonE]

Arpeggiator Clock parameter behaved a little strangely somehow, I can retest when I am at home again. Did you consider already all those different ranges in the English Pulse manual on page 58?

How can we tell in the .xml definition a different range than 0..127?

[atom]

I’ve updated Pulse builds with some Arp parameters added (they were in the XML but not on the gui). And i re-checked the ranges.

[TonE]

Thanks for the fast changes, unfortunately I can test only in around a week, I am not at home.

[Tijs]

Hi Atom,

Is it possible that you can state the few gotchas which you stated earlier in a short post when compiling the xcode projects? I’m really eager to start experimenting with programming ctrlr’s myself for my new gear.
Also if more people are able to build them it would save you lots time as forum members can also help each other so you can spend some more with your lady ” title=”Wink” />

[atom]

i’ll do my best this week to write this document, i guess it’s time.

[Author]

Posts