Displaying 20 results from an estimated 10000 matches similar to: "icecast2/libshout2 and MP3 metadata"
2004 Aug 06
0
dumpfile with libshout2/icecast2
On Wednesday 10 March 2004 06:56, Andrew Taylor wrote:
> Heyas,
>
> I'm trying to get setDumpfile working with the java libshout bindings.
> I am calling shout_set_dumpfile(shout,char*) after specifying the port,
> host, mount and password, yet, the dumpfile is not created on the server
> side. To be more specific, I'm trying this:
>
> bin/streamAdmin -d
2004 Aug 06
2
dumpfile with libshout2/icecast2
Heyas,
I'm trying to get setDumpfile working with the java libshout bindings.
I am calling shout_set_dumpfile(shout,char*) after specifying the port,
host, mount and password, yet, the dumpfile is not created on the server
side. To be more specific, I'm trying this:
bin/streamAdmin -d /tmp/test.mp3 -h streams.benow.ca -p 80 -P pass -m
/benow
which sets the dumpfile to be /tmp/test.mp3
2004 Aug 06
1
dumpfile with libshout2/icecast2
Thanks for the reply, Mike.
Is there currently any way to accomplish the same thing (ie, recording
of a dumpfile for a mount for a given duration) with icecast2 as it
stands? Perhaps through the admin interface, or via a config change and
reload? I'm surprised this feature has not been more requested, it
would certainly be welcome here.
If not, no biggie, I could just use a local
2004 Aug 06
0
libshout1-based mp3 streaming to icecast2
The short answer, as Geoff says, is to use ices 0.x from CVS with libshout 2.
The good news is CVS ices 0 has a number of bug fixes.
libshout2 may be found at anoncvs@cvs.xiph.org:/usr/local/cvsroot libshout
ices is at anoncvs@cvs.xiph.org:/cvs/ice ices
Note the different paths above!
Now, a little more detail:
On Sunday, 16 March 2003 at 02:41, jeremy@squat.net wrote:
> ices0 -b 24 -h
2004 Aug 06
3
libshout1-based mp3 streaming to icecast2
According to what I've read on this mailing list, it should be possible
to stream MP3 data to icecast2 using ices-0.2.3, which I assume also
should be the case for any other streaming client based on libshout1. So I
decided to test this out to see if we really could dispense with
icecast1 altogether on the server I help administer. My results were not
promising, to say the least.
I wiped out
2004 Aug 06
1
icecast2, libshout2, Shout.pm FreeBSD
On Mon, 26 May 2003, Michael Smith wrote:
> You'll have to port Shout.pm to use libshout2 - the API has changed (not in
> terribly major ways for the most part, so it should be a simple and
> straightforward port).
Didn't someone do this and post it to icecast-dev? Or was that something
else? I'm not a perl programmer. I'd just hate to see someone duplicate
work
2004 Aug 06
2
icecast2, libshout2, Shout.pm FreeBSD
Hi all,
Has anyone successfully managed to get icecast2 libshout2
and Shout.pm built under freebsd?
o far I've been able to build all of them except for
Shout.pm. I would like to migrate from icecast1 however
I can't do so until I can get everything built.
Here is the error I'm having trying to build Shout.pm
from the FreeBSD ports tree.
# make
cc -c -I/usr/local/include -O -pipe
2004 Aug 06
0
libshout1-based mp3 streaming to icecast2
just a side note:
as of 3/12/2003 I could not get ices0x from cvs to compile without errors.
the nightly snapsot compiled fine
<p><p><p><p>----- Original Message -----
From: Brendan Cully
To: icecast@xiph.org
Sent: Sat, 15 Mar 2003 21:15:01 -0500
Subject: Re: [icecast] libshout1-based mp3 streaming to icecast2
Sorry to follow up on my own post, but you may find it more
2004 Aug 06
0
Adventures with icecast2
At 07:38 PM 6/6/01 +1000, you wrote:
>On Wed, 6 Jun 2001, Michael Smith wrote:
>
>> Try linking it with an explicit library (like
>> gcc -o example example.c ../src/libshout.a (plus other arguments that it
>> needs)
>
>I *really* don't know about this stuff.
>
>I don't have a libshout.a. I have libshout.la which it didn't
>recognise, and
2004 Aug 06
0
Icecast 2 questions.
On Fri, 16 Nov 2001, Tom Murphy wrote:
> I just built icecast 2 from cvs. I tried to compile ices (also from
> cvs) and got:
>
> stream.c: In function `ices_instance_stream':
> stream.c:164: warning: passing arg 1 of `shout_strerror' makes pointer
> from integer without a cast
> stream.c:164: too few arguments to function `shout_strerror'
> stream.c:198:
2005 Dec 10
2
Cannot build ices0/libshout2 on Mac OSX 10.4.2
Hi -
I'm rebuilding my OSX system and I can't get ices0 to build - or to be
more exact, can't get libshout2 to build.
I started by using DarwinPorts, and icecast2 & libogg & libvorbis
seemed to build OK. The install of ices0 then gave up at the libshout2
config stage with output like this:
[...]
checking for libvorbis... ok
checking for struct ovectl_ratemanage_arg... no
2004 Aug 06
1
compilling error ices-0.2.3.tar.gz
thnks for the clarfication.
I downloaded libshout2 and ices-0.2 from cvs. I compiled libshout with out a problem but when i try
and compile ices I get the following error:
<p><p>checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
checking shout/shout.h usability... yes
checking
2004 Aug 06
1
Icecast2 ?
On Mon, 15 Oct 2001, Jack Moffitt wrote:
> It's in xiph.org cvs. All the information is at
> http://www.xiph.org/cvs.html
>
> you want the 'icecast' module. Instructions for building are in
> icecast/HACKING
FYI, libshout2 and ices2 are also in the xiph CVS, under libshout and ices,
respectively. All of these also have dependancies. These are:
icecast: avl, httpp,
2004 Aug 06
1
libshout2 namespace
At 05:30 PM 5/7/01 -0700, you wrote:
>any suggestions? I supposed to could make all calls shout2_*
>
>Michael, any suggestions here? How is this typically handled in other
>libs? Or do other libs never need to use both?
>
>I'll have to think about this a bit and see if I can't figure out a way
>to add mp3 into libshout2.
>
The easy solution is to just ensure the
2004 Aug 06
2
libshout2 compiling problems under FreeBSD?
----- Original Message -----
From: "Michael Smith" <msmith@xiph.org>
To: <icecast-dev@xiph.org>
Sent: Wednesday, June 04, 2003 3:47 PM
Subject: Re: [icecast-dev] libshout2 compiling problems under FreeBSD?
<p>> Whilst there may well be problems, there are no _known_ problems, and we
> certainly won't be able to fix them unless you actually tell us what the
2004 Aug 06
0
mp3 support and compatibility
On Wed, 21 May 2003, Remco B. Brink wrote:
> <quote who="Adon Irani">
>
> > i've been hearing of more and more people in my community who are
> > having troubles connecting to our netw0rk . in most cases , wind0ws
> > media player or realone is stealing the associations ;
>
> What associations?
Probably .M3U
> Only the full version of Winamp
2005 Dec 10
0
Cannot build ices0/libshout2 on Mac OSX 10.4.2
Hi,
On Sat, 10 Dec 2005 16:14:04 -0800 Dan Stowell
<danstowell@gmail.com> wrote:
> Hi -
>
> I'm rebuilding my OSX system and I can't get ices0
> to build - or to be more exact, can't get libshout2
> to build.
>
> I started by using DarwinPorts, and icecast2 &
> libogg & libvorbis seemed to build OK. The install
> of ices0 then gave up at the
2004 Aug 06
3
Adventures with icecast2
On Wed, 6 Jun 2001, Michael Smith wrote:
> Try linking it with an explicit library (like
> gcc -o example example.c ../src/libshout.a (plus other arguments that it
> needs)
I *really* don't know about this stuff.
I don't have a libshout.a. I have libshout.la which it didn't
recognise, and shout.lo which resulted in a host of undefined references.
So I guess I don't
2010 May 17
2
libshout2 with aac
On 17 May 2010, at 22:42, Romain Beauxis <toots at rastageeks.org> wrote:
> Le lundi 17 mai 2010 23:36:53, Jamie Bullock a ?crit :
>> On 17 May 2010, at 21:07, Geoff Shang wrote:
>>> On Mon, 17 May 2010, Jamie Bullock wrote:
>>>
>>>
>>>> I'm write an icecast source client and I'd like to support
>>>> streaming of
2004 Aug 06
0
cvs changes
On Sat, 20 Oct 2001, Jack Moffitt wrote:
> I changed the libshout2 and thread module apis. This broke everything.
> If you are tracking CVS, make sure to update your libshout2 and the
> thread module. Ices2 and Icecast2 already uses these new changes, which
> were implemented as part of general cleanup and getting Solaris builds
> out of clean tarballs.
>
> If anyone is