ProSoundWeb Community

Please login or register.

Login with username, password and session length
Advanced search  

Pages: [1]   Go Down

Author Topic: Sennheiser ew300 on Range A (516-558 MHz) - poor RF performance  (Read 1748 times)

Guy Tittley

  • Newbie
  • *
  • Offline Offline
  • Posts: 3
Sennheiser ew300 on Range A (516-558 MHz) - poor RF performance
« on: November 19, 2014, 09:30:36 AM »

Hi All

I have recently gone from older 800MHz Sennheiser G2 radio mics to new eW300 on Range A (516 - 558 MHz) and I'm getting poor RF performance. There are 6 mics, line-of-sight to stage 20m away and I'm getting drop outs regularly. Never had a problem with the older mics on 800MHz range. New site licence is range A.

Anyone come across anything similar?
Logged

Ray Aberle

  • Classic LAB
  • Hero Member
  • *
  • Offline Offline
  • Posts: 3455
  • Located in Vancouver, WA (and serves OR-WA-ID-BC)
    • Kelcema Audio
Re: Sennheiser ew300 on Range A (516-558 MHz) - poor RF performance
« Reply #1 on: November 19, 2014, 01:23:43 PM »

Hi All

I have recently gone from older 800MHz Sennheiser G2 radio mics to new eW300 on Range A (516 - 558 MHz) and I'm getting poor RF performance. There are 6 mics, line-of-sight to stage 20m away and I'm getting drop outs regularly. Never had a problem with the older mics on 800MHz range. New site licence is range A.

Anyone come across anything similar?

Hi Bigguy, welcome to the forums! Before anyone is permitted to assist you, though, you need to update your Display Name to be your real, full name. If you'd jump into your profile and do that, that would be awesome!

(And if you do it before a moderator sees this, your post won't get locked...)

Thanks, and welcome again!

-Ray
Logged
Kelcema Audio
Regional - Serving Pacific Northwest (OR, WA, ID, BC)

ProSoundWeb Community

Re: Sennheiser ew300 on Range A (516-558 MHz) - poor RF performance
« Reply #1 on: November 19, 2014, 01:23:43 PM »


Pages: [1]   Go Up
 



Site Hosted By Ashdown Technologies, Inc.

Page created in 0.032 seconds with 24 queries.