Posts

Posts

  • Stu
    iPad App Control135.0
    Topic posted May 12, 2013 by StuBeginner in Wireless Workbench > All Feature Request Topics public
    Title:
    iPad App Control
    Description:
    I would like to see WWB to be able to run on an iPad. As an app. Is that even possible?
    Also, make the App where more than one user could sign in to the same system with a passcode. Reasoning is for a screen in Monitor or wireless world and one that could be mobile with a tech to take with him on another iPad. For troubleshooting or changes during the show to gear not at the main hub.
  • Sam Drazin
    Devices Falling Offline for Macs - Troubleshooting5.0
    Topic posted May 18, 2015 by Sam DrazinExpert in Wireless Workbench > All Questions & Answers Topics public
    Title:
    Devices Falling Offline for Macs - Troubleshooting
    Personal Computer:
    Mac OS X 10.9 and later
    Description:

    There have been several reports of devices falling offline for users using Macs.  There may be several sources to this issue, so I wanted to capture solutions to them here for troubleshooting purposes.  If we find any other issues, I will update this post.

    App Nap

    • Background
      • Introduced in Mac OS X 10.9 Mavericks, this feature suspends background processes for applications that are not being run in the foreground.  
      • This can cause networking/discovery issues between Shure devices and WWB6.
    • How to Resolve
      • In Finder, open the Applications folder, and find "Wireless Workbench 6".
      • Right click, or Command click on "Wireless Workbench 6", and select "Get Info".
      • In the General section, ensure that "Prevent App Nap" is checked (see attached image).

     

    Image:
  • SteveCaldwell
    Spectrum Display Bandwidth...15.0
    Topic posted May 17, 2015 by SteveCaldwellBeginner in Wireless Workbench > All Feature Request Topics public
    Title:
    Spectrum Display Bandwidth...
    Description:

    Even though the Frequency Coordination algorithm used in WWB6 will compute almost any frequency, the graphical spectrum window will only display from 470MHz to around 950MHz. Is it possible to have this spectrum window cover frequencies down to 400MHz or so..? I often use WWB to resolve Two-way radio systems at the same time as I do the radio mics and IEM. the ability to see the markers that are resolved for devices under 470MHz would be great..

  • SteveCaldwell
    Frequency Coordination Marker colours...65.0
    Topic posted May 17, 2015 by SteveCaldwellBeginner in Wireless Workbench > All Feature Request Topics public
    Title:
    Frequency Coordination Marker colours...
    Description:

    In ver 6.11 you have changed the colour of the frequency markers on the coordination spectrum from reflecting the colour assigned to the channel, to reflecting just Red/Green for coordinated/uncoordinated. Is it possible to have these markers optionally reflect the colours assigned to the channels once more..? Or maybe selectable with a checkbox.

    Below is a screen shot of the previous version frequency markers with the channel colouring. attached below is a screenshot of the ver 6.11 before analysis.

    Image:
  • Andy Cooper
    ULXD4Q reports wrong Dante Latency setting after reboot.25.0
    Topic posted July 2, 2014 by Andy CooperNovice in Wireless Workbench > All Bug Topics public
    Title:
    ULXD4Q reports wrong Dante Latency setting after reboot.
    Personal Computer:
    MacBook Pro, OS10.8.5, from mid 2012. wired ethernet with auto DHCP setting.
    Shure Hardware:
    ULXD4Q, firmware 1.5.6.
    Description:

    Dante Controller v3.5.2.1 can be used to change the Dante latency setting of Shure ULXD4Q and other equipment.  I use a lot of Yamaha CL and QL mixers.

    The default latency setting is 1ms, but I want lower latency, so I choose 0.25ms because I have a small network.  So far, so good.

    But after switching off the ULXD4Q and switching on again, it reports the latency to Dante Controller to be 1ms again.  Even if the latency is still actually working at 0.25ms.  Using Dante Controller to reset the latency value puts it right again...until the next reboot.

    So it seems to be a reporting problem of this Dante parameter.  Or am I missing a step to store this parameter before turning off the power?  (other non-Shure Dante devices store the setting automatically).

    Image:
  • dtmmedia
    Support for RF Explorer5.0
    Topic posted June 17, 2014 by dtmmediaNovice, tagged WWB 6.8.1 in Wireless Workbench > All Questions & Answers Topics public
    Title:
    Support for RF Explorer
    Description:

    Does anyone know if there are plans to integrate support for performing live scans using the RF explorer devices?

  • bill.saltzer
    Network Connectivity5.0
    Topic posted May 28, 2014 by bill.saltzerNovice in Wireless Workbench > All Questions & Answers Topics public
    Title:
    Network Connectivity
    Personal Computer:
    Mac OSX, Windows XP, wired and wireless ethernet
    Shure Hardware:
    Axient, UHF-R, PSM-1000
    Description:

    I just had an issue on a show site when attempting to access workbench from an access point that was on a different subnet than the Shure hardware.  The network traffic was being handled by a router and while I could ping the hardware, Workbench could not handle the hop through the router.  I confirmed with Shure Tech Support today that this was a limitation of workbench and UHF-R hardware.  With more complex IT networks being built out on show sites controlling a host of different audio and video equipment, not to mention the onslaught of Dante, I am requesting that Shure add functionality to both workbench and existing hardware that allows workbench to see hardware across different subnets and routers, especially as they begin releasing IOS apps.


    Thanks

  • Evan Landry
    IR Preset Profile25.0
    Topic posted May 8, 2014 by Evan LandryBeginner in Wireless Workbench > All Feature Request Topics public
    Title:
    IR Preset Profile
    Personal Computer:
    MacBook Pro 2.4GHz i5 13", OS 10.8.5 64bit Wired Ethernet
    Shure Hardware:
    16x UHF-R (2x J5, 2x L3, 4x H4 UR4D) on 1.171
    Description:

    I'm reposting this idea on its own separate post because of its importance (it was previously posted by DPlander as an extra thought on another post):

    "Would you allow us to edit multiple units to set them to the same settings (i.e. power lock, button lock, audio levels, IR Presets, Gain, and Sensitivity)."

    So in monitor --> channel strip --> properties --> IR Presets, if you're assigning the same properties such as gain/sensitivity, frequency/power locks, power level and battery type, to multiple channels, currently you have to go into each channel strip, click properties, click IR presets, and click to set each of the aforementioned settings, for each channel.  While doing this in Workbench is significantly easier than doing it from the front panel of the receiver, the workflow could still be greatly improved.  

    I always set my lavs to +15 sens +3 gain, normal power, freq lock, alkaline battery

    If Shure were to develop a feature called Channel Profile or something to that effect, then you could click a profile, and then click any number of tick boxes for example, to assign that profile to any number of channels.  Then it would truly be an "IR Preset," as it is currently misleadingly called.  

  • bflugan
    PSM-1000 Sync Settings25.0
    Topic posted February 7, 2014 by bfluganCompetent in Wireless Workbench > All Feature Request Topics public
    Title:
    PSM-1000 Sync Settings
    Personal Computer:
    Macbook Pro 15in 2009
    Shure Hardware:
    PSM-1000
    Description:

    I'd like to be able to sync squelch, RF Pad and gain mode.  

  • Sam Drazin
    What is wrong with my network configuration?265.0
    Topic posted November 11, 2011 by Sam DrazinExpert, tagged how-to in Wireless Workbench > All Questions & Answers Topics public
    Title:
    What is wrong with my network configuration?
    Description:

    Overview

    This page will outline a set of tests and diagnostic measures you can run to ensure that your network is properly configured.

    The end-goal is to have a properly configured network such that Wireless Workbench discovers all Shure wireless devices online, and that your computer can effectively and reliably communicate with said devices. This page will act as a troubleshooting guide for debugging your network setup.

    Related Links

    Step 1: Selecting a Network Interface

    Wireless Workbench gives you the flexibility to choose which of your computer's network interfaces you would like to connect to. To inspect or modify which network interface Workbench is currently connected to, go to the Preferences menu and select the Network tab.

    To access the Preferences menu, select Tools -> Preferences.

    69c3c894c5_01.png

    From this display, all available network interfaces known to your computer are displayed. To view more details about a particular network interface, select the "Details" button next to one of the network interface options.

    69c3c894c5_02.png

    Once you have selected the network interface you'd like to use to connect to your devices, select "Save" to commit the change.

    Note: If you have configured your computer for both wired and wireless networking, the two IP addresses must be on separate subnets for WWB to work properly. The wired and wireless adapters on the computer should not be "bridged".

    Network Status Indicator

    Wireless Workbench offers a simple "Network Status" label that, at a cursory glance, allows you to assess the basic state of your connection to a network.

    The Network Status indicator is in the bottom right corner of the application, and is visible in all three tabs.

    69c3c894c5_03.png

    The Network Status indicator can read one of the following states:

    • Network Off: there is no network seen by your computer. If you see this, the network interface you've selected is either invalid, or disabled.

    69c3c894c5_04.png

    • Network On: there is a network seen by your computer, and the label will indicate the number of Shure wireless devices seen online.

    69c3c894c5_05.png

    When you first configure your network of wireless gear, this indicator can serve as a first-check of whether or not your computer sees a valid network or not.

    Step 2: Check your Computer/Hardware

    Pinging devices

    When configuring a network, you may find yourself in the scenario where you are not sure you have a valid connection to a particular networked device. Pinging a device is a precise way to discover whether or not a device is available on the network, regardless of other signs that it may or may not be exhibiting.

    First, isolate the device that you want to ping- you will need to get it's current IP address. On the device's front panel, access the Network menu. For Axient, PSM1000 and UHF-R rack devices, this menu can be accessed by selecting Util -> Network.

    69c3c894c5_06.png

    The device's IP adress will be listed next to the label "IP:".

    69c3c894c5_07.png

    If you are working with a UHF-R receiver, be sure to check the IP address on the left front panel, not the right. This is because the IP address for
    devices in DHCP (Automatic) IP mode is only listed on the left panel.

    Note the device's IP address. For this example, let's use the IP address of the AXT400 receiver above: 169.254.132.186.

    Next, open a command prompt on your computer. For Macs, this would be Terminal. For Windows machines, this would be Command Prompt.

    Type the following command:

    ping 169.254.132.186

    Press return. The results of this command will indicate to you whether your device is online or not.

    The ping command will send a small packet of information the IP address that you listed, and wait for a response. If none was heard, you will see messages similar to this:

    pcni4299al:~ drazins$ ping 169.254.0.1
    PING 169.254.132.186 (169.254.0.1): 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    ping: sendto: No route to host

    Notice that there was a "Request timeout". This indicates that your computer waited for a response for a certain amount of time, and none came.

    If your ping was successful, you will see a message similar to this:

    pcni4299al:~ drazins$ ping 169.254.132.186
    PING 169.254.132.186 (169.254.132.186): 56 data bytes
    64 bytes from 169.254.132.186: icmp_seq=0 ttl=30 time=0.863 ms
    64 bytes from 169.254.132.186: icmp_seq=1 ttl=30 time=1.086 ms
    64 bytes from 169.254.132.186: icmp_seq=2 ttl=30 time=1.120 ms
    64 bytes from 169.254.132.186: icmp_seq=3 ttl=30 time=1.050 ms
    64 bytes from 169.254.132.186: icmp_seq=4 ttl=30 time=1.088 ms
    64 bytes from 169.254.132.186: icmp_seq=5 ttl=30 time=1.183 ms

    Notice that each line after the PING command reads something like "64 bytes from 169.254.132.186". This is a sign that the device we pinged is on the network.

    If you're still not discovering devices in your inventory after a successful ping, check your firewall settings. Be sure to allow all processes listed in the "Firewall Setup" section of the Proper Network Setup through any and all security and firewall software your computer is running.

    If you ping a device and it does not appear to be connected on the network, some of your next steps should be:

    • ensure that there is a valid network connection from that device to your network (operational ethernet cables/ports, etc)
    • ensure that your computer is connected to the same network as the device you are trying to ping
    • ensure that the device itself is operational

    Common Mistakes

    Below is a listing of common mistakes made when setting up a network.

    • No two devices (including a computer on the network) can ever share identical IP addresses.
    • Ensure that all devices on your network share the same Subnet Mask. Consult the Automatic vs. Manual IP Mode section of this page for more details on proper IP/Subnet Mask configuration practices.
    • Do not connect a device to the same network twice, ie: via ethernet AND Wi-Fi. Connecting a device to the same network interface with two connections will not yield valid results.
    • Ensure that all devices on your network are set to the proper IP mode.
    • Check your ethernet cables and ethernet ports. Replace old cables and look for data transfer indicator lights on ethernet ports with LEDs to indicate such. If these lights are present but not illuminated, this may indicate a faulty or incomplete connection.
© 2009-2014 Shure Incorporated All rights reserved.
  • Privacy
  • Powered by RightNow