Linux-audio-dev May 2013

linux-audio-dev@lists.linuxaudio.org

45 participants
27 discussions

by Neil C Smith

Hi All, A new build of Praxis LIVE is now available for download. Praxis LIVE is an open-source, graphical environment for rapid development of intermedia performance tools, projections and interactive spaces. This release brings a range of new features for the video pipeline, OSC control, some major editing improvements (including copy & paste - who knew that would be so difficult to implement! :-) ), and the rather obviously missing stereo sample player, amongst many other tweaks and bug fixes. Praxis LIVE is available as a Linux .deb package, Windows .exe installer and as a .zip for un-installed usage (installed usage is recommended). Website (with downloads and manual) - http://code.google.com/p/praxis Release notes - http://code.google.com/p/praxis/wiki/ReleaseNotes Some of the new features are conspicuously under-documented at the moment. I'll improve this over the next few weeks, but feel free to fire questions via email. Best wishes, Neil -- Neil C Smith Artist : Technologist : Adviser http://neilcsmith.net Praxis LIVE - open-source, graphical environment for rapid development of intermedia performance tools, projections and interactive spaces - http://code.google.com/p/praxis OpenEye - specialist web solutions for the cultural, education, charitable and local government sectors - http://openeye.info

12 years, 2 months

[ANN] - Introducing the MOD - Your LV2 plugins at your feet

by Gianfranco Ceccolini

Dear Linux Audio users and developers We at AGR/HackLab are very proud to announce our newest creation: the MOD. In a nutshell, the MOD it is a programable Linux based hardware processor/controller with LV2 support. It’s main objective is to take the processing of any LV2 plugins to the stage. We will make a presentation at the 2013 LAC on saturday 11 of may, at 17:10. We hope to see some of you guys there! To make things more interesting there we also created the following - MOD Cloud, an online plugin repository - MOD Social Network, a place where MOD users can exchange their virtual pedalboards - MOD SDK - a software development kit - Control Chain - a hardware interface for external controllers You can see all costumer related info on the website www.portalmod.com/enand you can watch a video of the prototype working here http://portalmod.com/blog/2013/03/video-1-testando-o-prototipo/ The core software inside the MOD is Open Source and is being published at github (https://github.com/portalmod). You can download the LAC Paper at http://portalmod.com/blog/2013/05/mod-on-lac-and-berlin/. In it you will find an explanation of the MOD working structure, both software as hardware wise. As the MOD comprises both software (host and web-gui) and hardware which were not entirely predicted in the LV2 specification, there is some code to be added to the LV2 bundles in order to make it work nice on the MOD. All this added code refers only to the GUI and/or the controller. The actual audio code (the plugin .so file) is left intact. A LV2 without this extra code still will work, but will not have 100% of its potential. It will have a generic dashboard icon, no visible icon knobs and a generic controller display type. When using the MOD connected to your PC or tablet using the webgui you can browse the locally installed plugins (inside the MOD) as well as the ones that are online at the MOD Cloud, provided you PC / tablet is connected to the internet. The plugins from the cloud can be installed with a simple drag movement. The MOD Cloud is the place we expect to have the most interaction with the LAD comunity. It is a plugin repository divided in four sections: official, testing, contrib and commercial (any resemblance to apt-get’s sources.config is a mere coincidence...). The official branch is where you find the plugins uploaded by the MOD team. Most of them are well known open source plugins which were packaged with our gui and controller needed codes. The CAPS, CALF, INVADA, GUITARIX, MDA and many others are all there with custom HTML GUIs and some tweaks where needed. The testing branch is where you find all the plugins the MOD team wants to send to the official branch, but for any reason haven’t yet. The contrib branch is something like Arch Linux AUR. It is an open repository where you, the developers, can upload open source plugins to the MOD community. The commercial branch is just like the contrib, but for closed plugin to be sold to MOD users. We expect to generate a feasible business model for all LAD developers which intend to make a living on audio plugin programming. Last but not least there is the MOD SDK. The main goal of the SDK is to make it simple to set a GUI to your plugin before installing it into your MOD. We think that when using the SDK the developers will be able to concentrate on their audio code and spend the least amount of time with interface programming. The SDK has a package of ready available resources (pedal and rack skins, knobs, layout templates) with which you can pack your plugin by completing a simple wizard. There is also the documentation needed to create new screen widgets in order to develop your own custom plugin GUI. The included resource code can also be used as example. We would like to thank all the LAD community for its ongoing efforts towards having a decent plugin structure for linux audio. For the developers of the plugins we are packing we’d like to know whether you guys have any kind of objections. We believe that a lively MOD users community would expand the LAD plugins userbase and thus open new possibilities for developers. We hope you all like what we are doing and we would love to discuss further details with you. Kind Regards Gianfranco Ceccolini The MOD Team

12 years, 2 months

[ALPHA] ladspa.m.lv2 - Some questions :D

by Florian Paul Schmidt

