Nick wrote:
>> Mainly because MIDI is very primitive and supporting MIDI at a low
level
>> ties you to it to some extent. XAP has a highlevel control interface
that
>> MIDI can be converted into trivially, but can handle other things.
>I still have trouble understanding this view (except for non-standard
>tunings..)
Non-standard tunings are also part of the MIDI standard, in a later
extension called the MIDI Tuning Standard.
I tend to agree with you. No Linux softsynth fully implements all
MIDI codes at the moment! Then how can one expect support of an even
bigger standard?
Manuel
After some considerable thought as to the best way to organize such a
library, as well as what a project such as this will do to my free
time, I have a few ideas and questions to present to the list.
I'll start with the easy one first.
1) What exactly would this library hold? There's no need for this to be
restricted to loops. It could also contain other "musical raw
material", such as sample sets and softsynth patches. In that case,
calling it the Open Loop Library makes little sense. What else do you
think would work? Open Music Library? Sounds like it's a repository for
music, not for raw components. The upshot to the Open Loop Library name
is that the domain openloops.org is available. It also makes a good
working name for now.
Really, that was the main question, and it brings part of the proposal
with it. I would like to design and build a web service to act as a
library for loops, sample sets, and patches. Here are some thought on
the overall design.
1) The top level hierarchy would be (obviously enough) "Samples",
"Loops", and "Patches".
2) Below "Samples", the categorization would go something like
"Keyboards", "Brass", "Woodwinds", "Synth Leads", "Pads", "Strings"...
Well, you get the idea.
3) Below "Patches", would basically be the same kind of broad
categories as with samples.
Now, "Loops" is where things get fun. I've been thinking about Mr.
Knecht's comments on building an elegant organization system, which is
something that Acid itself apparently lacks. I think an extensive
metadata system is the best way to accomplish this.
Every loop would have attached to it:
a) Time signature
b) Tempo
c) Key (If applicable. Drum loops, for example, would not need this.)
d) Creator's name
e) Instrument(s) (This one is tricky, since there are so many
instruments in the world. It would need to be a free-text field, which
means misspellings could be a problem. Possible solutions?)
f) Loop or one-shot (Not everything meant for a loop-based composition
program need be an actual loop. Drum fills and cymbal hits come
immediately to mind.)
g) Style (This one creates some issues, due to how subjective it can
be.)
h) Comments (A free text field the creator of the loop can use to
attach whatever additional info they feel it needs.)
i) A million other things I can't think of at the moment. :)
One problem that needs to be solved is how to attach these kinds of
metadata to a loop. Also, another thing to consider are loop sets.
Thinking about the architecture for the web app itself led me to think
about how CPAN works, at least from a user perspective. I would set up
a central index server, which could then redirect clients to the
appropriate mirror to grab a file when a request is made. This also
brings up the idea of a client that could be built that would talk to
the servers from the user's machine. This client could be used to
maintain the organization of all the loops the user chooses to
download. This can be thought about after the main system is up and
running, though.
As for hosting, I have a good lead on a local colo facility. I have
some other projects I need to host anyway.
I apologize for the long email. Hopefully, this will start the ball
rolling, and if all goes well, it won't crush me when I try to catch it.
Regards,
Darren Landrum
who is hoping this hair-brained scheme doesn't spawn another mailing
list. ;)
> > Sounds good enough! Can it be used in real time ? Could i use it to
> > enhance LADSPA?
>
> I doubt it. The main problem is that these C++ classes probably do a lot
> of allocation/deallocation which is always a bad idea in a real time
> situation.
>
I sure know about it. That's why i need low level code in first place,
to avoid any kind of overhead.
> > I'm not afraid of learning new languages anymore, but surely i don't
> > have the time either... it takes a while to master it.
>
> I learnt the basics of Python in about 4 hours. Within another 3 hours I had
> my first useful Python script. Obviously the more complicated stuff like the
> Python numerical extension would take far more time.
>
> Erik
> --
I will consider looking at it. What are the reasons to use python
instead of c++? I have some experience in c++ code but has never seen
python, nor used any of its tools... and i sure would need the numerical
extension you mentioned.
Cheers
Fabio,
Hello all,
I'm new to the list, and to linux, and I'm looking for where I can find
info on the current status of windows VST plugins/instruments on (i386)
linux. After lots of googling, I've found lots of references to a couple
vst->LADSPA wrappers (i think one is called vstserver?), however I've
been unable to locate homepages of these projects. Does anyone know
where I can find downloadable source or binaries for any of these
projects and (hopefully) directions on their
compilation/installtion/use? Is there anything thats actually usable
yet, or are these just proof of concept type things?
Any and all info on this topic is appreciated. Thanks in advance for
your help.
--
Kevin Bowen <kbowen(a)ucsd.edu>
Emiliano Grilli wrote:
> I have an edirol SC D70 (Sound Canvas Digital) which works
> out-of-the-box with the usb-audio driver. I get 3 MIDI ports (2 MIDI
> ports of the SC and 1 external MIDI I/O).
> This device is also an audio interface, but I haven't found how to
> configure it (if it's possible).
The audio part of the SC-D70 doesn't conform to the USB Audio
specification, so the driver doesn't find it. (The MIDI part doesn't
conform either, but the driver has a workaround for that.)
Please post the output of "lsusb -v" and the contents of
/proc/bus/usb/devices.
HTH
Clemens
> >
> > Have you look at Octave?
> >
> > I think it can be expanded with c(++) modules.
>
> That is correct.
>
> It is a relativelu trivial matter to write C++ code which uses the
> Octave C++ matrix and array libraries (basically everything that is
> written in C++) to write extensions, much like the MEX files Matlab
> uses. The extensions have a .oct extension.
>
> Many of Octave's standard functions are written like this so you can
> grab one of these as a starting point.
>
Sounds good enough! Can it be used in real time ? Could i use it to
enhance LADSPA?
> I'd use Python ( www.python.org ). It has many scientific 3rd party
> expansions, can be extended with C/C++ and can
> be operated from a command line.
I'm not afraid of learning new languages anymore, but surely i don't
have the time either... it takes a while to master it.
> Haven't tried it, but ecasound has
> a Python interface, maybe you could use
> that to get audio plugins working?
In fact i wanna make it as generic as i can. My main purpose is
voice recognition, and my secondary target is generic signal processing,
not necessarily coming from soundcards. So i should need my own
customized program.
Cheers,
Fabio de Matos
I've been using Linux for quite some time now and finally got around to using
it for audio and MIDI. I must say i'm very impressed with all the
applications i've been using.
Thanks to all (developers and users) for making Linux audio/music development
a reality.
Levi
Hi all,
I have an edirol SC D70 (Sound Canvas Digital) which works
out-of-the-box with the usb-audio driver. I get 3 MIDI ports (2 MIDI
ports of the SC and 1 external MIDI I/O).
This device is also an audio interface, but I haven't found how to
configure it (if it's possible).
Maybe I have to add another snd-usb-audio driven card to modules.conf?
I tried to write to alsa-devel, but since I'm not subscribed to that
list, the message doesn't show in the archives... so I suspect that it
has never been received.
Also the page at alsa.opensrc.org doesn't seem to have information on
this for the SC D70
Can you help me?
TIA
PS: I'll have to second Levi and Brian and thank you all for making
linux+audio such an exiting combo !!!
PPS: sorry for my crappy english...
--
.---------------------.
| Emiliano Grilli |
| emillo(a)libero.it |
| Linux user #209089 |
'---------------------'
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I am considering to buy a soundcard for around 100$ and there is an
offer for a SB Audigy.
Any recommendations?
I read that the driver on Sourceforge is still experimental.
Did anyone experience problems using that driver?
What should I know or consider?
Thanks a lot,
- - Burkhard
- --
no html mail please, thank you. pub key at blackhole.pca.dfn.de
899B AFD7 14E9 D595 EA00 BE8B A348 851C 0F62 E91D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE93hdXo0iFHA9i6R0RAu6CAJ9iSrxXS0bPqCDNK93kuCvjPoL5QACdEC1U
CQymH3oCgVVjpg0DRyQxP1s=
=Kyxe
-----END PGP SIGNATURE-----
On Mon, 2003-01-13 at 09:04, Clemens Ladisch wrote:
> Mark Knecht wrote:
> > I recently purchased an RME HDSP 9652 card. The card is working fine
> > for audio, but the MIDI interface is a timing disaster. The interface
> > works, but won't keep time. A 2 minute song is Rosegarden takes abut
> > 2:45 to play every time. You can hear how the HDSP isn't delivering
> > closely spaced MIDI events together, but is sort of smearing them out.
>
> The hdsp driver doesn't send more than one MIDI byte per timer tick.
> IMHO it should be modified to send in a loop until the FIFO is full
> (however, I don't know if the HDSP has a FIFO at all). And it should start
> sending in output_trigger() instead of delaying it to the next timer tick.
>
Clemens,
Thanks for the response. One comment I forgot to make in the first
post. This MIDI interface works fine under Windows, so whatever causes
the problem is purely a Alsa MIDI issue. If we can figure it out, then
we can fix it.
I agree that it sounds like this sort of one note per timer tick.
When the interface is supposed to send a chord, it sends what sounds
like an arpegiated chord. It's all smeared out.
Is there some example code I could look at to understand implementing
a FIFO? However, if there is a FIFO Full indication, doesn't we need to
know _how_ it's indicated? I would assume it's different for all cards?
(Bus possibly similar for cards from the same manufacturer?
Also, this is the HDSP 9652, which is a single PCI card. Is this
problem showing up for the DigiFace/MultiFace type cards?
Thanks,
Mark
