Still Logic X Unresponsive State with 19.12.1.3

[sjgam]

On Control App, still getting this unresponsive state in Channel Mode typically when using Config with Inserts. The center of the app just lists the Channel Modes - Inserts, Input, EQ etc. Restarting Logic Project or Eucon fixes until it comes back again.

I thought this was fixed.

19.12.1.3 for Control App and Eucontrol

Current Logic, Mojave, MacbookPro 2013 Late, Current ipad

Happens wired through router and wireless. Stand alone with just iPad and with Dock. All works fine until this happens.

Constantly having to restart Eucontrol is not workable. Been like this for several versions and I have let this forum and Logic know over several releases.

See attachment.

[sjgam]

Tried uninstalling Eucon (using the Eucon uninstall app including prefs) and reinstalled and installed new control app and still eventually got this unresponsive state.

Only effects the channel mode and some of the channel features still work.

Restart Eucon and everything including Channel Features are fine.

I would be willing to lose features just so eucon stays operating without restarts.

[EddieJones]

Can I clarify this only happens in config mode ? The reason I ask is that you say you are willing to lose features to make this stable...so why not stop using config or am I missing something ?

[sjgam]

Originally Posted by EddieJones

Can I clarify this only happens in config mode ? The reason I ask is that you say you are willing to lose features to make this stable...so why not stop using config or am I missing something ?

It's not consistent - having trouble isolating it to one thing. But it occurs regularly and the only fix is restarting project or Eucontrol.

As I mentioned in this post - the "official" current Sweetwater Demo running on their S1 product section on their website shows this bug and in their case they are using Pro Tools. It's happening in my case with Logic. I took a screenshot of it in my post below.

http://duc.avid.com/showthread.php?t=407820

Are you guys at Avid seeing this screen/state and are you working on it?

[sjgam]

Originally Posted by EddieJones

Can I clarify this only happens in config mode ? The reason I ask is that you say you are willing to lose features to make this stable...so why not stop using config or am I missing something ?

Eddie - can you confirm if you are able to replicate this frozen state where in Channel mode the Channel Type Names are displayed on top left function cell in center of app and you cant access inserts any more.

I can confirm that using Config in Inserts and also selecting different Outputs in Mix mode produce this.

Again I am on Logic Pro X.

I thought you would have found it interesting that it appears in SweetWater's "Official" Current Demo of S1.

Again I am on Logic but Sweetwater Demo is on Pro Tools.

And again all functions fine until this happens and restart of Eucontrol or Project makes everything work again.

Can you confirm you are seeing/opinion on this?

(Reattached my screenshot and Sweetwaters for your convenience)

[Southsidemusic]

The left pic is the Avid Dock so are you saying that it hapoens on both S1 and Dock?

[sjgam]

Originally Posted by Southsidemusic

The left pic is the Avid Dock so are you saying that it hapoens on both S1 and Dock?

Yes in the Control app on its own, in s1 and dock.

[Southsidemusic]

Originally Posted by sjgam

Yes in the Control app on its own, in s1 and dock.

Wow! That NEEDS to be fixed Asap!

[sjgam]

Originally Posted by sjgam

Eddie - can you confirm if you are able to replicate this frozen state where in Channel mode the Channel Type Names are displayed on top left function cell in center of app and you cant access inserts any more.

I can confirm that using Config in Inserts and also selecting different Outputs in Mix mode produce this.

Again I am on Logic Pro X.

I thought you would have found it interesting that it appears in SweetWater's "Official" Current Demo of S1.

Again I am on Logic but Sweetwater Demo is on Pro Tools.

And again all functions fine until this happens and restart of Eucontrol or Project makes everything work again.

Can you confirm you are seeing/opinion on this?

(Reattached my screenshot and Sweetwaters for your convenience)

Bumping my question to Avid - still don't have confirmation from Avid whether they are seeing this non-responsive state as shown in current Sweetwater demo on their site with Pro Tools and with my screenshot on Logic Pro X.

[sjgam]

Bumping again to see if Avid is seeing/working on this.