Linux-audio-user September 2012

linux-audio-user@lists.linuxaudio.org

98 participants
100 discussions

by Ken Restivo

It's time to finally retire my 2008-vintage EEE 1000 netbook, and get one with a faster processor and dual cores. I won't need it for music-- the old one was plenty powerful enough for what I was doing anyway-- but I need it for work, and, java runs like an absolute pig on the old EEE (as does Firefox, and Chromium, and just about anything modern). I have come to love the layout of this old EEE though, the keyboard, the form-factor, and its low current consumption (about 1A @12v). So I'd like to keep those as similar as possible. If I could upgrade the processor and RAM and keep everything else, I would. So the EEE 1215N looks pretty good, and if I swap out its spinning-rust-platter drive with a cheap SSD, I can probably get the current consumption down. But I worry. I worry about graphics card not working, wifi not working, sound not working, sleep not working, etc. I looked at the DebianEEE wiki and it seems like not a lot has happened there in years. Any advice on a fast (approaching laptop performance) netbook? -ken

13 years, 4 months

Re: [LAU] MIDI keyboard not recognized

by Nigel Henry

On Sunday 09 September 2012 20:54, jy wrote: > > 2012/9/9 Nigel Henry <cave.dnb2m97pp(a)aliceadsl.fr> > > > On Sunday 09 September 2012 18:57, jy wrote: > > > Hi all, > > > > > > I've recently installed ubuntustudio 12.04 and after trying it out, i > > > discovered that my M-Audio Oxygen8 v2 MIDI USB (yes it is class > > > > compliant) > > > > > keyboard is not recognised. > > > It was recognised out of the box on my previous setup based on ubuntu > > > 10.04. > > > > > > By not recognized, i mean that it doesn't appear in qjackctl > > > connexions. thus i cant route the connexions correctly... > > > Below are some logs ! > > > > > > How come it doesn't work any more ? How can i correct this ? > > > > > > Thanks a lot > > > > > > Cheers, > > > jy > > > > > > ####LOGS#### > > > $cat /proc/asound/cards > > > 0 [Intel ]: HDA-Intel - HDA Intel > > > HDA Intel at 0xf0400000 irq 45 > > > > It's not showing up in the cards list above, which seems to indicate that > > the > > snd_usb_audio module isn't loaded, or you've forgotten to switch the > > keyboard > > on. Have a look in lsmod to see if the module is showing there. > > > > If not, load it with. > > sudo modprobe snd_usb_audio > > > > Then see if the keyboard shows up in the cards list. > > > > Nigel. > So : > > * module snd_usb_audio is already loaded > * after running aj2midid -e, keyboard is still missing from ALSA and JACK > tabs... > > It's true that I was surprised that the keyboard did not appear in > /proc/asound/cards but as it does appear in amidi -l, i'm thinking that > alsa is correctly recognizing the keyboard... Could i be wrong? > Thing is I'm not sure if this is an ALSA issue or jack/qjackctl one. > > how could i troubleshoot this ? > > jy Please send replies to the list and put your replies at the bottom of the post, which makes it easier to follow. Ok. It does need to be listed as a card in /proc/asound/cards, just as a webcam with built in mike (although not a soundcard as such) will have a card entry and uses snd_usb_audio. So why isn't it there? Does it need firmware loading? I know some M-audio keyboards do. My Evolution keyboard doesn't, but someone with the same as yours will say. Have you tried it in a different USB slot if you have spare ones? Not in a hub as some USB things don't like hubs. The only other thing I can think of is that both the sound card and the keyboard are trying to grab card0 and the soundcard is winning, thus the keyboard can't use it. Now I've seen this the other way round due to the USB coming up early in the boot process and my keyboard grabbing card0 leaving no place for the actual soundcard. This is a very old problem, but may for some reason be happening in your case, so I suggest putting some index options in /etc/modprobe.d/options, which will at least confirm if that is the problem or not. See below. options snd_hda_intel index=0 options snd_usb-audio index=1 Best to reboot and then see if /proc/asound/cards lists both. If not I'm a bit perplexed. Nigel. > > _______________________________________________ > > Linux-audio-user mailing list > > Linux-audio-user(a)lists.linuxaudio.org > > http://lists.linuxaudio.org/listinfo/linux-audio-user

