MIDI Kinetics Forum

Hello, i'm new to Lemur but I made my first control panel of my Quasimidi Rave-O-Lution 309 groove box.
Some of parameters of this gear could be tweaked via simple MIDI CC, some via SysEx. SysEx Dump data to device works just fine (here is the example)
but I want to request some parameters from 309.

Here is the manual of 309

http://cl.ly/U13F/QUASIMIDI_309.pdf

At 23 page you can see sequence to request data from device. Here it is.
So I've made a button with a script executed on "x" change which should grab the KICK sound number, it is just one byte length
When I press the button I can see the LED indicating MIDI signal comes to my MidiSport MIDI interface input, but after that I can't see LED flash at MIDI output indicating requested data comes from 309.

I have an object with custom MIDI with ON MIDI execution that grabs all incoming events, so if I dump from 309 manually - everything works just fine. Could you help me to resolve the problem?

High
Had a quick look and it looks like you got the address part wrong
Why are using 01 01 01 as the address? Have a look at the ' Address Map' section in manual . And address offset. Third byte.
This has all the vital info you need, and details where all the data is in memory so it can be asked for and found etc

05 00 00. Is the address of Kick- Sound 1 Parameter
05 01 00 is Sound 2 etc

I suspect you may have to then choose the particular sound parameter you are after from the Part - Parameter section
Would have to look further into it, not be familiar with device. Are you able to dump the data from the device.
Get yourself a midi monitor program for you computer and iPad to help sort things out as well . . ..

Hope that helps....

Cheers

PS and there you go, that was my 1000th post to the forum.

Why are using 01 01 01 as the address?

Because I don't need to request Sound (which is actually Program, or Preset of Kick), I need to edit just one parameter of temporary part.


I don't know what happened but my sysex request worked today! Yahoo! But I have Wi-Fi MIDI delay issues (maybe my project is a bit overloaded)

Anyway thank you very much for replay!

Oops my apologies..
Not sure how I missed that bit - ie temporary sound Kick . .
Good that you got it going, there are several factors in it all that can cause problems
Using midi monitors and sysex librarians can help in seeing what's being sent and deciphering or decoding what's there . .
A modern hardware midi connection will always be better than wifi, the iConnect stuff is particularly good
If you are going through a wifi router that can cause issues, fine for dev but for proper testing or use I would go adhoc..

Cheers