Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

4 participants
7502 discussions

by hermann meyer

The Guitarix developers proudly present Guitarix release 0.29.0 For the uninitiated, Guitarix is a tube amplifier simulation for jack, with effect modules and an additional stereo effect chain. Among with a couple changes in the source and some bug-fixes, this relase comes with a couple of new plugs (gx & LV2), were most of them comes from our new Development Member Fedor Uporov. The Simulation plugs been developed with the new Analog Circuit Simulation Toolkit by Andreas Degert. new plugs: * Record Mono/Stereo (gx) * JCM800PRE (Preamp simulation) (gx) * GCB_95 (WahWah simulation) (gx) * Duck Delay Mono/Stereo (gx / LV2) * Reverse Delay (gx) * Graphic EQ (gx / LV2) * Ring Modulator Mono/Stereo (gx) * Plate Reverb (gx) * Panorama Enhancer (gx) * Bass Enhancer (gx) * BarkGraphicEQ (24band LV2) Please refer to our project page for more information: http://guitarix.sourceforge.net/ Download Site: http://sourceforge.net/projects/guitarix/ Forum: http://guitarix.sourceforge.net/forum/ Please consider visiting our forum or leaving a message on guitarix-developer(a)lists.sourceforge.net <mailto:guitarix-developer@lists.sourceforge.net>

11 years, 2 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<-----

11 years, 2 months

ALSA docs

by Fons Adriaensen

Hello all, anyone knows where to find a state diagram for PCM devices ? What I want to find out in particular is - if a device supports the pcm_resume() function, and it returns 0, is a pcm_start() required or not (it is if pcm_resume() is not supported) ? Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)

11 years, 2 months

Transcribing piano rolls with Python

by Joel Roth

This guy isn't the only one to do it, but he's written it up nicely, and uses Lilypond and Frescobaldi for output. http://zulko.github.io/blog/2014/02/12/transcribing-piano-rolls/

11 years, 2 months

New kid on the block

by Will Godfrey

I've started making tentative steps towards improving yoshimi - in particular with respect to isolating MIDI, GUI and DSP. The jack ring buffer is already used for data transfers from jack midi to the dsp code, but I want to a) set up another buffer between jack midi and gui, and b) if possible, try to do the same for alsa midi. From what I've read, the jack ring buffer will happily work between any two threads on a garbage-in-garbage-out basis. However, around 2008 there was a lot of discussion about thread safety/memory barriers etc. Was this ever resolved? Also - and I don't know if this is actually a realistic situation - how would I handle an all alsa setup? Would there be anything preventing me just linking to the ring buffer itself? -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

11 years, 2 months

streaming multiple tracks with html5

by Patrick Shirkey

Hi, I can successfully play multiple independant tracks with html5 api. In order to achieve sample accurate glitch free playback I am using the prebuffer method. However, I would like to stream the media. Looking at the various options for streaming I have not run into a perfect solution for streaming multiple tracks with the html5 api. I can see several potential attack vectors. 1: extend icecast to support multiple tracks/stream 2: extend the JACK API to integrate with option 1 3: extend the html5 API - possible but it would need to have more than just me supporting the move. 4: custom solution with new/existing multichannel codec I'm sure that others have already thought about this problem so am I missing something obvious? This could be useful for other services like bandcamp, soundcloud, etc... I think we have an opportunity to guide the direction if we come up with a solid open source solution. *NB. This thread is intended to be a serious developer discussion. Please do not respond to this thread if you do not have specific information to add or discuss on this topic. -- Patrick Shirkey Boost Hardware Ltd

11 years, 2 months

[ANN] Vee One Suite 0.4.1 - A proto-beta bis release!

by Rui Nuno Capela

The Vee One Suite of (maybe not so anymore) old-school specialized instruments gets an update to a new bis encore... the changes for this second proto-beta release are: - once so called 'Noise' wave-shapes are now being made a lot more deterministic, read idempotent ;). - fully alias-free/band-limited wavetable oscillators are now in place, making it a better virtual-analog synthesizer (esp. for running sample-rates below 96KHz; synthv1 [1] only). - late optimizations to basic wave-table oscillators. - make sure the LV2 plugin back-end always builds first, before its respective LV2 UI front-end client. all still available in dual form: - a pure stand-alone JACK client with JACK-session, NSM (Non Session management) and both JACK MIDI and ALSA MIDI input support; - a LV2 instrument plugin. all made free and open-source Linux Audio software, distributed under the terms of the GNU General Public License (GPL) version 2 or later. and there they are: [1] synthv1 - an old-school polyphonic synthesizer synthv1 is an old-school all-digital 4-oscillator subtractive polyphonic synthesizer with stereo fx. LV2 URI: http://synthv1.sourceforge.net/lv2 website: http://synthv1.sourceforge.net downloads: http://sourceforge.net/projects/synthv1/files - source tarball: http://download.sourceforge.net/synthv1/synthv1-0.4.1.tar.gz - source package: http://download.sourceforge.net/synthv1/synthv1-0.4.1-15.rncbc.suse131.src.… - binary packages: http://download.sourceforge.net/synthv1/synthv1-0.4.1-15.rncbc.suse131.i586… http://download.sourceforge.net/synthv1/synthv1-0.4.1-15.rncbc.suse131.x86_… [2] samplv1 - an old-school polyphonic sampler samplv1 is an(other) old-school all-digital polyphonic sampler synthesizer with stereo fx. LV2 URI: http://samplv1.sourceforge.net/lv2 website: http://samplv1.sourceforge.net downloads: http://sourceforge.net/projects/samplv1/files - source tarball: http://download.sourceforge.net/samplv1/samplv1-0.4.1.tar.gz - source package: http://download.sourceforge.net/samplv1/samplv1-0.4.1-15.rncbc.suse131.src.… - binary packages: http://download.sourceforge.net/samplv1/samplv1-0.4.1-15.rncbc.suse131.i586… http://download.sourceforge.net/samplv1/samplv1-0.4.1-15.rncbc.suse131.x86_… [3] drumkv1 - an old-school drum-kit sampler drumkv1 is (yet) an(other) old-school all-digital drum-kit sampler synthesizer with stereo fx. LV2 URI: http://drumkv1.sourceforge.net/lv2 website: http://drumkv1.sourceforge.net downloads: http://sourceforge.net/projects/drumkv1/files - source tarball: http://download.sourceforge.net/drumkv1/drumkv1-0.4.1.tar.gz - source package: http://download.sourceforge.net/drumkv1/drumkv1-0.4.1-11.rncbc.suse131.src.… - binary packages: http://download.sourceforge.net/drumkv1/drumkv1-0.4.1-11.rncbc.suse131.i586… http://download.sourceforge.net/drumkv1/drumkv1-0.4.1-11.rncbc.suse131.x86_… see also: http://www.rncbc.org/drupal/node/775 enjoy && again, have fun! -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org

