Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7520 discussions

11th Real-Time Linux Workshop, September 28 to 30, Dresden, Germany

by Jörn Nettingsmeier

way over my head, but it would give me a warm fuzzy feeling if some hotshot linux audio people were attending: http://www.osadl.org/RTLWS-2009.rtlws-2009.0.html best, jörn

16 years, 4 months

Email from Beat Kangz

by Michael Fisher

For what its worth... I received this from AJ at Beat Kangz. Could have just been an honest mistake really. I still have mixed emotions. --- *Hey Guys* * * *I have personaly contacted the creators of the LADSP plug ins we used and let them know our plans etc. In a rush to get the product out the door we forgot to include those credits. Which is now corrected on everyone that goes out the door. If you notice we didnt include the manual either lol. We are finishing that today and will be posting it as well as emailing it to all our customers so far. It will also include the list of credits. We regret not having it in the initial release and we have corrected that. in addition we will send them free copies etc.* * * *"That would be pretty awesome if they decided to open development"* This is exactly why we chose to go with LADSPA instead of VST. We want to shine a big spotlight on that dev community and also Donate funds to further help them create cool plug ins. We would even love to create a dedicated page on our site where they can sell or give away their creations and benefit from our marketing efforts. The more plugins the better for all of us! We are also now looking for talented programmers to write cool synths we can use too...... If you guys know who can do that, send them my way. We appreciate your biz Michael and hope you enjoy the product. Ronald I also appreciate your call today and hope we can find ways to work on projects together in the future. Give me some time to get this Thang off the ground and by 2010 i may be able get you those angels you are looking for. Peace and Respect AJA Prez of tha kangz

16 years, 4 months

Impro-visor source code and fork

by laseray＠gmail.com

Hi all, If anybody is interested, I have decompiled the latest Impro-visor version, which has only been provide as a binary (in contradiction to the terms of the GPL). So if you want the source code just let me know and I will send it. I'm sure it won't compile immediately, since there are a number of incorrect constructs returned by the decompilation. I will work on this in the next while to have it compile. I think someone else mentioned they posted the older binary/source somewhere. Perhaps this can be hosted at the same location (have to look back to see where that is/who posted). Apart from that, I will be looking into forking Impro-visor in the next few days. After making contact with the responsible parties about the GPL violations, I have received no reply and the source code has not been posted along with the binaries as is legally required. I also contacted the department head at the institution responsible for this work to see if they would look into the matter. Perhaps they can sort this out in the next little while. Failing that, I will probably start a new project on SourceForge and be looking to put together a development team. Contributions to the software by users will also be welcome. There will be a need for new leadsheets, transcriptions, documentation, and even translations of the user interface. Cheer, Raymond

16 years, 4 months

GPL Violation Alert! - I talked with the President of Beat Kangz Today

by Ronald Stewart

GPL Violation Alert! - I talked with the President of Beat Kangz today his name is A.J. and he is a sweetheart and his head is on straight. He is currently going to work on an official statement and he wants to embrace and thank the developers and give the authors credit on their software and materials moving forward. Additionally, Beat Kangz is interested in opening up development with authors to make Beat Kangz even better including funding open source development and projects. I think the hiccup is that they didn't know how to properly thank/engage in regards to GPL and such. It's sounds like more of a noob thing and definitely not a jerk thing. Let's give these guys the benefit of the doubt because their heads are on stragiht. Stay tuned. Much Love. Thank you Ronald Stewart Creative Director Trinity Audio Group Inc. 9854 National Blvd. #322 Los Angeles CA 90034 310-733-9285 ronaldjstewart(a)gmail.com www.indamixx.com

16 years, 4 months

Re: [LAD] [LAU] Python and MIDI orientation for a project

by Dominic Sacré

On Monday 03 of August 2009 23:06:34 harryhaaren(a)gmail.com wrote: > And on the topic for a second, python bindings exist for MidiDings, a > module that can use both AlsaSeq & Jack Midi. > I have a very limited amound of experince with it, as i found the > AlsaSeq python package to be much simpler to use. Just to clarify, mididings is primarily intended as a standalone MIDI processor. Usually its sole input/output is MIDI, and it just happens to use Python for its configuration. It's not really a MIDI API to be used in larger Python programs, and I'm pretty sure it completely sucks for that purpose. Now... who's going to finally write proper Python bindings for JACK MIDI? :) Dominic

