No products in the cart.
Forum Replies Created
Viewing 15 posts - 1 through 15 (of 89 total)
Hi endogen, if you press the refresh button, it should update all the controls. This is just in case you have a slow wifi connection, or the connection drops OSC.
It’s not going to be possible to use Midi instead of OSC, we’ve tried to implement it and it’s just not possible at this time.
- This reply was modified 5 years, 11 months ago by xmonsta.
Yes, this is possible in a future update. However, it would need to be done inside max, because it wouldnt be efficient inside Lemur. We will look at it and see if its something we can implement soon.
Yes, it works fine and doesn’t need to be updated for each new version of live because its mostly written in Max and not the Python API.
Yes, lots of templates coming soon – stay tuned. Lots of tutorials also on how to make templates etc and new software coming up 🙂 We make updates on our facebook page as well, so you might want to follow that for updates.
- This reply was modified 7 years, 1 month ago by xmonsta.
We have a fix for monosequencer as well, so fixed both of those issues. Look forward to hearing from you so we can send you the updated files in the meantime.
It does seem there is these bugs have crept in on the latest release. For Operator this can be fixed easily (as its just a script not loading), we will have to look a bit deeper into Monosequencer random button, but definitely can be fixed. If you can contact us at email@example.com we are able to provide fixed files you can use for the meantime while these fixes are getting added to the new release.
There is an intended lag with Monosequencer, because it’s being sent to the Lemur and takes time for the template to reach its destination, whereas all the other Ableton native templates are already loaded (if you’re using “Switched” template mode). Addon templates will always be sent to the Lemur (whether using Switched or Send template mode) because we’re using most of the available memory on Lemur with the Large template in Switched mode. You can add templates to the large template, so Monosequencer loads instantly like the native device templates, this is covered in the help file. However, you may need to delete templates you don’t use regularly (because they start not to show up, due to memory being taken up). Lemur has had some memory increases lately, so this may not be a problem any more (Lemur editor outlines its template memory size int the bottom right hand corner). However, if areas of the templates you’re using start not to show, you’ve likely gone over the memory size.
The reasons we enable the “Switched” template mode is because its a faster experience for those that use native device in ableton a lot. Its also possible to build your own large template and delete all native devices, and just put max and vst device templates in there. So a few options for those that need it.
Send mode is a great mode if you want to keep the memory low on the Lemur (no template is loaded until you select). There isnt much difference in terms of performance (just a couple of seconds lag when you rest on a template) and it gives you the added benefit of being able to use other templates on the Lemur with PULL. In time we will likely default to “Send mode”, because it’s much better in terms of performance on the Lemur and Ableton.
Hope it helps
Hi Brian, We’re going to be releasing lots of templates soon, in a matter of weeks. Serum is at the top of our list!
Sorry to hear you’re having these problems. Getting the Lemur working over a network can be a bit difficult sometimes, because of varying set ups (firewalls, antivirus, different os’s etc).
However, I’m confident that we can resolve this problem for you, because we’ve had users with this issue before, and we’ve got every one of them set up and working so far.
To get to the crux of what is happening, there is something blocking your OSC messages being sent from your Lemur to the Computer. This could either be a firewall or an incorrect set up of communication between the Lemur and PULL. This issue is related to Lemur network set up, rather than PULL set up. The Lemur is just not functioning properly over a network. Maybe, Midi works over a network, but OSC (which Lemur and PULL also uses) may not work.
It looks more likely to be a firewall, since your IP addresses seem to be correct. Do you have a firewall, or antivirus switched on? If so, is it possible to switch these off momentarily? Some of our users have actually needed to put a rule in their firewall, even though it was switched off (somehow the windows firewall still keeps blocking even when it’s turned off). I can dig out this rule if it’s needed.
Are you on Windows or Mac? Which version?
If you wouldn’t mind, would it be possible to detail your network set up?
IP address of your Router (it’s definitely best to start with this rather than setting up an adhoc address)
IP address of Computer
IP address of iPad
IP address and Port inside Lemur settings
IP address and Port inside PULL amxd
We also have a firstname.lastname@example.org email , so if it’s quicker for you there, we’re available pretty much 24/7 and we generally answer support queries within 24 hours, even at the weekend.
Hope it helps,
Is there any chance you can contact email@example.com ? we can give better support on email .
The short answer is In Max 7.2.1 Cycling74 have removed Snapshots in Max for Live. We are releasing a solution for this soon though.
You will probably need to delete some templates in the large template if you want to include diva and monosequencer for faster loading. If Lemur memory is overloaded, you will find that some scripts dont work (like switches) and also some elements of the template (knobs, sliders) will be missing. If you want to see how large the templates are you can check the file sizes in the “LiveDevices” folder. Lemur editor also shows you whether you are reaching the memory limit (bottom right hand corner)
You might find Send mode works really well though. It’s incredibly stable and it’s only a very short time before templates load. Then you don’ta have to worry about memory and building your own large template.
The DIVA problem with loading is likely due to the template being in the VST folder, rather than the MaxDevices folder. This time we’re loading diva inside max (the xPlugin amxd), so it’s recognised as a MaxDevice template. We have to do it this way, because Ableton doesn’t allow you to see all the parameters (only 128) in Live natively, so we have to load the VST in xPlugin Max Device and then load the xPlugin in Live.
DIVA is updated to the latest version of Diva (with the Digital Oscillators etc).
Just delete the Max app from your applications folder and reinstall max, then install PULL. 🙂
It might be worth getting in touch with our support email on these – support [at] xmonsta.com
We are working through some of these issues with C74, as their most recent update has removed some things that were previously working fine with VST in Max for Live. In any case, we have solutions for these problems and we can surely resolve them.
Apologies for the slow response. There is a fix that has been sent to your email. Let me know if you have any problems.
Cheers and Happy New Year!
Is there any chance you can contact firstname.lastname@example.org ? Some users have experienced problems with Yosemite OSX, so we have a fix available for this.
Lemur has not yet been updated for IOS 9. There are people requesting on the Liine facebook page, so it doesn’t look like it’s released yet.
Viewing 15 posts - 1 through 15 (of 89 total)