Not sure where to put this question (as so many questions start off) but I'm posting some information tonight just in case I'm overlooking something obvious.
I have been capturing the BBC radio stream using mplayer/lame and was intending to capture 170 minutes of stream. the first three nights the mp3 produced all stopped after they had captured 95,110Kb of information (about 1:41:27 of stream - so nowhere near the 170 mins I expected).
Basically the command I used was:
Code:
mplayer -cache 1024 mms://wmlive-nonacl.bbc.net.uk/wms/bbc_ami/radio1/radio1_bb_live_int_eq1_sw0 -vc null -vo null -ao pcm:file=/dev/fd/3 3>&1 2>logs/test.log 1>&2 | lame -h - /mediaData/Family/Music/BBCRadio/x.mp3
However if I split it into 2 commands :
Code:
mplayer -cache 1024 mms://wmlive-nonacl.bbc.net.uk/wms/bbc_ami/radio1/radio1_bb_live_int_eq1_sw0 -vc null -vo null -ao pcm:file=/mediaData/Family/Music/BBCRadio/x.wav 2>logs/test.log 1>&2
This produced a file 3.7Gb big when I cancelled it
I then then followed it with:
Code:
lame -h --nohist /mediaData/Family/Music/BBCRadio/x.wav /mediaData/Family/Music/BBCRadio/x.mp3
and this produced a file 170,659Kb in size (about 3:02:02 in length).
From the above I assume both mplayer and lame are capable of processing lareg streams/files by themselves and so it must be the combining them that causes the problem.
I also did another test where I converted the larger file down to about 2G in size using:
Code:
head -c 2G /mediaData/Family/Music/BBCRadio/x.wav >/mediaData/Family/Music/BBCRadio/x2.wav
and then ran lame on this file. It produced a file that was 94,692kb in size (just under the size where the piped stream conversion stops), which perhaps indicates that I'm hitting some sort of 2G pipe limit - but I'm open to any suggestions.
I'm running openSuSe 13.2 64 bit, LAME 3.99.5 64bits, and MPlayer -4.8.
My limits are set as:
Code:
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 10990
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 10990
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Any suggestions would be much appreciated as I haven't found any information on piping size limitations (but maybe that is just my searching ability)