Topic: "I just pulled up my man sox": comand line sound recording!

I really wanted to call this thread:
"I just pulled up my man sox", or, "How I Learned to stop worrying and use command line sound recording"
like a clever little parody of "Dr Strange Love, or How I Learned To Stop Worrying And Love The Bomb", with a dash of manpage humour.
couldnt resist not putting in the man gag.  wink

so, i installed "sox" after waking up ridiculously early, with an idea buzzing in my mind...  "do a search for command line sound recorder!", like some piece of subconscious genius after "sleeping on" all the drop out, latency, realtime issues that are sure to plague any other musician / sound engineer / audio designer.

and yeah, after just throwing the command sox to see what it alone would do, and getting some reasonably unhelpful help back, i moved to the next step... "man sox".

omigosh!  a useful manpage!   big_smile   it does happen, and is always a welcome joy when it does.

i havnt tried recording with sox yet (let alone without xorg & all it's bugles blaring), but got so excited i thought i'd make this thread documenting the discovery.
I'm sure it will be just that extra smidgen more successful for recording our band sessions cleanly in their entirety so we dont miss those genius little unrepeatable bits that always seem to receive the inevitable "Oh Man! that was genius, lets get that down, hit record", then recording a shallow pathetic mockery of the original spark.

educate yourself so you may educate others.DeNoob&UnBloat PCs!
the only free webhosting i use.
say "NO!" to a chemical lobotomy in your food
flattr me, thnx

Re: "I just pulled up my man sox": comand line sound recording!

a little update:

seems "realtime" would still be a good idea.
it started off great (as i monitored from a second tty with htop), but after some many minutes i noticed that both the cpu was getting chewed up quite a lot, often with one of the cores up at the high 90s or even 100%, while the other trickling along at 2-6%, and more to the point, it was lagging...  the feedback was a little behind, and as i found out from playing back, and having read out the numbers, there was a 5 second gap after 7 minutes into recording a stereo wav (with default 48000, 16bit) from when i said the numbers, to the numbers that showed up in playback (if i managed to make that make sense).

but the audio it recorded was clean, nothing noticeably lost, and it retained the top spot.

success.  smile

educate yourself so you may educate others.DeNoob&UnBloat PCs!
the only free webhosting i use.
say "NO!" to a chemical lobotomy in your food
flattr me, thnx

Re: "I just pulled up my man sox": comand line sound recording!

Digit wrote:

I really wanted to call this thread:
"I just pulled up my man sox", or, "How I Learned to stop worrying and use command line sound recording"
like a clever little parody of "Dr Strange Love, or How I Learned To Stop Worrying And Love The Bomb", with a dash of manpage humour.
couldnt resist not putting in the man gag.  wink

GEEK ALERT! Quick everyone, make a run for it! lol

Seriously though, nice one, I might have to try sox myself. smile

Re: "I just pulled up my man sox": comand line sound recording!

Heh. Looking for a quick way to test if my mic is working and this popped up. Just had to bump it cos it's exactly the kind of bad pun/cult film reference combo I think there should be more of in the world.

Re: "I just pulled up my man sox": comand line sound recording!

There is a very simple way to test your mic:

cat /dev/{your mic} | aplay

:-)

I'm so meta, even this acronym