Re: [Dorset] Syntax for aplay

2016-11-11 Thread Terry Coles
On Friday, 11 November 2016 16:10:45 GMT Ralph Corderoy wrote:
> > For some reason the listserver stripped out the middle part of my
> > message (when I view what I sent, it only shows up if I view html, but
> > there wasn't nay html in the message) ;-(  Most of the missing text
> > consists of the man page fragment for -f, so that is available to all.
>
> When viewing your outgoing email to the list, are the missing bits in
> the text/plain alternative part of your outgoing copy?  Or was KMail
> unable to represent your words in text/plain?

Yes.

> The list's current configuration has it take a multipart/alternative
> email, e.g. with text/plain and text/html parts, strip that down to just
> one alternative, probably the text/html as it's indicated to be the
> "better" representation by coming second, and then convert text/html to
> text/plain before sending out.
> 
> It's possibly the omitted bits were due to some fancy HTML you produced.
> Ideally, send just text/plain to the list so the list won't interfere.
> That's how the list used to work IIRC, before Mailman fept some
> creatures.

I simply copied the text from within a terminal displaying the output of 'man 
aplay'.

The last missing line, I typed myself.

-- 



Terry Coles

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Ralph Corderoy
Hi Terry,

> For some reason the listserver stripped out the middle part of my
> message (when I view what I sent, it only shows up if I view html, but
> there wasn't nay html in the message) ;-(  Most of the missing text
> consists of the man page fragment for -f, so that is available to all.

When viewing your outgoing email to the list, are the missing bits in
the text/plain alternative part of your outgoing copy?  Or was KMail
unable to represent your words in text/plain?

The list's current configuration has it take a multipart/alternative
email, e.g. with text/plain and text/html parts, strip that down to just
one alternative, probably the text/html as it's indicated to be the
"better" representation by coming second, and then convert text/html to
text/plain before sending out.

It's possibly the omitted bits were due to some fancy HTML you produced.
Ideally, send just text/plain to the list so the list won't interfere.
That's how the list used to work IIRC, before Mailman fept some
creatures.

Cheers, Ralph.

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Terry Coles
On Friday, 11 November 2016 13:35:27 GMT Terry Coles wrote:
> Now I am trying to work out how to direct the output of mpg123 to the same
> audio devices.  The format of the command seems to be different to aplay and
> it keeps defaulting to the PC sound card.
> 
> Any thoughts on that anyone?

Never mind, I've done it.

-- 



Terry Coles

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Terry Coles
On Friday, 11 November 2016 12:37:53 GMT Ralph Corderoy wrote:
> > I installed sox, but found the man page a bit dense
> 
> It just needs reading many more times.  :-)

Maybe next time :-)

> sox has a soxexam man page too with examples so you can then work
> backwards and look at the options in the reference sox(1).  BTW, that
> soxexam mentions sticking with PCM if you're doing multiple
> modifications and that's probably good advice as WAV files can contain
> MP3 lossy compressed sound and not just PCM.  soxexam also introduces
> some of the effects sox can produce;  perhaps they might be helpful if
> you need more of an "echo", etc.

Well at the end of the day I want to play mp3 files, since that is what the WMT 
staff will have most readily available.  I was only using .wav, because the 
Tutorial used aplay and that doesn't support mp3.

Now I am trying to work out how to direct the output of mpg123 to the same 
audio devices.  The format of the command seems to be different to aplay and 
it keeps defaulting to the PC sound card.

Any thoughts on that anyone?

-- 



Terry Coles

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Ralph Corderoy
Hi Terry,

> I installed sox, but found the man page a bit dense

It just needs reading many more times.  :-)

sox has a soxexam man page too with examples so you can then work
backwards and look at the options in the reference sox(1).  BTW, that
soxexam mentions sticking with PCM if you're doing multiple
modifications and that's probably good advice as WAV files can contain
MP3 lossy compressed sound and not just PCM.  soxexam also introduces
some of the effects sox can produce;  perhaps they might be helpful if
you need more of an "echo", etc.

