Project
Launchpad template working >>video<<
Started by wul on .
Sign in or create an account to join the conversation.
To add to my last post... User1 is sending midi as expected. In session and mixer view, I can see that midi is being sent, but there is no visual feedback on the lemur and no "control-red_square" in ableton to say that a connection is established.
Thanks for the response regarding the mackie script . I would expect user1 to work normally along with the transport / navigation buttons , because the logic for those is within lemur and uses midi1 the rest of the template including handshake uses midi 0 .
I have been informed that it does work on a mac.
One thing you could do is set up a monitor object to monitor the initial handshake sysex message comming into lemur, because if it is and it meets the conditions , the template will respond on midi 0 and the red square will appear
Or use a midi monitor app to monitor traffic both ways
I have been informed that it does work on a mac.
One thing you could do is set up a monitor object to monitor the initial handshake sysex message comming into lemur, because if it is and it meets the conditions , the template will respond on midi 0 and the red square will appear
Or use a midi monitor app to monitor traffic both ways
Just had a thought , is there a sysex filter on the midi ports you are using
So has anyone got this working on a Mac?
If so post screenshots of the connections.
THNX
If so post screenshots of the connections.
THNX
I managed to get this working on my Mac with Live 9 beta, but I needed to modify the template as the handshake was incorrect for me.
Using information from http://liine.net/forum/viewtopic.php?f=25&t=2010, I changed the handshake() function in the lp_hand section of the template so it reads:
Using information from http://liine.net/forum/viewtopic.php?f=25&t=2010, I changed the handshake() function in the lp_hand section of the template so it reads:
//if(cc16==1&cc17==0x7b&cc18==0x6f&cc19==0x13&cc20==0x14) Monitor.value=33;
ctlout(0,16,1,1);
//midiout(0,{0xf0,0x00,0x20,0x29,0x06,0x74,0x5a,0xf7});
midiout(0,{0,32,41,6,19,32,247});
With this handshake response, the template works! Nice work.Any chance you'd be willing to share your "new" jzml file?tdmusic wrote:I managed to get this working on my Mac with Live 9 beta, but I needed to modify the template as the handshake was incorrect for me.
@tdmusic, never mind, I got it. Thanks so much for figuring this out! I'm sure there's a few other mac users on here who will greatly appreciate this, and of course, thanks Wul!
No worries, glad it works! Must be a different handshake depending on whether the client is on Windows or Mac.
I would have uploaded the jzml but was in a rush to get to work, will try to upload it over the weekend (unless you fancy uploading yours?
)
Cheers
I would have uploaded the jzml but was in a rush to get to work, will try to upload it over the weekend (unless you fancy uploading yours?
Cheers
Glad you got it sorted, if i remember right i tried that response originally and it didn't work for me on windows, hence the different midiout message
Iv'e nearly finished an iphone/pod version so ill include both responses in that.
looks like novations release is just a standalone loop player not an emulator.
they maybe don't know how to do it..........he he he
Iv'e nearly finished an iphone/pod version so ill include both responses in that.
looks like novations release is just a standalone loop player not an emulator.
they maybe don't know how to do it..........he he he
This works perfect for me, thanks a million u guys.
Great, now its works flawlesstdmusic wrote:I managed to get this working on my Mac with Live 9 beta, but I needed to modify the template as the handshake was incorrect for me.
Using information from http://liine.net/forum/viewtopic.php?f=25&t=2010, I changed the handshake() function in the lp_hand section of the template so it reads:
With this handshake response, the template works! Nice work.//if(cc16==1&cc17==0x7b&cc18==0x6f&cc19==0x13&cc20==0x14) Monitor.value=33; ctlout(0,16,1,1); //midiout(0,{0xf0,0x00,0x20,0x29,0x06,0x74,0x5a,0xf7}); midiout(0,{0,32,41,6,19,32,247});
Thank you
update nearly complete should be ready "early 2013" so your guess is as good as mine!!
all colours works same as the hardware so full feedback is available. just like on the new promo video for launchpad S
as well as live ,it should also work with flstudio, numerology . + owt else that uses it except of course for automap.... bugger. as it looks for the real thing .. never mind.
it would be ready sooner but for the problems with the editor. i.e. loss of connection, constant crash, window corruption, very high cpu usage.
don't anyone dare suggest using the in app editor.
all colours works same as the hardware so full feedback is available. just like on the new promo video for launchpad S
as well as live ,it should also work with flstudio, numerology . + owt else that uses it except of course for automap.... bugger. as it looks for the real thing .. never mind.
it would be ready sooner but for the problems with the editor. i.e. loss of connection, constant crash, window corruption, very high cpu usage.
don't anyone dare suggest using the in app editor.
Man I was trying Launchpad85 the other day (with the real hardware) and then I thought of trying your emulation - I was thinking of having a more intuitive midi clip editor-sequencer.
I hadnt seen ( or rather, I had forgotten) that you had made it also compatible with it - and when the buttons changed names I was puking rainbows and driven crazy thinking how did this happen at the same time!
I know its probably too late to be saying this, but if the "blinking" thing "burdains" the scripts too much I dont think ANYONE would have a problem if the emulation just used different (static) colors instead of "blinking" - if that would make the template "lighter".....After all, the hardware is limited in colors by nature - we dont have that limitation in Lemur!
In any case, once again congrats for the work you 've done!
I hadnt seen ( or rather, I had forgotten) that you had made it also compatible with it - and when the buttons changed names I was puking rainbows and driven crazy thinking how did this happen at the same time!
I know its probably too late to be saying this, but if the "blinking" thing "burdains" the scripts too much I dont think ANYONE would have a problem if the emulation just used different (static) colors instead of "blinking" - if that would make the template "lighter".....After all, the hardware is limited in colors by nature - we dont have that limitation in Lemur!
In any case, once again congrats for the work you 've done!
"Puking rainbows" never heard that one before. Should be able to script it though.
Re flashing it can easily be disabled just uncheck the toggle script should do it.
Re flashing it can easily be disabled just uncheck the toggle script should do it.
lol!
http://knowyourmeme.com/memes/puking-rainbows
1. to vomit rainbows at the sight of something amazing on teh internet.
source:
http://www.urbandictionary.com/define.php?term=rainbows.%20puking%20rainbows
http://knowyourmeme.com/memes/puking-rainbows
1. to vomit rainbows at the sight of something amazing on teh internet.
source:
http://www.urbandictionary.com/define.php?term=rainbows.%20puking%20rainbows