Sox stopped working

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm using sox in this setup: sudo timeout 20 rtl_fm -f 115.5M -s 60k -g 45 -p 55 -E wav -E deemp -F 9 - | sox -t wav - test.wav rate 11025, it worked for quite a while but since last week it stopped working and prints this error message:
sox FAIL formats: can't open input `-': WAVE: RIFF header not found
The error message is not really useful though because I specifies the header already with -t wav...What do I need to change to get it to work?
sox
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I'm using sox in this setup: sudo timeout 20 rtl_fm -f 115.5M -s 60k -g 45 -p 55 -E wav -E deemp -F 9 - | sox -t wav - test.wav rate 11025, it worked for quite a while but since last week it stopped working and prints this error message:
sox FAIL formats: can't open input `-': WAVE: RIFF header not found
The error message is not really useful though because I specifies the header already with -t wav...What do I need to change to get it to work?
sox
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using sox in this setup: sudo timeout 20 rtl_fm -f 115.5M -s 60k -g 45 -p 55 -E wav -E deemp -F 9 - | sox -t wav - test.wav rate 11025, it worked for quite a while but since last week it stopped working and prints this error message:
sox FAIL formats: can't open input `-': WAVE: RIFF header not found
The error message is not really useful though because I specifies the header already with -t wav...What do I need to change to get it to work?
sox
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm using sox in this setup: sudo timeout 20 rtl_fm -f 115.5M -s 60k -g 45 -p 55 -E wav -E deemp -F 9 - | sox -t wav - test.wav rate 11025, it worked for quite a while but since last week it stopped working and prints this error message:
sox FAIL formats: can't open input `-': WAVE: RIFF header not found
The error message is not really useful though because I specifies the header already with -t wav...What do I need to change to get it to work?
sox
sox
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 21 at 13:54
Rui F Ribeiro
38.3k1475126
38.3k1475126
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 10:52
MrGrimod
33
33
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MrGrimod is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
You don't "specify the header" with -t wav, you tell sox that it should expect a file in WAV format on stdin. So sox dutifully starts to parse stdin, and expects a RIFF header as part of the WAV format, but doesn't get it.
So it's not "sox stopped working", it's rtl_fm which is for some reason not producing a valid WAV format. Checking the man page, at least for the version of rtl_fm on the man page, the file type is given by -t wav, and not by -E wav. So check the options to rtl_fm.
Did you introduce a typo last week in the command line?
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
You don't "specify the header" with -t wav, you tell sox that it should expect a file in WAV format on stdin. So sox dutifully starts to parse stdin, and expects a RIFF header as part of the WAV format, but doesn't get it.
So it's not "sox stopped working", it's rtl_fm which is for some reason not producing a valid WAV format. Checking the man page, at least for the version of rtl_fm on the man page, the file type is given by -t wav, and not by -E wav. So check the options to rtl_fm.
Did you introduce a typo last week in the command line?
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
add a comment |
up vote
0
down vote
accepted
You don't "specify the header" with -t wav, you tell sox that it should expect a file in WAV format on stdin. So sox dutifully starts to parse stdin, and expects a RIFF header as part of the WAV format, but doesn't get it.
So it's not "sox stopped working", it's rtl_fm which is for some reason not producing a valid WAV format. Checking the man page, at least for the version of rtl_fm on the man page, the file type is given by -t wav, and not by -E wav. So check the options to rtl_fm.
Did you introduce a typo last week in the command line?
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
You don't "specify the header" with -t wav, you tell sox that it should expect a file in WAV format on stdin. So sox dutifully starts to parse stdin, and expects a RIFF header as part of the WAV format, but doesn't get it.
So it's not "sox stopped working", it's rtl_fm which is for some reason not producing a valid WAV format. Checking the man page, at least for the version of rtl_fm on the man page, the file type is given by -t wav, and not by -E wav. So check the options to rtl_fm.
Did you introduce a typo last week in the command line?
You don't "specify the header" with -t wav, you tell sox that it should expect a file in WAV format on stdin. So sox dutifully starts to parse stdin, and expects a RIFF header as part of the WAV format, but doesn't get it.
So it's not "sox stopped working", it's rtl_fm which is for some reason not producing a valid WAV format. Checking the man page, at least for the version of rtl_fm on the man page, the file type is given by -t wav, and not by -E wav. So check the options to rtl_fm.
Did you introduce a typo last week in the command line?
answered Nov 21 at 11:12
dirkt
16.2k21234
16.2k21234
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
add a comment |
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
I found the problem. It was not that rtl_fm send the wrong header but that it sent no header at all because there was no data. After a quick reboot it worked again as usual ;D. Thx for the quick help!
– MrGrimod
Nov 21 at 16:22
add a comment |
MrGrimod is a new contributor. Be nice, and check out our Code of Conduct.
MrGrimod is a new contributor. Be nice, and check out our Code of Conduct.
MrGrimod is a new contributor. Be nice, and check out our Code of Conduct.
MrGrimod is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483179%2fsox-stopped-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown