Newbie question ... fallback mounts

View: New views
10 Messages — Rating Filter:   Alert me  

Newbie question ... fallback mounts

by Mike Allen-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Attached is my config file.  The purpose is to interrupt my regular
stream sith a station (stream) ID once per hour (time synchronized
externally).

I use ezstream to play the pre-recorded stream ID.

I never hear the stream ID while listening to the stream.  (There is a
10 second break in the stream once per hour)  What am I doing wrong?  
Thanks in advance.

Mike



<icecast>
    <limits>
        <clients>100</clients>
        <sources>2</sources>
        <threadpool>5</threadpool>
        <queue-size>524288</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>10</source-timeout>
        <!-- If enabled, this will provide a burst of data when a client
             first connects, thereby significantly reducing the startup
             time for listeners that do substantial buffering. However,
             it also significantly increases latency between the source
             client and listening client.  For low-latency setups, you
             might want to disable this. -->
        <burst-on-connect>0</burst-on-connect>
        <!-- same as burst-on-connect, but this allows for being more
             specific on how much to burst. Most people won't need to
             change from the default 64k. Applies to all mountpoints  -->
        <burst-size>65535</burst-size>
    </limits>

    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>password</source-password>
        <!-- Relays log in username 'relay' -->
        <relay-password>password</relay-password>

        <!-- Admin logs in with the username given below -->
        <admin-user>admin</admin-user>
        <admin-password>password</admin-password>
    </authentication>

<!--     set the mountpoint for a shoutcast source to use, the default if not
         specified is /stream but you can change it here if an alternative is
         wanted or an extension is required -->
    <shoutcast-mount>/stream</shoutcast-mount>

    <!-- Uncomment this if you want directory listings -->
    <!--
    <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
    </directory>
     -->

    <!-- This is the hostname other people will use to connect to your server.
    It affects mainly the urls generated by Icecast for playlists and yp
    listings. -->
    <hostname>famrad.familyradio.org</hostname>

    <!-- You may have multiple <listener> elements -->
    <listen-socket>
        <port>8100</port>
        <bind-address>209.10.202.162</bind-address>
        <shoutcast-mount>/stream</shoutcast-mount>
    </listen-socket>
 
    <listen-socket>
        <port>8100</port>
    </listen-socket>

    <listen-socket>
        <port>8150</port>
        <mount>/stationid</mount>
    </listen-socket>

    <!--
    <master-server>209.10.202.162</master-server>
    <master-server-port>8100</master-server-port>
    <master-update-interval>120</master-update-interval>
    <master-password>password</master-password>
    -->
<!-- setting this makes all relays on-demand unless overridden, this is
         useful for master relays which do not have <relay> definitions here.
         The default is 0 -->
    <relays-on-demand>1</relays-on-demand>
-->  
   
    <relay>
        <server>209.10.202.162</server>
        <port>8100</port>
        <mount>/</mount>
        <local-mount></local-mount>
        <on-demand>0</on-demand>

        <relay-shoutcast-metadata>1</relay-shoutcast-metadata>
    </relay>

    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords -->
    <mount>
        <mount-name>/stationid</mount-name>

        <max-listeners>100</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/stream</fallback-mount>
        <fallback-override>1</fallback-override>
    </mount>
    <mount>
        <mount-name>/stream</mount-name>
    </mount>

    <fileserve>1</fileserve>

    <paths>
        <!-- basedir is only used if chroot is enabled -->
        <basedir>/usr/local/share/icecast</basedir>

        <!-- Note that if <chroot> is turned on below, these paths must both
             be relative to the new root, not the original root -->
        <logdir>/usr/local/var/log/icecast</logdir>
        <webroot>/usr/local/share/icecast/web</webroot>
        <adminroot>/usr/local/share/icecast/admin</adminroot>
        <!-- <pidfile>/usr/local/share/icecast/icecast.pid</pidfile> -->

        <!-- Aliases: treat requests for 'source' path as being for 'dest' path
             May be made specific to a port or bound address using the "port"
             and "bind-address" attributes.
          -->
        <!--
        <alias source="/foo" dest="/bar"/>
          -->
       <!-- Aliases: can also be used for simple redirections as well,
             this example will redirect all requests for http://server:port/ to
             the status page
          -->
        <alias source="/stream" dest="/status.xsl"/>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
      <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
      <logsize>10000</logsize> <!-- Max size of a logfile -->
        <!-- If logarchive is enabled (1), then when logsize is reached
             the logfile will be moved to [error|access|playlist].log.DATESTAMP,
             otherwise it will be moved to [error|access|playlist].log.old.
             Default is non-archive mode (i.e. overwrite)
        -->
        <!-- <logarchive>1</logarchive> -->
    </logging>

    <security>
        <chroot>0</chroot>
        <!--
        <changeowner>
            <user>nobody</user>
            <group>nogroup</group>
        </changeowner>
        -->
    </security>
</icecast>

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Wireless Mic System

by jduran-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Audio pro's out there...
Now that my crew has had several events broadcasted, we've found our sound
system to be of a lesser quality than is desired.
 
I'm hoping you could recommend wireless mic systems that would work well for
our use. We're looking for a higher quality hand held and lavaliere sound
system. One that I found while researching is the  Sennheiser EW 122 G2
(http://www.sweetwater.com/store/detail/EW122G2-B/ )  but we need to know if
that would be a worthwhile product for the money. What is a good brand - or
what exactly should I be looking for? Any help and suggestions would be
appreciated if you'd share your experiences with such equipment.

...Your wisdom please!
Thanks,
j

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Wireless Mic System

by Dick Trump :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

jduran wrote:
> Your wisdom please!

Sennheiser is a reputable brand.  The model you cited is in their lowest cost series.  I have sold a number of these systems over the years.  Their first generation (not G2) were problematic in not being very durable.  I don't have as much experience with the G2, but the few we have sold have worked fine for several years.

My first choice for most applications is from Shure.  They also have more models to choose from, starting lower in cost and going even higher than the Sennheiser.

Other reputable brands are:

Lectrosonics (mostly high end)
Audio-Technica (wide range)
Telex (mid-range)
Sony (mid-range)

I would stay away from any brands that do not offer any products that are considerably more expensive than the Sennheiser that you are looking at.  The quality engineered into the best systems does affect the manufacturer's understanding of how to build lesser expensive systems that can perform well.

Among the differences among series within a given brand:

Durability and overall reliability
Quality of sound attributable to the microphone itself
Quality of sound attributable to the transmit/receive electronics
Range of frequencies available
Convenience in selecting compatible channels to be used simultaneously
Features such as eliminating pops or thumps when a transmitter is turned on or off, battery indicators on the receiver, remoteable antennas, etc.
How many similar units can be used simultaneously without interference
Form factor (sometimes different for differing applications)
The list goes on

A local dealer may or may not be able to give you similar pricing to Sweetwater (the price they list is Minimum Advertised Price for that product), but may be able to provide more guidance in choosing the correct product for your application.

You should only purchase from somebody that can help you choose the proper frequencies for your locality.  The manufacturers that I have mentioned all maintain databases that will provide guidance to avoid conflicts with the changing landscape of analog and digital television transmission in your area.  A dealer can and should consult that information before selling you anything.  Not doing so is negligent.  Buying mail order and just accepting what they happen to have in stock could be buying trouble.

--
Regards
Dick Trump

Triad AV Services
1910 Ingersoll Ave.
Des Moines, IA 50309
515-243-2125
515-243-2055 (fax)
http://www.triadav.com
dtrump1@...

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Wireless Mic System

by xiphmont :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have used several Shure systems, a few Sennheisers and a few
AudioTechnica systems.

Do not expect any of these systems, even the highest end, to be
anywhere as reliable as a wired mic.  As the years went on, I
generally moved higher and higher end to try to weed out problems I
had with units that were due to design or unit flaws.  I've been out
of the biz for a few years now (since my kids arrived), but I nearly
always tried to use the best I/we could afford.  At that time, the
Shure UCs were my most common choice.  When I couldn't afford to roll
out UCs, ULX systems were a solid, cheaper alternative.  I don't
remember much about the Sennheisers beyond them performing as expected
and (as usual) not having compatible connectors ;-)

I owned several high end Audio Technica models and found every unit
unreliable.  They were digitally controlled transmitters and all had
an odd tendency to lose their settings in the middle of performances.
Dropouts are one thing-- having a microphone suddenly decide to boost
its output 60dB in the middle of a quiet choral number for no reason
is absolutely unacceptable.  They all went in for service, all came
back with clean bills of health, all repeated the problems and I
dumped the whole lot.

If at all possible, buy units that run on AAs, not 9v.  Rechargables,
in general, work *very* poorly in wireless mics.  Batteries will cost
you a surprising amount of money, and 9v make that 4x worse.

If at possible buy units that you make the settings using physical
switches, preferrably requiring a screwdriver.  All-analog packs
survive alot longer than digital packs. All the fancy digital
pushbutton systems are begging to fail, and actors/performers can't
resist playing with them.  Covers that snap shut over the pushbuttons;
the overs are flimsy and the puttins get mashed right through the
flimy shield.  If sweat gets in, the microprocessor is done.

Prefer units that have cheply replacable connectors, and hoard spares.
 We had one actor who constantly broke connectors because they'd pop