Cheers, Ralph.

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Ralph Corderoy
Hi Terry,

> $ aplay -D hw:3,0 01_Wedding_March.wav 
> Playing WAVE '01_Wedding_March.wav' : Signed 32 bit Little Endian,
> Rate 44100 Hz, Stereo
> aplay: set_params:1297: Sample format not available
> Available formats:
> - S16_LE

Without looking into it, I'd say you've a S32_LE WAV file and it can't
be shipped to the hardware that has the sole format of S16_LE.  You need
to produce a new WAV file.  See sox(1) IIRC.

Cheers, Ralph.

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

Re: [Dorset] Syntax for aplay

2016-11-11 Thread Terry Coles
For some reason the listserver stripped out the middle part of my message 
(when I view what I sent, it only shows up if I view html, but there wasn't 
nay html in the message) ;-(  Most of the missing text consists of the man 
page fragment for -f, so that is available to all.

Apart from that, the following line was also stripped out:

'I've tried every possible incantation of -f that I can think of, but always 
get the same result.'
 

On Friday, 11 November 2016 10:55:32 GMT Terry Coles wrote:
> Hi,
> 
> I've just received a set of these:
> 
> https://thepihut.com/products/usb-audio-adapter[1]
> 
> As far as I can tell, these are identical to the ones sold by Modmypi and
> others, so I've been trying to get them to play using the tutorial I found
> on the Modmypi site.
> 
> Initially, I'm doing this on my PC for convenience.
> 
> I can identify the devices and aplay attempts to play the file, but
> complains that I've asked for the wrong format:
> 
> ../Playlist1$ aplay -D hw:3,0 01_Wedding_March.wav
> Playing WAVE '01_Wedding_March.wav' : Signed 32 bit Little Endian, Rate
> 44100 Hz, Stereo aplay: set_params:1297: Sample format not available
> Available formats:
> - S16_LE
> 
> I can get the file to play to the default audio device on hw:0,0 without
> complaint, but that of course is my PC sound card.
> 
> The man page for aplay says:
> 
> -f --format=FORMAT
> 
> 
> So my question is twofold:
> 
> 1. What is it that doesn't like the format; the device or the tool?
> 
> 2. If it's the tool; how do I write it to make it work.
> 
> BTW.  I really want to do this using mpg123 eventually, but I haven't found
> a tutorial to help me make that work, so I started with this.


-- 



Terry Coles

-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR

[Dorset] Syntax for aplay

2016-11-11 Thread Terry Coles
Hi,

I've just received a set of these:

https://thepihut.com/products/usb-audio-adapter[1] 

As far as I can tell, these are identical to the ones sold by Modmypi and 
others, so I've 
been trying to get them to play using the tutorial I found on the Modmypi site.

Initially, I'm doing this on my PC for convenience.

I can identify the devices and aplay attempts to play the file, but complains 
that I've asked 
for the wrong format:

../Playlist1$ aplay -D hw:3,0 01_Wedding_March.wav 
Playing WAVE '01_Wedding_March.wav' : Signed 32 bit Little Endian, Rate 44100 
Hz, Stereo
aplay: set_params:1297: Sample format not available
Available formats:
- S16_LE

I can get the file to play to the default audio device on hw:0,0 without 
complaint, but that 
of course is my PC sound card.

The man page for aplay says:

-f --format=FORMAT 


So my question is twofold: 

1. What is it that doesn't like the format; the device or the tool?

2. If it's the tool; how do I write it to make it work.

BTW.  I really want to do this using mpg123 eventually, but I haven't found a 
tutorial to 
help me make that work, so I started with this.

-- 



Terry Coles


[1] https://thepihut.com/products/usb-audio-adapter
-- 
Next meeting:  Bournemouth, Tuesday, 2016-12-06 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
New thread:  mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING
Reporting bugs well:  http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR