RTMPDUMP issues with OSX 10.8 and Windows XP
Posted: 02 Aug 2012 03:50
As this problem is happening with both Windows XP and OSX 10.8, it did not make sense to me to pick one OS over the other. Under OSX, I am running VLC 2.0.3 and under Windows I am running the August 1st build of VLC 2.0.4. I am also running rtmpdump 2.4 on both platforms.
Basically I am performing the following command on the two platforms (on OSX the "vlc" command is "VLC"):
rtmpdump -v -r rtmp://cp80871.live.edgefcs.net/live/TOR680_AAC@14190 -o - | vlc -
On either platform, I will not hear anything until I kill rtmpdump. Once I do that, VLC starts playing what has been buffered up to the point I terminate rtmpdump. If I redirect rtmpdump's output to a file such as temp.flv, terminate it after several seconds and then cat/type the file to a pipe connected to VLC, it plays immediately. I am assuming there is a buffering issue with the pipes on both Windows and OSX but I am not sure if it is an rtmpdump issue or a VLC issue. The fact that cat/type to VLC works leads me to believe this is an rtmpdump issue.
I have searched the forums and others have reported seeing the same behavior but no one has ever responded with a solution that I can find.
Basically I am performing the following command on the two platforms (on OSX the "vlc" command is "VLC"):
rtmpdump -v -r rtmp://cp80871.live.edgefcs.net/live/TOR680_AAC@14190 -o - | vlc -
On either platform, I will not hear anything until I kill rtmpdump. Once I do that, VLC starts playing what has been buffered up to the point I terminate rtmpdump. If I redirect rtmpdump's output to a file such as temp.flv, terminate it after several seconds and then cat/type the file to a pipe connected to VLC, it plays immediately. I am assuming there is a buffering issue with the pipes on both Windows and OSX but I am not sure if it is an rtmpdump issue or a VLC issue. The fact that cat/type to VLC works leads me to believe this is an rtmpdump issue.
I have searched the forums and others have reported seeing the same behavior but no one has ever responded with a solution that I can find.