On Fri, 20 Jul 2001 14:12, Paul Davis wrote:
...
The problem is that the bookkeeping is based only on what the .spec
file declares. Since this is never comparable to the kinds of tests
that ./configure performs, the bookkeeping is inadequate as a way to
test for compile or run-time
Joe Pfeiffer wrote:
(I apologize if something substantially similar to this goes out
twice -- I meant to send it to the list, but it seems to have fallen
in a hole...).
My last experience with RPMs, just under a year ago, convinced me that
they are basically broken. Every distribution
Hi Jay, Ts wrote:
[..]
Paul Davis presented Ardour as an equivalant of the Mackie hardware
recorder which complement their digital mixing desk.
It seems to me that Ardour is nice for this task but what kind of
editing does it offer?
An interesting comment, considering that just
Paul Davis wrote:
Don't know original author...tongue-in-cheek response
Please, would people stop building libraries or binaries from source on
a package-based system? It causes so many problems. If you are
building a tool from source and it needs library X, I energetically
encourage you
anyone know when demudi is due?
haven't seen guenter around these parts / guess he'd know.
de|
Hello,
I've been a bit of a lurker on this list for a while. I'm both a developer
(mostly at the moment of closed source billing software..) and a user of
midi software (got a small midi rig at home - Akai sampler, couple of synths
and an ageing Atari ST).
Anyway, a similar packaging issue was
On Thu, Jul 19, 2001 at 03:40:45PM -0500, Kevin Conder wrote:
On Thu, 19 Jul 2001, Paul Davis wrote:
Please, would people stop using RPM's or any package system for that
matter to install libraries that they need to use with applications
that they have to compile from source?
On Thu, Jul 19, 2001 at 10:15:29PM -0400, Paul Davis wrote:
then you haven't done much with C++ libraries, especially since the
debacle of RH's move to gcc 2.96, which broke binary compatibility
with g++ 2.95. not only that, but i have heard that there were
intermediate versions of gcc they
Hi,
Paul Davis wrote:
[...]
If someone has an actual, real-world, working example of how to do all
this stuff better, bring it on. The library stuff is a total
hassle. But I've been hacking Unix systems and open source for 13 or
14 years now, and I don't see any good solutions for what is
A problem with depending on CVS is that, in my experience,
CVS seems to encourage very sloppy attitudes -- I think
I have better luck with tarballs. Apparently many developers
don't think it's a bug if the CVS version won't build, since
it's just there for developers or something -- when I
I run my Korg Triton with Cubase. What I like to do is create all my midi
tracks first, with no extra effects on them. This way I can work with the
song and arrange the parts (I can get 16 channels out of the Korg). Once
I am done and satisfied (for now) I save a copy as a backup, then each
On Fri, Jul 20, 2001 at 09:21:14AM -0400, Richard C. Burnett wrote:
I guess I am wondering what methods/practices do others use when creating
music that has audio and midi requirements. It would probably be good to
see what people 'like' in a tool, what they 'dislike'.
I tend to record
Paul Davis [EMAIL PROTECTED] writes:
i think the right way is for the user to define the current port that
is associated with audio output 1. sort of like port aliases. this
seems like a nice idea. something like:
int laaga_set_port_alias (const char *alias, laaga_port_t *port);
this
In-Reply-To: [EMAIL PROTECTED]
On Thu, 19 Jul 2001, Joe Pfeiffer wrote:
My experience with RPMs, a little under a year ago, was that the whole
system is basically broken. All the different RPM-based distributions
have their own versions of the same packages,
This
As nobody did mention GLAME yet: GLAME has a audio file editor component
I'm using Linux for pre-production with an Akai MPC2000XL.
I've been using GLAME. Much to my amazement it was able to yank in
all 94.4 MB of Siberian Khatru and allowed me to extract my samples
without crashing. I now
Joe Pfeiffer wrote:
In-Reply-To: [EMAIL PROTECTED]
On Thu, 19 Jul 2001, Joe Pfeiffer wrote:
My experience with RPMs, a little under a year ago, was that the whole
system is basically broken. All the different RPM-based distributions
have their own versions of the
I realized what the problem really is and what the answer really is, akin to a
real modular studio setup. The default audio I/O hooking should be done
with a patchbay client. That is, a client that has pairs of ports like audio
output 1 and audio output to driver 1 which are tied together (zero
17 matches
Mail list logo