Hi, These last few days I found some time to work on ladspa.m.lv2, an LV2 plugin to load ladspa.m.proto instrument definition files: https://github.com/fps/ladspa.m.lv2 It is in a somewhat usable state, i.e. used in ardour3 it loads the example instrument generated by this python script: https://github.com/fps/ladspa.m.proto/blob/master/example_instrument.py which is a very simple polyphonic sawtooth synth with exponential envelopes and an echo with differing delay times per voice. There's still some things to do (e.g. expose control ports, implement All-Notes-Off midi messages, lots of optimizations - right now I care more for correctness than for efficiency, etc.) and I also have some questions: 1] This one is regarding waf. I'm not used to writing wscript files and I adapted the whole thing from the example sampler from the LV2-distribution. I wonder how I can make waf to use e.g. -fPIC and other compiler flags needed for my 64-bit system. Right now I have put a little makefile into the repository which passes the missing options along as CXXFLAGS environment variable. This is a dirty hack. So if anyone waf guru might want to take a look, I'd be so ever grateful. https://github.com/fps/ladspa.m.lv2/blob/master/makefile https://github.com/fps/ladspa.m.lv2/blob/master/wscript 2] I'm a little bit puzzled by how the patch_set messages together with the LV2 worker extension works. If you take a look at this run() function https://github.com/fps/ladspa.m.lv2/blob/master/instrument.cc#L702 you'll see that I have an extra LV2_ATOM_SEQUENCE_FOR_EACH at the start of the function to process the patch_set messages. I tried to integrate that into the loop later on (that iterates over the sample_count frames and lets the midi events take effect at their respective frame), but once I do that, patch loading stops to work. I must be missing something fundamental. So if any LV2 guru might want to take a look, I'd be very grateful, too Thanks and have fun, Flo -- Florian Paul Schmidt http://fps.io

12 years, 2 months

LAC2013 starts now!

by IOhannes m zmölnig

Dear all, at 10:00am (in about 10 minutes), the Linux Audio Conference 2013 is about to start. There is a live stream available, so you can follow the event, even if you have not made it physically to Graz http://lac.linuxaudio.org/2013/stream Remote participants are invited to join #lac2013 on irc.freenode.net[1], to be able to take part in the discussions, ask questions, and get technical assistance in case of stream problems. See you on the conference - here and everywhere fgmdasr IOhannes [1] http://webchat.freenode.net/?channels=lac2013

12 years, 2 months

Yoshimi 1.1.0

by Jeremy Jongepier

Dear all, There she is, Yoshimi 1.1.0! Looking better than ever, working better than ever, capable of doing more than ever. Simply put, better than ever. Made possible by the much appreciated and very valuable help, contributions and feedback from the Linux Audio community. http://downloads.sourceforge.net/yoshimi/yoshimi-1.1.0.tar.bz2 For this release I'd like to thank the following people in particular but in no particular order: * Kristian Amlie for making Yoshimi less CPU hungry. * Andrew Deryabin for making Yoshimi a little more CPU hungry again, but for a good reason, Yoshimi now has per part JACK outputs! * Nikita Zlobin for having Yoshimi handle state files better. * Florian Dupeyron for his custom best of My?terious bank. * Will J. Godfrey for his continuous testing and monitoring of new developments. * Alessandro Preziosi for Yoshimi's lovely new knobs. * David Adler for the AZERTY virtual keyboard support. * Rob Couto for the helpful insights and general help. * Alan Calvert. Best regards, Jeremy Jongepier

12 years, 2 months

Two strange problems

by Fons Adriaensen

I'm preparing a seminar that will take place tomorrow (4 May), it will involve live mixing of surround sound using Ardour. While setting up the PC to be used, two problems occured. The first one is solved, but its cause remains misterious. A some point it appeared that the sound card (HDSP-MADI, used every day since years) had decided to meet its creator. Every program trying to access it - from jackd to aplay -L not only blocked, but turned out to be impossible to kill. Replaced the card - same result. It turned out to be a corrupt /var/lib/alsa/asound.state. The systemd service doing the 'alsactl restore' while booting choked on it, blocked, and this apperently blocked all others trying to use the card later. What I don't understand is how alsactl exactly failed, and why these processes seemed to be immune to a 'kill -9'. The second one is an Ardour2 session that worked perfectly on another similar PC, but becomes completely unresponsive on the one to be used. It has four mono tracks and three 10-channel ones, and little else. DSP load is not the problem, it's less than 15%. Things look like it's the graphics. When Ardour's playhead reaches the right end of the editor window, it takes something like 5 seconds for the editor display to update - everything seems to freeze during that time but audio is not interrupted. Same when trying to scroll or change the zoom factor. Video card is Nvidia GeForce 7300, indeed quite old, but the same PC does full-screen HD youtube videos without problem. Video driver is nouveau as nv seems to be no longer supported by Archlinux. I'm pretty sure this system didn't have such problems when it was using nv. OTOH nouveau works very well on other systems... I could try and install the proprietary Nvidia driver, but with just some hours to go I'd rather not take any risks... Any hints ? 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)

12 years, 2 months

How do I write meta data into a wave file? (Command line tools?)

by Nils Gey

Hello list, libsndfile-info shows various useful information like the one at the end of this mail. I have Sonatina Symphonic Orchestra waves here (violins 1) and a one note wave includes "Midi Note", "Loop Count" and "Cue Start : 92078 End : 223977", which is the actual loop start/end Is this custom data or does it follow a standard? And no matter what, how do I write that into my own wave files? I would prefer command line tools. But programming interfaces are fine as well. Greetings, Nils $ sndfile-info test.wav Version : libsndfile-1.0.25 ======================================== File : test.wav Length : 896548 RIFF : 896540 WAVE fmt : 16 Format : 0x1 => WAVE_FORMAT_PCM Channels : 2 Sample Rate : 44100 Block Align : 4 Bit Width : 16 Bytes/sec : 176400 data : 895916 *** SAUR : 512 (unknown marker) smpl : 60 Manufacturer : 0 Product : 0 Period : 22675 nsec Midi Note : 76 Pitch Fract. : 0 SMPTE Format : 0 SMPTE Offset : 00:00:00 00 Loop Count : 1 Cue ID : 0 Type : 0 Start : 92078 End : 223977 Fraction : 0 Count : 0 Sampler Data : 0 End ---------------------------------------- Sample Rate : 44100 Frames : 223979 Channels : 2 Format : 0x00010002 Sections : 1 Seekable : TRUE Duration : 00:00:05.079 Signal Max : 31468 (-0.35 dB)

12 years, 2 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 May 2013