I don’t know why I keep getting these error messages and I can’t reproduce when they appear:
Gradient.amxd . upsend . OpenSoundControl unrecognized argument type
(I try to attach a screenshot)
I only get these for Gradient devices. I use both Videosync 1.4 and Videosync 2.0 Gradient devices in my set, most recently the 2.0 ones are from the latest Alpha version. But I alredy got the error messages before I started to test the Alpha.
I use quite a few envelope followers throughout the set that I map to Videosync device parameters. Additionally, I automate Videosync parameters by using helper clips (silent/empty audio clips that I only use for automation).
I don’t use any OSC in the set, at least not that I know of, no TouchOSC or any dedicated devices for OSC messages like from the Connection Kit.
I have not noticed any changed behaviour when these messages come, everything seems to work normally. It’s just that I have the M4L window pop up (due to another device in my set) which is really annoying when I play live.
Setup is:
MacBook Pro 16" 2021, Apple M1 Max chip
macOS Sonoma 14.7
Ableton Live 12.1.5b3 using bundled Max build to 8.6.5.
Videosync 2 Alpha 2.0.4
Do you have any idea where this could come from and what I should change or check to avoid these messages?
I’m trying with a set that only has two gradients in two tracks and some automation: one for rotation, the other one for spacing. So far, I don’t get this error message.
It looks like it only happens in this rather complex set with many devices for both audio and video and various automations and parameters mapped from envelope followers.
it’ll be a big package… if you don’t mind that, yes, sure, I can send it over.
It has a lot of files and devices, with many automations and mapped envelope followers.
I’ll try to debug myself first, double check all envelope followers and automated parameters. Will also try to pin it down to certain scenes and then send it over.
One other thing to check is if your complex Live Set actually exclusively uses the Videosync 2.0.4 devices, and not any older versions that were (perhaps accidentally) copied when using Collect All and Save.
The source of the issues that the 2.0.4 release should resolve is in the Max for Live devices. Using any older devices with the 2.0.4 application will therefor not resolve the stability issues.
okay, that’s great to know! because I still use a few 1.4 effects for color adjustments and probably something else, too.
I was too lazy to replace the older devices that work differently in 2.0 (like color devices). I will do this.
That’s great info! Unfortunately, all devices of prior released versions contain this bug that 2.0.4 is supposed to resolve, so I highly recommend switching to using only the devices that come with the Alpha build. It would be great to know if this indeed improves things for you.
That depends on what exactly you were using it for. Some of ColorControl’s features were moved to Color Mixer (Gain and Curve), while the rest turned into the new Colorize. It may be tricky to achieve the exact same effect however, needing a bit a tweaking, as some parameters’ exponents and ranges are different compared to ColorControl.
I won’t be able to replace the 1.4 devices. Too many interdependent things render differently or create mapping errors from my envelope followers and lfos. Colors look different, it would take me too much time…
Alright, we have a 1.4.7 Beta build that contains the fixed devices. Download it here, open the application and let the User Library Installer do its thing (the fixed devices will be installed in the Videosync 1.4 Plugins folder, overwriting the existing 1.4 devices), and then make sure all 1.4 devices in your complex Live Set are actually using these new devices, and not any older ones.
Hi Jean-Paul, thanks so much for the 1.4.7 Beta build!
I played two shows this week and worked on the set with the updated 1.4.7 Beta devices and the 2 Alpha devices and I did not get any of these M4L error messages anymore
