Push for lemur

Tremendous kudos for developing this, wul. Awesome work.

Unfortunately, it seems I'm having Newtfish's problems with Shove too. Same symptoms.

But man, love what I CAN use. Hope the fix is indeed easily sorted.

L'Pad seems to be working for me over here on Win7 x64.

the next lemur update may fix it, if not the template will need fixing

Ah, thanks for that.

Still way grateful for the effort you put into this; the time you must have spent is impossible to calculate but looks monstrous.

...though I must say, just the inspiration of the thing makes me toy with the idea of doing something more stripped-down and specific to my particular workflow...as foolhardy as that would be for one who hasn't coded since his Atari 400 days, lol...

Cheers to all.

Hello,
I am trying to use this awesome template since I found out about it (late, ha). I've been fiddling with things for a couple days now and have gotten everything working except the Drum Rack Sequencing functions.

I am on Live 9.1.1. The problem that i have is that when I use the browse button to create a drum rack track, Live lags out and freezes. Using a MIDI monitor app I am able to see that when the Drum Rack is inserted, Live is flooded with an endless series of 'From Daemon Input 0 Control 1 Expression (fine) 127'.

My question is, where is the fault likely to exist? I am not sure exactly how the situation works script wise, though I am assuming that anything relating to the actual Push functions (i.e. Sequencing) is handled by Clyphx. Any insight at all would be great. Thanks again for all the work it took to create this in the first place, it really is pretty amazing.

It will be difficult for me to simulate your set up as I only have an earlier demo of live and I did not use the clyphx method.
The expression cc is controller number 11 if I remember right , I will check the template to see if it sends that message.
I do know of some issues that a couple of people reported after updating to version 5 , ( see earlier posts) but it was to do with the scene buttons .

Hey WuL, longtime!

You can update your version of Live and still run it under the demo license I believe - it's a very generous system in that respect.

Thanks WuL, I appreciate it. This is all fairly new script to me.

There's is nothing in the script sending a cc11 message , this is confirmed if you look in the midi mapping window of the editor , that's assuming its cc11 can you confirm that.

Hey joe...... There's a song there somewhere! Yep long time
I tried downloading the latest update , it said my demo time had expired so I was stuck with the earlier version albeit in demo mode.

The Expression (fine) is a CC 43 from what I can see...not sure if that makes any difference at all.

I think I may have found what pad it is, it appears to be pad08 is the only one sending a controller message 43, though I am not sure I am understanding it correctly. However, after changing this value to 44, I still have the problem with CC 43, which leads me to believe that there is something in a feedback script that may be causing the issue.

It's been a while since I had to make do with the demo license, but I'm pretty sure you can install the latest version regardless of the demo license having expired, but run said latest version in read-only (ie. 'demo') mode.

Now, whether that's useful to you to develop the template or scripts further I dunno - but it's bloody handy for running extra copies on extra machines for performance purposes all the same.

It's the same problem as reported in the above posts , here is what's happening....
There is a midi feedback loop from the top scene button and the label instruction which for some reason in version 5 is sending the cc 43 value out and live feeds it back only for the label instruction to send it back out again, it certainly didn't do it on version 4 so due to the oversight on my part in leaving midi0 selected in the label mapping pane . It does not sound as though everybody is encountering the problem. I wondered if the issue would go away in the latest lemur update.
Clearly it ain't.
Here's what to do.. expand each scene button highlight the label instruction , then deselect midi0 in the target field for each of the scene buttons . That will do it.

I have tried to simulate the issue in a basic template but I am unable to, so I've no idea as to why it's started doing it all of a sudden.

That worked very well, thanks Wul.

Well, that definitely solved the issue. You sir, are the man. Hopefully I can learn a lot more about Lemur, this is a really cool concept to build things with.

Glad it worked , another useful mod is to change the encoders behaviour to linear, then create a sensitivity control

hey tested out after doing mod works great on windows 7 64 bit with 9.1.2 and clyphx. thanks can you explain more how to get knobs to work better. thanks.

anthony

I was very happy with Shove, it did everything a Push would do including work well with many M4L plugins (Dope Matrix for example). Okay, there are obvious limitations because it's an iPad. But this simple mod has made it so much better - quicker, more reliable, the encoders are much more responsive. Talk about gilding the lily! I'm using Shove more than Push over the past few days.

What's going on? I'm guessing from Wul's brief explanation there's far less midi traffic over the network?

Now to change the encoders behaviour to linear...

Wul - you da man!

change the control field in the behavour tab to linear that alone is ok but not responsive enough, so create an expression called response with the following expression

tres.x>0?abs(tres.x*16):1

now create a fader called tres thats identical in size etc. to the velocity and aftertouch sliders, and make it so it views in rotation with the other faders , by adding this to the action script for the cpb button

if(i==4) {show(tres,1);setattribute(getobject(),'color',{8421376,8421376});
setattribute(getobject(), 'labels', 'Res');
show(tpb,0);show(tv,0);show(tat,0);}

and then increasing the greater than to 3.

now in each encoder add this

decl i;
for(i=0;i<response;i++)
before the ctrlout instruction.

thats it , the only other mod i did was to stop the pan progress bar changing colour , but i cant remember how i did that at the moment

Nice, didn't take very long and I think it's working properly.

wul wrote: now in each encoder add this

decl i;
for(i=0;i<response;i++)
before the ctrlout instruction.

Is that for both enccw() and enccw2() in each encoder? I've done both and it appears to work okay in the very limited time I've had to play with it.

I copied the tv fader to use as tres, it wouldn't display properly until I did a Send to Back action on it.

Thanks yet again Wul - for me, doing modification stuff this way is a great way to learn more about how Lemur works!

Yep in both enccw(). And encccw()

I thought that too about doing mods in this way,

Also some users will have changed the layout , so uploading an already modified template would be going back to square one

I'll try and work out what was needed to cure the multi coloured pan bug

wurlt yeah works great thanks.


here's what i did to get button to work.

if(i>3)i=0;
i=i+1;
if(i==1) {show(tpb,1);setattribute(getobject(),'color',{127,127});
setattribute(getobject(), 'labels', 'PB');
show(tv,0);show(tat,0);show(tres,0);}
if(i==2) {show(tv,1);setattribute(getobject(),'color',{32768,32768});
setattribute(getobject(), 'labels', 'Vel');
show(tat,0);show(tres,0);show(tpb,0);}
if(i==3) {show(tat,1);setattribute(getobject(),'color',{8343069,8343069});
setattribute(getobject(), 'labels', 'AT');
show(tres,0);show(tpb,0);show(tv,0);}
if(i==4) {show(tres,1);setattribute(getobject(),'color',{8421376,8421376});
setattribute(getobject(),'labels', 'Res');
show(tpb,0);show(tv,0);show(tat,0);}