On Mon, Sep 22, 2003 at 07:12:35PM -0700, Thomas Webb wrote:
Anyhoo, now that I'm over them, I would love to get
cracking on some chunky
audio projects but I'm a bit unsure of a kind of
best practises approach
for audio programming. What should I study? Whats
the best way to go?!
On Tuesday 23 September 2003 04.12, Thomas Webb wrote:
[...]
SDL is cool. I like it, but I mostly just use it for
games because as far as sound goes, it's very basic.
It kinda uses the lest common denominator approach
for cross-platform capability. Last time I used it for
audio, It only
On Tuesday 23 September 2003 09.50, Steve Harris wrote:
[...SDL...]
Its pretty hard to build UIs out of it, I tried and gave up (cf.
PressGang/JAMin). I think GTK and Qt are just better for that kind
of thing.
Tried ParaGUI?
Anyway, I still think GTK+, Qt or FLTK is more suitable for normal
Wow, thanks a lot everyone. I'm certainly going to check out JACK, but
is GTK+ flexible enough (can you make your own buttons and stuff)
Actually, don't answer that, that's just laziness on my part - Its just
that I've noticed that the graphics sometimes take a back seat in the
linux world :)
...
On Tue, Sep 23, 2003 at 10:27:03 +1000, Earle Castledine wrote:
Wow, thanks a lot everyone. I'm certainly going to check out JACK, but
is GTK+ flexible enough (can you make your own buttons and stuff)
It's a not a google question, as I think you want to know how easy it is.
Its actually pretty
On Tuesday 23 September 2003 09:01, Steve Harris wrote:
It's a not a google question, as I think you want to know how easy it is.
Its actually pretty easy (at least in GTK2.2), I made a meter and scale
widget for GTK very easily and I was a GTK newbie.
If you're a C++ hacker, you might also
Me too!
For me Jack has been confusing as I'm not sure in what process/thread
my audio routine runs. Somebody here wrote Jack's interesting thing is
that it can route audio through applications. I don't want that.
I want that Jack takes my C function (or its compiled object) and
executes that
On Fri, Sep 12, 2003 at 11:00:19AM +1000, Earle wrote:
I was hoping someone could help me with my first newbie steps in linux audio
programming. I finally made it over to Linux, and discovered that I arrived
here before cubase and fruityloops did. They never did what I wanted them to
anyway.
Juhana Sadeharju [EMAIL PROTECTED] writes:
For me Jack has been confusing as I'm not sure in what process/thread
my audio routine runs. Somebody here wrote Jack's interesting thing is
that it can route audio through applications. I don't want that.
I want that Jack takes my C function (or its
The coolest thing about OSS for me was when I finally realized that all
I had to do was open a file (/dev/dsp), read from it and write to it to
capture sound and play it back. I made a stupid little 'feedback'
application in about 10 lines of code.
Figuring that out took a while. I just knew it
For me Jack has been confusing as I'm not sure in what process/thread
my audio routine runs. Somebody here wrote Jack's interesting thing is
its not your job to know which thread, only that it runs in a
different thread that you do not control, and that you should not block.
that it can route
It sounds like Jack is a system to learn like on Windows/Mac.
JACK is arguably simpler than either OSS or anything else. you don't
configure any device parameters, you don't use system calls to move
data around, etc. the minimal JACK client (which copies 1 channel's
worth of data from its input
Greetings LADders:
I'm working with Kjetil's vstserver, testing various plugins, and
occasionally I get this error from the server :
VSTSERVER/SMS_new: Unable to allocate 12288 bytes of shared memory.
VSTSERVER/CH_new: Could not set up shared memory.
The plugin then politely
13 matches
Mail list logo
