I reported an issue with Ableton regarding some Max4Live issues that I was seeing (issues with redraw and Max devices not working) they instantly replied that they had seen issues with Hybrid & Loom (suspected OpenGL issue) both of which were in my project, they also said that they and Cycling '74 had tried to contact Air to investigate and work on a solution but so far had had no response.
Following my conversation with Ableton I tested the interaction between Air & Max4Live and found the following:
These plugins appear to cause Max for Live Issues
Hybrid
Vaccuum Pro
Loom
Xpand2
Strike 2
These plugins do not appear to cause Max for Live issues
Velvet
Structure
MiniGrand
DB33
The Riser
The Effects plugins do not seem cause issues.
Has this issue been acknowledged and being worked on?
Dean
-
Hello,
Could a member of the support team, acknowledge this post and tell me if this issue is:-
a) known about;
b) known and being looked into;
or
c) just being ignored.
Thanks -
-
Hi Dean,
Thanks for posting.
This isn't something I've heard of before. Can you please elaborate on the issues you're experiencing with Hybrid, Vaccuum Pro, Loom, Xpand2, and Strike 2?
Can you also confirm you're running the latest versions of the plugins? -
-
Hi Bill,
Thanks for replying. Yes all Air plug ins are up to date.
The problem occurs with Max4Live devices in Ableton sets using some Air VSTs, just them being in the set is enough
The issue is that loading up an Ableton set with Max4Live devices, the GUIs don't update or you can control the settings but you get zero visual feedback it's like the GUIs are frozen also Max4Live devices lose their mappings such as the LFO object which loses the parameter it's controlling.
I contacted Ableton who replied back saying that they'd seen issues with Hybrid and Loom in in sets using Max4Live devices and that both Ableton & Cycling '74 had previously attempted to report to Air to investigate but had so far had no response and suggested that I report which I did (no response) and also the forum.
With the information Ableton gave me I spent some time swapping out and trying various instruments and indeed did find that I had the problems with Hybrid and Loom but also Xpand2, Vacuum 2 and Strike 2 but not the others. I have not seen this issue with other non-Air VSTs.
Regards,
Dean -
-
Interesting. Let's have you get in touch with your nearest Support Office. Log on to www.airmusictech.com/support to contact Technical Support.
-
-
Hi Bill,
I did a week or so before posting here but I will try again and reference this thread.
Is it possible for you to help progress the incident if I get no reply again? So far I've reported two issues, the first was fixed but I only found that out from one of your posts here! The second was this one.
Dean -
-
If you do not get a response within 3 business days, please call our Support team.
-
-
Hi Bill,
Sorry for digging up thread but the problem still persists, I got a call back in June from an InBrand support guy to get some more details after I sent a video showing the issue but since then not a word back despite a few emails asking if there is an update.
Is there any chance you can look into it?
Dean -
-
One of my support agents should be in touch with you shortly :)
-
-
-
-
Hi Bill,
Unless I've missed an email or something, still nobody has contacted me about this issue.
Also sadly I downloaded a trial of Loom 2 and the problem still exists which is disappointing as the original Loom is still, despite the apparent conflict, one of my favourite synths but unfortunately doesn't get used as much as I'd like without some planning.
Another thing I'd like to raise about Loom 2 is that the VST is called Loom_x64.dll so overwrites the "classic" Loom vst.
Dean -
-
Hi Dean,
Sorry about that, I'm having someone reach out to you right now. -
-
Hi Bill,
Is there a way for you to PM me? The support and reporting of this issue is at best a nightmare, I reported this back in July and Cycling 74 & Ableton are keen to get it sorted but Air Tech do not seem to be able to co-ordinate this.
Because my the video shows a non-Air plugin affecting Max4Live devices by the presence of Xpand!2 in the project, I've been told that "I don't appear to be having a problem with Air products"
It's all rather like a jokeless Groundhog Day.
Dean -
-
Once again no response from support, this was reported 4 months or so ago, Ableton stated that they had seen issues with some Air plugins causing Max Issues, Air unresponsive to thier requests to investigate with Cycling 74.
so here's the video...
https://www.dropbox.com/s/ptoj3agq4py...
1. Ableton Set with three LFOs controlling Synplant - Xpand2 (mentioned above as problematic) is also in the Set. The LFOs are not working.
2. Xpand2 removed from the Set is saved and Ableton closed.
3. Black part is where the screen capture loses focus once Ableton closed - resumes once loaded.
4. Ableton re-opened and Project without Xpand2 opened.
5. LFOs working as expected with Synplant.
Do Air developers need anymore details?
Dean -
-
Hi Dean,
One of my technicians sent you an email last week and has been waiting for your response. Please follow up with them when you can. Thanks! -
-
Hi Dean,
One of my technicians sent you an email last week and has been waiting for your response. Please follow up with them when you can. Thanks! -