similar to: Newbie question about soundcards

> Nope, llvm's .s output is only compatible with GAS and other at&t syntax > assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is > not production quality for use by a compiler.  This is why visual studio > doesn't go through it.  Long term, we'd like LLVM to be able to write out .o > files directly, if you're interested in adding PECOFF

read 'announce' of new release for firefox-45.5.0, then for firefox-45.5.0, decided, wrongly, to upgrade. my bad. nothing but problems. on opening what moz devs considered as 'latest and greatest', found that it was more crapola from moz devs. first run was to login with my isp, only to find page would not fully load and a message bar saying; Firefox prevented this page from

My icecast server (1.3.11) has been getting 404 errors for the past couple of days from the yp.shoutcast.com server. If I send the URL manually by telneting to the webserver at yp.shoutcast.com I get the following response: [chrisp@ayeka httpd]$ telnet yp.shoutcast.com 80 Trying 205.188.234.56... Connected to scastlb1.shoutcast.com. Escape character is '^]'. GET

All I can tell you is that I've been unable to ever get meta_data to stream, and the question I sent about it a week or two ago has gone unanswered. I never actually checked that I was using WinAmp 2.75, but I do know that whatever version of winamp I *was* using could stream metadata from other sites. On Fri, 13 Sep 2002, zeek wrote: > > > I've searched the archives on xiph

also, keep in mind that support for streaming song titles is also a function of the source client you use.... I've been very successful with use_meta_data=1 and using either my DSP source (oddcast) or the Shoutcast DSP source.... and you can always know for sure if song titles are supported on your server by looking at the HTTP response headers from a request of the stream, (your request

Hi, I've just switched to icecast 2... I was using some shell script that were re-encoding stream at differents bitrate but they aren't working anymore with icecast 2 :-( What is the new authentification protocol ? Previously, I was sending : SOURCE $PASSWORD $DESTMOUNTPOINT x-audiocast-name: $NAME x-audiocast-url: $URL x-audiocast-genre: $GENRE x-audiocast-bitrate: $BITRATE

I've searched the archives on xiph and elsewhere in hopes of finding an answer on whether song titles will work. There seems to be no definitive answer. use_meta_data 1 DOES work for WinAmp 2.75 but nothing else I've tried (which includes the latest WinAmp and Sonique). Also, I can get some header by telnetting into my port (see below) but still the "meta_data" issue remains a

Just built myself a little test server with an Atom 230 processor in it and am quite impressed with it so-far. Wondering is anyones used one in anger for a VoIP platform? I'm after something with a bit more oomph than the VIAs I'm currently using that I can use in a small box (mini ATX size) without going full-blown Xeons, etc. Cheers, Gordon

Dave Hayes <dave@jetcafe.org> writes: > Darkice has: > public = yes > So I check darkice: > Icecast.cpp: > ... > str = "\nx-audiocast-public: "; > sink->write( str, strlen( str)); > str = getIsPublic() ? "yes" : "no"; > sink->write( str, strlen( str)); > and then icecast: > .... > else if

> Thanks for the network dumps. As you say, it's weird because Flash, even > when embedded, can access the stream of Icecast2. I already noticed it by > analyzing Icecast2's logs as I wrote in the first message of this topic. > There is something I couldn't see in the network dumps: is the embedded > flash DOWNLOADING the stream even if it doesn't play it (with

Hi Assorgia, Thanks for the network dumps. As you say, it's weird because Flash, even when embedded, can access the stream of Icecast2. I already noticed it by analyzing Icecast2's logs as I wrote in the first message of this topic. There is something I couldn't see in the network dumps: is the embedded flash DOWNLOADING the stream even if it doesn't play it (with Icecast2)? I

I know I am luddite when it comes to list-based languages, such as R. But, even these beasts must occasionally want to access objects at a literal level. For example, to a naive twit like me, x<--print (y) should deposit in x a literal print out of y; that is, x should contain the *results* of applying the print method to y (e.g., something like a tab (or space)-delimited flat

At 19:57 2/27/2001 -0600, dj66 wrote: >Hi, I've been running Icecast on my server for over five months now and am >having lots of problems with it. I must have pulled out half of my hair on >this product, mostly due to lack of support. (I mean, have you ever gotten >an answer to your question at icecast.org?) I've tried it all: sc_serv, >Icecast, shout, ices, streamcast,

Hmm.. just switched back to icecast hoping that 1.3.9 would have fixed some of the bugs I was running into, such as icecast gobbling up more and more memory until it would tank around 200M or so (in a box with 256) if left running a few days, and got some general questions for anyone in-the-know. ;) 1. Is there a definitive list of what players on what platforms support the x-audiocast

Hello All, I wrote a PHP function to parse the icecast stats log and return as much information in a structured array as possible (well, as much as I care about, anyway). Because the stats log is not easily machine-parseable, I thought this might be useful to somebody. The log is parsed using Perl-compatible regexps, so it should easily port. I have only my own setup to test this on, so

Jack Moffitt <jack@xiph.org> writes: > I assume the public flag is not set for that source. I don't see it in > there. Ah ha! I think I found the problem. Remember my setup is: xmms -> darkice 0.7 -> relay icecast server -> main icecast server | +->to other networks Darkice has: public = yes So I check

<?xml version="1.0" ?> <head> <title></title> </head> <body> <div align="left"><font face="Arial" color="#7f0000"><span style="font-size:10pt">> you only have the header info in this, for protocol break up the actual</span></font></div> <div

Hi, Could anyone tell me about the different login schemes sources can use to connect to IceCast, ShoutCast, etc? From what I can tell: ShoutCast uses something called icy login? IceCast uses something called x-audiocast, but can also use icy? IceCast2 uses what? Also, where can I find details about these login schemes? I sort of figured out a basic use of x-audiocast by looking at the JScream

i'm having the same problem... touches seem to work fine, but the stream doesn't show up on the yp servers... i've trimmed my list of directory servers to only yp.icecast.org and yp.mp3.de. i did a tcpdump trace of a touch, and upon analyzing it, things seem to work correctly... in the interest of verbosity, the sessions are as follows: ============================ yp.icecast.org

this is almost certainly a driver or device mapping issue. the answer depends on whether you use alsa or oss. if you're using oss: use alsa :) if you're using alsa: are both cards correctly installed? what does aplay -l say? what does lsmod | grep snd say? have you specified the correct device to use? depending on your installation, the onboard sound chip might be set to be the default