[xmonsta]

Apologies for this Ben, you dont need the MyMxDCore file. This is a test file. I will remove it from the install

There are a few reasons why your problem could happen:

1) Incorrect files, or files missing from _MxDCore (however I think this is not your issue, because you’re only missing MyMxDCore which isnt needed)
2) IP/Port set up incorrectly on the Lemur settings (The IP/port in Lemur settings should be your MAC IP and the port on the amxd device 8004)
3) Firewall blocking the port (turn your firewall off while you get it set up – we can send you a rule for your firewall if needed). A good tool for checking whether your computer is responding to your lemur is this – https://itunes.apple.com/en/app/network-ping-lite/id289967115?mt=8 which allows you to ping your computer, to check whether connections are received.

You’re always welcome to contact us at support@xmonsta.com for dedicated support. We’ve been able to get it set up for everyone so far.

[xmonsta]

Hi,

Contact support@xmonsta.com and we’ll be able to help you. Please can you provide a description of what is happening? Also, right click on the Max device and select “open max window”, to find out if there are any errors in there.

Cheers

[xmonsta]

Hi Mike,

I think we’ve fixed the performance issue. The good news is you dont have to reinstall again. Just overwrite 3 files, PULL vX.X.amxd, large_template.jzml and large_template-fits-editor.jzml

Cheers

[xmonsta]

Hi Kirkwood,

There is a new update which has fixed this and a performance issue. The good news is you dont have to reinstall again. Just overwrite 4 files, PULL vX.X.amxd, large_template.jzml and large_template-fits-editor.jzml and FrequencyShifter.jzlib

Cheers

[xmonsta]

Excellent, glad you got it fixed. The main two things that will stop the lemur sending to the computer are, ip/port not filled in incorrectly on the lemur, or a firewall issue on the computer.

Glad you got it sorted. You may get a quicker response from the support email support[at]xmonsta[dot]com

Cheers

[xmonsta]

Hi William

You can solve the problem of Ableton freezing on load by moving the device to a different location on your computer, or deleting it. Then open ableton and it won’t be able to load the device and therefore won’t freeze. Then delete the device (the one that ableton has created a placeholder for because its missing) from your master channel and save your default set.

The large template takes around 20 seconds to complete sending to the iPad. If it takes longer then it might be due to and old max installation. Do you have he latest version of max? 6.1.8

Not to worry about the _dis files. These shouldn’t be in the manual. Sorry about this I’ll remove them

Cheers

X

[xmonsta]

Yes, the ability to manage templates with third party max devices and vsts is coming soon. The whole reason for building PULL is interoperability, so all your popular max devices and VST’s will be controllable. We will start with some tutorials on how to build your own templates, with a few examples. We will also build some packs to save you time rather than building them yourself. We’re also working on a new product that will make VST management a lot easier on all sorts of controllers including touchscreen’s.

[xmonsta]

Hi Kirkwood,

Yes, the menu still works in terms of selecting between the two different knobs, but it should be toggling, not selecting both.

Thanks, we will fix this in the next update.

[xmonsta]

Hi Kirkwood,

The knobs are in linear mode, except for the ones that are bipolar (where 0 is in the middle).

The great thing about the Lemur is that when you touch a control you can move your finger outwards of the knob to obtain a wider surface area. A knob may be small, but you can make it as large as you want by using it this way.

Cheers,

[xmonsta]

Hey Mike, just a quick note to say that you can always select “load” on the device instead of “auto”. In this case the device will do absolutely nothing, until you have pushed the “pull” button on your lemur. You have various controls to slow down/speed up the loading of templates as well. Would be great to hear your feedback on these things as we strive to make sure that PULL is instantaneous as it can be.

[xmonsta]

Hi Mike,

After looking at the ADSR breakpoint for the Analog filter, it seems as if there is a slight issue with the decay. It doesn’t go as far to the right as it should do and stops you from moving any further (it is limiting up to a certain point). The one in Ableton goes further when moving in-line with the Attack. A simple workaround for the time being is to get the decay where you need it with the breakpoint and then if you need it to go further, using the decay fader (that is being controlled by the breakpoint) to move adjust it for fine control (this fader allows you to go over the limit).

We will add this to our next update though. It’s a fairly straight forward fix.

Is there any other problem you’re having with the breakpoint? The rest of it seems to work fairly well in-line with the one on Analog. I’m not sure we can get it to resemble exactly how the Analog breakpoint works, but it’s mainly there as a visual representation. It might be easier to use the ADSR to get near enough the sound you’re looking for and then use the faders (that are controlled by the ADSR) to fine tune the sound.

Just a quick tip (you might know this already), but if you touch an item on the lemur (breakpoint, fader, or anything) if you keep your finger held down, and you move it further away from the item, you can get a much wider resolution for the item youre trying to control.

[xmonsta]

Hey Mike,

Will take a look at the filter cut off to see If this can be improved.

In the meantime let’s fix your speed issues. PULL shouldn’t slow down depending on the size Of your set. The sigabort fix appears to be not working. You could try reinstalling this and see if it helps. One thing you could check to see if the fix is working, is when your set starts to slow down, delete the pull device and reinstate a new pull device. Are things faster then?

As for using python this is something we have looked into and may use in the future. However, there shouldn’t be much difference with max vs python, because max uses python to communicate with ableton.

Hope it helps

X

[xmonsta]

You’re absolutely right Jon. Looper state buttons do work in all versions of Live 9, seems to work if there is a clip playing in an audio track too. Thanks for pointing this out.

The one thing I’ve noticed (and caught me out) is that abletons transport needs to be playing in order for looper state buttons to work. I now think this might be the bug that ableton are referring to, because when you press play on the status, abletons transport should start (but it doesn’t). Whereas if you click on the play button with a mouse, abletons transport starts up.

Also, with looper its worth mentioning that when you use the state button through max for live, it doesnt work in sync, like when you press it with your mouse (looper waits until it’s sycn is ready). We might try to find a workaround for this in the device itself, where we recognise the looper’s quantization and then make the state changes made with lemur wait until the sync is ready. Pretty hard but not impossible.

Cheers

[xmonsta]

Thanks Jon.

Just wondering are the play, stop, overdub buttons really working from the lemur? Ableton say this is a known bug and they’re still trying to fix it

[xmonsta]

Hi Brian,

On windows the files should be in:

C:\ProgramData\Ableton\Live 9 Suite 9.x.x\Resources\MIDI Remote Scripts\_MxDCore

You don’t have to apply the sigabort fix, but it will speed up the operation a lot. You can test it out yourself, by using the hot-switch button on a large device like operator. Pick two presets that change only operators parameters and switch between them back and forth 10-20 times.

Without sigabort fix – 6-10 seconds to hot-switch
With sigabort fix – less than 1 second to hot-switch

Also without the sigabort fix, the time was increasing, so over time it will be 20, 30, 40 seconds to change parameters. This has improved with later versions of live (from our testing). However, we would recommend using live 9.0.6 because this seems to be the most stable (we’ve been using it for months with PULL without problems). Live 9.1.4 has some problems with the fix which we’re currently looking into.

Also, make sure to at least back up your _MxDCore folder, if you want to go back, you can just plop the files in. If you don’t back it up you may have to reinstall live, which can be a pain.

Hope this helps

xmonsta

[Author]

Posts