13 years, 4 months

[LAU] A praat question - optimising quality of speaker change

by Julien Claassen

Hello everyone! Ihave been experimenting with Praat. I'm using it to change the speaker, meaning: changing pitch, vowels and relativ pitch range. I'm assuming, that they use something based on FFT. But they don't allow access to underlying parameters. Perhaps - on the other hand - they're using something different. My question is: How can I optimise the output result? I don't need pitch perfection, since I'm experimenting for a small radioplay project. currently I'm mainly changing male to female, though I might need male to old male later on as well. The parameters this function offers are these: bass pitch: minimum pitch to consider high pitch: Highest pitch to consider Vowel change (1.0 = normal, 1.1 for male to female) Pitch factor (1.0 = normal) speed factor (1.0 = normal) So what could I do to get a clearer tone quality. Raise the sample rate? Prefilter the voice signal (bandpass), compress the volume range? Record with more bit depth than necessary? what are your ideas on this subject? Warmly yours Julien ---------------------------------------- http://juliencoder.de/nama/music.html

13 years, 4 months

Re: [LAU] Buying a new soundcard.

by Gerhard Zintel

Subject: Re: [LAU] Buying a new soundcard. Date: Monday 10 September 2012, 14:33:56 From: Gerhard Zintel <gerhard.zintel(a)mrs-thomas.de> To: linux-audio-user(a)lists.linuxaudio.org > > Are the recommendations here still accurate: > > http://wiki.linuxmusicians.com/doku.php?id=hardware#recommendations > > This Wiki article is pretty up to date: > http://wiki.linuxaudio.org/wiki/current_audio_gear > That's a page with really good information for anyone who want's to buy new audio gear for Linux - thank you! But - I can not find any link to this page from the frontpage of the Wiki http://wiki.linuxaudio.org/wiki/start or from any other Wiki page except for its Sitemap. If this is true that's a big drawback. How should someone be able to find this important information? If I have missed it, can please anyone enlightens me where I have to look. If there is no link available I'd advocate to create one on the Frontpage. The content of current_audio_gear page deserves it. Gerhard

13 years, 4 months

Re: [LAU] [off-list] Buying a new soundcard.

by Arve Barsnes

On 11 September 2012 11:47, Arve Barsnes <arve.barsnes(a)gmail.com> wrote: > On 11 September 2012 11:24, Florian Paul Schmidt <mista.tapas(a)gmx.net> wrote: >> Interesting. Did you perform or have sources for measurements? Or is this a >> technical limitation of USB MIDI? And if so, could you elaborate on that? >> >> Thanks, >> Flo >> >> >> On 09/11/2012 11:10 AM, Ralf Mardorf wrote: >>> >>> On Tue, 2012-09-11 at 10:46 +0200, Florian Paul Schmidt wrote: >>>> >>>> I wouldn't put too much weight on MIDI. You can get USB midi devices for >>>> ca. 10 bucks (whatever currency :D).. >>> >>> [off-list] since my provider's server is blackhole listed and mails >>> don't come through the list at the moment. >>> >>> USB MIDI devices do cause too much jitter. Further to my RME's PCIe >>> MIDI, I use two TerraTec EWX 24/96 PCI cards, for MIDI only. Such a >>> TerraTec or any other simple stereo Envy24 card does cost around 30 >>> EUR/USD at Ebay and does protect against too much MIDI jitter. For >>> serious MIDI work one hw interface anyway isn't enough. >>> >>> Regards, >>> Ralf >>> >> > > I already have one of those super cheap MIDI USB devices, and in > addition to what Ralf is saying above, which I can't confirm or deny, > it's been nothing but trouble. > > As for eBay, yeah, I noticed already yesterday that there are always a > bunch of the Delta 1010 for sale, but for big stuff like this, not > many sellers ship abroad, and I live in Europe. > > Regards, > Arve Things popped off-list there for a bit, see above for some stuff Ralf provided. I just started wondering if I could even use the 1010 if I got that, since I'm not sure if I have any PCI ports at all. I have a few express ports, but lspci only shows this about regular PCI: 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) Not sure what that means. I have a firewire port though, maybe that is actually the way I should be looking. Arve