apart before he'd run on stage and he couldn't get them back together
correctly in haste and on three consecutive nights, he destroyed three
$1000 sender units.  After that show, I ripped all the
'high-durability unscoopable' connectors out of the packs and
hand-soldered in 1/8" stereo connectors.  They popped apart somewhat
more easily, but they never broke.  I think Sennheiser might have the
advantage on this front.

Whatever mic you get, dropouts will be a problem.  The best units are
better in this regard, but unless you plan to have an antenna array
front of house less than 15' away, expect them to just randomly lose
occasionally.   The stated ranges are fantasy.

Sweat kills microphones.  A drop of sweat in the capsule itself, and
you're out a $300 Countryman.  But most people think sweat doesn't get
inside the packs.  One show of having a 'beltpack' stuffed into a bra
because 'it's the only place it will fit in the costume' means you
will have a dead transmitter by the end of the run.  Putting the
sender in a condom will help, but sweat still tends to get in
eventually.  Yeah, the packs look ugly outside, but they're called
beltpacks for a reason.  That said--- our Shure UCs and ULX packs went
through multiple successful soakings in rubbing alchohol after
sweat-induced failures, dried out fine, and kept performing.

That's my 0.02.

Monty
_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Newbie question ... fallback mounts

by Mike Allen-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Mike Allen wrote:
Attached is my config file.  The purpose is to interrupt my regular stream sith a station (stream) ID once per hour (time synchronized externally).

I use ezstream to play the pre-recorded stream ID.

I never hear the stream ID while listening to the stream.  (There is a 10 second break in the stream once per hour)  What am I doing wrong?  Thanks in advance.

Mike



_______________________________________________ Icecast mailing list Icecast@... http://lists.xiph.org/mailman/listinfo/icecast
What I am trying to accomplish with this configuration is:

1.  Listen to the stream on mountpoint /stream when there is no 'stream ID' playing.
2.  All listeners to stream hear the 'stream ID' when played without hearing the stream.
3.  Resume hearing the stream as soon as the 'stream ID' is finished.

What am I doing wrong?


Thanks in advance.

Mike

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Wireless Mic System

by xiphmont :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

(BTW, remember the dialogue from the Blues Brothers:

"You traded the Bluesmobile for this piece of shit?"
"No, for a microphone."
".... okay, I can see that."

I didn't realize until I got into professional sound that the joke
there is that it's not a joke.  Doubly true for wireless.

Monty
_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Wireless Mic System

by Dick Trump :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

xiphmont@... wrote:
> Do not expect any of these systems, even the highest end, to be
> anywhere as reliable as a wired mic.

Amen to that!  The very best of the best wireless microphones only attempt to be as good as wired.  It will never achieve that goal
 
All other advice should be tempered with that knowledge.

> If at all possible, buy units that run on AAs, not 9v.  Rechargables,
> in general, work *very* poorly in wireless mics.  Batteries will cost
> you a surprising amount of money, and 9v make that 4x worse.

Good advice again, although there have recently been a few wireless microphones designed specifically to handle rechargables.  If they have not, the batteries will have a very short usable life and may cause problems even with brand new fully charged.  Unless the manufacturer recommends rechargables, don't even consider it.

> If at possible buy units that you make the settings using physical
> switches, preferrably requiring a screwdriver.  All-analog packs
> survive alot longer than digital packs.

Not bad advice but only the very cheapest and a few of the most expensive fit that category anymore.

> Whatever mic you get, dropouts will be a problem.  The best units are
> better in this regard, but unless you plan to have an antenna array
> front of house less than 15' away, expect them to just randomly lose
> occasionally.   The stated ranges are fantasy.

Here's where you need somebody with real RF experience and technical knowledge.  100% may not be achievable, but a well engineered installation can come close.  I can say that at my own church, with 3 Shure ULX-P, we have NEVER had a drop out that I have witnessed in the 7 years they have been installed.  About 75' from chancel to antennas.  I'm there every Sunday.

> Sweat kills microphones.  

Only one manufacturer makes a pack that is "water resistant" - Lectrosonics.  And even then, I have a saying - "water always wins", and sweat is worse than water - much worse.

--
Regards
Dick Trump

Triad AV Services
1910 Ingersoll Ave.
Des Moines, IA 50309
515-243-2125
515-243-2055 (fax)
http://www.triadav.com
dtrump1@...

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Newbie question ... fallback mounts

by Thomas B. Ruecker-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Mike Allen schrieb:
> Attached is my config file.  The purpose is to interrupt my regular
> stream sith a station (stream) ID once per hour (time synchronized
> externally).
>
> I use ezstream to play the pre-recorded stream ID.
>
> I never hear the stream ID while listening to the stream.  (There is a
> 10 second break in the stream once per hour)  What am I doing wrong?  
> Thanks in advance.
You didn't define a local-mount in the relay?

As pointed out in the other thread already - inserting anything that way
is error prone. Some listener software will choke.
_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Re: Newbie question ... fallback mounts

by abitar.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hey,

  Are you  stopping the main stream, disconnecting it?

 You have to make sure you use the same codex, bite rate and other
parameter on you station ID.

if you can get ezstream to change source, instead of having the server
do it for you Station ID it would be a beter solution to the stream
matching aspect of it.

But we have problems with DJ switch overs sometimes, One will drop the
stream then the other will start it. Some clients still get messed up
in the transition and have to restart the stream on there end to fix
it.  This is setting the sources up exactly the same.  Only difference
that could not be truly check was if they were using the same codex to
encode it.  Since this is common problem across all streaming servers,
and clients , and most listeners understand this and are told to
restart the client and it resolves the issue.  It helps to be in a 3d
virtual world to remind them to via a text channel. :)