16 years, 4 months

Re: [LAD] Python and MIDI orientation for a project

by Carlos Sanchiavedraz

Hi Harry. It's curious... you got the point I had in mind :) My main idea is to extend the configuration dialog so that, same as you can map wiimote keys/events to keyboard keys, you could map wiimote keys/events to CCs helped by a select box with a list of available CCs; first maybe a usefull and comprehensive subset and then the whole set in later versions. Maybe we can add the "advanced" section as well. But first I'm trying to get information about the other topics on my list :) Thanks Harry. //On my mobile device. Sorry for top-posting and any mistakes 2009/8/2, Harry Van Haaren <harryhaaren(a)gmail.com>: > Hey Carlos, > > Python & the wiimote is a nice combo, i've played with it and midi a little > too.. > Not at all familiar with desktop applet coding, so ill leave that to the > pro's! > > As far as the "what midi CC bindings" are useful, could you put in a > "Drop-down-box" or "Entry-Box" > for the CC's? Because there will always be some use for it. Perhaps have an > "Advanced" section, in > which one can manually type the CC Numbers, and have the "Simple" section > up > with a drop down of > the most common CC's? > > Becuase I can really see the use of having a wiiMote around for debugging > audio/midi progams with you applet. > It would mean you could easily send any Midi CC's to a program using an > "Easy-Access" unit. (IE: pick it up, use it, > not like a keyboard where you'd spend time mapping a key to a different > MIDI > CC etc) > > Hope the project goes well for you, once im home ill check how much is done > and where to get the Alpha release.. ;-) > -Harry > > > > > On Sun, Aug 2, 2009 at 3:32 PM, Carlos Sanchiavedraz > <csanchezgs(a)gmail.com>wrote: > >> I have notice I forgot to send this mail to LAD as well. Sorry :) >> >> Here it is. >> Of course, thanks in advance. >> >> >> ---------- Forwarded message ---------- >> From: Carlos Sanchiavedraz <csanchezgs(a)gmail.com> >> Date: Sat, 1 Aug 2009 19:18:17 +0200 >> Subject: Python and MIDI orientation for a project >> To: linux-audio-user <Linux-audio-user(a)lists.linuxaudio.org> >> >> Hi folks. >> >> I'm cooperating with a friend and fellow to improve his project >> related to wiimote. >> >> The project is Wiican[1]. In short, it is a tool (a system tray icon >> actually) that makes it easier to connect the wiimote and configure >> and create key mappings for use at your will. It's written in python >> and uses bluez, hal with dbus, wminput and cwiid. >> >> My goal is to add some layer in such a way that you can map wiimote >> events to MIDI. And maybe, to include it on the next improved release >> of Musix. >> >> So, in adittion to my researches on the subject and what I already >> know about MIDI CCs and so, I would like some advice and guidance >> about how to: >> - implement MIDI in python (which CCs are a must for you, create and >> send MIDI messages, libs, bindings, reference projects), >> - implement Jack and Alsa MIDI ports in python (libs, bindings, >> reference projects), >> >> ... and every other interesting information or experiences on this. >> >> Thanks in advance. >> >> [1] https://launchpad.net/wiican >> >> >> -- >> Carlos "Sanchiavedraz" >> * Musix GNU+Linux >> http://www.musix.es >> >> >> >> -- >> Carlos "Sanchiavedraz" >> * Musix GNU+Linux >> http://www.musix.es >> _______________________________________________ >> Linux-audio-user mailing list >> Linux-audio-user(a)lists.linuxaudio.org >> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user >> > -- Carlos "Sanchiavedraz" * Musix GNU+Linux http://www.musix.es

16 years, 4 months

Test app for LADSPA plugins

by Damon Chaplin

