Hmmmm. I understand the desire to get away from the Win32 builds
completely. I think its kind of a neat feature, but it doesn't break my
heart they are being done away with.
I do have a tendency to be long winded, so I'll try to cut right to the
chase here:
The point you bring up about how we should be headed off in the
direction of VNC via virtual desktops for clock/log maintenance is
understood. However, with the work I have done so far that leaves ONE
question that isn't Rivendell related:
Does anyone know if x11vnc and vnc-server can peacefully co-exist
(assuming they are configured on different ports)? One would be used
for desktop sharing/file transfers by support staff, the other for
clock/log maintenance by the remaining station staff.
Thanks,
-Alan
.On 11/14/2018 6:26 PM, Fred Gleason wrote:
On Nov 14, 2018, at 15:31, Alan Smith <alansm...@flinn.com
<mailto:alansm...@flinn.com>> wrote:
1) Is it possible to specify multiple target systems from the Win32
Rivdendell modules? Say by maybe specifying different .ini files on
the shortcut/command line?
Shouldn’t be necessary, assuming that all of the stations are using a
common DB/audio store (the usual setup).
Further clarification if needed: In the upcoming year we are going
to be replacing all of our playout systems, hopefully with
Rivendell. In our group we have PDs that do logs for multiple
stations. Rather than having them remote accessing the systems (via
Teamviewer) and be intrusive to the on-air staff, I want to install
the Win32 builds on the PDs system for clock/ log maintenance. If
one PD does the logs for multiple stations, I would like to give them
any easy way to accomplish it.
You can do this using a VNC viewer on the Windows desktop and a
virtual VNC desktop on a Rivendell system, such that it won’t be
intrusive to the on-air staff at all. In fact, they will be totally
oblivious to the fact that the virtual desktop is even there. The
win32 build is going away completely in 3.x, so you really want to be
moving in this direction anyway.
2) Not really as important, by say I wanted to have the same access
from home over SSH. Will creating a tunnel on port 3306 be all this
is required? Again, not a big deal, as I have VNC over SSH setup if
need be, but trying to be as less intrusive as possible if needed.
That would get you access to the DB, but not the audio store. If the
remote system is Windows, you’d be better using VNC (for reasons
explained above).
I realize this and some of my other posts have been really minor
features and mostly *fluff*, but I am trying to get everything all
set just the way I think it needs to be before rolling out the first
system. After that, it will just be a duplication of my efforts, so
that is why I am trying to nail all this little stuff down now!
Ready, aim, and then fire! Last I looked, that *was* the preferred
sequence… :)
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| Nothing can be done in one trip. |
| -- Snider |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
