Pogoplug audio baby monitor

Ask questions about Arch Linux ARM. Please search before making a new topic.

Re: Pogoplug audio baby monitor

Postby moonman » Sat Sep 07, 2013 4:37 am

Most routers filter udp broadcast packets for the wireless interface so it doesn't get flooded with useless udp. The reason behind this is that broadcast gets sent to EVERY wireless device which means the device will have to wake up even though the packaet may not be for that device. More power consumption. Then wireless has limited throughput and there's only one radio on the router shared between multiple devices. Some routers have an option to enable it (running dd-wrt or tomato on yours?). Why not stream TCP or UDP unicast?
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Pogoplug audio baby monitor

Postby permitivity » Sat Sep 07, 2013 4:53 am

Oh, didn't know that about routers filtering UDP.

Yes, I'm running Tomato. I would prefer to stream via TCP, especially if it means less wasted network traffic, but I thought the command for ffmpeg on the baby unit could only do rtp, and rtp is multicast? I could be totally off here. Might have to do some reading to understand your last reply. I'm not sure how to make this work using TCP. Would it be a router setting or a change in the ffmpeg command on the baby unit pogoplug?
permitivity
 
Posts: 141
Joined: Mon Feb 18, 2013 3:08 am

Re: Pogoplug audio baby monitor

Postby moonman » Sat Sep 07, 2013 6:13 am

To enable multicast in Tomato go to Advanced --> Firewall and enable IGMPproxy for LAN (two checkboxes, one for IGMPporxy, the other for LAN). Not a very good solution.

You can still use UDP unicast. In your server specify the IP of the client you are streaming to after rtp://

Source: http://trac.ffmpeg.org/wiki/StreamingGu ... tstreaming
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: Pogoplug audio baby monitor

Postby permitivity » Sun Sep 08, 2013 9:00 pm

Thanks Moonman, the direct point to point rtp works well. It works when both parent and baby units on wireless USB adapters.

For those who might be interested, here what I did:
$this->bbcode_second_pass_quote('', '
')Baby unit Pogoplug IP (audio source): 192.168.1.42
Parent unit (plays audio): 192.168.1.41

Parent unit, used to play audio, points to audio source:
ffmpeg -i rtp://192.168.1.42:1234 -f alsa default

Baby unit command, audio source, send audio to parent unit's IP:
ffmpeg -re -f alsa -i plughw:0 -acodec mp2 -ab 192000 -ar 48000 -ac 1 -filter 'bandpass=f=1000:csg=0:width_type=q:w=.806' -f rtp rtp://192.168.1.41:1234


But this works only for a single parent unit (1 server, 1 client). On webcams apps like Motion, multiple clients connect to one server, and the server doesn't need to know which IP addresses the clients have. The handy link you supplied has a TCP option, I'll try to see if the TCP option can do single server multiple clients.
permitivity
 
Posts: 141
Joined: Mon Feb 18, 2013 3:08 am

Previous

Return to User Questions

Who is online

Users browsing this forum: No registered users and 3 guests

cron