vlc as relay/fowarding/repeater server for asf

[isync]

Using the command:

Code: Select all

vlc.exe udp://@:8777 --sout-mux-caching 45000 --sout "#standard{access=http,mux=ts,dst=127.0.0.1:9070}" --intf rc

I had success using a daemonized vlc as stream relay for ts muxed streams. Now, using this knowledge, so far I wasn't able to relay asf streams - can anyone help?

Not shown in the command above: I use a vlc instance to stream/feed content to my relay vlc-server via UDP. I do so as I was unable to get vlc into listening on http (can someone fill me in why?).
Looking at the stream feature matrix, I see that I can't feed asf muxed content via UDP, thus I decided to mux asf in a ts stream for the connection feed-source -> repeater and then, re-mux on my repeater (which shouldn't be too much overhead as no transcoding happens here - I need to keep an eye on CPU on the repeater server...). On the repeater I use this command trying to relay asf:

Code: Select all

vlc.exe udp://@:8777 --sout-mux-caching 45000 --sout "#standard{access=http,mux=asf,dst=127.0.0.1:9070}" --intf rc

And it does not work. You see, I try to receive the incoming ts stream, re-mux it, and send it out. Any ideas, hints?
Why does on HTTP sources vlc tests for input and then just exits, while with UDP it continuusly listens.

In another scenario I saw that vlc accepts HTTP as source if you start the Feeder first (so input is already there), then the Relay, which I think is unacceptable for a relay daemon...

Why did the --daemon switch disappear?
How to relay asf without the ts-remux-trick? Anything? I am lost here.

OR: is vlc as relay a bad idea and I should use Darwin instead? Why?

Versions used were 1.0.2, Grishenko and a nightly from git.