13 years, 4 months

[LAU] An article about Nama & My new website

by S. Massy

Hello, all, You may have heard a few of us occasionally speak of an arcane piece of software called Nama and have wondered in passing just exactly what it is. Well, I have just posted an article attempting to explain that. The first half of the article is somewhat autobiographical and may safely be skipped bu those unwilling to learn more about the author than they rightly need to, but the second half should prove instructive to those who may have heard of Nama and Ecasound but have lacked the time or energy to investigate. The publication of this article also marks the opening of my new website www.wolfdream.ca which is mainly meant to showcase my writing but will hopefully include further articles about Linux, audio, and accessibility issues, as well as my audio work and, maybe, (god willing) some recordings of my own. If you think you might care to be exposed to such things, please bookmark the site or subscribe to the RSS feed. The article: http://www.wolfdream.ca/article3 Thanks for reading. Cheers, S.M. --

13 years, 4 months

[LAU] BCF2000, qjackctl and ardour

by Kevin Cosgrove

Hiya, A few years back I was using my BCF2000 with ardour. After upgrades to my computer hardware and Linux distribution the combination no longer works. The BCF shows up in /proc/asound fine. I can send and receive data with the BCF using amidi. The test of tracing communication between the BCF and ardour fails. I think this is because the mcu (port?) of ardour isn't connected to the BCF. But, qjackctl won't let me connect those. They don't show up in the MIDI tab of qjackctl. They only show up in the ALSA tab of qjackctl. A long time ago there was an issue with my distribution where qjackctl wasn't linked against libasound. But, that's not the problem this time around. I know people would need more info from me to help me troubleshoot this. But, I'd rather not spew 5-6 pages of stuff to the list. What would be useful here? Thanks.... -- Kevin

13 years, 4 months

[LAU] Buying a new soundcard.

by Arve Barsnes

Looking into upgrading my old failing usb sound card, and go for something slightly more professional. Are the recommendations here still accurate: http://wiki.linuxmusicians.com/doku.php?id=hardware#recommendations The M-Audio Delta line seems great for my little home studio, but since the page hadn't been updated for a year I thought I'd check in with the list first! Regards, Arve

13 years, 4 months

[LAU] New music video : Song for Nicole #musicmadewithlinux

by Patrick Shirkey

Hi, Some of you into the esoteric, ambient and psychedelic may be interested in a new music video I put up on youtube. http://linuxmusicvideos.com/2012/09/song-for-nicole-kotau/ Created with Blender, Ardour2, Hydrogen, AlsaModularSynth, Alsaplayer, LADSPA (calf reverb) with a contribution from another artist too. CC-By-SA , length - 3:10 If you like it, share it. -- Patrick Shirkey Boost Hardware Ltd

13 years, 4 months

Re: [LAU] BCF2000, qjackctl and ardour

by Kevin Cosgrove

