TCP Remote access

[bassthumper]

I am not sure if this has been addressed. I do remember a thread about this subject awhile back. Greg and I just did a test set tonight for a deal we are doing tomorrow afternoon. I noticed when I did a remote connection to the host the mix template that we were using was not on my computer so it gave me a message along the lines of file not found, however, even without the template I had signal and was able to adjust the levels of the inputs and outputs the only problem is it did not have labels on anything so it was like mixing blind. Another thing I noticed is that I could not adjust fx such as reverb or add dynamics to any channel. Matter of fact when I attempted to add a comp to a channel my laptop locked up which caused the host to freeze (it did not lock up completely and no buffer slippage) until after my machine disconnected. We are still planning on making a go of this tomorrow. If all goes well we will be doing FOH and 4 possibly 5 monitor mixes using a host and 2 remotes.
Our remotes will be connected via cat6 and a linksys switch. We are not brave enough to do the wi-fi thingy yet..............

[ambler]

You need to set up network shares for TCP Remote control to work. You don't need to have any files on the remote machine, the file not found errors happen because the remote machine doesn't have access to the files on the host.

See this thread for details.
http://www.sawstudiouser.com/forums/sho ... php?t=7596

Mark

[Bob L]

Correct... you do not need files on the remote machine... it reads what it needs from the host... but you must have a connection and read/write access for that to happen.

As far as plugin control on the remote... that concept has not been implemented and not figured out yet... it is very involved and may require a remote screen and mouse positioning type concept like remote access programs.... but I am not fond of that because there is no quick way to transfer that much screen data across the network and every mouse move and click to point to the plugins which have their own interfaces not controlled by the host SAC code.

Bob L

[bassthumper]

You need to set up network shares for TCP Remote control to work. You don't need to have any files on the remote machine, the file not found errors happen because the remote machine doesn't have access to the files on the host.

See this thread for details.
http://www.sawstudiouser.com/forums/sho ... php?t=7596

Mark

Thanks Mark and Bob. I knew there was a reason and I knew there was a thread on it I just could not find it when I searched for it.

Bob, even if you do not implement the ability to access plugins remotely I think this will fly.

Greg is planning on getting images of our configuration to post.

Another thing I forgot to mention about our test last night, we used the crossover on the 7 band and drove 4 jbl 15's and 2 horns. If we had more outputs on the fireface (or another fireface) we could eliminate one whole rack of external equipment and drastically reduce the strain on our backs....................

[Pedro Itriago]

Correct... you do not need files on the remote machine... it reads what it needs from the host... but you must have a connection and read/write access for that to happen.

As far as plugin control on the remote... that concept has not been implemented and not figured out yet... it is very involved and may require a remote screen and mouse positioning type concept like remote access programs.... but I am not fond of that because there is no quick way to transfer that much screen data across the network and every mouse move and click to point to the plugins which have their own interfaces not controlled by the host SAC code.

Bob L

Could you implement something like having a copy of the plug-in in the remote and have just the data change sent to the plug-in over the network?

Of course, this would only work for native plug-ins and after adding some kind of support via the plug-in API. I don't see this happening on vts/directx, unless you could add midi over ethernet.

[Bob L]

Looking into various possibilities... but other things are at the top of the todo list before this gets handled.

Bob L

[jazzboxmaker]

I've noticed that shutting down SAC with the Remote or Master TCP/IP Options still selected on the respective machines causes the nasty Windows Error message. I guess something makes Windows think there was an abnormal program termination even though SAC shuts down the link on the way out.

Clearing the option before shutdown results in normal termination. Seems like a "housekeeping" issue only as the mix is saved and all is otherwise well.

Are there others seeing this?

[mako]

Yes Vinnie - I often get the windows error message.

mako

[Bob L]

Yes... I know about that one... working on a fix.

Bob L