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
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
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
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
It feels like my several year old PC will crap out soon for one reason
or another, so I need a replacement, better sooner than later.
This time it should be a laptop and I heard that formerly IBM and now
Lenovo thinkpads are of good build quality, even if they only come
with intel CPUs and cost an arm and a leg.
So, do you have any experience with those for audio work?
I'd be most interested in the T and R series and more recent models.
Also helpful would be some data that's impossible to find on websites:
- What chipsets are built in?
- do the usb buses and the like share interrupts with something nasty
like graphics?
Helpful commands to gather that data:
cat /proc/interrupts
lspci
lsusb
Thanks in advance for any help.
Regards,
Philipp
Hi Alex
> Adrian,
> Not sure what you are referring to regarding "Jonathan's email?".
This would have been the email that I sent to yourself, Adrian and (for his
reference) Pieter on 29 July 2009 to follow up on your initial post to LAD.
> Could you send that to me so I can see what it is about?
Here it is again for your reference.
====
I received this via the CCed mail from Adrian Knoth (thanks Adrian!). It
appears to have originated on LAD at some point but I somehow missed the
initial post there. Possibly it got lost in amongst the intense discussion
that's been going on over the last few days. :-)
> > I have tried the contact form on the FFADO website and through the email
> > address provided in the contact pages at the SourceForge.net project
> > page to
>
> I wonder why Pieter Palmers (head) has not already contacted you.
>
> Find his address CCed in this e-mail. I also CC Jonathan Woithe in case
> Pieter is on vacation, I haven't heard from him for weeks.
Pieter's been fairly quiet over the last few weeks - I think he's been
fairly busy on non-FFADO related things.
Anyway, I have no idea what your original query was since the mail from
Adrian didn't seem to include that information. If you want to point me to
the original or just forward me your query I'll do my best to address it.
====
This is the email what Adrian would be referring to.
On 31 July 2009 I sent another followup to your original LAD posting. This
one went to yourself and the list:
====
On Tue, 28 Jul 2009 23:42:02 you wrote:
> I have tried the contact form on the FFADO website and through the email
> address provided in the contact pages at the SourceForge.net project page
> to no avail. I'm not sure where else to ask except here. Are any of the
> FFADO developers on this email group that can provide a contact email that
> will garner a response?
I *think* I responded to an email later in this thread, but in case it was
missed feel free to contact me off-list about whatever it is you were
wanting to ask and I'll attempt to help you out.
====
I am very keen to talk to you about whatever information you require about
the FFADO project. Please drop me a line off-list and we can work through
it.
Regards
jonathan
Greetings,
Sorry for the forward. Kim Cascone sent this message to the LAU list, but I think it needs the Eyes Of LAD. His email is kim(a)anechoicmedia.com. AFAIK he does not sub to this group.
Here's Kim's text:
*********************
my config:
Dell Studio
Ubuntu 9.04
rt kernel 2.6.29.4-rt15-rt
jackd version 0.116.1 tmpdir /dev/shm protocol 24
Ardour 2.7.1 (built from revision 4296)
USB iMic audio interface
KOrg nanoKontrol
cpufreq-set - both cpu's are set to 2.0GHz and userspace
I'm trying to get Jack and Ardour set up/optimized for my fall tour
I'm using the rt kernel as stated above
my Jack settings are 44.1kHz: frames 512: periods 5
latency is not a huge issue for me since I'm only playing back audio for
a live mix situation
and xruns in Jack seem to be tamed to 0 during playback
my Ardour session is 30 minutes in length, has 8 tracks of audio, and
the fader levels are assigned to the nanoKontrol
everything works fine for the session except at some random point after
playing for a while I get a single short burst of AM sideband noise,
like I'm multiplying the audio on the mix buss by another audio signal
it doesn't happen (so far) more than once per session and it doesn't
seem to be correlated to anything like mix buss levels or clipping on a
single channel etc
is there a setting in Jack that I'm overlooking or has anyone
experienced a similar intermittent burst of noise in playback with
similar Jack settings? or if this topic has already been discussed can
someone point me to a link in the archives? I wasn't able to find
anything on a cursory search
================
-- also, I started Ardour from command line when Jack wasn't running
and I got three panels in the open dialog box -- one of them being a
Audio Setup panel
-- is there a way to see this panel after starting Ardour with Jack
already running?
***********************
Kim Cascone <kim(a)anechoicmedia.com>
> On Sun, Aug 2, 2009 at 8:25 AM, Patrick Shirkey
> <pshirkey(a)boosthardware.com <mailto:pshirkey@boosthardware.com>> wrote:
>
>
>
>
> This whole problem could have been solved if you had originally
> provided Ray with access to the source when he asked for it, but
> in essence you should be making your code available from the start
> at a public location.
>
>
> I did make the code available when he asked for it, as I've already
> stated. My understanding of the GPL is that it is not essential to
> post the code publicly, as long as it is made available on request. I
> certainly did that.
>
Sorry, I missed this previous statement. In this case then I don't see
how you have violated the terms of the GPL. If you provided the code
when requested that should have been enough.
I read in Ray's earlier posts on the issue that he had not received any
code.
> As far as I can tell, no parties in this group are damaged as a result
> of our efforts to provide the fruits of our labors. If there are
> developers who think they were damaged, they should write to me and
> state the case, then we can try to resolve it. However, I must
> speculate that this is very unlikely; we treat our developers as
> colleagues, not as adversaries.
>
Certainly your own party has been damaged due to the controversy that
has been stirred. However I don't see it as a permanent problem as it
seems that Ray has made his point and you have come to the party
and clarified the issue, even going so far as to publically release your
latest version of the code on Source Forge, IIUC.
Warmest regards.
Patrick Shirkey
Boost Hardware Ltd
Just on a more serious note, amidst all this mayhem and frivolity, we
forked a project recently to more specifically add and modify a set of
tools for a defined purpose.
Unlike this trainwreck, we not only tried our best to do so in a
decent way, but the original author was thoroughly civilised about it,
and showed a lot of class in his positive and encouraging responses.
I certainly learned a lot from the process, and have even more respect
for Chris (Cannam) as a result.
It goes without saying that if Chris can use anything we write, then
he's most welcome to do so, and has our encouragement as well.
There's a way to do this that doesn't involve throwing digital
hatchets or burning anyone at the stake.
Alex.
> www.openoctave.org
>
> midi-subscribe(a)openoctave.org
> development-subscribe(a)openoctave.org
>
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org