[damien]

dnaldoog wrote:

Hi Damien,

Try this in a lua function: (See attached panel)

os.execute(sleep(200)) -- 200 milliseconds

Good luck,

Thanks a lot! This will help.
I achieved a small delay between messages with blank messages inbetween :

SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 00 00 F7
--
--
--
--
--
SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 08 00 F7

The blanks instructions give me 1ms between the two hex messages which is enough for the unit to process the request without errors.
I’ll implement your LUA delay method later on.

Thanks!

• This reply was modified 4 years ago by damien.
• This reply was modified 4 years ago by damien.

[damien]

Hi just found the full sysex implementation for the Ensoniq DP/4.
I worked today on a panel to control the DP/4 with Ctrlr like a remote.
I downloaded the demo version of Midi Quest SoundQuest to monitor the messages between the APP and the Ensoniq.
The Midi Quest is full of bugs and the edit of the different settings of Unit1 Unit2 Unit3 & Unit4 is not working. SOunddiver just dumps the programs without any way to control remotely the FX.

So, here I come… with your help 😉 I’ll finally work on this Cntrlr Pannel and share with you my progress.

* My first issue is : To emulate pressing a button, it requires 2 messages 1 Down then 1 UP.

let’s say :

SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 00 00 F7
SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 08 00 F7

The manual says that the unit requires a delay between sysex messages of at least 100ms.
When I check the Mini Monitor log, both messages are sent without delay. This is why I get a sysex error message on the DP/4.

Is there an easy way to separate all the sysex messages with a delay like 100ms, 200ms or so?

SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 00 00 F7
100ms
SysEx,Direct,Direct,-1,-1,F0 0F 40 00 00 01 00 02 08 00 F7

thanks a lot!
Damien

[Author]

Posts