![]() You have the right to be dissapointed, but keep in mind what I already mentioned “This is version 1” of LiveControl2 and it does work well for many, many users, like me. My expectations were based upon communications from Liine and I, as a paying customer, have a right to feel let down. Mark, There was nothing disrespectful in my comment which actually opened up with “I’m sorry to post such negative feedback” However, as a customer who paid $50 the the Lemur app mostly for access to Live Control 2, who waited much longer than the advertised release date, receive little or no updates to explain the said delay only to get a buggy software, I’m allowed to be disappointed. This is not perfect but a big improvement on the static cc numbers option.Īlso I originally loaded the lemur livecontrol2 template via the lemur app editor, but it wouldn’t save the project file in lemur, so now loaded the same file using the iTunes approach and now my projec Other than that LC2 is working great for me under Live 9.0.4 on Mac OSX 10.8.4. The other option is to create your template, and then use the ‘midi remote script’ option to create a control surface. Which is all fine and dandy, but I’ve always found this ‘non-dynamic’ method of creating a controller for live pretty limited (as it won’t react to dynamically added scenes and tracks) What would be ideal would be some smart fucker (well much smarter than me anyway) writing a python script (like the incredible LaunchPad95) to facilitate a much more integrated solution. In other words you don’t seem to be able to ‘overwrite’ existing templates (despite the dialogue box which states this) Once you’ve successfully done this you can then then map this in the midi setup page (accessed via the ‘midi’ button top right of the screen as you’re probably aware) in Ableton. I worked out that you have to save your revised template with a new name and then send it (where it is added to the bottom of the list of templates) in order for it to work. A slight anomaly occurred when i then tried to port this newly revised template over to the device however. But this is only a hypothesis.So one method of getting it to work is to open the live template in the editor and then assign a unique cc number to each and every control. This time I would reboot the iPad to see if that makes a difference.Īnother possible issue is that TouchOSC Editor is written in Java, and uses an implementation of Bonjour that is perhaps not perfect or does not play well with iOS's mDNSResponder. So that could mean that the mDNSResponder of the iPad is not … responding. Now, what you describe is in fact the other way round : TouchOSC Editor is not able to find your iPad running TouchOSC. ![]() The reason was that mDNSResponder was not responding for some reason, and a reboot of the computer was needed. On 10.5, a bug was happening from time to time, where TouchOSC was not able to find OSCulator in the Network Settings. This is also known as the Zeroconf protocol. This program is actually the "Bonjour" stack used for example by OSCulator and TouchOSC to detect the devices on the network without configuration. ![]() FYI, Mac OS and iOS devices are running a small program that is called mDNSResponder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |