Confused about input stream settings
  • Hi there

    I'm confused as to what to do here.
    I want to stream live with Mixx and not understanding what settings to put in the input stream boxes in Airtime.

    I understand if I was to stream directly to my Shoutcast server from Mixx, that's just my Shoutcast ip address and port number and password.

    Airtime is hosted on my VPS and I just use a ip address to connect to it.

    Any help would be much apprciated.

    Mark
  • 56 Comments sorted by
  • Hi Mark,

    Have you checked out our manual?

    http://en.flossmanuals.net/airtime-en-2-2/stream-settings/

    Check out the input streaming section.

    Thank you.
  • Yes I've read them but I don't understand them.
  • Well here's what settings I've put in the master input stream

    master username: master
    master password: password
    master source port: 8000
    master source point: test
    master source connection url: http://5.133.180.173:8000/test

    Tried connecting using Mixx and get a error: could not connect to server.

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    What's the mountpoint value you filled in Mixxx, "/test"?
    Cloud Radio -> http://airtime.pro
  • just test with no forward slash
  • Hi Mark,

    So 5.133.180.173 is the ip of your VPS?
    Can you confirm that port 8000 is open on your VPS?

    Thank you
  • Yes that's the ip of my VPS

    How do I check if the port is open?

    As well if I just goto: 5.133.180.173 I get the "It work's" page telling me that apache is setup (I'm assuming that's what it means).
    Also to login to airtime I have to go to: 5.133.180.173/airtime
  • > Also to login to airtime I have to go to: 5.133.180.173/airtime


    This doesn't sound right. Currently Airtime does not work if it's not the root document (should be fixed for 2.3).

    What's the output of airtime-check-system?
    Airtime Pro Hosting: http://airtime.pro
  • Here's my airtime check:

    AIRTIME_STATUS_URL             = http://localhost:80/api/status/format/json/api_                                              key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 2.6.32-042stab061.2
    MACHINE_ARCHITECTURE           = x86_64
    TOTAL_MEMORY_MBYTES            = 262144
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = 2.2.0
    OS                             = Ubuntu 10.04.4 LTS x86_64
    CPU                            = Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = 313
    PLAYOUT_ENGINE_RUNNING_SECONDS = 415
    PLAYOUT_ENGINE_MEM_PERC        = 5.5%
    PLAYOUT_ENGINE_CPU_PERC        = 0.0%
    LIQUIDSOAP_PROCESS_ID          = 296
    LIQUIDSOAP_RUNNING_SECONDS     = 415
    LIQUIDSOAP_MEM_PERC            = 7.6%
    LIQUIDSOAP_CPU_PERC            = 0.1%
    MEDIA_MONITOR_PROCESS_ID       = 302
    MEDIA_MONITOR_RUNNING_SECONDS  = 415
    MEDIA_MONITOR_MEM_PERC         = 5.6%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    RABBITMQ_PROCESS_ID            = 503
    RABBITMQ_RUNNING_SECONDS       = 411
    RABBITMQ_MEM_PERC              = 9.0%
    RABBITMQ_CPU_PERC              = 0.0%
    -- Your installation of Airtime looks OK!
    root@1162-2990-4227:~#

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Hey, Mark,

    Can you try to execute "netstat -a | grep 8000" to check if it's listened? 

    Thanks.
    Cloud Radio -> http://airtime.pro
  • I tried the command but it didn't do anything.

    I've looked at my iptables and they don't seem to be saving at all :(
  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Oops, try "netstat -an | grep 8000", I miss "n" before.
    Cloud Radio -> http://airtime.pro
  • I tired it and it doesn't do anything, by iptables are saving now. Can I add a rule in there to open this port?

    here's the output of the command:-
    root@1162-2990-4227:~# netstat -an | grep 8000
    root@1162-2990-4227:~#

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Please go ahead, it sounds port 8000 is not listened after you set it in Airtime.
    Cloud Radio -> http://airtime.pro
  • I've added a rule I don't think it's right though.

    here's my iptables:-
    root@1162-2990-4227:~# iptables -L
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    ACCEPT     all  --  anywhere             anywhere
    ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ssh
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:www
    DROP       all  --  anywhere             anywhere
    ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:8000

    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination

    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    root@1162-2990-4227:~#

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Please try netstat -an | grep 8000 and telnet your_ipaddress 8000 to make sure it works
    Cloud Radio -> http://airtime.pro
  • this is what I get from doing that:-

    root@1162-2990-4227:~#  netstat -an | grep 8000
    tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN
    tcp        0      0 127.0.0.1:8000          127.0.0.1:47852         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:49977         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:48381         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:50472         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:47317         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:48909         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:46233         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:51001         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:49437         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:46776         TIME_WAIT
    tcp        0      0 127.0.0.1:8000          127.0.0.1:45617         TIME_WAIT

  • Then I get this message when I use telnet.

    root@1162-2990-4227:~# telnet 5.133.180.173:8000
    telnet: could not resolve 5.133.180.173:8000/telnet: Name or service not known
    root@1162-2990-4227:~#

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Actually, the default Airtime output port is 8000. Can you try to set another "not occupied" port if you are still not able to use Mixxx to connect master source?
    Cloud Radio -> http://airtime.pro
  • I've opened up 8010 and this is the result:-
    root@1162-2990-4227:~# netstat -an | grep 8010
    tcp        0      0 0.0.0.0:8010            0.0.0.0:*               LISTEN
    root@1162-2990-4227:~#

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    How about the result to use Mixxx connecting Airtime? Does it work?
    Cloud Radio -> http://airtime.pro
  • No it doesn't work
  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Try to check the settings, should be similar with the following screenshots, one is for Mixxx and another is for Airtime.
    719 x 571 - 64K
    497 x 553 - 39K
    Cloud Radio -> http://airtime.pro
  • Still the same. I'm using Shoutcast does that make a difference, also this mount point, do I need to create a file of some sort?
  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    Any debug information from Mixxx? 

    BTW, Encoder format should be MP3 if connection is Shoutcast, and make sure libmp3lame is installed.
    Cloud Radio -> http://airtime.pro
  • Just says check username and password.

    Lame eoncoder is installed.
  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    No clue what's happening, do you mind email me a temporary password of master resource and the ip address, let me try to connect, my email address is cliff dot wang at sourcefabric dot org

    Post edited by Cliff Wang at 2012-11-08 16:45:40
    Cloud Radio -> http://airtime.pro
  • Yeah sure
    I've emailed them to you
  • Well it's solved I had shoutcast selected in the dropdown in Mixx rather than Icecast 2

    Thanks so much for all of your help.
  • I currently have Airtime working using a remote shoutcast server. I want to connect to Airtime using MIXX. But to connect to Airtime remotely I need another streaming server like an icecast server on the same machine where Airtime is installed. Is this so?
  • Hi Anthony,

    No you don't need any stream server installed on the machine to connect MIXX to Airtime.
    Check out 'Input Stream Setting' section in this manual: http://en.flossmanuals.net/airtime-en-2-2/stream-settings/

    Thank you
  • I have opened the router port settings, do I have to set the ports of the airtime server too? I thought this was done at the input stream gui settings...
    This looks so simple, I must be missing something.
  • First you need to pick a port and configure in airtime stream setting page.
    you also need to set username, password and mount point.

    If your machine is behind a firewall and if the port you picked from airtime stream page is block, you need to do port forwarding.

    At this point, airtime should be ready to accept connection from MIXX.
    Of course you have to configure Mixx so it has correct setting(username, password, port, mountpoint, server host name and etc).
    Post edited by James Moon at 2012-11-27 14:05:45
  • I've been through this many times. Right now I'm using BUTT as the server client, on a machine different than the Airtime Server, however it is in the same network. The settings are matched in both BUTT and Airtime, and yes I had the same results with MIXXX.

    Settings on Airtime--

    Master Username: "source"
    Master Password: "same-as-set-in-streaming-client"
    Master Source Port: "7000"
    Master Src Mt Pt: "http://mydomain.com:7000"

    BUTT just stays in connecting mode...





    Post edited by Anthony Bouchard at 2012-11-27 14:35:46
  • master source port should be a number not the complete url.
  • Sorry was a error in typing not in actual settings, correction to settings in post.
  • I never used BUTT, but since it support both icecast and shoutcast, you also want to make sure that the server type is set to icecast on BUTT.
  • Ok can you post the screen shot of BUTT setting screen? also airtime stream page as well.
    Make sure you don't display any password.

    Thank you.
  • So it's only icecast as an input?
  • Master source mount point should be some kind of word(eg. master_source), not the url.
    You might also have to configure mount_point on BUTT side as well.
  • Yes Airtime only accept icecast protocol for the input stream. This shouldn't be problem as BUTT supports both protocol(according to their doc).
  • @Anthony,

    Try this youtube tutorial video. It might help you to solve the problem.


  • Okay changed over to icecast. At least now I am getting a prompt back in BUTT-- "connect: invalid password!"...

    Checked in Butt client and reset the password in Airtime to the same and still have the same prompt.
  • Please post screenshot of BUTT and Airtime stream page.

    Thanks
  • I restarted BUTT and now it's streaming. However I do not see the indicator on Airtime come on, and when I click on the "X", it says there's no source connected to this input".
  • Good news it's streaming to Airtime and out-putting as well. But when I
    disconnect the stream, the source connection indicator remains on. Is this normal?

  • Which line are you referring to? the one before the switch? or after?
    Also, what was the issue? can you please share with us?

    Thank you.
  • At this point I'm not sure what the issue was after I changed the settings to icecast...I believe "BUTT tool" was locked up since it started streaming after restart. However the delay is puzzling -- why would it take so long for the connect-indicator to come on in Airtime...

    Now it seems the indicator will not go off after streaming is disconnected from master source.

    BTW, I switched the on/off controls to test them and it does automatically switch broadcasting source.
  • And  James, Thank you for your help!
  • Oh one last thing, probably the wrong thread here. MIXXX doesn't have a mic always on feature, so it's not good for live radio. Any ideas?