Linux-audio-dev January 2014

linux-audio-dev@lists.linuxaudio.org

50 participants
26 discussions

by Frank Kober

Hi, QMidiArp 0.5.2 has just seen the light of the day. It brings mainly two improvements. One is a comeback, that of tempo changes on the fly, and that now includes also tempo changes of a potential Jack Transport master. Also the Jack Transport starting position is finally taken into account, so that QMidiArp should be in sync also when starting the transport master not at zero. The second one is Non Session Manager support, mainly thanks to the work done by Roy Vegard Ovesen! Note that for compiling in NSM support you will now need liblo as dependency. Enjoy, and enjoy LAC in Graz this year Frank ________________________________ QMidiArp is an advanced MIDI arpeggiator, programmable step sequencer and LFO. Everything is on http://qmidiarp.sourceforge.net qmidiarp-0.5.2 (2013-05-09) New Features o Tempo changes are again possible while running, both manually or by a Jack Transport Master o Jack Transport position is now taken into account when starting, QMidiArp used to start always at zero o Muting and sequencer parameter changes can be deferred to pattern end using a new toolbutton o Modules in the Global Storage window have mute/defer buttons o Global Storage location switches can be set to affect only the pattern o Non Session Manager support with "switch" capability (thanks to Roy Vegard Ovesen) General Changes o NSM support requires liblo development headers (liblo-dev package)

10 years, 3 months

OpenAV Productions : Sorcer

by Harry van Haaren

Hey Everybody, I'm happy to announce OpenAV productions: http://openavproductions.com OpenAV productions is a label under which I intend to release my linux-audio software projects. The focus of the software is on the workflow of creating live-electronic music and video. The release system for OpenAV productions is one based on donations and time, details are available on http://openavproductions.com/support Sorcer is a wavetable synth, and is ready for release. Check out the interface and demo reel on http://openavproductions.com/sorcer Greetings from the LAC, -Harry

10 years, 8 months

itop

by elboulangero

Hello everyone, lately I had to fight big XRUN troubles, and thanks to this forum I finally solved that. This excellent thread saved me: http://linuxaudio.org/mailarchive/lau/2012/9/5/192706 On my long quest, I tried to see a little bit more what happened with the IRQs on my system. I searched for a kind of 'top' utility to monitor the interrupts, but the only apps I found were either deprecated, or missed some cool features. So, I ended up writing my own tool to monitor the file /proc/interrupts. It's available a this address: https://gitorious.org/elboulangero/itop As its name indicates, it behaves pretty much like top, but for interrupts. It's quite a simple thing, that I tried to enhance a bit with some cool features: + refresh period can be specified. + two display modes: display interrupts for every CPU, or only a sum of all CPU. + display every interrupt (sorted like /proc/interrupts), or only active interrupts (sorted by activity). + in case the number of interrupts changes during the execution of itop (due to a rmmod/modprobe), it's handled without any fuss. + command-line options are also available as hotkeys for convenience. + at last, the program display a summary on exit. The idea is that this summary could be copied/pasted in emails to help debugging. If anyone is interested, feel free to try and comment ! Cheers

10 years, 8 months

Support for Steinberg UR22 (Yamaha USB chipset 0499:1509)?

by cullinan＠rocketmail.com

Hi, there! I just got a Steinberg UR22 USB<->Audio / MIDI interface for my semi-prof. DJ work. I am working on Linux (only), but wanted to give this new product a chance. Well, it's basically a nice device but with an Yamaha chipset in it which seem unfortunately not supported from the latest (3.7.9) linux kernel(s). My questions are: - How likely is it to get this device fully supported on linux? - What needs to be done to get this device fully supported? I am an electrical engineer and did some linux device driver development in the past on some DMA stuff, but I am quite new to linux audio. But I am willing to help somewhere... I could try to reverse-engineer the USB stuff on Windows with the usbmon/usbsnoop/libusb things... But if it's too much work, to get it working, I could also just decide to send it back to Steinberg and thank them for not supporting Linux with their products. The USB information I could get is: $ aplay -l doesn't list that device $ lsusb ... Bus 002 Device 016: ID 0499:1509 Yamaha Corp. ... (See the more comprehensive $ lsusb -v below...) Related USB devices are: 0499:1501 Yamaha 0499:1507 Yamaha THR10 0499:1509 Yamaha Steinberg UR22 (what I am talking about) 0499:150c Yamaha THR10C Related search resuls are: Getting a Steinberg CI1 USB audio interface to work http://ubuntuforums.org/showthread.php?t=1696336 Yamaha THR10 amp / USB2.0 audio interface http://linux-audio.4202.n7.nabble.com/Yamaha-THR10-amp-USB2-0-audio-interfa… Thank you, Clemens (different one as in last link) -----8<----- $ lsusb -v -d 0499:1509 Bus 002 Device 014: ID 0499:1509 Yamaha Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x0499 Yamaha Corp. idProduct 0x1509 bcdDevice 1.00 iManufacturer 1 Yamaha Corporation iProduct 2 Steinberg UR22 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 442 bNumInterfaces 5 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 0a 24 01 00 01 34 00 02 01 02 ** UNRECOGNIZED: 0c 24 02 01 01 01 00 02 03 00 00 00 ** UNRECOGNIZED: 09 24 03 02 01 03 00 01 00 ** UNRECOGNIZED: 0c 24 02 03 03 06 00 02 03 00 00 00 ** UNRECOGNIZED: 09 24 03 04 01 01 00 03 00 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 01 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 44 ac 00 80 bb 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x07 EP 7 OUT bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x002a 1x 42 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 01 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 88 58 01 00 77 01 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x07 EP 7 OUT bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x004e 1x 78 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 01 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 10 b1 02 00 ee 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x07 EP 7 OUT bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0096 1x 150 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 04 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 44 ac 00 80 bb 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x002a 1x 42 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 04 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 88 58 01 00 77 01 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x004e 1x 78 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 3 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 07 24 01 04 01 01 00 ** UNRECOGNIZED: 0e 24 02 01 02 03 18 02 10 b1 02 00 ee 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x86 EP 6 IN bmAttributes 5 Transfer Type Isochronous Synch Type Asynchronous Usage Type Data wMaxPacketSize 0x0096 1x 150 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 3 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 3 bInterfaceProtocol 255 iInterface 0 ** UNRECOGNIZED: 07 24 01 00 01 24 00 ** UNRECOGNIZED: 06 24 02 02 01 00 ** UNRECOGNIZED: 09 24 03 02 01 01 01 01 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 4 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 ** UNRECOGNIZED: 07 24 01 00 01 24 00 ** UNRECOGNIZED: 06 24 02 02 01 00 ** UNRECOGNIZED: 09 24 03 02 01 01 01 01 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0000 (Bus Powered) -----8<-----

