Logic X track stacks are not fully recognized by EuCon

[robertg]

Hey Eddie, what do you think about this one?

EuCon doesn't see plugins on some type of Logic tracks, it's like they're not there.

Start with a new project, create a few tracks. Shift-select them all, right click and create track stack. summing stack.

Now, the parent of this stack will be called Sum 1. If you insert a plugin on this track from the EuCon controller, all is well, but if you insert it with the mouse the conventional way, EuCon sees no plugin in that slot.

That's a workflow hinderance for me and people who have come to rely on this Logic feature.

Thanks

[EddieJones]

I'll take a look Monday..EDIT Wednesday now..sorry

[EddieJones]

This is an old bug(and discussed in another post) and nothing to do with Stacks, it affects all tracks. This has been reported to Apple but please can you post on their forum. To see them you have to save and reopen the session.

[robertg]

Originally Posted by EddieJones

This is an old bug(and discussed in another post) and nothing to do with Stacks, it affects all tracks. This has been reported to Apple but please can you post on their forum. To see them you have to save and reopen the session.

Thanks Eddie, it seems that these old bugs are not ever going to be fixed, it's been 5 years for some.

I'm also doubtful that I could have any impact in bug reporting to them, I am just one user. You do have a lot more weight as the developer of a major control protocol. Is there anything you can do to encourage them to increase the priority of bug fixes?

[EddieJones]

You maybe one user but if all the one users report this (and there are 1000's of Logic Artist users) then they would give Avid more argument to get them to work on it.

[robertg]

Eddie, in messing with this some more I've determined that we're talking about 2 different Logic bugs involving missing plugins. One is that the plugin is "there" but just has no name shown - it's selectable and you can turn it on and off, the other is that it's completely invisible to the surfaces.

Regardless, I really have a tough time accepting that the burden is on *us* to get Apple to fix these. Here's another possibility, what if they're not bugs at all in Apple's view, and these are changes made to Logic's behavior and it's up to AVID to adjust Eucon and adapt to them. But maybe that's not happening because it's too much of an undertaking and would risk breaking other things?

I am strongly considering buying an S3 and PT dock sometime this year to replace my five surfaces. It's not something I am likely to do however if these ancient flaws are not fixed, regardless of who is to blame for it.

Thanks again for your time and attention to these issues.
Rob

[EddieJones]

The burden is on both of us. If we go to Apple with bugs that they haven't heard of from their customers they will be a lot lower priority than if customers had reported them directly too. EUCON is a API/SDK the states how a DAW should connect and work with the Consoles. All EUCON partners have to follow that otherwise it would be a nightmare writing code specifically for each of the 50+ EUCON partners. The missing plugin bug, is that after inserting one, Logic should refresh the knobsets. It doesnt. No amount of code on our side could magically get those new names if Logic doesnt present them.

We are working with them though so hopefully we can get them resolved.