From: Mikko Olkkonen <molkko@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: Help With SoX
Date: Sun, 8 Apr 2018 18:12:06 +0300 [thread overview]
Message-ID: <CANWtmUAGrk-zfc7kg=uBXtQU0QEe+_nzVnRtBPJg0kBedr764w@mail.gmail.com> (raw)
In-Reply-To: <CABCFZCdyeZeHGX2+Sg1=MfsnYDsmRizkb+eVMZpkx_k0m7atYQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 5649 bytes --]
That "mpg123 -w output.wav input.mp3" above.
M
On Sun, Apr 8, 2018 at 5:59 PM, parikshit hooda <phooda804@gmail.com> wrote:
> Can you tell me how you are converting MP3 to wav? Maybe I will do the
> same.
>
> Regards
> Parikshit Hooda
>
> On Sun, 8 Apr 2018, 8:24 pm Mikko Olkkonen, <molkko@gmail.com> wrote:
>
>> okay. I have the same "use case". I am doing it this way: mpg123 -w
>> output.wav input.mp3; sox output.wav -b 16 -r 8000 output2.wav channels 1
>> .... i.e. I am using another program to turn mp3 to wav before sox
>> processing. I dont know if this approach is applicable in your case. I dont
>> know how to build/configure sox so that one could do this entirely with
>> sox. Good luck.
>> br, Mikko
>>
>>
>> On Sun, Apr 8, 2018 at 5:22 PM, parikshit hooda <phooda804@gmail.com>
>> wrote:
>>
>>> I checked out in the SOx manual that if we have to convert MP3 files to
>>> wav format we have to proceed with the SOx installation differently like
>>> something related to source scripts and lame encoder and things like that
>>> so I wanted to ask if that is the way to go or I can just figure out
>>> something with the normal installation.
>>>
>>> Regards
>>> Parikshit Hooda
>>>
>>> On Sun, 8 Apr 2018, 7:10 pm Mikko Olkkonen, <molkko@gmail.com> wrote:
>>>
>>>> If the input file is properly closed and available (Refer to Jeremy's
>>>> comment) it should be ok whatever is its format as long as the format is
>>>> supported i.e. you should be ok to substitute my "input.wav" with whatever
>>>> is your input filename/format.
>>>> regards, M
>>>>
>>>> On Sun, Apr 8, 2018 at 4:08 PM, parikshit hooda <phooda804@gmail.com>
>>>> wrote:
>>>>
>>>>> Actually, I am requiring the user to upload input file in any format.
>>>>> I know that we can convert between different audio formats but I don't know
>>>>> how. Wait, let me send you the code.
>>>>>
>>>>> Regards
>>>>> Parikshit Hooda
>>>>>
>>>>> On Sun, 8 Apr 2018, 6:36 pm Mikko Olkkonen, <molkko@gmail.com> wrote:
>>>>>
>>>>>> Can you wait until you have the audio in input.wav and then issue
>>>>>> node exec() with sox input.wav -b 16 -r 8000 output.wav channels 1
>>>>>> regards, M
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Apr 8, 2018 at 1:52 PM, parikshit hooda <phooda804@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello all!
>>>>>>> I am new to this community and I feel awesome being a part of this
>>>>>>> community.
>>>>>>> I am developing a Node application which needs to convert any audio
>>>>>>> format to WAV 16bit mono 8MHz.
>>>>>>> Can anyone provide me with the command on how to do that.
>>>>>>> I have searched through the documentation and couldn't find what I
>>>>>>> was looking for.
>>>>>>> Thanks in advance.
>>>>>>> --
>>>>>>> Regards
>>>>>>> Parikshit Hooda
>>>>>>> DTU
>>>>>>>
>>>>>>> ------------------------------------------------------------
>>>>>>> ------------------
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>> ------------------------------------------------------------
>>>>>> ------------------
>>>>>> 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
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> 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
>>>>>
>>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> 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
>>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> 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
>>>
>>>
>> ------------------------------------------------------------
>> ------------------
>> 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
>>
>
> ------------------------------------------------------------
> ------------------
> 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
>
>
[-- Attachment #1.2: Type: text/html, Size: 11165 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:[~2018-04-08 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 10:52 Help With SoX parikshit hooda
2018-04-08 11:23 ` Jeremy Nicoll - ml sox users
2018-04-08 13:05 ` Mikko Olkkonen
2018-04-08 13:08 ` parikshit hooda
2018-04-08 13:40 ` Mikko Olkkonen
2018-04-08 14:22 ` parikshit hooda
2018-04-08 14:54 ` Mikko Olkkonen
2018-04-08 14:59 ` parikshit hooda
2018-04-08 15:12 ` Mikko Olkkonen [this message]
2018-04-09 4:20 ` Glenn English
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='CANWtmUAGrk-zfc7kg=uBXtQU0QEe+_nzVnRtBPJg0kBedr764w@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).