From: harsh kurra <harshkurra21@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: Several beginner q's about Sox encoding (mp3/aac)?
Date: Tue, 21 Feb 2017 11:36:46 +0530 [thread overview]
Message-ID: <CA+t4TwA25RL10exvjHgugUJi9TYjoZdLWPHXDJ+bdGqogVcBfg@mail.gmail.com> (raw)
In-Reply-To: <CAMmPYJ3Z8Tg3rTS3M-bUyey2cpGMkis4R=cpmvzP_v9NFc-Mrg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]
*3. Is it possible to compile SOX with AAC encoding support? I want to try
AAC encoding to see if that eliminates the clicks and pops .*
I used FAAD2 AAC <http://www.audiocoding.com/downloads.html> decoder to add
support for .m4a or any AAC format in SOX for my own personal use on
windows platform.
The code is available on Bitbucket repo <https://bitbucket.org/hkurra/sox>.
On Tue, Feb 21, 2017 at 9:13 AM, christina zou <zou.christina@gmail.com>
wrote:
> Hi,
>
> I have a Raspberry Pi running Debian Jessie, as well as a MEMS I2S mic and
> a Pi Camera. My mic records 32bit raw PCM audio. I am trying to stream
> video and audio to Youtube Live. I am using Sox for audio recording and
> encoding.
>
> YouTube Live only accepts mp3 or aac encoded audio.
>
> I have installed sudo apt-get install libsox-fmt-mp3, so my Sox is able
> to encode mp3.
>
> I am using this command to record and encode audio:
>
> rec --buffer 2000000 -c 1 -r 44100 -b 32 test.mp3
>
> /usr/bin/rec WARN formats: mp3 can't encode to 32-bit
>
> Input File : 'mic_mono' (alsa)
>
> Channels : 1
>
> Sample Rate : 44100
>
> Precision : 32-bit
>
> Sample Encoding: 32-bit Signed Integer PCM
> -------
> 1. I get the warning: " mp3 can't encode to 32-bit" - what should I do
> about this?
> 2. My resultant MP3 file has small clicks and popping noises throughout. I
> know this is not a problem with my mic, as I've produced AAC encoded audio
> with FFMPEG that was perfectly clean. Any idea why this is happening?
> 3. Is it possible to compile SOX with AAC encoding support? I want to try
> AAC encoding to see if that eliminates the clicks and pops.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
>
>
--
Thanks
Harsh kurra ¯\(ツ)/¯
[-- Attachment #1.2: Type: text/html, Size: 4741 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
next prev parent reply other threads:[~2017-02-21 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 3:43 Several beginner q's about Sox encoding (mp3/aac)? christina zou
2017-02-21 5:52 ` Erich Eckner
2017-02-21 6:06 ` harsh kurra [this message]
2017-02-21 8:16 ` unosonic
2017-02-22 11:00 ` Alexander Stephen Thomas Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+t4TwA25RL10exvjHgugUJi9TYjoZdLWPHXDJ+bdGqogVcBfg@mail.gmail.com \
--to=sox-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).