On 10 September 2012 at 18:50, "Len Ovens" <len(a)ovenwerks.net> wrote: > On Mon, September 10, 2012 5:57 pm, Kevin Cosgrove wrote: > > On 10 September 2012 at 15:14, Paul Davis <paul(a)linuxaudiosystems.com> > > wrote: > > > >> > A few years back I was using my BCF2000 with ardour. After upgrades > >> > to my computer hardware and Linux distribution the combination no > >> > longer works. > >> > > >> > The BCF shows up in /proc/asound fine. I can send and receive data > >> > with the BCF using amidi. > >> > > >> > The test of tracing communication between the BCF and ardour fails. > >> > I think this is because the mcu (port?) of ardour isn't connected to > >> > the BCF. But, qjackctl won't let me connect those. They don't > >> > show up in the MIDI tab of qjackctl. They only show up in the ALSA > >> > tab of qjackctl. > >> > > >> > >> run a2jmidid -e > > > Right now MIDI Driver is set to "raw". I'm not sure when or if > > I set that, or whether it might be the default. > > Try none. Raw takes the place of a2j With "seq" or with "none", then not only can I see the MIDI (not just ALSA) ports in qjackctl, but I can connect them. Setting the MIDI-Driver to "none" and using "a2jmidid -e" I get this out of a2jmidid: JACK MIDI <-> ALSA sequencer MIDI bridge, version 6 (a500771941cd42419a2418ee28259cde718a82bb) built on Wed Dec 31 16:00:00 1969 Copyright 2006,2007 Dmitry S. Baikov Copyright 2007,2008,2009 Nedko Arnaudov Bridge starting... Using JACK server 'default' Hardware ports will be exported. Cannot lock down memory area (Cannot allocate memory) Bridge started Press ctrl-c to stop the bridge port created: Midi Through [14] (capture): Midi Through Port-0 port created: Midi Through [14] (playback): Midi Through Port-0 port created: M Audio Delta 1010 [20] (capture): M Audio Delta 1010 MIDI port created: M Audio Delta 1010 [20] (playback): M Audio Delta 1010 MIDI port created: BCF2000 [24] (capture): BCF2000 MIDI 1 port created: BCF2000 [24] (playback): BCF2000 MIDI 1 port created: BCF2000 [24] (capture): BCF2000 MIDI 2 port created: BCF2000 [24] (playback): BCF2000 MIDI 2 port created: ardour [129] (capture): control port created: ardour [129] (playback): control port created: ardour [129] (capture): mcu port created: ardour [129] (playback): mcu port created: ardour [129] (capture): seq port created: ardour [129] (playback): seq port deleted: ardour [129] (capture): control port deleted: ardour [129] (capture): mcu port deleted: ardour [129] (capture): seq port deleted: ardour [129] (playback): control port deleted: ardour [129] (playback): mcu port deleted: ardour [129] (playback): seq port created: ardour [129] (capture): control port created: ardour [129] (playback): control port created: ardour [129] (capture): mcu port created: ardour [129] (playback): mcu port created: ardour [129] (capture): seq port created: ardour [129] (playback): seq port deleted: ardour [129] (capture): control port deleted: ardour [129] (capture): mcu port deleted: ardour [129] (capture): seq port deleted: ardour [129] (playback): control port deleted: ardour [129] (playback): mcu port deleted: ardour [129] (playback): seq That looks good to me. Setting the MIDI-Driver to "seq" also has no errors. Next I set ardour's conrol surface to Mackie. Ardour stalled for a bit, then produced the following text in the window where I started ardour: MackiePort::connect_any already connected MackiePort::connect_any already connected MackiePort::connect_any already connected mcu input: Channel mcu output: Channel 1 NoteOn NoteNum 32 Vel 01 NoteOn NoteNum 32 Vel 0 mcu input: Channel 1 NoteOn NoteNum 16 Vel 127 mcu output: Channel 1 NoteOn NoteNum 16 Vel 127 mcu input: Channel 1 Pitch Bend 7887 mcu output: Channel 1 Pitch Bend 7887 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 0 6b 69 63 6b 20 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 38 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 48 Value 70 mcu output: Channel 1 NoteOn NoteNum 24 Vel 0 mcu output: Channel 1 NoteOn NoteNum 33 Vel 0 mcu output: Channel 1 NoteOn NoteNum 17 Vel 127 mcu output: Channel 2 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 7 73 6e 61 72 65 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 3f 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 49 Value 70 mcu output: Channel 1 NoteOn NoteNum 25 Vel 0 mcu output: Channel 1 NoteOn NoteNum 34 Vel 0 mcu output: Channel 1 NoteOn NoteNum 18 Vel 127 mcu output: Channel 3 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 e 74 6f 6d 73 4c 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 46 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 50 Value 70 mcu output: Channel 1 NoteOn NoteNum 26 Vel 0 mcu output: Channel 1 NoteOn NoteNum 35 Vel 0 mcu output: Channel 1 NoteOn NoteNum 19 Vel 127 mcu output: Channel 4 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 15 74 6f 6d 73 43 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 4d 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 51 Value 70 mcu output: Channel 1 NoteOn NoteNum 27 Vel 0 mcu output: Channel 1 NoteOn NoteNum 36 Vel 0 mcu output: Channel 1 NoteOn NoteNum 20 Vel 127 mcu output: Channel 5 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 1c 74 6f 6d 73 52 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 54 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 52 Value 70 mcu output: Channel 1 NoteOn NoteNum 28 Vel 0 mcu output: Channel 1 NoteOn NoteNum 37 Vel 0 mcu output: Channel 1 NoteOn NoteNum 21 Vel 127 mcu output: Channel 6 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 23 68 69 68 61 74 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 5b 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 53 Value 70 mcu output: Channel 1 NoteOn NoteNum 29 Vel 0 mcu output: Channel 1 NoteOn NoteNum 38 Vel 0 mcu output: Channel 1 NoteOn NoteNum 22 Vel 127 mcu output: Channel 7 Pitch Bend 7893 mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 2a 6f 68 4c 20 20 20 20 f7 ] mcu output: System Exclusive (15) = [ f0 0 0 66 10 12 62 20 20 20 20 20 20 20 f7 ] mcu output: Channel 1 Controller 54 Value 70 mcu output: Channel 1 NoteOn NoteNum 30 Vel 0 mcu output: Channel 1 Controller 74 Value 82 mcu output: Channel 1 Controller 75 Value 65 mcu output: Channel 1 NoteOn NoteNum 23 Vel 0 mcu output: Channel 8 Pitch Bend 12349 mcu output: Channel 1 Controller 55 Value 0 mcu output: Channel 1 NoteOn NoteNum 31 Vel 0 mcu output: Channel 1 NoteOn NoteNum 94 Vel 0 mcu output: Channel 1 NoteOn NoteNum 93 Vel 127 mcu output: Channel 1 NoteOn NoteNum 70 Vel 0 mcu output: Channel 1 NoteOn NoteNum 31 Vel 0 mcu output: Channel 1 NoteOn NoteNum 114 Vel 127 mcu output: Channel 1 NoteOn NoteNum 113 Vel 0 mcu input: Channel 1 NoteOn NoteNum 110 Vel 127 mcu input: Channel 7 Pitch Bend 7744 mcu input: Channel 7 Pitch Bend 7600 mcu input: Channel 7 Pitch Bend 7536 mcu input: Channel 7 Pitch Bend 7456 mcu input: Channel 7 Pitch Bend 7360 mcu input: Channel 7 Pitch Bend 7280 mcu input: Channel 7 Pitch Bend 7216 mcu input: Channel 7 Pitch Bend 7088 mcu input: Channel 7 Pitch Bend 7040 mcu input: Channel 7 Pitch Bend 6976 mcu input: Channel 7 Pitch Bend 6864 mcu input: Channel 7 Pitch Bend 6736 mcu input: Channel 7 Pitch Bend 6512 mcu input: Channel 7 Pitch Bend 6464 mcu input: Channel 7 Pitch Bend 6352 mcu input: Channel 7 Pitch Bend 6336 Segmentation fault Well, at least they're communicating. Does this ring a bell with someone? How to proceed from here? Thanks again..... -- Kevin

13 years, 4 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user September 2012