|
|
ALSA for audio
Hi,
Just to let people know I've now written an initial webpage on how the user can set up their Linux sound system. All being well, I'll add a couple of more pages in due course to cover more of the topic. First page done, at http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Tue, 12 Feb 2013 16:39:20 +0000 (GMT)
Jim Lesurf wrote: Hi, Just to let people know I've now written an initial webpage on how the user can set up their Linux sound system. All being well, I'll add a couple of more pages in due course to cover more of the topic. First page done, at http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html Slainte, Jim I shall test-drive it, and see how well it reflects the problems I had, and you fixed! -- Davey. |
ALSA for audio
In article , Davey
wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Wed, 13 Feb 2013 09:45:53 +0000 (GMT)
Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Don't forget to point us to the magazine with your article in it. I had a very quick glance at your webpage, and I noticed all the vertical bars; whereas my system just has several [00]s, due to a different internal setup. Hopefully this is covered if I read it in more depth. I will follow this with interest, thanks. -- Davey. |
ALSA for audio
In article , Jim Lesurf
wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) However, first, I intend writing a magazine article. Correction! Having started writing the magazine article I ended up writing the 'next webpage' first. My mind does that to me at times... :-) So I now have a rought draft of that. All being well I'll edit/tweak it to being nearer to English and put it up as a webpage in the next day or two. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Wed, 13 Feb 2013 09:45:53 +0000 (GMT)
Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. -- Davey. |
ALSA for audio
On 2013-02-13, Davey wrote:
On Wed, 13 Feb 2013 09:45:53 +0000 (GMT) Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. In principle yes. However most mic inputs have a dc voltage on them to power the FET on the microphones. Thus your line out should make sure it has a capacitive output or you could have a fight. |
ALSA for audio
On Thu, 14 Feb 2013 00:11:13 GMT
unruh wrote: On 2013-02-13, Davey wrote: On Wed, 13 Feb 2013 09:45:53 +0000 (GMT) Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. In principle yes. However most mic inputs have a dc voltage on them to power the FET on the microphones. Thus your line out should make sure it has a capacitive output or you could have a fight. Thanks. That's just the sort of thing I was looking out for, not knowing enough about these things. The line out in question is from the headphone-out socket of an AIWA cassette deck, I'll see if I can find a spec. sheet anywhere. Or is it likely to be typical in some way? -- Davey. |
ALSA for audio
On Thu, 14 Feb 2013 00:22:51 +0000, Davey wrote:
On Thu, 14 Feb 2013 00:11:13 GMT unruh wrote: On 2013-02-13, Davey wrote: On Wed, 13 Feb 2013 09:45:53 +0000 (GMT) Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. In principle yes. However most mic inputs have a dc voltage on them to power the FET on the microphones. Thus your line out should make sure it has a capacitive output or you could have a fight. Thanks. That's just the sort of thing I was looking out for, not knowing enough about these things. The line out in question is from the headphone-out socket of an AIWA cassette deck, I'll see if I can find a spec. sheet anywhere. Or is it likely to be typical in some way? Alternatively, you might want to look at using an Ion U-Record, just under 30 squids from Amazon. Its a USB stereo ADC, accepts line-in or MC pickup levels and is powered off the USB connection. Works well with Audacity. RCA connectors on the analogue side. I got mine because it was cheap to see if this was a good way to digitise some tapes and vinyl and have kept it because I can't see any reason the replace it with a more expensive device. Caveat: mine was working well in March last year with whatever the semi- current Fedora was (probably F15) and Audacity (probably 1.38). When I tried it a day or two ago (F17, Audacity 2.0.2) no joy: looks like there's a problem with either the OS or Audacity and the USB codec. This might be specific to the U-record but it could equally apply to all external USB sound cards. I bugged it against Fedora but no resolution as yet. However, I reckon its hard to go wrong at that price, especially as it uses a decent Burr-Brown ADC. -- martin@ | Martin Gregorie gregorie. | Essex, UK org | |
ALSA for audio
In article , Davey
wrote: Don't forget to point us to the magazine with your article in it. Thereby hangs a tale... :-) What has appeared on my website was originally aimed at being published in 'Linux Format'. I sent them a copy and their Editor said, yes, they wanted to publish. We agreed it should be a 4-page 'tutorial' and I planned others to follow. I got their contract document from the Publishers. Didn't like the look of it. The essence of that was their contract wanted *all* rights on an exclusive basis. Inc all 'moral' rights, etc. The lot. I explained to the Editor that I only sell 'first serial' rights and *non* exclusive republication rights as I wish to be able to re-use parts of material, or put the articles on the web at a later date. The point being to ensure that useful data isn't 'lost' to people later in time. (When they can't get the mag, or the publisher shuts down.) I've not had any problem with other publishers with this. e.g. Hi Fi News are happy with it. But their response was that they insist on taking all rights. Full stop. I pointed out this seemed particularly weird as an attitude for a *Linux* magazine! :-) The Editor agreed, but said it wasn't in his hands, and the publishers insist. So no publication in Linux Format. Fortunately, I don't write for a living, so can decide to go without the fees. However there will be an article in Hi Fi News. Just have to get around to writing it. :-) Shame, though, as I'd like to write about this for LXF. May see if they will publish a brief item pointing at the webpages for details. Might get though that way... I had a very quick glance at your webpage, and I noticed all the vertical bars; whereas my system just has several [00]s, due to a different internal setup. Hopefully this is covered if I read it in more depth. I will follow this with interest, thanks. It depends entirely on the hardware ALSA finds. Some devices have gain or volume controls. Others don't (and so you rely on software you use to scale gains or volumes). I get different alsamixer displays on all three of the Linux machines I use. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
In article , unruh
wrote: On 2013-02-13, Davey wrote: Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. In principle yes. However most mic inputs have a dc voltage on them to power the FET on the microphones. Thus your line out should make sure it has a capacitive output or you could have a fight. You may also find that the mic input clips 'line' level voltages since a mic input may have a preamp stage which can't cope with such 'high' levels. Any hardware gain adjustment may be after this stage. This, again, all depends on the specific hardware in the box. In general I'd be wary of the analogue stages of hardware in a normal computer. Might be OK. But a dedicated special purpose external 'sound card' may well give much better results. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Thu, 14 Feb 2013 09:20:15 +0000 (GMT)
Jim Lesurf wrote: In article , Davey wrote: Don't forget to point us to the magazine with your article in it. Thereby hangs a tale... :-) What has appeared on my website was originally aimed at being published in 'Linux Format'. I sent them a copy and their Editor said, yes, they wanted to publish. We agreed it should be a 4-page 'tutorial' and I planned others to follow. I got their contract document from the Publishers. Didn't like the look of it. The essence of that was their contract wanted *all* rights on an exclusive basis. Inc all 'moral' rights, etc. The lot. I explained to the Editor that I only sell 'first serial' rights and *non* exclusive republication rights as I wish to be able to re-use parts of material, or put the articles on the web at a later date. The point being to ensure that useful data isn't 'lost' to people later in time. (When they can't get the mag, or the publisher shuts down.) I've not had any problem with other publishers with this. e.g. Hi Fi News are happy with it. But their response was that they insist on taking all rights. Full stop. I pointed out this seemed particularly weird as an attitude for a *Linux* magazine! :-) The Editor agreed, but said it wasn't in his hands, and the publishers insist. So no publication in Linux Format. Fortunately, I don't write for a living, so can decide to go without the fees. However there will be an article in Hi Fi News. Just have to get around to writing it. :-) Shame, though, as I'd like to write about this for LXF. May see if they will publish a brief item pointing at the webpages for details. Might get though that way... Well, that is sad. It sounds as though the editor didn't really care to even try to change Management's thinking, but he may know there is no chance of changing their ideas. I remember looking at Photobucket's Ts&Cs once, and being horrified at what they took as their rights. I had a very quick glance at your webpage, and I noticed all the vertical bars; whereas my system just has several [00]s, due to a different internal setup. Hopefully this is covered if I read it in more depth. I will follow this with interest, thanks. It depends entirely on the hardware ALSA finds. Some devices have gain or volume controls. Others don't (and so you rely on software you use to scale gains or volumes). I get different alsamixer displays on all three of the Linux machines I use. So many options, so much scope for confusion of the unwary...... -- Davey. |
ALSA for audio
On Thu, 14 Feb 2013 02:21:21 +0000 (UTC)
Martin Gregorie wrote: On Thu, 14 Feb 2013 00:22:51 +0000, Davey wrote: snip Alternatively, you might want to look at using an Ion U-Record, just under 30 squids from Amazon. Its a USB stereo ADC, accepts line-in or MC pickup levels and is powered off the USB connection. Works well with Audacity. RCA connectors on the analogue side. I got mine because it was cheap to see if this was a good way to digitise some tapes and vinyl and have kept it because I can't see any reason the replace it with a more expensive device. Caveat: mine was working well in March last year with whatever the semi- current Fedora was (probably F15) and Audacity (probably 1.38). When I tried it a day or two ago (F17, Audacity 2.0.2) no joy: looks like there's a problem with either the OS or Audacity and the USB codec. This might be specific to the U-record but it could equally apply to all external USB sound cards. I bugged it against Fedora but no resolution as yet. However, I reckon its hard to go wrong at that price, especially as it uses a decent Burr-Brown ADC. I had seen adverts. for Ion stuff, but was wary due to many bad reports of their slide and negative copying devices; I just made my own, from a couple of cardboard boxes and Sellotape, and have successfully digitised hundreds of slides for a History Society. In my case, I already had a working setup, with a proper sound card and Audacity in an old Dell desktop PC, but the PC was moved to the other end of the house, for use with Zoneminder and CCTV. As my need of this recording setup is now rare, I think I do not need to buy more stuff, where there is little space for it anyway, for a limited use, but rather I will take the cassette deck down to the PC to do the job, and just leave it there, under the PC. But I should one day re-load Audacity, as it got hosed when I did a full new Ubuntu installation. But I thank you for your thoughts, it is good to hear that the Ion device does work. Another thought: I have two different TV- PC USB devices. I wonder if one of them would do the same job, just using the stereo sound inputs? Even if I had to provide a dummy TV signal for it to lock on to while acting as a TV device, I could then possibly take the recorded sound track, although I would need to work out what to do to enable this, and then to do it. But is it viable? Maybe it would just work with Audacity as it is. -- Davey. |
ALSA for audio
On Thu, 14 Feb 2013 00:11:13 GMT
unruh wrote: On 2013-02-13, Davey wrote: On Wed, 13 Feb 2013 09:45:53 +0000 (GMT) Jim Lesurf wrote: In article , Davey wrote: On Tue, 12 Feb 2013 16:39:20 +0000 (GMT) Jim Lesurf wrote: http://www.audiomisc.co.uk/Linux/ALSA/ALSAforUsers.html I shall test-drive it, and see how well it reflects the problems I had, and you fixed! You'll probably need the 'next' page - which I've not written yet! :-) That will cover things like using aplay to investigate your card playout devices and how to write a suitable .asoundrc to control and direct output. Thought it best to start with alsamixer, etc, as it means starting with a nice graphic display showing users what they have. However, first, I intend writing a magazine article. Needed a wepage in place first so I could give a URL to point readers toward for more specific data. Once the article is done I'll have a while to add another page or two to the above, and then all will be findable by someone who reads the magazine. Slainte, Jim Having read the whole article now, one question: Can I use the Mic Input on my laptop, which already has a built-in Mic, as a Line Input, or is there going to be some horrid mis-match? I have a tape deck nearby, and I would like to send its output into the laptop, but it only has the Mic Input. In principle yes. However most mic inputs have a dc voltage on them to power the FET on the microphones. Thus your line out should make sure it has a capacitive output or you could have a fight. On a similar vein, but in the opposite direction, I would like to send the PC headphone output signal to my HiFi, since my stupid TV will only send out of the SCART connector the sound track from whatever TV channel it's tuned to, even if the HDMI input is selected for display. But I know that there is going to be a mismatch between the PC's output and any input on the amplifier, as it is not designed to accept such an input signal. Another idea shelved. -- Davey. |
ALSA for audio
Davey wrote... But I know that there is going to be a mismatch between the PC's output and any input on the amplifier, as it is not designed to accept such an input signal. You shouldn't have any problems as long as you take it easy with the volume control. In pre USB days this was the only practical way to get audio from a PC to the hifi. I'm currently feeding the output of a cheap and quite cheerful USB audio dongle: http://www.lindy.co.uk/usb-2-audio-adapter/42961.html to a 70's JVC amplifier which has an input sensitivity of 150mV and have not noted any mismatch or overload. More recent amps designed to cope with the typical 2V output of CD players should have more headroom. -- Ken O'Meara |
ALSA for audio
In article , Davey
wrote: On Thu, 14 Feb 2013 09:20:15 +0000 (GMT) Jim Lesurf wrote: But their response was that they insist on taking all rights. Full stop. I pointed out this seemed particularly weird as an attitude for a *Linux* magazine! :-) The Editor agreed, but said it wasn't in his hands, and the publishers insist. Well, that is sad. It sounds as though the editor didn't really care to even try to change Management's thinking, but he may know there is no chance of changing their ideas. From what he said my feeling is that he has tried and given up. They own the mag and set the rules. In a way, no different to, say, 'left wing' magazines that treat their staff poorly, etc, when you'd expect them to care about pay and conditions and how to treat staff. Bear in mind that many publishers run a 'stable' of mags purely on the basis of leaving all content, etc, to the editorial staff, and treating the result as a widget factory providing income. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Thu, 14 Feb 2013 12:23:35 -0000
UnsteadyKen wrote: Davey wrote... But I know that there is going to be a mismatch between the PC's output and any input on the amplifier, as it is not designed to accept such an input signal. You shouldn't have any problems as long as you take it easy with the volume control. In pre USB days this was the only practical way to get audio from a PC to the hifi. I'm currently feeding the output of a cheap and quite cheerful USB audio dongle: http://www.lindy.co.uk/usb-2-audio-adapter/42961.html to a 70's JVC amplifier which has an input sensitivity of 150mV and have not noted any mismatch or overload. More recent amps designed to cope with the typical 2V output of CD players should have more headroom. The Amp. in question is a Goodmans Module 80, of the late 1970s! Works fine, after I replaced some blown lamps, and some funny-looking bulging capacitors, but cannot be described as 'more recent'! It is of the same era as your JVC. But I might still try it, I have a collection of old phono and jack sockets from a much-loved but now dead cassette player, so I should be able to make up the correct 3.5mm jack to 5-pin DIN connector required. Your dongle (that sounds rude, but isn't meant to be!) looks good value. Thanks for help and ideas. -- Davey. |
ALSA for audio
In article , Davey
wrote: On Thu, 14 Feb 2013 12:23:35 -0000 UnsteadyKen wrote: The Amp. in question is a Goodmans Module 80, of the late 1970s! Works fine, after I replaced some blown lamps, and some funny-looking bulging capacitors, but cannot be described as 'more recent'! It is of the same era as your JVC. I'd have to dig though my old mags and documents to be sure. But I'd guess it uses DIN sockets and has a line sensitivity of about 500 - 100 mV. So would need some resistors to cope with modern line voltages (circa 1V to 2V). IIRC the audio on a SCART is about 1V. So could also be used. You can buy adaptors for this which output to phono/RCA sockets. CPC is your friend. :-) Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
I've now added another page at
http://www.audiomisc.co.uk/Linux/ALS...reSilence.html which focusses more on how to set up audio playback as you prefer. I have at least one more page in mind, but will try again to make my mind get on to writing an article instead! :-) Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Thu, 14 Feb 2013 13:55:37 +0000 (GMT)
Jim Lesurf wrote: In article , Davey wrote: On Thu, 14 Feb 2013 12:23:35 -0000 UnsteadyKen wrote: The Amp. in question is a Goodmans Module 80, of the late 1970s! Works fine, after I replaced some blown lamps, and some funny-looking bulging capacitors, but cannot be described as 'more recent'! It is of the same era as your JVC. I'd have to dig though my old mags and documents to be sure. But I'd guess it uses DIN sockets and has a line sensitivity of about 500 - 100 mV. So would need some resistors to cope with modern line voltages (circa 1V to 2V). IIRC the audio on a SCART is about 1V. So could also be used. You can buy adaptors for this which output to phono/RCA sockets. CPC is your friend. :-) Slainte, Jim I already send the audio from the TV's SCART output to the Goodmans, but as I mentioned, it only sends the audio of whatever TV channel the TV is or was tuned to, so is no use when I'm using the PC as a video source; hence the desire to use the PC's headphone output instead. I can look for the specs. on the Goodmans, but I think I will be in no hurry to do this, in case it damages something. I would be using the Tape Recorder Input on the Goodmans. Physically, I can get the signals there, after a bit of soldering. Interestingly, the DIN socket from the dead donor cassette deck has a bunch of resistors on the DIN socket board, but I can't see what colours the bands are, they are hidden. At the moment. I have a DIN-DIN cable already, it's a matter of getting the signal to it that requires the soldering and construction of a connector. This is possible. -- Davey. |
ALSA for audio
On Thu, 14 Feb 2013 14:32:23 +0000 (GMT)
Jim Lesurf wrote: I've now added another page at http://www.audiomisc.co.uk/Linux/ALS...reSilence.html which focusses more on how to set up audio playback as you prefer. I have at least one more page in mind, but will try again to make my mind get on to writing an article instead! :-) Slainte, Jim Ok, I follow all that, especially as we have been through it! The 'Tip' text has a couple of small typos, but that's easy to fix. -- Davey. |
ALSA for audio
In ,
Davey wrote: On Thu, 14 Feb 2013 02:21:21 +0000 (UTC) Martin Gregorie wrote: Alternatively, you might want to look at using an Ion U-Record, just under 30 squids from Amazon. Its a USB stereo ADC, accepts line-in or MC pickup levels and is powered off the USB connection. [Snip] I had seen adverts. for Ion stuff, but was wary due to many bad reports of their slide and negative copying devices; I just made my own, from a couple of cardboard boxes and Sellotape, and have successfully digitised hundreds of slides for a History Society. Behringer also make this sort of thing. I think they have a good reputation among audio people. I bought a UFO202 a few years ago; I can't remember how much it cost, but I'm pretty sure it was less than £30. I've never had any problems with it. -- TH * http://www.realh.co.uk |
ALSA for audio
In ,
Jim Lesurf wrote: You may also find that the mic input clips 'line' level voltages since a mic input may have a preamp stage which can't cope with such 'high' levels. Any hardware gain adjustment may be after this stage. This, again, all depends on the specific hardware in the box. In general I'd be wary of the analogue stages of hardware in a normal computer. Might be OK. But a dedicated special purpose external 'sound card' may well give much better results. From what I've read you're quite right to be wary of standard sound cards or onboard audio. A few years ago one of the regulars on uk.comp.homebuilt used to point out that a reference design for sound cards had an over-severe clipping circuit on the line-in (not just mic) which would clip at well under the usual maximum level. And this design was used by the vast majority of sound cards. -- TH * http://www.realh.co.uk |
ALSA for audio
On Thu, 14 Feb 2013 15:06:05 +0000 (UTC)
Tony Houghton wrote: In , Davey wrote: On Thu, 14 Feb 2013 02:21:21 +0000 (UTC) Martin Gregorie wrote: Alternatively, you might want to look at using an Ion U-Record, just under 30 squids from Amazon. Its a USB stereo ADC, accepts line-in or MC pickup levels and is powered off the USB connection. [Snip] I had seen adverts. for Ion stuff, but was wary due to many bad reports of their slide and negative copying devices; I just made my own, from a couple of cardboard boxes and Sellotape, and have successfully digitised hundreds of slides for a History Society. Behringer also make this sort of thing. I think they have a good reputation among audio people. I bought a UFO202 a few years ago; I can't remember how much it cost, but I'm pretty sure it was less than £30. I've never had any problems with it. Sounds interesting. I see it for £30 or £46 ! I just tried to open Audacity on my laptop, and it fails, and of course, I can't find what I see in any of the Help files. I get: "audacity: pcm_plug.c:388: snd_pcm_plug_change_channels: Assertion `snd_pcm_format_linear(slv-format)' failed. Aborted" I think I'll stop there, unless this means something to somebody! I did the Reset Preferences procedure as described in the Wiki, but it made no difference. -- Davey. |
ALSA for audio
In article , Davey
wrote: On Thu, 14 Feb 2013 13:55:37 +0000 (GMT) Jim Lesurf wrote: I'd have to dig though my old mags and documents to be sure. But I'd guess it uses DIN sockets and has a line sensitivity of about 500 - 100 mV. So would need some resistors to cope with modern line voltages (circa 1V to 2V). I would be using the Tape Recorder Input on the Goodmans. Physically, I can get the signals there, after a bit of soldering. Interestingly, the DIN socket from the dead donor cassette deck has a bunch of resistors on the DIN socket board, but I can't see what colours the bands are, they are hidden. At the moment. I have a DIN-DIN cable already, it's a matter of getting the signal to it that requires the soldering and construction of a connector. This is possible. A possible complication is that the original DIN specification included that the signal should be a *current* source. Not everyone was mad enough to impliment that, and instead went for voltage. So you can easily find items from the period that aren't compatable with others unless there are some 'bodge' resistors in the circuit! Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
In article ,
Davey wrote: http://www.audiomisc.co.uk/Linux/ALS...reSilence.html Ok, I follow all that, especially as we have been through it! The 'Tip' text has a couple of small typos, but that's easy to fix. Situation Normal. :-) I'll check when I get a chance. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
In article ,
Davey wrote: I just tried to open Audacity on my laptop, and it fails, and of course, I can't find what I see in any of the Help files. I get: "audacity: pcm_plug.c:388: snd_pcm_plug_change_channels: Assertion `snd_pcm_format_linear(slv-format)' failed. Aborted" I think I'll stop there, unless this means something to somebody! I did the Reset Preferences procedure as described in the Wiki, but it made no difference. It certainly means something to Google, though what it means seems to be something to do with the JACK audio subsystem which I have never used. If it still means nothing to you then perhaps uninstalling anything JACK-related may be a good idea. Linux audio has so many different systems anyway that removing ones you don't need can only help (says the man who once again has given up with PulseAudio and uninstalled it, although this time Pulse lasted as much as 14 months before getting its automagic settings into such an irrecoverable twist that it was no longer usable). Nick -- "The Internet, a sort of ersatz counterfeit of real life" -- Janet Street-Porter, BBC2, 19th March 1996 |
ALSA for audio
On Thu, 14 Feb 2013 22:18:37 +0000 (UTC)
Nick Leverton wrote: In article , Davey wrote: I just tried to open Audacity on my laptop, and it fails, and of course, I can't find what I see in any of the Help files. I get: "audacity: pcm_plug.c:388: snd_pcm_plug_change_channels: Assertion `snd_pcm_format_linear(slv-format)' failed. Aborted" I think I'll stop there, unless this means something to somebody! I did the Reset Preferences procedure as described in the Wiki, but it made no difference. It certainly means something to Google, though what it means seems to be something to do with the JACK audio subsystem which I have never used. If it still means nothing to you then perhaps uninstalling anything JACK-related may be a good idea. Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Linux audio has so many different systems anyway that removing ones you don't need can only help (says the man who once again has given up with PulseAudio and uninstalled it, although this time Pulse lasted as much as 14 months before getting its automagic settings into such an irrecoverable twist that it was no longer usable). Nick -- Davey. |
ALSA for audio
On 14/02/13 22:56, Davey wrote:
Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? If it came as a dependency, something might stop working by being uninstalled. If it came as a recommended package, something obscure might no longer work, but you might well not notice it unless you do obscure things. Try removing it and check that it isn't going to take anything else with it. If it is, then it was a dependency, and it's up to you to decide whether you can live without whatever else is going to be removed or cancel the removal. Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. e.g. some sound cards have more flexible routing than ALSA supports, so you could do multitrack monitoring in a way which eliminates the latency you would get if the monitor channel were subject to the same delay the recorded signal is. It's a bit like having a patch panel, hence the name. It's essential in a recording studio, not so common in home music systems. It also helps to know how to use it, as if you don't you probably aren't getting much benefit from it. -- ╔═╦═╦═════╦═══╗ ║ ║ ║ ║ ║ ╔═╝ ║ ║ ║ ║ ║ ╔═╝ ╚═══╩═╩═╩═╩═╩═╝ -- JimP. |
ALSA for audio
In article , Jim Price
wrote: On 14/02/13 22:56, Davey wrote: Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. I continue to wonder about that. I haven't ever use 'Jack'. Never needed it, despite recording things as well as playing and processing them. But my impression is that it has been developed as a 'user friendly' sic way to do things which its creators *think* people "can't do" with ALSA. However the "can't" may mean "don't know how" rather than "physically impossible" - mainly, perhaps, because making sense of ALSA can be a real struggle. And may involve hand-editing files, etc, which is hardly user-friendly if people want to dump the old image of Linux = "Typing arcane commands into terminals". Plus documentation that only makes sense when you've hacked your way to a solution. ...erm IMHO. Indeed, I keep feeling that people have invented and added extra "sound systems" as an alternative to understanding and documenting (and making programs to ease) doing this using ALSA. The result now seems to be a pile of 'different' sound systems, which can easily interfere with simple user choices that don't fit the auto-magical assumptions of an install. Hence Jack, Pulse, etc, become a PITA for many rather than a solution. And make some people feel it is a hopeless task to do something as simply play music as they prefer. So far as practical, I'd advise people to avoid Jack, Pulse, etc, as they just complicate issues for basic uses. As far as I'm concerned, Pulse is a virus. But as usual, YMMV. ;- 2p ended. :-) Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Fri, 15 Feb 2013 09:30:56 +0000 (GMT)
Jim Lesurf wrote: In article , Jim Price wrote: On 14/02/13 22:56, Davey wrote: Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. I continue to wonder about that. I haven't ever use 'Jack'. Never needed it, despite recording things as well as playing and processing them. But my impression is that it has been developed as a 'user friendly' sic way to do things which its creators *think* people "can't do" with ALSA. However the "can't" may mean "don't know how" rather than "physically impossible" - mainly, perhaps, because making sense of ALSA can be a real struggle. And may involve hand-editing files, etc, which is hardly user-friendly if people want to dump the old image of Linux = "Typing arcane commands into terminals". Plus documentation that only makes sense when you've hacked your way to a solution. ...erm IMHO. Indeed, I keep feeling that people have invented and added extra "sound systems" as an alternative to understanding and documenting (and making programs to ease) doing this using ALSA. The result now seems to be a pile of 'different' sound systems, which can easily interfere with simple user choices that don't fit the auto-magical assumptions of an install. Hence Jack, Pulse, etc, become a PITA for many rather than a solution. And make some people feel it is a hopeless task to do something as simply play music as they prefer. So far as practical, I'd advise people to avoid Jack, Pulse, etc, as they just complicate issues for basic uses. As far as I'm concerned, Pulse is a virus. But as usual, YMMV. ;- 2p ended. :-) Jim As I mentioned partially above, I looked for jack on my PC, and it was listed by Synaptic as not installed, in any guise. Yet I did a 'whereis', and found: jack: /usr/lib/jack /usr/lib64/jack And the terminal tells me that it is not currently installed, just like Synaptic. From this, I deduce that there are some files loaded, but they are not in use. Which leaves me still with the question: What does my Audacity fail message mean? -- Davey. |
ALSA for audio
In article , Davey
wrote: As I mentioned partially above, I looked for jack on my PC, and it was listed by Synaptic as not installed, in any guise. Yet I did a 'whereis', and found: jack: /usr/lib/jack /usr/lib64/jack And the terminal tells me that it is not currently installed, just like Synaptic. From this, I deduce that there are some files loaded, but they are not in use. Which leaves me still with the question: What does my Audacity fail message mean? My *guess* is that Audacity is looking for a device connected with a wrong pcm format. However its not a problem I've encountered, so I can't predict how to cure it. Can you play files with aplay and record them with arecord? If so, your sound system is basically setup OK and the problem is some assumptions that Audacity is making. If Audacity refuses to even run you may have to look at its config files or remove and re-install it if you can't find settings to adjust. If you can get it to run and give you a GUI, you can use that to change what input and output setup it expects to match the reality. But I'm afraid I don't use Audacity much. So can't give more than general suggestions here. snd_pcm_format_linear() is probably called to arrange the pcm format for something by Audacity. The error is probably because the response isn't one it can match. Why, dunno! :-/ Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Fri, 15 Feb 2013 14:11:17 +0000 (GMT)
Jim Lesurf wrote: In article , Davey wrote: As I mentioned partially above, I looked for jack on my PC, and it was listed by Synaptic as not installed, in any guise. Yet I did a 'whereis', and found: jack: /usr/lib/jack /usr/lib64/jack And the terminal tells me that it is not currently installed, just like Synaptic. From this, I deduce that there are some files loaded, but they are not in use. Which leaves me still with the question: What does my Audacity fail message mean? My *guess* is that Audacity is looking for a device connected with a wrong pcm format. However its not a problem I've encountered, so I can't predict how to cure it. Can you play files with aplay and record them with arecord? If so, your sound system is basically setup OK and the problem is some assumptions that Audacity is making. If Audacity refuses to even run you may have to look at its config files or remove and re-install it if you can't find settings to adjust. aplay works fine, I just checked. Not tried arecord (ever). All that happens is that I get the message I showed. -- Davey. |
ALSA for audio
On Fri, 15 Feb 2013 14:47:17 +0000 (GMT)
Jim Lesurf wrote: On 15 Feb, wrote: In article , Davey wrote: If Audacity refuses to even run you may have to look at its config files or remove and re-install it if you can't find settings to adjust. Not sure if this will help, but just in case... All help is welcome! You should have something like an .audacity-data directory, inside of which will be an audacity.cfg file. That is the default Audacity will check when it is run. In my main machine's copy it includes [AudioIO] RecordingDevice=HDA Intel PCH: STAC92xx Analog (hw:0,0) Host=ALSA PlaybackDevice=HDA Intel PCH: STAC92xx Analog (hw:0,0) Which tells Audacity what to try and connect to by default when run. It then uses these as the default recording and playing devices. Make a backup copy of the file for safety. Then do an 'aplay -L' and 'arecord -L' to get the details of your soundcard devices. Edit the audacity.cfg file to point at the sound devices you want have have the host as ALSA. That *might* cure the problem. Following advice I found in the Audacity Forums, yesterday I found that file, and deleted everything except the first line, then relaunched Audacity. It is supposed to repopulate the file with info. when it restarts, but it didn't restart. And of course, I didn't make a backup (slaps own wrist!). I might look through my Backup records, though, just in case. But I don't think it's going to work anyway. I have also tried Completely removing, and reinstalling, audacity, already. I'll give arecord a go. -- Davey. |
ALSA for audio
On Fri, 15 Feb 2013 09:30:56 +0000 (GMT)
Jim Lesurf wrote: In article , Jim Price wrote: On 14/02/13 22:56, Davey wrote: Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. I continue to wonder about that. I haven't ever use 'Jack'. Never needed it, despite recording things as well as playing and processing them. But my impression is that it has been developed as a 'user friendly' sic way to do things which its creators *think* people "can't do" with ALSA. Jack allows you to look at audio links in a totally different way. It uses ALSA to make the physical connections, but (using something like Qjackctl) presents all the information in a sane manner. The problem arises when using something like Audacity, which although very good in it own right, is a bodge when connecting up. I simply could not do much of the composition work I do without jack. I can, and do kick out pulseaudio as a waste of resources, and *never* use Audacity for recording. Timemachine is just so much simpler, reliable and above all routable. -- W J G |
ALSA for audio
In article 20130215203017.02b60dda@debian, Folderol
wrote: On Fri, 15 Feb 2013 09:30:56 +0000 (GMT) Jim Lesurf wrote: In article , Jim Price wrote: On 14/02/13 22:56, Davey wrote: Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. I continue to wonder about that. I haven't ever use 'Jack'. Never needed it, despite recording things as well as playing and processing them. But my impression is that it has been developed as a 'user friendly' sic way to do things which its creators *think* people "can't do" with ALSA. Jack allows you to look at audio links in a totally different way. It uses ALSA to make the physical connections, but (using something like Qjackctl) presents all the information in a sane manner. In effect, that's a part of my point. Jack is effectively acting as a 'human interface' to ALSA. People use it because they can make sense of how to use Jack, but are baffled by how to get ALSA directly to achieve the same specific task. If Jack (or indeed Pulse, etc) work for you or anyone else, that's fine with me. Matter of personal preference and convenience. However my feeling is that we have got into this situation of having 'many different sound systems' due to a lack of awareness of how to simply use ALSA. That, in turn, is because it can be a real PITA to work out how to get ALSA set up in the way a specific task requires. I've managed by banging rocks together for a few years to sort out the basics of just getting music to play or record using ALSA. I've still not sussed out the more complex requirements. So I can quite understand why people use Jack, etc. The problem in my experience, though, is that sometimes systems like Pulse actually cause problems because they 'nanny' the user and actually stop them getting what they want. Once that happens I feel the user can easily end up in the kind of situation familiar to some Windows/Mac users: Of the system refusing to do what is wanted, and behaviing in an opaque manner which resists the user's attempts to correct its incorrect behaviour. For the sake of my own sanity I gave up fighting Pulse years ago. I just bypass it. But I just need to play or record/capture one stream at a time. If I were trying to do multichannel recordings, mixdowns, etc, I'd probably do something else. Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
ALSA for audio
On Sat, 16 Feb 2013 09:47:52 +0000 (GMT)
Jim Lesurf wrote: In article 20130215203017.02b60dda@debian, Folderol wrote: On Fri, 15 Feb 2013 09:30:56 +0000 (GMT) Jim Lesurf wrote: In article , Jim Price wrote: On 14/02/13 22:56, Davey wrote: Indeed. I have no idea what Jack is, but it is there, in /usr/lib64. But what happens otherwise if I remove it? Jack is handy for music production, as you can often use some of the features of your sound card which might not be supported by ALSA alone. I continue to wonder about that. I haven't ever use 'Jack'. Never needed it, despite recording things as well as playing and processing them. But my impression is that it has been developed as a 'user friendly' sic way to do things which its creators *think* people "can't do" with ALSA. Jack allows you to look at audio links in a totally different way. It uses ALSA to make the physical connections, but (using something like Qjackctl) presents all the information in a sane manner. In effect, that's a part of my point. Jack is effectively acting as a 'human interface' to ALSA. People use it because they can make sense of how to use Jack, but are baffled by how to get ALSA directly to achieve the same specific task. If Jack (or indeed Pulse, etc) work for you or anyone else, that's fine with me. Matter of personal preference and convenience. However my feeling is that we have got into this situation of having 'many different sound systems' due to a lack of awareness of how to simply use ALSA. That, in turn, is because it can be a real PITA to work out how to get ALSA set up in the way a specific task requires. I've managed by banging rocks together for a few years to sort out the basics of just getting music to play or record using ALSA. I've still not sussed out the more complex requirements. So I can quite understand why people use Jack, etc. The problem in my experience, though, is that sometimes systems like Pulse actually cause problems because they 'nanny' the user and actually stop them getting what they want. Once that happens I feel the user can easily end up in the kind of situation familiar to some Windows/Mac users: Of the system refusing to do what is wanted, and behaviing in an opaque manner which resists the user's attempts to correct its incorrect behaviour. For the sake of my own sanity I gave up fighting Pulse years ago. I just bypass it. But I just need to play or record/capture one stream at a time. If I were trying to do multichannel recordings, mixdowns, etc, I'd probably do something else. Slainte, Jim That sounds like a sensible viewpoint, from my perspective of very limited experience of this business. If Folderol finds Jack useful, good for him, but since I am struggling getting the basics working, I don't think I'll go there. I did some basic testing yesterday, I'll post the results later on, for your comments. -- Davey. |
ALSA for audio
On Fri, 15 Feb 2013 14:11:17 +0000 (GMT)
Jim Lesurf wrote: arecord Ok, here is what I found out. Bear in mind I have never used arecord, only aplay. Both of my TV encoders work fine with their respective WIN 7 programs, so that is how I use them, I never succeeded in getting either of them to work with Linux. With a lot more time, maybe I would be able to. Maybe. So, still in Ubuntu 10.04, I ran aplay -l and aplay -L, and arecord -l, and arecord -L, before inserting the EZCap into a USB port. aplay -L with the EZCap added the line: iec958:CARD=U0xeb1a0x2861,DEV=0 USB Device 0xeb1a:0x2861, USB Audio IEC958 (S/PDIF) Digital Audio Output arecord -l added: card 2: U0xeb1a0x2861 [USB Device 0xeb1a:0x2861], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 This sounds to me as though the device is being seen and recognised. Volume Control Sound Preferences also shows it as: 2861 / 1 Input / Analog Stereo Input, which is good. alsamixer shows one L R CAPTURE volume bar whether or not the device is plugged in, so it is probably referring to an internal device, such as the internal Intel soundcard. If so, where is the USB device? I now need to work out what arecord instruction to give to record something, but I need to do some reading for that. Just tried a basic arecord, and whatever I do, it returns: arecord: main:608: audio open error: No such file or directory Got other stuff to do, back to this later. -- Davey. |
ALSA for audio
In article , Davey
wrote: On Fri, 15 Feb 2013 14:11:17 +0000 (GMT) Jim Lesurf wrote: arecord Ok, here is what I found out. Bear in mind I have never used arecord, only aplay. Both of my TV encoders work fine with their respective WIN 7 programs, so that is how I use them, I never succeeded in getting either of them to work with Linux. With a lot more time, maybe I would be able to. Maybe. So, still in Ubuntu 10.04, I ran aplay -l and aplay -L, and arecord -l, and arecord -L, before inserting the EZCap into a USB port. A problem with this is that I have no real idea what "EZCap" is. You'd have to say more about that. aplay -L with the EZCap added the line: iec958:CARD=U0xeb1a0x2861,DEV=0 USB Device 0xeb1a:0x2861, USB Audio IEC958 (S/PDIF) Digital Audio Output How does aplay -l list it? I'd have guessed from its name that it is a 'capture' device so wouldn't appear at all for aplay -l. arecord -l added: card 2: U0xeb1a0x2861 [USB Device 0xeb1a:0x2861], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 That says it is hw:2,0,0 for capture. This sounds to me as though the device is being seen and recognised. Volume Control Sound Preferences also shows it as: 2861 / 1 Input / Analog Stereo Input, which is good. What "Volume Control Sound Preferences" do you mean here? How are you getting that info? alsamixer shows one L R CAPTURE volume bar whether or not the device is plugged in, so it is probably referring to an internal device, such as the internal Intel soundcard. If so, where is the USB device? I now need to work out what arecord instruction to give to record something, but I need to do some reading for that. Just tried a basic arecord, and whatever I do, it returns: arecord: main:608: audio open error: No such file or directory You'd need to say what you mean by a 'basic' arecord. Try something like arecord -D plughw:2,0,0 -f dat -t wav -d 5 fred.wav If it can find the device it should give you a five second long wave file called fred.wav, stereo 48k rate. If not, say what errors it returns. If it works, try arecord -D hw:2,0,0 -f dat -t wav -d 5 fred.wav and if that doesn't work, what errors does it return? Slainte, Jim -- Please use the address on the audiomisc page if you wish to email me. Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html Audio Misc http://www.audiomisc.co.uk/index.html |
| All times are GMT. The time now is 12:21 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.0.0
Copyright 2004-2006 AudioBanter.co.uk