Device Capabilities (new set of properties)

[atom]

Ok so i’m working on some standard for program/data/bank transmission reception (what we would call a program manager). I need to define a set of capabilities that a MIDI device can have, here is a initial list, what do you think, what to add/remove/rename? What do you think about that idea, all these capabilities will be handled by custom Lua code written by the author, Lua will provide request data and interpretation of the received data (all your program methods will be working the same way, we’re not changing anything here).

 

<id name="deviceIdentityRequestExists"            text="MIDI standarized identity request can be sent, standard answer should be received" type="Capability" />
<id name="deviceEditBufferExists"                 text="Edit buffer exists"                                 type="Capability" />
<id name="deviceEditBufferNameTransmitted"        text="Edit buffer name can be transmitted by the device"  type="Capability" />
<id name="deviceEditBufferNameRequest"            text="Edit buffer name request data"                      type="Capability" />
<id name="deviceEditBufferTransmitted"            text="Edit buffer can be transmitted"                     type="Capability" />
<id name="deviceEditBufferRequest"                text="Edit buffer request data"                           type="Capability" />
<id name="deviceBankExists" />
<id name="deviceBankNumber" />
<id name="deviceBankNameTransmitted" />
<id name="deviceBankNameRequest" />
<id name="deviceBankTransmitted" />
<id name="deviceBankRequest" />
<id name="deviceProgramExists" />
<id name="deviceProgramNumber" />
<id name="deviceProgramNameTransmitted" />
<id name="deviceProgramNameRequest" />
<id name="deviceProgramTransmitted" />
<id name="deviceProgramRequest" />
<id name="deviceCustomContainerExists"            text="Custom container exists"                  type="Capability" />
<id name="deviceCustomContainerVisibleName"       text="Custom container visible name"            type="Capability" />
<id name="deviceCustomContainerNameTransmitted"   text="Custom container name can be transmitted" type="Capability" />
<id name="deviceCustomContainerNameRequest"       text="Custom container name request data"       type="Capability" />
<id name="deviceCustomContainerNumber"            text="Custom container count"                   type="Capability" />

<id name="deviceCustomContainerTransmitted"       text="Custom container can be transmitted"      type="Capability" />
<id name="deviceCustomContainerRequest"           text="Custom container request data"            type="Capability" />
<id name="deviceCustomDataExists" />
<id name="deviceCustomDataVisibleName" />
<id name="deviceCustomDataNameTransmitted" />
<id name="deviceCustomDataNameRequest" />
<id name="deviceCustomDataNumber" />
<id name="deviceCustomDataTransmitted" />
<id name="deviceCustomDataRequest" />
<id name="deviceFirmwareExists" />
<id name="deviceFirmwareNameTransmitted" />
<id name="devicFirmwareNameRequest" />
<id name="deviceFirmwareTransmitted" />
<id name="deviceFirmwareRequest" />

[dasfaker]

I still don’t know what’s the difference between our own methods for patch management and your program manager. Will there be any pros/cons using one or another?

[atom]

Yes mine will be standard across all panels, and the programs/banks will be saved with the panel in a standard program manager.

[dasfaker]

For me you’ve listed more than enough capabilities. I need to see it working to know what’s all about.

[Hecticcc]

Wow Atom this really adds alot of extra value to Ctrlr, and i think it will make alot more people interested in Ctrlr. From what i see (and with my very limited programming skills) this list looks pretty complete for preset management, and the customContainer will no doubt be able to fill in specific needs.

My weekly radioshow @ Belgium's best local radio station - - - - - -
Updates and news about the Emu eos sampler panel

[moroe]

Cool

I am waiting soo long for a general program manager.

Then we can really use hardware synths like vsti´s.

Greets

Moroe

 

[moroe]

Please do +- buttons for preset sending to synth

Also buttons for request presets (singledumps, multidumps)  from synth

Would be nice if we could control the buttons via cc controlers,sysex  or as vsti parameter (then we could use buttons on the NI Maschine control them)

Greets

 

Moroe

[Author]

Posts