similar to: Source client with HTTP PUT

Good afternoon, On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > On Fri, 2019-05-03 at 13:19 +0000, Jürgen Bund wrote: > > I’m writting a source client in c#, in which I’m sending chunks of a > > mp3 file with http Put to IceCast. > > My problem is, that it is not a continues stream. Each http PUT > > request is an extra track. > > How can I generate an

Good morning, On Mon, 2019-05-06 at 08:44 +0000, Jürgen Bund wrote: > Hello again, > thanks for your response. > > I have still some questions: > I want to stream a 24/7 radiochannel with mp3s. So I can't send all mp3s with one http PUT request. > So is there a possibility for that with http PUT? > If yes, how can I send the next mp3, so that icecast is playing it

Good afternoon, On Sat, 2019-05-04 at 10:19 -0400, Fred Gleason wrote: > On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > > > Don't use PUT at all. Instead, open a TCP socket connection to the > port > > that the server is running on, write all of your headers to that > > (terminating each one with a CR/LF), send a naked CR/LF to tell > Icecast >

Hello again, for now I figuered out to send a mp3 stream to IceCast with TCP Socket communication. Now I'm challenged with the correct timing for the data packets. Are there any API calls for getting the state of IceCast's buffer? I'm programming now on a scheduler for sending the mp3 frames, depending on the metada of each frame. I hope, that this is precisly enough. Can you tell

Hello again, thanks for your response. I have still some questions: I want to stream a 24/7 radiochannel with mp3s. So I can't send all mp3s with one http PUT request. So is there a possibility for that with http PUT? If yes, how can I send the next mp3, so that icecast is playing it fluently (continuesly)? If not, is there a documentation for a TCP Socket Communication? Libshout is a c++

On Sat, 2019-05-04 at 17:05 +0000, Philipp Schafft wrote: > Which exact open tickets do you refer to with "certain bits"? Would > be > happy to look into them with you. Also feel free to offer some > sponsoring to implement them. AAC+ support for starters. It was lack of this specific feature that compelled me to roll my own [Ice|Shout]Cast client support. >

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

can't find help on this anywhere! using ice get error message from ice: [ ices]$ bin/ices -F ~uo/dilated.txt -P ***** Logfile opened Mounted on http://127.0.0.1:8000/ices Playing /export/mp3/My Music/Rawkus/Lyricist Lounge 2/Dilated Peoples - Right and Exact.mp3 Error during send: Libshout reported send error, disconnecting: Libshout socket error. Mounted on http://127.0.0.1:8000/ices Ices

I'm looking for specifications of the ICE/1.0 protocol. Not everything could be derived from the source code of the icecast 2.0 server. Which headers (ice-tags) have to be sent to the server, which are optional? What are possible responses of the server? Does the client have to wait for a response? Does the server have to send a response? <p>Please help to make the ICE/1.0 clients

Hi -- I had a pretty quick R question since unfortunately I have not been able to find an answer on Google. It shouldn't take much more than a minute to answer. I'm trying to add up the major gleason grade and minor gleason grade for an analysis of patients with prostate cancer. One column has values under "Major Gleason" and another column has values under "Minor

all.. any list. can play mp3 with other apps. more info: OS :rh7.2 on intel i686 Wade Carroll wrote: >Does this only occur with that one mp3 file or all? > >-----Original Message----- >From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org]On Behalf Of >MR I >Sent: Monday, May 13, 2002 8:02 PM >To: icecast@xiph.org >Subject: [icecast] error with libshout > >

Hello. I'm one of the maintainer of ices packages found at http://plf.zarb.org. I'm currently trying to rebuild the whole ice/icecast/libshout trilogy. However, i'm running into some troubles.

So I'm sure many of you are using or have tried to use TrixBox. Thus far, I'm in love with it. I haven't had a single snag. Then again, I don't need to get into anything overly nitty gritty with my Asterisk box. What are your views? -- Want a free copy of "TrixBox Made Easy"? Read the contest rules

thanks... Icecast doesn't log this problem. the icecast.log file (icecast.log) hasn't been updated for some time only the stats.* and useage.log have changed <p>Wade Carroll wrote: >I don't know what's happening there. Thought maybe it was a mp3 file (I've >had troubles with certain mp3s). > >Check your messages log in icecast (you can change the message

To all CVS users of ices 0.x: I've just merged the ices-libshout_2 branch onto HEAD. Anyone using that branch should switch back to HEAD to continue to get the latest updates. This also means you now need the latest version of libshout2 from CVS in order to build ices from CVS. libshout2: :pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot libshout ices:

Hey folks, I've been getting requests from the users that they want the OCFS2 filesystems aligned to 64k boundaries, however, when I began the project, the dummy of me, created the OCFS2 filesystem on top of the whole disk device (no partition) for example, one of the SAN devices would show up as /dev/dm-10, I created the filesystem using the following command: mkfs.ocfs2 -L SOMELABEL

so no one else has an idea???? K Wade Carroll wrote: >Good luck with that. > >Actually I didn't mean log. I meant the icecast console itself. If it's in >the right console mode (2?) it will display everything that's happening and >any error messages. Seems like the log only shows uptime info by default. > >Any ol' how, i think i've exhausted my

On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > Don't use PUT at all. Instead, open a TCP socket connection to the port > that the server is running on, write all of your headers to that > (terminating each one with a CR/LF), send a naked CR/LF to tell Icecast > that your done sending headers and then start writing content. On May 4, 2019, at 09:15, Philipp Schafft

Hello, I use rpart to predict survival time and have a problem in interpreting the output of ?estimated rate?. Here is an example of what I do: > stagec <- > read.table("http://www.stanford.edu/class/stats202/DATA/stagec.data", > col.names=c("pgtime", "pgstat", "age","eet", "g2", "grade", "gleason", >

> libshout: :pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot > ices: :pserver:anoncvs@cvs.xiph.org:/cvs/ice > > Check out the ices-libshout_2 branch of ices. Libshout compiles fine, but ices wont configure correctly. It wouldn't find shout_new in libshout, lame_encode_flush_nogap in mp3lame nor ov_open in libvorbisfile.. (nor is libtool found, but I copied it from libshout.)