11 years, 3 months

wav composer not toilet non-release

by James Morris

Hello, After an intensive development of my ten year old project Wav Composer Not toilet, from September 2013 up to the new year, I was intending to make a new release in February, and then March, and then... Unfortunately an official release has not materialized so I'm just saying here is the code, do what the kcuff you like with it. -=-=-=-=-=-= What? Wav Composer Not Toilet is a text based non-professional non-realtime non-interactive modular audio synthesis, sampler, and sequencer by a hobbyist developer scratching an itch which has eased off for now. -=-=-=-=-=-= What's new? The main focus of recent development was intended to create greater flexibility for the user in how modules and 'data objects' are specified within a file. This flexibility allows: * arbitrary ordering of items * optional items * optional groups of items * multiple choice items * self connection of optional inputs This is available in the master branch and can be built like so: git clone https://github.com/jwm-art-net/wcnt.git cd wcnt sed -i 's/DEFS=-ggdb/#DEFS=-ggdb/' Makefile make make examples (the sed command above will remove debugging info that should be removed in a release). After running `make examples` look in the examples/ directory to see what wcnt has done. Wav Composer Not Toilet is hardcoded to use a limited selection of LADSPA plugins and no others, these are: * Bode Frequency Shifter * C* PlateX2 * DC Offset Remover * Fast Lookahead Limiter * Glame Low and High pass filters (+ Butterworth versions) * Single Band Parametric EQ The examples will fail to complete if these are not available. They reside in the C* (formerly Caps) and SWH LADSPA plugin suites. However, in the custom_names branch on github a generic LADSPA module is available which allows specification of arbitrary LADSPA plugins. It is working to a basic extent but unfinished. Carry on. char*s James Morris

11 years, 3 months

Re: [LAD] Input/output error alsa api

by Thiago Carísio

Hi Harry, Do you know if there is some rule to compiling using librtaudio? Because, there is an error..and i don't know what's wrong. I'm using g++ 4.7.2 and i'm compiling using: $ g++<programname.cpp> -o <programname> The error is: undefined reference to 'RtAudio::RtAudio(RtAudio::Api)' i'm including the lib in the program, normally! 2014-03-29 11:11 GMT-03:00 Thiago Carísio <thiago.carisio(a)gmail.com>: > Hi, Harry! > > I don't know...hehe...i'm just was searching for api's and alsa seemed to > be a good ideia. But, it's a bit difficult. I'm gonna take a look at this > others api's > > Thanks! > > > 2014-03-29 6:07 GMT-03:00 Harry van Haaren <harryhaaren(a)gmail.com>: > > Hi Thiago, >> >> Slightly other question: are you *sure* you want to write directly using >> the ALSA API? >> Generally, writing a JACK[1] client (for linux-pro-audio use-cases), or >> RtAudio[2] is a better idea, and easier in my opinion... >> >> They're easier to write to, and abstract away some of the details of the >> soundcard settings / channels etc. >> HTH, -Harry >> >> [1] >> https://github.com/jackaudio/example-clients/blob/master/simple_client.c >> [2] https://www.music.mcgill.ca/~gary/rtaudio/ >> >> >> On Sat, Mar 29, 2014 at 5:00 AM, Thiago Carísio <thiago.carisio(a)gmail.com >> > wrote: >> >>> Hi! I am Thiago and i'm starting to use the alsa api. I'm testing one >>> function to make the sound capture and i got this input/output error. I >>> don't get it why this is happening...so, please...some kind soul can help >>> me? >>> >>> Thanks >>> >>> _______________________________________________ >>> Linux-audio-dev mailing list >>> Linux-audio-dev(a)lists.linuxaudio.org >>> http://lists.linuxaudio.org/listinfo/linux-audio-dev >>> >>> >> >

11 years, 3 months

Re: [LAD] NetJack question

by Paul Davis

On Mon, Feb 24, 2014 at 12:48 PM, David J Myers < david.myers(a)amg-panogenics.com> wrote: > 0.121.2 is the version I got from ubuntu with apt-get install. > > I removed that version and downloaded and built 0.124.1, however when I > now try to run > > jackd -d alsa > > I get back > > jackd: unknown driver 'alsa' > > > > What's going on? > Your system is missing the development version of the ALSA library. So JACK was built without ALSA support. What version of Ubuntu are you using? I am unable to believe that 0.121 is the latest version available for any reasonably recent version of that distro. --p

11 years, 3 months

Jump to page:

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