10 years, 9 months

Releasing source code is not enough, I think...

by Filipe Coelho

Hi there everyone, specially developers. I think we should stop assuming releasing source code is enough. [GNU/] Linux is getting more user friendly, and most users are not able to compile software, plus some distributions make it specially hard (debian, ubuntu, fedora, opensuse) by having the libs installed but not the headers. Releasing software on windows or mac, even open-source, *always* comes in a binary, and most users come from there. Now, I have a "toolchain" repository for ubuntu 10.04 with gcc4.8, python3+qt4 and a bunch of other useful stuff. I use this to get generic linux binaries that (from what I know) work everywhere. I can make a developer-oriented tutorial on how to use that, so that developers can provide linux binaries to its users. Would that be something useful to Linux Audio?

10 years, 10 months

Call for testing (final): ALSA driver for some firewire devices

by Takashi Sakamoto

Hi all, This is a final call for testing my ALSA drivers for some firewire devices. Please test my drivers if you have some devices listed in the end of this mail. Or please contact to me if you have some deviices listed as 'able to be supported'. About the way to install drivers, please refer to my previous post: [LAD] Call for testing: ALSA driver for Fireworks/BeBoB based devices http://lists.linuxaudio.org/pipermail/linux-audio-dev/2013-October/034344.h… I've already posted my last RFC to alsa-devel. So this may be a final call. Please read my previous mail for testing. [alsa-devel] [RFC v3] [PATCH 00/52] Enhancement for support of firewire devices http://mailman.alsa-project.org/pipermail/alsa-devel/2014-January/071820.ht… I have one request to you. Currently I'm preparing merge-request to ALSA. Then I want to add testers' name into the patches with 'Tested-By' field. Of cource, testers can reject it. Please inform me if you hope or not when reporting. [Currently supported devices] snd-bebob: * Edirol, FA-66 * Edirol, FA-101 * Presonus, FIREBOX * PreSonus, FP10 (former known as FIREPOD) * PreSonus, Inspire1394 * BridgeCo, RDAudio1 * BridgeCo, Audio5 * Mackie, Onyx 1220/1620/1640 (Firewire I/O Card) * Mackie, d.2 (Firewire Option) * Stanton, ScratchAmp * Tascam, IF-FW DM * Behringer, XENIX UFX 1204 * Behringer, XENIX UFX 1604 * Behringer, Digital Mixer X32 series (X-UF Card) * Apogee Electronics, Rosetta 200/400 (X-FireWire card) * Apogee Electronics, DA/AD/DD-16X (X-FireWire card) * Apogee Electronics, Ensemble * ESI, Quatafire610 * AcousticReality, eARMasterOne * CME, MatrixKFW * Phonic, Helix Board 12 MkII * Phonic, Helix Board 18 MkII * Phonic, Helix Board 24 MkII * Phonic, Helix Board 12 Universal/18 Universal/24 Universal * Lynx, Aurora 8/16 (LT-FW) * ICON, FireXon * PrismSound, Orpheus * PrismSound, ADA-8XR * TerraTec Electronic GmbH, PHASE 88 Rack FW * TerraTec Electronic GmbH, PHASE 24 FW * TerraTec Electronic GmbH, Phase X24 FW * TerraTec Electronic GmbH, EWS MIC2/MIC8 * Terratec Electronic GmbH, Aureon 7.1 Firewire * Yamaha, GO44 * YAMAHA, GO46 * Focusrite, SaffirePro 26 I/O * Focusrite, SaffirePro 10 I/O * Focusrite, Saffire(no label and LE) * M-Audio, Firewire 410 * M-Audio, Firewire Audiophile * M-Audio, Firewire Solo * M-Audio, Ozonic * M-Audio NRV10 * M-Audio, ProFireLightbridge * Firewire, 1814 * M-Audio, ProjectMix I/O snd-fireworks: * Mackie(Loud), Onyx 400F * Mackie(Loud), Onyx 1200F * Echo Audio, AudioFire2 * Echo Audio, AudioFire4 * Echo Audio, AudioFirePre8 * Echo Audio, AudioFire8 * Echo Audio, AudioFire12 * Gibson, Robot Interface Pack snd-oxfw: * Griffin, FireWave * Lacie FireWire Speakers * Behringer,F-Control Audio 202 * Mackie, Onyx-i series (former models) * Mackie, Onyx Satellite [IDs are unknown but able to be supported] snd-bebob: * Apogee, Mini-ME Firewire * Apogee, Mini-DAC Firewire * Behringer, F-Control Audio 1616 * Behringer, F-Control Audio 610 * Cakawalk, Sonar Power Studio 66 * CME, UF400e * ESI, Quotafire XL * Infrasonic, DewX * Infrasonic, Windy6 * Mackie, Digital X Bus x.200 * Mackie, Digital X Bus x.400 * Phonic, HB 12 * Phonic, HB 24 * Phonic, HB 18 * Phonic, FireFly 202 * Phonic, FireFly 302 * Rolf Spuler, Firewire Guitar snd-oxfw: * Mackie(Loud), d.2 pro * Mackie(Loud), d.4 pro * Mackie(Loud), U.420 * Mackie(Loud), U.420d * Mackie(Loud), Tapco Link.Firewire Regards Takashi Sakamoto o-takashi(a)sakamocchi.jp

