top

View previous topic Element - New Source Sharing Scheme for Version 2.x View next topic

Post new topic This topic is locked: you cannot edit posts or make replies. Axia Discussion Board Forum Index | Tech Tips    Page 1 of 1

Fri Jul 11, 2008 12:15 am
PostPost subject: Element - New Source Sharing Scheme for Version 2.x Reply with quote
Bruce Wilkinson



Joined: 06 Jun 2007
Posts: 15

The source sharing logic has changed as of Version 2.0.x, so here is an explanation the new logic in a consolidated form.


1. Source sharing control no longer relies on the shareability property associated with the source at the node level. The Element versions 2.0 and higher will fully ignore the value advertised by the sources and only rely on the source profile settings. Node shared source parameter should be set to "no"

2. In the source profile we have two independent settings:
    a) Backward feed enabled/disabled
    b) Sending and receiving GPIO/CAN commands enabled/disabled

The two attributes above determine the way the source would be used, when it is being taken to a fader channel:
    a) "Listen only" mode: if neither the backfeed nor GPIO is enabled
    b) "Full control" mode: if any one of them or the both are enabled
    These modes can only affect the fader channels, as in all other cases the sources are only being used for listening.


3. The Element application will not attempt to lock the source and will ignore the state of the lock if a source is being taken for listening only. This includes the following cases:
    a) Taking the source to a fader input in the "listen only" mode (both the backfeed and GPIO functions are disabled in the source profile). In this case the source audio stream is simply connected to the fader input, and regardless of the source type no backfeed or GPIO would be activated. This way the same source can be used as an input on an unlimited number of faders at a time
    b) Taking the source to a monitor input of a console, including the individual headphones inputs on accessory modules
    c) Taking the source to a return input of a console
    d) Taking the source on a destination port of another device type, like audio node, engine V-Mixer or V-Mode input, PC with Axia IP driver, Omnia, Zephyr, etc.


4. If a source is being taken on a fader channel, and the source profile attributes specify the "full control" mode, then the result will depend on the attempt to lock the source:
    a) If the source appears already locked by another client, it will be taken in the "listen only" mode with the accordingly limited functionality, exactly the same way as if it was directly specified by the source profile
    b) If the source appears free, it will be locked now and allocated to the fader issuing the locking request. This grants the fader the rights to use the backfeed and GPIO functions, according to the source type and profile settings.
    This mechanism ensures that only one fader, per system, at a time can take a source for "full control", whereas all others will be forced to "listen only". Thus it will be impossible to originate the backfeed and GPIO commands for the same source from two or more different faders.


5. If you wish to know who owns a source, you can press the channel options button and that info will be displayed on the screen

6. Marking on the fader channel status symbol display:
    a) If a channel takes the source in the listen-only mode, no special marking
    b) If a channel locks the source, no special marking
    c) If a channel has loaded a source that is locked elsewhere causing it to be listen only, a small "x" will be displayed

Back to top View user's profile Send private message
 
Post new topic This topic is locked: you cannot edit posts or make replies. Axia Discussion Board Forum Index | Tech Tips    Page 1 of 1
Display posts from previous:   
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum