Device that worked in beta not working in shipping build.

[synnack]

You clicked the refresh button, then choose a device, but the parameter menu stays empty. Did I understand that right?

Correct.

But if I hit the "edit" button and choose an item from the "device" menu in the Max programming environment, the parameter menu populates as expected.

That's exactly what was happening for me but it just suddenly started working. Makes it very difficult to troubleshoot and fix since I can't get it to NOT work again.

All the code I'm using to populate those umenu's is default stuff that comes with Max-for-live so maybe Ralf can still help us. I would have to guess that any device using those patches that come with it will have the same weirdness.

[Ralf]

Correct.

But if I hit the "edit" button and choose an item from the "device" menu in the Max programming environment, the parameter menu populates as expected.

So, could you please tell me what you see in the Max Window?

Thanks,
Ralf

[stringbot]

So, could you please tell me what you see in the Max Window?

Here's what shows up in the Max window when I open the editor:

1: 0
1: 0
live.object: get: no valid object set
live.path: set path: invalid path

Some more notes:

The first time I tried to use the plugin, it worked correctly. This was on a new Live session with only one device loaded and the LineFO plug-in loaded into the only MIDI track.

I was able to reproduce the problem by loading a saved session which already had two MIDI tracks on it and creating a third MIDI track to host the LineFO. It will load parameters for devices on the first (left-most) track but not on other tracks.

I tried another new session and had varying degrees of success when moving a plug-in from track to track -- sometimes the LineFO would be able to load the parameters, other times it would not.

When it does work correctly, the Max Window has the following output:

1: 0
1: 0
live.path: set path: invalid path

Hope this helps!

[Martyn]

Same results for me too, also with the Parameter LFO from http://www.extendlive.com/. Can't get parameters.

[aevidence]

Hi-
I'm having this same problem, except it is a bit more extreme. Every time I select a device from the ubumenu (using M4L.api.SelectDevice), LIVE crashes entirely without, obviously, populating the following M4L.api.SelectParameter ubumenu. This is 100% consistent on my PC running XP. Have not tried on a mac. It did this in the beta versions as well as the current released version.

It all seems to work fine in the max environment, ie. with Preview On. Is there anything I should be doing differently between Preview On and within LIVE?

I get nothing in the Max window when the crash occurs, but when I run it in Preview On mode, I get:

live.path set path: invalid path

Any suggestions would be much appreciated...total LIVE crashes are no fun!

Thanks.
-Halsey

[Ralf]

We have reproduced the issue with the "id id". It happens
after deleting/moving devices. We are looking for a fix.

We could not yet reproduce the crash. Halsey, would you
please send a crash log to [email protected] with a
reference to this thread (or give me a reference if you
already sent it)?

Thanks alot.
Ralf

[synnack]

Thank you Ralf. If you need someone to test the fix just let me know.

[LLF]

Just to confirm this problem occurs on my system, with both the lineFO patches and my own.

They will both function when accessed through the Max interface, but the parameter field seems to break when newly loaded.

However, after 'initializing' the list in this way (loading editor), I can save and reopen the set without problems.

[Martyn]

Any news on this prob? I really want to play around with this sort of device and possibly start learning to make things along this sort of line. Nothing with a get parameters field is working for me though.

[Parametex]

Yes I'd be really happy to see this bug fixed as many of my devices are based on this function ... functioning...

[wiggle]

My plugin also does not work on my system anymore:
http://www.unsound.com/M4L/
[A Max4Live plugin which sends numerical audio peak data to Processing via OSC.
Any program that can tap into OSC can use the data (Super Collider, Blender, etc.)]

Some users say it works, but for some reason does not work for me
after I installed Ableton Live 8.1 Suite release (Unibody Macbook, OSX 10.6.2)
I can see that OSC packets are being sent from Live to Max, but Processing
can not catch the data anymore.

Would anyone else be kind enough to try this out?

Thanks!

[LLF]

We have reproduced the issue with the "id id". It happens
after deleting/moving devices.

Another problem along these lines, for me:

When dragging an .als with embedded parameter lists into an existing set, the lists will not recall properly. It seems the objects are not able to "lock on" to a specific track / device / parameter name (when things are jumbled around a bit, they lose their assignments). I often save clip groupings in this way, so its a bit of a problem.

I have otherwise been working successfully with the parameter sends in sets, and am able to load sets directly with all the assignments intact. I haven't experienced the populate issue directly since switching to the *clipped* input (2nd one) of the api object. I know that is weird and it's probably not really a fix.

[Martyn]

Still not working in Beta2, although if I open the device in the editor and lock components it does work. After shutting it again it returns to disfunctionality with the connection still functioning.

[Ralf]

Still not working in Beta2.

The fix for the original issue will be in the next Max version.

Ralf

[Martyn]

Still not working in Beta2.

The fix for the original issue will be in the next Max version.

Ralf

Thanks, cripes you still working!?