supervision

Helio Chissini de Castro helio at kde.org
Mon Aug 11 14:48:51 UTC 2014


On Monday 11 August 2014 16:11:25 Aaron J. Seigo wrote:
> * what are the use cases?
> * what exactly should be tunable / controlled?
> 
> What sorts of applications did you have in mind?
> 

Use cases, for example is a setup for studio musicians/ live setups on shows / lights


Case:

VM 1 is running a application such as Live or Cubase, usually modern usage contains 
several software based synths running on same machine, and is resource hungry

VM 2 is running a visual effects software that need be in sync with the music app on 
VM1, but is another resource monster eater

VM 3 is running a proper distribution channels for all the video and audio directions, 
like you have a museum multimedia installation where all parts are interconnected in 
different rooms

It can spans in case of live presentations to have mixed live video with recorded video 
and video effects.

For the current world, it relies in external solutions, like several computers, all running 
independent software, using an specific control method, that, when is not proprietary, 
it relies on MIDI time code. 

So, unless you have a well designed several multicore computer ( and backup ) with 
applications designed to work each other ( not likely ), only complex solutions to 
control and supervise this several machines is needed.

The idea behind the process owner would help in plug proceses that could not affect 
the master controller to mess with other resources


I know is a little bit more complex than the car, but match the needs


-- 
Helio Chissini de Castro
KDE and Linux Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kde.org/pipermail/funq-devel/attachments/20140811/da6c43af/attachment.html>


More information about the Funq-devel mailing list