Thread: [Pythonmidi-devel] And there was much rejoicing!
Status: Pre-Alpha
Brought to you by:
regebro
Menu
▾
▴
pythonmidi-devel
|
From: Lennart R. <le...@re...> - 2004-10-27 23:13:29
|
Welcome to this nice, clean spring-fresh (or autumn-fresh, rather) list. Although this list ends in "devel" and is ment for the discussion of the development of PythonMIDI, you are free to discuss anything remotely related for the moment, becuase this is the only list there is. ;-) After a first proper release has been done I guess a "user" list should be created as well. So, next step should be having a unix implementation of similarily basic level, and then a unification of these APIs. Also the low-level API needs to be extended with SysEx support. At the moment only short messages can be sent. I'm not sure ALSA distinguishes between them. Does anybody else know? and how about Mac OS X? Any Mac developer here? I assume OSS support has lost it's interest now with ALSA, right? //Lennart |
|
From: Jay V. <jv...@ac...> - 2004-10-27 23:27:44
|
At 1:13 Uhr +0200 28.10.2004, Lennart Regebro wrote: >Welcome to this nice, clean spring-fresh (or autumn-fresh, rather) list. the trees are orange here in the fat RE, bit strange to me really. not used to it. >So, next step should be having a unix implementation of similarily >basic level, and then a unification of these APIs. Also the >low-level API needs to be extended with SysEx support. At the moment >only short messages can be sent. I'm not sure ALSA distinguishes >between them. You're pretty sure about ALSA for MIDI? >Does anybody else know? and how about Mac OS X? Any Mac developer here? >I assume OSS support has lost it's interest now with ALSA, right? Me, personally, I'd be happy to see midishare support added to python, not just ALSA. So any work on making pythonmidi less crufty in the ALSA usage is happy to me! :) there already is midishare support in python, just not that much python midi applications being written .. seems like the right language for the job to me though. -- ; Jay Vaughan |
|
From: Lennart R. <re...@nu...> - 2004-10-28 09:06:42
|
Jay Vaughan wrote: > At 1:13 Uhr +0200 28.10.2004, Lennart Regebro wrote: > >> Welcome to this nice, clean spring-fresh (or autumn-fresh, rather) list. > > the trees are orange here in the fat RE, bit strange to me really. not > used to it. Looks nice though! >> So, next step should be having a unix implementation of similarily >> basic level, and then a unification of these APIs. Also the >> low-level API needs to be extended with SysEx support. At the moment >> only short messages can be sent. I'm not sure ALSA distinguishes >> between them. > > You're pretty sure about ALSA for MIDI? I know ALSA does MIDI, yes. But other than that i'm not sure I understand then question. > Me, personally, I'd be happy to see midishare support added to python, > not just ALSA. So any work on making pythonmidi less crufty in the ALSA > usage is happy to me! :) > there already is midishare support in python, just not that much python > midi applications being written .. seems like the right language for the > job to me though. MidiShare is a big library. Nothing wrong with that, but as you mention there are already python wrappers for it. It is aimed for writing sequencers and stuff like that, which is cool, but it seems to me that this is overkill for most applications. However, I just noticed that since two weeks ago, Midishare is also on source forge, which is great! |
|
From: Jack J. <Jac...@cw...> - 2004-10-28 09:55:16
|
On 28-okt-04, at 1:13, Lennart Regebro wrote: > and how about Mac OS X? Any Mac developer here? I'm a Mac developer (and, incidentally, responsible for Python on the Mac:-). But: I have very little time for Python work right now, let alone PythonMIDI work:-( But if there are more Mac developers, and people could point me in the right direction as to which bits of QuickTime or Audio Units would need to be exposed to Python to enable MIDI support I can make those bits available pretty easily: the Python interfaces to the MacOS API's can be generated from the Apple headers with not too much effort. Unfortunately the tool to do so is so quirky that I seem to be the only person who's able to drive it:-) -- Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman |
|
From: Lennart R. <re...@nu...> - 2004-10-28 10:36:02
|
Jack Jansen wrote: > But if there are more Mac developers, and people could point me in the > right direction as to which bits of QuickTime or Audio Units would need > to be exposed to Python to enable MIDI support I can make those bits > available pretty easily: the Python interfaces to the MacOS API's can be > generated from the Apple headers with not too much effort. Unfortunately > the tool to do so is so quirky that I seem to be the only person who's > able to drive it:-) Well, that should be enough. But of course, I can't point you in that direction. ;) Not yet at least. Maybe I'll dig up some Mac documentation and look into it later. //Lennart |
|
From: Jay V. <jv...@ac...> - 2004-10-29 11:42:39
|
>But if there are more Mac developers, i'm a mac/unix/embedded developer. i like darwin a lot. >and people could point me in >the right direction as to which bits of QuickTime or Audio Units >would need to be exposed to Python to enable MIDI support I can make >those bits available pretty easily: i don't think you have to -only- do the built-in Apple/MIDI API. if you do python for midishare, then you get cross-platform MIDI support: MidiShare runs on everything. if use use MidiShare for the MIDI abtraction layer, in other words, there need not be individual 'fixes' for each platforms' MIDI side. MidiShare is a clean, well-proven, well-designed, abstract C API. I rank it higher than CoreMIDI for plain ol' MIDI hacking fun. CoreMIDI implies CoreEverythingElse, yuck. I like Darwin, and since its Darwin, I don't -need- to use the AppleAPI's for everything.. >the Python interfaces to the >MacOS API's can be generated from the Apple headers with not too >much effort. Do MidiShare first, and you get linux/win32/osx MIDI from the get-go. >Unfortunately the tool to do so is so quirky that I >seem to be the only person who's able to drive it:-) what a sucky tool. -- ; Jay Vaughan |
|
From: Jack J. <Jac...@cw...> - 2004-10-29 15:09:41
Attachments:
smime.p7s
|
On 29-okt-04, at 13:40, Jay Vaughan wrote: >> But if there are more Mac developers, > > i'm a mac/unix/embedded developer. i like darwin a lot. > >> and people could point me in >> the right direction as to which bits of QuickTime or Audio Units >> would need to be exposed to Python to enable MIDI support I can make >> those bits available pretty easily: > > i don't think you have to -only- do the built-in Apple/MIDI API. if > you do python for midishare, then you get cross-platform MIDI support: > MidiShare runs on everything. If you mean: "you don't have to do anything platform-specific when you use MidiShare": that's good news! I had a quick look at the API and it looks pretty decent. Has it only been open-sourced recently? [...] >> Unfortunately the tool to do so is so quirky that I >> seem to be the only person who's able to drive it:-) > > what a sucky tool. Ah, yes, good idea. Let's start randomly insulting each other:-( (For the record: bgen may be quirky, but it has enabled me to almost single-handedly open up all major MacOS APIs to Python, and keep those interfaces up to date over the last 10 years, from MacOS 7 straight to MacOS X. So, while quirky I wouldn't call it "sucky"). -- Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman |
|
From: Jay V. <jv...@ac...> - 2004-10-29 15:43:07
|
At 17:08 Uhr +0200 29.10.2004, Jack Jansen wrote: >I had a quick look at the API and it looks pretty decent. Has it >only been open-sourced recently? > no, MidiShare has been around for years. >>>Unfortunately the tool to do so is so quirky that I >>>seem to be the only person who's able to drive it:-) >>what a sucky tool. >Ah, yes, good idea. Let's start randomly insulting each other:-( > hey, i was talking about the tool not you! if you wrote it, don't take offense! >(For the record: bgen may be quirky, but it has enabled me to almost >single-handedly open up all major MacOS APIs to Python, and keep >those interfaces up to date over the last 10 years, from MacOS 7 >straight to MacOS X. So, while quirky I wouldn't call it "sucky"). well, if its gonna be a tool, i'd warrant that more than one person should be able to use it. thats all. i had no idea you were talking about something you have such an investment in, since you brought up how hard it is to use ... -- ; Jay Vaughan |
|
From: Donovan P. <dp...@ul...> - 2005-01-07 17:27:07
|
On Oct 29, 2004, at 8:41 AM, Jay Vaughan wrote: > At 17:08 Uhr +0200 29.10.2004, Jack Jansen wrote: >> (For the record: bgen may be quirky, but it has enabled me to almost >> single-handedly open up all major MacOS APIs to Python, and keep >> those interfaces up to date over the last 10 years, from MacOS 7 >> straight to MacOS X. So, while quirky I wouldn't call it "sucky"). > > well, if its gonna be a tool, i'd warrant that more than one person > should be able to use it. thats all. i had no idea you were talking > about something you have such an investment in, since you brought up > how hard it is to use ...\ I would just like to defend bgen. I have used it, and it was not very difficult to learn, and once I had it working, it wrapped a large number of C apis automatically. It's main problem is lack of documentation and interest, then. I'd say it's pretty similar to SWIG, but better at what it does (which is less than swig does), but SWIG has more documentation and language support, so people use it. dp |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X