Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7516 discussions

by Aurélien Leblond

Hello Sebastian, A few weeks ago when discussed on the LAD a few enhancements for Hydrogen, one of them was to be able to switch between open, half-open and closed hihat samples when playing with the hihat foot control on an E-Drum. In this fork https://github.com/blablack/hydrogen I worked out the basic backend solution: - instruments can be set to be part of a hihat - if they are, they have a range associated that say to what level of foot control pressure they react - in the midi_input class, when a 'note on' is received, the method will check if the instrument is a hihat, check the foot pressure and change the note played to the one of the right hihat instrument if needed I still need to modify the GUI (at the moment I need to change the xml of the drumkit to be able to set that up), but if you could have a look at this to give me some feedback that would be great. Thanks in advance, Aurélien

11 years, 6 months

DAW extra feature proposal: reversed clips, clip status info display

by Zlobin Nikita

There is one usage case, i can call - reversing recorded piano and some other instruments. One case, when sequencer and even instrument settings are not last step before mastering. I'm not expert and at all badly aware of existing music to mention examples, but i know at least one - in Black Mesa game - some soundtracks, marked as "mesa remix". I don't see it bad to mention such stuff there, since it is done completely by fans, no matter with what resources and software. Additionally, in gui clips may display inline status, with indicators for direction and all other clip-individual info, such as speed (probably, that's all - don't know, what other indicators are good to have there).

11 years, 6 months

ALSA frustration

by Fons Adriaensen

For the N-th time I've set aside a day to try and read some of the ALSA documentation. For the N-th time I've completely lost my way in a web consisting of * The complete lack of any documentation that explains the concepts, the big picture, and the terminology. * Completely useless docs, of the form: function xxx_set_yyy (parm_zzz) sets the yyy of xxx to zzz. or similar, in other words something generated automagically and completely uninformative and redundant. In particalur if it's impossible to find out what yyy is supposed to be or do in the first place. * Uncomprehensible English. * When trying to learn something from actual source code or examples, layer upon layer of syntactic sugar making it virtually impossible to understand what's going on. All this more than ten years after ALSA was announced. I *do* understand those hardware manufactureres who just refuse to try and write an ALSA driver. In this case my very humble endeavour was just to find out if or not it would be possible to create something similar to the alsa_jack plugin that would actually present itself as a sound card, so that (badly written) apps would be prepared to use it. If someone knows the answer to that question and can also explain it I'll commend him/her in my prayers. -- 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, 6 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

11 years, 6 months

[LAA] Guitarix 0.29.0 released

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, 6 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, 6 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, 6 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, 7 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, 7 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, 7 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