Comments

  • Sam Drazin

    Hi Franco,

    Sorry you were seeing issues with WWB crashing.  You are correct, though, in that WWB 6.11.3 no longer supports Mac OS X 10.7.  In order to stay up to date with the latest operating systems in terms of security, functionality and stability, we have adopted a practice of supporting only the latest several versions of OSes from Mac and Windows.  For a full list of supported OSes per release, see this Downloads page on the forum, as well as a list of previous WWB versions and their supported OSes.

    You mention a good point that the update process could check for potential incompatibilities; I will inform the team and see if we can add this as an improvement in a future release.

    Thanks for your comment,

    -Sam

  • Sam Drazin

    Hi austriaaudio,

    The behavior you are seeing is the result of a known issue.  The issue results when you import an Equipment Profile, and I'll explain in greater detail:

    • When an Equipment Profile is imported, the file location of the imported file becomes the new location where WWB expects to see your custom profile database ("CustomSeries.cds").  
    • If it doesn't see that file there at the new location, it creates one.
    • Further to the issue, this newly created CustomSeries.cds will not have any existing custom profiles you may have created in the past.  The issue you may see after this new file is created is that your existing Custom Profiles are not available in the "Add Devices" dialog, or visible to add as a part of Frequency Coordination.

    First, we know this is an issue, and are actively working to resolve it in an upcoming release.

    Second, as a work-around, here is what you can do to ensure that your existing custom Equipment Profiles are available for use:

    • Locate the path of your original CustomSeries.cds file.  
      • By default, this is typically Username/Documents/Shure/Equipment Profiles.
    • Find any custom Equipment Profile (these export as ".eqp" files), and place them in the same directory as your original CustomSeries.cds file.
    • Launch WWB, and open Tools > Equipment Profiles dialog.  
    • In the Equipment Profiles dialog, select "Import" and then select the .eqp file you placed in the same directory as your original CustomSeries.cds file.

    After you import that .eqp file, WWB will have located and re-associated itself with the original CustomSeries.cds file, and all of your existing custom Equipment Profiles should be available again.

    Sorry for any inconvenience this bug may have caused you, and I hope this explanation helps in the short term.

    Thanks,

    -Sam

     

  • Sam Drazin

    Hi Guy,

    The TV channel shown on channel strips is calculated based on the frequency of the channel, and where that frequency falls on the TV Channel Map selected within your instance of WWB.  This TV Map is selected in the TV Channels dialog, in the Frequency Coordination tab, and is set by selecting the country of wireless system operation.  By default, the selected country is United States.  My guess is that you have this country field set to the United States, as 611.775 is in the US TV channel 37.

    To fix this, you can:

    1. Go to the Frequency Coordination tab, and select the gear next to the TV Channels section.  Within that dialog, select your country from the "Country" drop down at the top of the dialog - (in your case, United Kingdom).
    2. For the future, you can set your default country to be your primary country of operation in Preferences > Coordination, by selecting your country in the "Default Country"  drop down.

    Hope these tips help. Let me know if you have any other questions!

    -Sam

  • Sam Drazin

    Hi Mike.  

    Thanks for this feedback.  I've added this as an improvement for us to work on.  Hope to have good news for you soon!

    -Sam

  • Sam Drazin

    Hi,

    Typically, when you use the "More Frequencies" Compatibility Level (selectable in the RF Coordination Results dialog), the 2T7O, 2T9O, and 3T3O IMD spacing considerations are zeroed out.  You can confirm this by selecting Tools > Equipment Profiles, and selecting Manufacture/Model/Band of the device in question, and viewing the coordination data used on the "Filtering and Intermods" tab.

    If you want, you can also modify these profiles, but they must be saved as new equipment profiles (with altered manufacturer or model names) so they are differentiate-able from the stock profiles provided by Shure.

    I hope this helps.  Let me know if you have further questions!

    -Sam

  • Sam Drazin

    Thank you for posting this great tutorial, Diogo!

  • Sam Drazin

    Hi, I have a few questions, and some suggestions you might try to remedy the issue.

    • How are you networking all of your UHF-R receivers together?
      • I would recommend using a switch or router, connecting each UHF-R (as well as your computer) with a direct ethernet connection to it.  This is both a sound networking topology, and will help debug any further issues (like faulty cables, etc).
    • What firmware version is each of your UHF-R receivers running?
      • You can view this on the boot-up screen of the receiver
      • If any of the devices are running versions earlier than 1.166, they are incompatible with WWB6, and need to be updated to be discoverable by the application.  Also, the latest UHF-R firmware (1.171) addresses some networking stability issues for UHF-R when in use with WWB6, so I would recommend updating to that version.
      • The Shure Update Utility is a free utility that updates Shure firmware and software.  Here's a tutorial video describing how to get up and running with it.
    • What firewall settings/applications do you have enabled on your computer?
      • Which OS are you running?  
      • Do you have any third-party security software?
      • In general, we recommend disabling firewall software, or being sure that the executable applications within WWB6 are explicitly allowed network access. 

    I hope this info helps.  Let us know if we can do anything else to get to the bottom of this issue.

    Thanks,

    -Sam

  • Sam Drazin

    Mike,

    For both WWB6 and the Shure Update Utility, there are minimum version requirements for the self-check software update workflow to work.  Please confirm that your software meets these versions or later:

    1. Shure Update Utility 2.0.2
    2. WWB 6.9

    Then, follow these steps for either WWB6 or Shure Update Utility:

    1. Ensure you have a valid internet connection
    2. Launch the application
    3. From the menu, select Help > Check for <application name> Updates
    4. The Shure Update Utility will show you if any software updates were found for that application.
    5. If updates are found, you can select to "Download" them right from that dialog.  All downloads are placed at the following path
      1. Documents/Shure/Firmware
        
    6. The files placed at that path have the .pack extension, which is how Shure packages software/firmware assets.  These can be unzipped to access the installer file if necessary.

    Let me know how this goes... 

    -Sam

  • Sam Drazin

    Hi Mike,

    I'm sorry to hear that you're still having issues with the update process for WWB6.  Since this original post (Jan. 2012), we have tried to make the update process significantly more streamlined.

    I am not sure if you are familiar with the Shure Update Utility, but this relatively new application was built specifically to facilitate quick, secure, and stable software and firmware updates for all things Shure.  

    When launched explicitly, the Shure Update Utility is a firmware update application, which can check for and send updates to all Shure networked devices (tutorial video here).  With WWB6 6.9 and later, the Shure Update Utility can check for new WWB6 versions, and can launch the installer if desired (no more digging around your computer for the downloaded installer file).  To do this, open WWB6 (6.9 or later) and select Help > Check for Wireless Workbench 6 Updates from the menu.  

    Please let us know if you continue to have any other issues.  I hope that you have better luck updating your Shure software in the future.  

    Thanks,

    -Sam

  • Sam Drazin

    Hi Danny,

    Thanks for posting your question.  If I understand correctly, the ultimate goal is: to have WWB6 avoid the frequencies that are stored within an existing show file.  If that is case, I understand why you'd want to "import that Show File's frequencies as an Exclusions file (.fxl)", but there is an easier method that will yield the same result.

    I would recommend exporting the Inventory of the existing show file and importing it into the new show file.  This would load the channels from the inventory of the existing show file (complete with specific models, channel names, frequencies, etc) into the new one.  After that, you would want to ensure that WWB6 locks those imported frequencies to their current values, ensuring that all other coordinated frequencies avoid them (as they would with exclusions).

    The steps to do this would be:

    1. Open existing show file
    2. Ensure that the inventory contains only the channels you want to "export" as exclusions
    3. Select File > Export > Inventory... and save the file
    4. Open/create the new show file
    5. Select File > Import > Inventory... and select the file you saved.
    6. Once opened, the inventory from the old show file will be imported.
    7. Go to the Frequency Coordination tab, and select "Manage Channels"
    8. Uncheck all channels that were imported from the existing show file (to lock them to their current frequency)
    9. Proceed with adding/coordinating frequencies

    Functionally, WWB6 avoids unchecked channels in the inventory in the same manner that it would with exclusions.  The only difference is that exclusions are not visible in the Inventory.

    This workaround may not be exactly what you were looking for, but if I interpreted your need accurately, I think this should functionally fit the bill. Let me know if you have any other questions, and/or if things work out.

    Thanks,

    -Sam

© 2009-2014 Shure Incorporated All rights reserved.
  • Privacy
  • Powered by RightNow