Replies: 6 comments 22 replies
-
This was actually exactly how it worked few weeks ago, but it had unfortunate side-effect that the entire board was "stuck" until USB connection was opened. On USB connection all values have been sent at once, which is good, but before that the board was unusable, which was bad (for example you couldn't use DIN MIDI or switch pages on touchscreen etc.). I will look into how to implement this again without the side effects. |
Beta Was this translation helpful? Give feedback.
-
Now part of v5.4.0 |
Beta Was this translation helpful? Give feedback.
-
Maybe in some future release.
…-------- Original Message --------
On 19 Feb 2021, 14:30, gitrimius wrote:
That would be great.
This is the method I would use to send the sysex message (excerpt from other forum of audio DSP):
> you can generate it using custom object or a midi script.
> using the call :
> MidiSendSysEx(device ,port ,buffer, buflen);
> note: its just really a 'raw send' , ie. you need to put the enter sysex in the buffer
—
You are receiving this because you commented.
Reply to this email directly, [view it on GitHub](#44 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AATNDXXALIX4LI5ZX6CBZ2TS7ZRWXANCNFSM4XLUSGXQ).
|
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Part of new firmware now: |
Beta Was this translation helpful? Give feedback.
-
Is it possible to make this burst on a sysex request? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have noticed that when you power on a board with OpenDeck fw on it (in my case STM32F411) the current state of the controls is not spit out as midi messages. This means that the midi receiver is not aware of the current state of a certain control (or all controls for that matter) before the corresponding control has been moved..
For example: an oscilator on a dsp board will use its default value instead of the corresponding potentiometer value at startup..
I do understand that that is to limit the amount of data, otherwise a pot would continuously send midi data and that behaviour is ok once the controller is running.
But it would be a super nice feature to have a kind of setting for "burst all messages once, x secs after booting". That would allow the dsp to receive the values and put all internal controls on the correct pot value.
Another interesting way would be to allow for a certain midi message to come in that triggers a burst of all controller values. The latter would be more interesting in my application since it would allow to trigger the burst every time the dsp changes 'patches'/program (thus entering again the unknown value state..).
Any ideas on this?
greetings!
Beta Was this translation helpful? Give feedback.
All reactions