Page 1 of 1
Errors and issues with maxforlive devices, since forever.
Posted: Tue Dec 06, 2022 11:28 am
by chrisfreeq
Hi,
I started using Ableton around 3-4 years ago now. During all my time using Ableton, I have either gotten errors almost no matter what 3rd party maxforlive device I use, or it's resulted in corrupt project, making me very reluctant to use these amazing tools.
I recently reinstalled Windows 10 and Ableton 11, and surprise surprise, I still get errors.
Right now, I'm trying to use Chronology and Polymath, and I get the errors live.path - set path: invalid path.
If I add any device *instruments and effects( from the "inspired by Nature" pack, I get ever-persistent "jit.gi: invalid extension called" errors. Can't even remove the device again because of the persistent error-window. If I collapse the device, the persistent errors stops, and gives me "jit.gl.render: finish: GL Error: Invalid operation". Apparently the first errors occurring with this device are "jit.gl.render: finish: GL Error: Invalid operation" and "jit_gl_support_init: initial: GL Error: Invalid enumeration"
I could go on, but I think this might already be too much for one post.
Cheers,
Chris
Re: Errors and issues with maxforlive devices, since forever.
Posted: Tue Dec 06, 2022 12:06 pm
by [jur]
Where do these error messages appear? Are they making the devices unusable?
Re: Errors and issues with maxforlive devices, since forever.
Posted: Tue Dec 06, 2022 3:59 pm
by chapelier fou
[jur] wrote: ↑Tue Dec 06, 2022 12:06 pm
Where do these error messages appear? Are they making the devices unusable?
That's an important question. Sometimes it's hard to get rid off error messages in Max (especially when a device is loaded), but it doesn't mean that they have an impact on the device.
Re: Errors and issues with maxforlive devices, since forever.
Posted: Thu Dec 08, 2022 12:11 pm
by chrisfreeq
[jur] wrote: ↑Tue Dec 06, 2022 12:06 pm
Where do these error messages appear? Are they making the devices unusable?
Well, not sure I understand the question; they appear in the max for live debug window. This one:
https://ibb.co/Kxm1Qrz
In the case of the Seeds devices (Chronology, Polymath etc., it's fine to keep working, I can just close down the window.
However it does make me nervous, with regards to projects turning corrupt / unusable later on.
In the case of the Inspired by Nature devices, yes. They're rendered useless because the maxforlive windows is persistent.
chapelier fou wrote: ↑Tue Dec 06, 2022 3:59 pm
[jur] wrote: ↑Tue Dec 06, 2022 12:06 pm
Where do these error messages appear? Are they making the devices unusable?
That's an important question. Sometimes it's hard to get rid off error messages in Max (especially when a device is loaded), but it doesn't mean that they have an impact on the device.
Right. But could it cause instabilities and possibly corrupt projects?
Cheers,
Chris
Re: Errors and issues with maxforlive devices, since forever.
Posted: Thu Dec 08, 2022 1:08 pm
by S4racen
report it to support then....
Cheers
D
Re: Errors and issues with maxforlive devices, since forever.
Posted: Thu Dec 08, 2022 3:10 pm
by [jur]
chrisfreeq wrote: ↑Thu Dec 08, 2022 12:11 pm
[jur] wrote: ↑Tue Dec 06, 2022 12:06 pm
Where do these error messages appear? Are they making the devices unusable?
Well, not sure I understand the question; they appear in the max for live debug window. This one:
https://ibb.co/Kxm1Qrz
In the case of the Seeds devices (Chronology, Polymath etc., it's fine to keep working, I can just close down the window.
However it does make me nervous, with regards to projects turning corrupt / unusable later on.
In the case of the Inspired by Nature devices, yes. They're rendered useless because the maxforlive windows is persistent.
chapelier fou wrote: ↑Tue Dec 06, 2022 3:59 pm
[jur] wrote: ↑Tue Dec 06, 2022 12:06 pm
Where do these error messages appear? Are they making the devices unusable?
That's an important question. Sometimes it's hard to get rid off error messages in Max (especially when a device is loaded), but it doesn't mean that they have an impact on the device.
Right. But could it cause instabilities and possibly corrupt projects?
Cheers,
Chris
As Chapelier said, it doesn't matter most of the time.
What I suspect is that you have an old instance of Granulator in your set, and because of it ht eMax Console pops up constantly... and that is the real problem.
Am I right?
If yes, then just make sure to downalod the lastest Granulator II version, it has an option to prevent the Max Console to open up automatically. This is mostly a developer tool that should have never been in the final version of the device.