10 years, 11 months

Release of new WORLD-based voice synthesizer

by Tobias Platen

Hello WORLD is a free software speech synthesizer on the basis of a Vocoder. It has been widely used as a backend for UTAU[1] but it should be also possible to use it as a backend for eSpeak and other accessibility and/or music applications such as the "Singing Computer"[2]. My modified version of WORLD uses the well known vorbis codec for compression. The world4espeak synthesizer is interface compatible to MBROLA, and can be used to synthesize both singing and speech in real time on a modern computer. It is hosted at gitorious.org [3]. Currently there are no voices yet, a manual how to create voices will be published soon. Tobias Platen [1] http://en.wikipedia.org/wiki/Utau [2] http://devel.freebsoft.org/singing-computer [3] https://gitorious.org/sekai

10 years, 11 months

Converting specimen banks to petri-foo

by Thomas Mayer

Hi, I have played around with petri-foo the first time, and I am thinking about switching from specimen to it. Is there a utility to convert specimen banks to petri-foo banks? As far as I can tell, it is a simple XML transformation, and I would try that, if such a utility does not exist. Thanks, Thomas -- "Ich komme aus dem Staunen nicht heraus." "Dann bleib halt drin, du Seppel" (Dietmar Dath - Die Abschaffung der Arten) http://www.residuum.org/

10 years, 11 months

LAC 2014: the Linux Audio Conference - Deadline Extension

by Frank Neumann

Since this didn't make it yet to the LAD list, I thought I'd better forward it - --- Hi all, The Linux Audio Conference submissions deadline has been extended! It is now February 3rd, 2014 (23:59 HAST) So, if you were considering to submit a paper but couldn't make up your mind yet, here is your chance to become active! Never forget that this conference lives through the people participating in it. February 3rd is the new deadline for all submission types: papers, music, installations, workshop proposals. Check out the link below for more info: http://lac.linuxaudio.org/2014/participation Please spread this information to anyone who might be interested. If you have any questions, drop us a line at lac(a)linuxaudio.org We are looking forward to seeing you in Karlsruhe in May! Thanks, The LAC2014 organization team

10 years, 11 months

Re: [LAD] Releasing source code is not enough, I think...

by Filipe Coelho

On 01/21/2014 07:10 PM, John Hammen wrote: >> Then they should wait until their distro or someone else provides >> > >a package. Or pay someone to do the work for them, just as they >> > >have to for commercial software, or for the mechanic you mention. > > (...) > > the idea being: a person whose paid responsibility it is to make us > LAUs happy with fresh new packages and, ideally also work with folks > upstream on build sanity issues. Filipe, would you be willing to > supervise such a person, feed them the less fun parts of what you do > and check their work? If the community is willing to pay for it, sure. But I find that a bit hard to believe... There's a difference on how KXStudio repositories are done vs regular debian/ubuntu repos. Debian and Ubuntu usually build against a specific version, and don't usually do backports. on KX repos I'm starting build all packages the same way (ie, the generic linux builds), and update software very often (sometimes minutes after release :D ). I hate when distros only package new stuff for the their newest, unreleased/testing/upcoming version and completely ignore the users running stable versions... :(

10 years, 11 months

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-dev January 2014