MIDI Kinetics Forum

oldgearguy wrote:So if our app is now broken under 5.0, do you have any suggestions for fixing it?

Quick summary -
(the reverse order of the operators is due to the way Yamaha laid out the data in the sysex messages. By using a reverse order in the array, it makes life much easier in other places)
the code looked like this:

decl i, tmpOp, operators = {OP7, OP6, OP5, OP4, OP3, OP2, OP1}; // OP7, OP6, etc are the names of containers.

// Focus is a custom button inside each container and I want to reset it for OP1->OP6
for (i=1; i < 7; i++) {
tmpOp = operators;
setexpression(tmpOp.Focus, 'x', 0);
}

Lemur 4.1.1 allowed me to reference the custom button inside the container using tmpOp.Focus. Lemur 5.0 does not.

nick_liine wrote:

electrofux wrote:I tested around a bit with the sequencers. The timing is pretty spot on especially when used wired. Over Wifi (no adhoc) it wasn't that tight though still alot better than it used to be.

There is one thing that is a bit annoying and that is the little hickup when the Clock sending Apllication (in my case Reason) is going through a loop. Seems like Step 1 is triggered twice when the Song Pointer jumps from the right to the left loop marker. I have checked for the correct loop setting.
Maybe it is Reason, maybe something is intepreted as a clock pulse that shouldnt be. Can someone check this with another program? I am using the iconnect midi2+ without the daemon running. You can even see the little hickup on the Lemur.

Edit: checked Genome slaved to Reason and the hickup doesnt appear.

Also the provided sequencers seem to not respond to stop messages. They keep on running when stop in the sequencer is pressed. Is this because they are coded this way?

There are a couple different ways to handle clock start/stop/run messages, we've tried to accomodate for all cases but there might be some particularities about the way Reason handles clock messages.

Does this problem occur with other DAWs, or only with Reason?

oldgearguy wrote: The new code looks like this:

decl i, tmpOp, tmpOp2, operators = {OP7, OP6, OP5, OP4, OP3, OP2, OP1}; // OP7, OP6, etc are the names of containers.

// Focus is a custom button inside each container and I want to reset it for OP1->OP6
for (i=1; i < 7; i++) {
tmpOp = findobject('OP' + (7 - i)); // note that the operators vector is no longer needed
tmpOp2 = getexpression(tmpOp, 'Focus');
setexpression(tmpOp2, 'x', 0);
}

electrofux wrote:

nick_liine wrote: There are a couple different ways to handle clock start/stop/run messages, we've tried to accomodate for all cases but there might be some particularities about the way Reason handles clock messages.

Does this problem occur with other DAWs, or only with Reason?

Well, what can i say. I installed Ableton Demo and tried it out and there is no problem. Now i have to make the Propellerheads to fix this, sigh.

nick_liine wrote:

electrofux wrote:

nick_liine wrote: There are a couple different ways to handle clock start/stop/run messages, we've tried to accomodate for all cases but there might be some particularities about the way Reason handles clock messages.

Does this problem occur with other DAWs, or only with Reason?

Well, what can i say. I installed Ableton Demo and tried it out and there is no problem. Now i have to make the Propellerheads to fix this, sigh.

Keep us posted, and please feel free to contact support directly at support@liine.net when you get more info about the issue.