MTRX II. Preamp control across multiple devices.

[theAlien]

Originally Posted by uptheoctave

I have figured out part of the issue.
A few weeks ago I had to create a new user account on my Mac Studio because iCloud documents stopped syncing. I was unable to turn syncing back on with that user account. You click the button in iCloud settings and it automatically turns itself off.

So I created a new administrator account and that was the one that I have tried to get Pre control working with.
I have logged back into the original account (which still does not work with iCloud syncing) but Pre control DOES work.

I have tried creating a 3rd user account on this machine and it also does not work with Pre control.
The original account works just fine, in either Rosetta or Silicon.

So it is something to do with creating a new user account and perhaps some permissions or privilege issue?

Very strange and it isn't solved for me yet, I need it to work with a newly created user account, because I rely on iCloud document sync.

Edit: I managed to fix the original account by turning off iCloud, deleting the backup, deleting a hidden 'Documents' alias in Macintosh HD/Users/~user, creating a new Documents folder, then turning on iCloud and then turning on Desktop and Documents sync.
What a PITA.

Still, it doesn't explain why creating a new user account will not allow Pre control to work.

Due to how 'Desktop and Documents' sync feature is designed (and implemented) it can have unpleasing side effects (or bugs), esp. when macOS is set to manage/optimize storage. I never used it but have read about complaints.

For all data not depending on Apple's CloudKit you may want to consider manual syncing, at least as a fallback solution.

What I do is to have ~/Archive folder (or volume) where I frequently toss all important data (hierarchies) on (manually or via rsync scripts; can be set as cron, Calendar action (AppleScript) or Shortcuts) and sync this manually with a cloud storage.

You can also use apps ofc like Mike Bombich's Carbon Copy Cloner, Superduper, Chronosync etc.

If you need (not self hosted) Cloud backup/sync solutions: Backblaze (https://www.backblaze.com/), Arq Backup (https://www.arqbackup.com/), Expandrive Strongsync (https://www.expandrive.com/strongsync/), Goodsync (https://www.goodsync.com), Syncthing (https://syncthing.net)

Only leave copies on iCloud and use multiple services as backups.

Account and permission troubleshooting can be really mean. My biggest gripe: I am battling user disrespecting vendors jeopardizing my system ignoring platform guidelines and polluting with BS file permissions. Have to run scripts and correct the whole system after any update or find new offenders. Arrrgh.

[uptheoctave]

Originally Posted by theAlien

Due to how 'Desktop and Documents' sync feature is designed (and implemented) it can have unpleasing side effects (or bugs), esp. when macOS is set to manage/optimize storage. I never used it but have read about complaints.

For all data not depending on Apple's CloudKit you may want to consider manual syncing, at least as a fallback solution.

What I do is to have ~/Archive folder (or volume) where I frequently toss all important data (hierarchies) on (manually or via rsync scripts; can be set as cron, Calendar action (AppleScript) or Shortcuts) and sync this manually with a cloud storage.

You can also use apps ofc like Mike Bombich's Carbon Copy Cloner, Superduper, Chronosync etc.

If you need (not self hosted) Cloud backup/sync solutions: Backblaze (https://www.backblaze.com/), Arq Backup (https://www.arqbackup.com/), Expandrive Strongsync (https://www.expandrive.com/strongsync/), Goodsync (https://www.goodsync.com), Syncthing (https://syncthing.net)

Only leave copies on iCloud and use multiple services as backups.

Account and permission troubleshooting can be really mean. My biggest gripe: I am battling user disrespecting vendors jeopardizing my system ignoring platform guidelines and polluting with BS file permissions. Have to run scripts and correct the whole system after any update or find new offenders. Arrrgh.

It is the first time I've had a problem with iCloud in 15 odd years of using it.

I don't use it for audio data and I have a robust backup strategy otherwise.

[ntp-jl]

Just to clarify a thing here.

The MIDI commands are sent from Pro Tools to the DADman software through a virtual MIDI interface. DADman "translates" the MIDI commands into MTRX/AX64 commands and then sends the pre amp commands (gain, phantom power, etc.) to the MTRX through the regular control connection.

The control connection is either through TB3 or network. If the computer running the DADman software is connected to an MTRX 2 or MTRX Studio through a TB3 connection, then the control connection goes through the TB3 connection. This is also the case even if the computer has a network connection to the same MTRX 2/MTRX Studio.

If there is no TB3 connection between the computer and the MTRX 2/MTRX Studio, then the control connection is done via the network.

MIDI commands are not sent from Pro Tools directly to the MTRX/MTRX Studio.

The MTRX can therefore not see whether a gain command is initiated in Pro Tools or in DADman.

[uptheoctave]

Originally Posted by ntp-jl

Just to clarify a thing here.

The MIDI commands are sent from Pro Tools to the DADman software through a virtual MIDI interface. DADman "translates" the MIDI commands into MTRX/AX64 commands and then sends the pre amp commands (gain, phantom power, etc.) to the MTRX through the regular control connection.

The control connection is either through TB3 or network. If the computer running the DADman software is connected to an MTRX 2 or MTRX Studio through a TB3 connection, then the control connection goes through the TB3 connection. This is also the case even if the computer has a network connection to the same MTRX 2/MTRX Studio.

If there is no TB3 connection between the computer and the MTRX 2/MTRX Studio, then the control connection is done via the network.

MIDI commands are not sent from Pro Tools directly to the MTRX/MTRX Studio.

The MTRX can therefore not see whether a gain command is initiated in Pro Tools or in DADman.

Thanks Jan.

Any idea why this only works with the original computer's admin account and not with any admin accounts created later?

[gives]

Originally Posted by ntp-jl

Just to clarify a thing here.

The MIDI commands are sent from Pro Tools to the DADman software through a virtual MIDI interface. DADman "translates" the MIDI commands into MTRX/AX64 commands and then sends the pre amp commands (gain, phantom power, etc.) to the MTRX through the regular control connection.

The control connection is either through TB3 or network. If the computer running the DADman software is connected to an MTRX 2 or MTRX Studio through a TB3 connection, then the control connection goes through the TB3 connection. This is also the case even if the computer has a network connection to the same MTRX 2/MTRX Studio.

If there is no TB3 connection between the computer and the MTRX 2/MTRX Studio, then the control connection is done via the network.

MIDI commands are not sent from Pro Tools directly to the MTRX/MTRX Studio.

The MTRX can therefore not see whether a gain command is initiated in Pro Tools or in DADman.

Great explanation! Good info for a colleague who was asking about this!

G

[uptheoctave]

Originally Posted by ntp-jl

Just to clarify a thing here.

The MIDI commands are sent from Pro Tools to the DADman software through a virtual MIDI interface. DADman "translates" the MIDI commands into MTRX/AX64 commands and then sends the pre amp commands (gain, phantom power, etc.) to the MTRX through the regular control connection.

The control connection is either through TB3 or network. If the computer running the DADman software is connected to an MTRX 2 or MTRX Studio through a TB3 connection, then the control connection goes through the TB3 connection. This is also the case even if the computer has a network connection to the same MTRX 2/MTRX Studio.

If there is no TB3 connection between the computer and the MTRX 2/MTRX Studio, then the control connection is done via the network.

MIDI commands are not sent from Pro Tools directly to the MTRX/MTRX Studio.

The MTRX can therefore not see whether a gain command is initiated in Pro Tools or in DADman.

Just FYI, I've had a second email from Avid support insisting that pre control is over Thunderbolt.

I've linked them to your post for clarification.