David

On Thu, Mar 5, 2009 at 2:26 AM, Thomas B. Ruecker
<dm8tbr@...> wrote:

> Mike Allen schrieb:
>> Attached is my config file.  The purpose is to interrupt my regular
>> stream sith a station (stream) ID once per hour (time synchronized
>> externally).
>>
>> I use ezstream to play the pre-recorded stream ID.
>>
>> I never hear the stream ID while listening to the stream.  (There is a
>> 10 second break in the stream once per hour)  What am I doing wrong?
>> Thanks in advance.
> You didn't define a local-mount in the relay?
>
> As pointed out in the other thread already - inserting anything that way
> is error prone. Some listener software will choke.
> _______________________________________________
> Icecast mailing list
> Icecast@...
> http://lists.xiph.org/mailman/listinfo/icecast
>
_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

Parent Message unknown Re: Newbie question ... fallback mounts

by SomaRadio :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

David,

You email is confusing. The problem is that we've done everything
we can do get listed on Icecast Directory but we never get
listed. help?

This is our config file (below).  The IceCast documentation only said to add the <directory> section which adds the yp url to the icecast server.  So far as I'm aware from the documentation, anything after that should come from the encoder. (http://www.icecast.org/docs/icecast-2.3.2/icecast2_yp.html)

<!-- This config file contains a minimal set of configurable parameters,
    and mostly just contains the things you need to change.  We created
    this for those who got scared away from the rather large and heavily
    commented icecast.xml.dist file. -->
<icecast>
   <limits>
    <clients>100</clients>
       <sources>6</sources>
   </limits>
   <authentication>
   </authentication>

   <hostname>localhost</hostname>
   <listen-socket>
       <port>8000</port>
   </listen-socket>
   <fileserve>1</fileserve>
   <paths>
       <logdir>./logs</logdir>
       <webroot>./web</webroot>
       <adminroot>./admin</adminroot>
       <alias source="/" dest="/status.xsl"/>
   </paths>
   <logging>
       <accesslog>access.log</accesslog>
       <errorlog>error.log</errorlog>
       <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
   </logging>
   <directory>
       <yp-url-timeout>15</yp-url-timeout>
       <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
   </directory>
</icecast>


>>> David Saunders <abitar.com@...> 03/06/09 1:09 PM >>>
hey,

  Are you  stopping the main stream, disconnecting it?

 You have to make sure you use the same codex, bite rate and other
parameter on you station ID.

if you can get ezstream to change source, instead of having the server
do it for you Station ID it would be a beter solution to the stream
matching aspect of it.

But we have problems with DJ switch overs sometimes, One will drop the
stream then the other will start it. Some clients still get messed up
in the transition and have to restart the stream on there end to fix
it.  This is setting the sources up exactly the same.  Only difference
that could not be truly check was if they were using the same codex to
encode it.  Since this is common problem across all streaming servers,
and clients , and most listeners understand this and are told to
restart the client and it resolves the issue.  It helps to be in a 3d
virtual world to remind them to via a text channel. :)

David

On Thu, Mar 5, 2009 at 2:26 AM, Thomas B. Ruecker
<dm8tbr@...> wrote:

> Mike Allen schrieb:
>> Attached is my config file.  The purpose is to interrupt my regular
>> stream sith a station (stream) ID once per hour (time synchronized
>> externally).
>>
>> I use ezstream to play the pre-recorded stream ID.
>>
>> I never hear the stream ID while listening to the stream.  (There is a
>> 10 second break in the stream once per hour)  What am I doing wrong?
>> Thanks in advance.
> You didn't define a local-mount in the relay?
>
> As pointed out in the other thread already - inserting anything that way
> is error prone. Some listener software will choke.
> _______________________________________________
> Icecast mailing list
> Icecast@...
> http://lists.xiph.org/mailman/listinfo/icecast
>
_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast

_______________________________________________
Icecast mailing list
Icecast@...
http://lists.xiph.org/mailman/listinfo/icecast