Hi, I've been having problems with a few LADSPA plugins recently, so I've written a little test app that loads all LADSPA plugins, connects the ports and runs them for one cycle. (I've attached it here.) I've run it on the plugin packages I have installed, using valgrind, and the results are: amb crashes blop memory errors (patches sent for some of the errors) calf memory errors in Flanger & MultiChorus plugins caps memory errors in 3 plugins cmt memory errors (patches sent) fil OK ladspa memory errors in Sine plugin (mismatched free/deletes) mcp OK rev OK swh crashes tap memory errors in 5 plugins vco OK Note that not all memory errors are bugs, but most are. (There's also a chance that my test app is buggy, rather than the plugins.) I've sent a few patches for cmt and blop, and will probably try to track down the bugs in a few other packages. If others want to help (especially the owners of the above packages!) that would be good. Damon

16 years, 4 months

List archives

by Arnout Engelen

Hi, There seem to be several archives of this list: http://lalists.stanford.edu/lad/ as linked to and searchable from http://lad.linuxaudio.org/archive/lad.html and http://lists.linuxaudio.org/pipermail/linux-audio-dev/ as linked to from http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev/ Additionally, there's search functionality at http://www.linuxaudio.org/search/swishmail/ .. and another, not very convenient archive at http://www.linuxaudio.org/mailarchive/lad This is a bit confusing. Perhaps we should replace the references to the archive hosted at stanford with references to http://lists.linuxaudio.org/pipermail/linux-audio-dev and http://www.linuxaudio.org/search/swishmail http://www.linuxaudio.org/mailarchive/lad is kindof neat, so I wouldn't want to propose doing away with it, but in its current form it's not too useful either: a 'thread view' of a whole month instead of only a single day would make it much better. What software is backing this? Perhaps we could upgrade/improve it. Regards, Arnout

16 years, 4 months

Re: [LAD] Python and MIDI orientation for a project

by Carlos Sanchiavedraz

Maybe I should start with the Alsaseq python package and HelperMudule, but I would like to have Jack MIDI so I'll give MidiDings a try. But remembering the field "Midi driver" on Qjackctl config I wonder, if it is set to alsa_seq you can see AlsaMidi ports on JackMidi tab, could it be better to choose Alsaseq python package because you could also have your MIDI port on JackMidi? (at least for a first release) Am I missing something? 2009/8/3, harryhaaren(a)gmail.com <harryhaaren(a)gmail.com>: > Hey, > > Just to say, I think this is mainly related to Lin-Audio-Dev, so I wont be > sending to lin-user in furthur replies.. > > And on the topic for a second, python bindings exist for MidiDings, a > module that can use both AlsaSeq & Jack Midi. > I have a very limited amound of experince with it, as i found the AlsaSeq > python package to be much simpler to use. > (It does however not support Jack Midi.) Might i suggest to use AlsaSeq > first if this is your first Python/Midi project, > despite there only being a few demos/tutorials for AlsaSeq, its a great way > to get acces to the Alsa Sequencer. > > AlsaSeq also has a "Helper-Module", called alsamidi, which helps creating > messages in a generic & easy way without > getting your hands dirty in Midi bytes, commands & the likes. (it comes > with the AlsaSeq tarball, so you'll get it automatically.) > > Cheers, -Harry > -- Carlos "Sanchiavedraz" * Musix GNU+Linux http://www.musix.es

16 years, 4 months

Re: [LAD] Python and MIDI orientation for a project

by Carlos Sanchiavedraz

You're right Harry. I succumbed to the temptation to reach to more people at the same time :). I'm replying on LAD. //On my mobile device. Sorry for top-posting and any mistakes 2009/8/3, harryhaaren(a)gmail.com <harryhaaren(a)gmail.com>: > Hey, > > Just to say, I think this is mainly related to Lin-Audio-Dev, so I wont be > sending to lin-user in furthur replies.. > > And on the topic for a second, python bindings exist for MidiDings, a > module that can use both AlsaSeq & Jack Midi. > I have a very limited amound of experince with it, as i found the AlsaSeq > python package to be much simpler to use. > (It does however not support Jack Midi.) Might i suggest to use AlsaSeq > first if this is your first Python/Midi project, > despite there only being a few demos/tutorials for AlsaSeq, its a great way > to get acces to the Alsa Sequencer. > > AlsaSeq also has a "Helper-Module", called alsamidi, which helps creating > messages in a generic & easy way without > getting your hands dirty in Midi bytes, commands & the likes. (it comes > with the AlsaSeq tarball, so you'll get it automatically.) > > Cheers, -Harry > -- Carlos "Sanchiavedraz" * Musix GNU+Linux http://www.musix.es

16 years, 4 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