No subject
Tue Jan 10 15:13:26 UTC 2012
What that is (I think) I understand.
Why I dont...
--90e6ba6e86fce8cf2a04b79a9f8f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">On Sat, Jan 28, 2012 at 11:22 PM, Al Tho=
mpson <span dir=3D"ltr"><<a href=3D"mailto:althompson58 at gmail.com">altho=
mpson58 at gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class=3D"h5">On 01/28/2012 12:41 PM, Rustom Mody wrote=
:<br>
> Ive been wanting to record the output of firefox(flash of some sort).<=
br>
><br>
> I followed <a href=3D"http://jackaudio.org/routing_alsa" target=3D"_bl=
ank">http://jackaudio.org/routing_alsa</a><br>
> and connected the firefox output into audacity.<br>
> It works but the original firefox sound is much louder and clearer<br>
> than the recording even when done at full volume.<br>
><br>
> So two questions<br>
><br>
> 1. Is it possible to capture the pcm data that jack is sending into a<=
br>
> file and then to convert that file (sox??) to wav.<br>
> I tried arecord and audacity -- they were both similar<br>
><br>
> 2. Any better/more proper way to do this?<br>
<br>
</div></div>Why not just normalize the wave once you have it in audacity??<=
br></blockquote></div><br>Thanks for directing me to normalize.<br>From tha=
t I get that there is significant 'DC offset'.<br>What that is (I t=
hink) I understand.<br>
Why I dont...<br>
--90e6ba6e86fce8cf2a04b79a9f8f--
More information about the Linux-audio-user
mailing list