Home› BSS User Forum › BSS Archive Threads› Discussion› London Architect with Soundweb London

Blu8 controlling a Source Selector - problem

SteVENSteVEN Posts: 27
in London Architect with Soundweb London
Ayone else having issues with Blu8s consistently not recalling the last available source?

I've tried with 6 position, 7 position and 8 position source selector objects. The Blu8 correctly scales the controls so that you don't see 7 and 8 with a 6 position source selector, for example, but when you try to select the last source (6 in this example) it won't take first time.

I tried turning allow none to off and using properties to disable the unused positions on the encoder but it's still intermittent.

This is with 2.06r3 and I've tried several different Blu8s and Blu800 and Blu160 frames.

Use proxy device was always turned on too.

Comments

  • Dan LynchDan Lynch Posts: 472
    Nope. Works perfectly every time.

    FYI: proxy mode is meaningless unless the BLU-8 needs to control SVs on more than 9 different devices.

    Dan
  • SteVENSteVEN Posts: 27
    Well a colleague who first spotted the problem tried it at the venue and continues to have the problem. I also tried it independently with completely different hardware at the BSS distributor in Stockholm who also witnessed the same behaviour.
  • Dan LynchDan Lynch Posts: 472
    1) Create a new design file
    2) Place a BLU-80
    3) Place a BLU-8
    4) Place a source selector in the BLU-80
    5) Set the source selector to 6 inputs
    6) Drag&drop the source selector to the rotary selector on the BLU-8
    7) Go online and load the design file
    8) Use the BLU-8 to select source 6
    9) Watch the source selector in London Architect change to input 6
    10) Repeat all of the above steps using a 7 input selector
    11) Repeat all of the above steps using a 5 input selector
    12) Repeat all of the above steps using an 8 input selector

    There are my steps to make it work perfectly every time without exception. Provide your steps which will make it malfunction and tech support will have something to work with.

    Dan
  • Dan LynchDan Lynch Posts: 472
    ...and then repeat the entire process with a BLU-160. Same results.

    Dan
  • Dan LynchDan Lynch Posts: 472
    The problem appears to be:
    If you rotate the BLU-8 knob TO the last position of the source selector and push the knob in, it selects the correct position. If you rotate the knob PAST the last position, the LED will remain white at the last position, but pushing the knob does nothing.

    Dan
  • SteVENSteVEN Posts: 27
    Ok, I can see that now. I'll be back at the venue on 12th October and can try that myself and will instruct my colleague who will be on site on the 4th to try it too.

    Is there a way for BSS to fix this in London Architect or should I just train the users to avoid going too far at the last position?
  • SteVENSteVEN Posts: 27
    \Dan Lynch\ wrote:
    ...and then repeat the entire process with a BLU-160. Same results.

    Dan

    We basically did the same as you when I visited the BSS Dealer in Stockholm. At the venue we were using a design file that simply had source selectors dropped onto the Blu8 encoder as well.
  • Dan LynchDan Lynch Posts: 472
    \SteVEN\ wrote:
    Is there a way for BSS to fix this in London Architect or should I just train the users to avoid going too far at the last position?

    Yes and yes.

    Dan
  • SteVENSteVEN Posts: 27
    \Dan Lynch\ wrote:
    \SteVEN\ wrote:
    Is there a way for BSS to fix this in London Architect or should I just train the users to avoid going too far at the last position?

    Yes and yes.

    Dan

    So will that be a patch fix or do we have to wait for the next release of LA?
  • Dan LynchDan Lynch Posts: 472
    There's no loss of function caused by this bug, which is a strike against it when figuring priority for fixing it. If it's really simple to fix, somebody may crank out the fix it on a bored Friday afternoon. If it turns out to be flaming nightmare to fix, it'll likely end up staying exactly as is forever.

    There's no way to know what changes will be released to the software or when they will happen until after all of the changes have been tested. If the fix for a non-fatal bug ends up causing more problems or just different problems, it'll be pulled from the release. That means there's really no definite way to know in advance what will be released or when (except for fixes of fatal problems). Anybody who tells you otherwise is just guessing or hoping.

    Dan
  • GrahamGraham Posts: 27
    This has been fixed in 2.06.R4.
This discussion has been closed.