Hi !!
I'm getting some errors when compiling jack_fst.
fst compiled just fine.
Of course, I did what you say in the readme; I removed the constructors
with ../fixheaders and change " VstFileType *fileTypes; // list of fileTypes"
to "struct VstFileType *fileTypes; // list of fileTypes".
When I run make in the jack_fst-1.2 directory, I'm getting these errors:
yves@Yves:~/jack_fst-1.2> make
make all-am
make[1]: Entering directory `/home/Yves/jack_fst-1.2'
if gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -DXTHREADS -D_REENTRANT
-DXUSE_MTSAFE_API -I/opt/gnome/include/gtk-2.0
-I/opt/gnome/lib/gtk-2.0/include -I/usr/X11R6/include
-I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/freetype2/config
-I/opt/gnome/include/glib-2.0-I/opt/gnome/lib/glib-2.0/include
-I/usr/local/include -I/usr/local/include/vst -MT jfst.o -MD -MP -MF
".deps/jfst.Tpo" \
-c -o jfst.o `test -f 'jfst.c' || echo './'`jfst.c; \
then mv -f ".deps/jfst.Tpo" ".deps/jfst.Po"; \
else rm -f ".deps/jfst.Tpo"; exit 1; \
fi
In file included from jfst.c:25:
/usr/local/include/vst/aeffectx.h:918: error: parse error before "VstFileType"
/usr/local/include/vst/aeffectx.h:939: error: parse error before '}' token
jfst.c: In function `main':
jfst.c:258: error: `JackThreadInitCallback' undeclared (first use in this
function)
jfst.c:258: error: (Each undeclared identifier is reported only once
jfst.c:258: error: for each function it appears in.)
jfst.c:258: error: parse error before "jack_thread_init"
make[1]: *** [jfst.o] Erreur 1
make[1]: Leaving directory `/home/Yves/jack_fst-1.2'
make: *** [all] Erreur 2
I checked if the constructors where really removed in
usr/local/include/vst/aeffectx.h ...yes they are.
Could somebody tell me how to fix this please ?
Thanks in advance,,,,and sorry for my Bad english, I'm french :)
Hi all,
Although this is probably as OT as it gets, but what the heck, I decided to
share my latest [non-musical] creation with the fellow LAU members as some
of you may find this thingy [remotely] useful :-). I had a tough week so
please be lenient with the flames :-)
During the last couple of days I did some hacking on my Superkaramba
low-cpu-footprint desktop eye-candy theme "Borealis" (association with the
sound theme intentional) that provides bunch of useful system data as well
as some additional toys and gizmos (although I presume that most of the hard
core audio users on this list may very well avoid it in order to prevent
wasting of precious CPU cycles). It's geared primarily towards KDE users and
those of you who have a weak spot for the desktop eye-candy :-).
So, without boring you any further, if interested please visit:
http://kde-look.org/content/show.php?content=13876
Online docs at:
http://meowing.ccm.uc.edu/~ico/Linux/Borealis/Borealis_manual/index.html
Comments and/or suggestions are most welcome and appreciated!
Greets to all LAU's out there! Hope your week is/was better than mine!
Best wishes,
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.795 / Virus Database: 539 - Release Date: 11/12/2004
Hello all, I've got a question regarding MIDI and sequencing in linux.
How can I record a "bulk dump" from a drum-machine/synth in Linux?
I have tried Muse which just doesn't work, can't even specify what
channel to listen to! I'm lost and it's really frustrating.
MIDI isn't my strong side (or even interest) but I have been able to
record both regular MIDI notes on a specified channel in Pro Tools on
the Mac and also record a bulk-dump of all the settings. How to do it in
linux? It should be basic stuff...
Any tips and suggestions are very welcome /thanks z
Jan,
We sort of started working through some ideas last week some time.
It would be expensive, but I don't think it would be anywhere near the
number Ron talked about. Also, we were not talking about doing
anything particularly commercial. Much like Ardour, Rosegarden, etc.,
are great apps but not necessarily marketable to the mass market, this
card was envisioned by a few of us as something that starts to break
the idea that you had to buy cards where you knew nothing about what
was inside.
All that said, there is no way that this device would be as cost
effective as a commercially available device. The difference is that
this community would actually have control over what a device like
this does.
My idea for a while has been to do a 1394-based device that uses
some sort of Xilinx FPGA to implement most of the hardware. Possibly
it might have a hardware mixer, zero-latency monitoring, etc., of
possibly not. Beyond that it's pretty much A/D & D/A, possibly some
digital I/Os like spdif or ADAT.
Anyway, it's just an idea. Being that I recently find myself
unemployed it seems like a way to pass some time until next year when
I start looking for work again. (Although Apple is hiring now...)
Anyway, I'm a bit old and out of touch with good tools. For this to be
really interesting I think all the tools need to be Linux tools. I'm
not even sure what's available for doing board design.
As for internal software, if it was 1394-based then at a minimum we
need a microcontroller to handle config ROM and general packet
transmission/reception issues. We could certainly use someone with
some experience in embedded and/or realtime software design.
But again, this is mostly talk right now. I'm drawing a couple of
block diagrams to sort of scope out what the parts list might look
like.
cheers,
Mark
On Thu, 25 Nov 2004 10:12:42 -0600, Jan Depner <eviltwin69(a)cableone.net> wrote:
> Mark,
>
> I'd be really interested in this assuming there is some software
> involved. I used to write real-time data acquisition systems for GPS
> (early 80's when there were only 3 or 4 birds up). It just seems like
> you'd need three or four prototypes for testing. I'd think the money
> requirements would be prohibitive.
>
> Jan
>
>
>
> On Thu, 2004-11-25 at 09:24, Mark Knecht wrote:
> > Hi,
> > I haven't read anything except this thread. I don't pretend to know
> > what it really means. My understanding of RME's support for Linux was
> > only that they provided some technical info. That info was then used
> > by Alsa developers to do the drivers. RME did not actually develop or
> > support any of the Alsa drivers TTBOMK. (They were 'supportive'.)
> > Please correct me if I'm wrong.
> >
> > That said, I'm on vacation this week, but still interested in the
> > Open Source hardware sound card solution many of us spoke about in an
> > earlier thread on this list. (I think it was this list...)
> >
> > Creating something ourselves is a path to freedom and continued
> > support from the community.
> >
> > with best regards,
> > Mark
> >
> >
> > On Thu, 25 Nov 2004 02:47:57 +0100, Marek Peteraj <marpet(a)naex.sk> wrote:
> > > I forgot, this is the product i'm talking about:
> > >
> > > http://www.rme-audio.de/firewire/ff800.htm
> > >
> > > Marek
> > >
> > >
>
>
I've been trying to get rosegarden v2.1 working on
knoppix HD install (to ultimately be remastered to my
custom liveCD).
The Knoppix liveCD autoconfigures almost everything
automatically (video, network card, soundcard audio)
but not the soundcard MIDI portion. I believe knoppix
is using the OSS driver to be able to run rosegarden
2.1
By booting with the ALSA cheatcode, knoppix liveCD
supposedly boots up using the ALSA drivers. The
problem is that I've not found anyone that got
rosegarden working with the midiports, whether using
ALSA or OSS. Since I'm experimenting with a harddisk
install however, I will be able to install any missing
libraries & modules. However in looking at the
rosegarden4 tutorial ch.2, I dont know where to begin
since a lot of the ALSA modules are not installed,
however hopefully I wouldnt need ALSA if I can get
midi working under OSS for rosegarden 2.1?
I'm not sure where to begin since rosegarden v2.1 says
/dev/sequencer is invalid. Can somebody please offer
a suggestion of a starting point to help get me on the
track to troubleshoot and get rosegarden working? thanks.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Greetings:
I need to work on some graphics for an article, and I'd like to know
if it's possible to do some specific things with the GIMP. If you can
help, please reply off-list, it's pretty much off-topic stuff.
Best,
dp
Hello,
I recently bought a Terratec Aureon 5.1 USB soundcard for my Dell
Latitude C640, running an up-to-date installation of Fedora Core 3
as well as Demudi 1.2.
I managed to get the soundcard to work with the software I care
about (e.g., jack, rezound, ogle, mplayer) by making it the default
soundcard for ALSA, hacking configuration files like .oglerc, and
experimenting with alsamixer.
There's one remaining problem, though. The input levels from the
microphone and line in are extremely low. I've sort of managed to
record from line in, but the input was very faint. When recording
from the microphone, I can hear (and record) a little spike when
switching the mic on, but nothing else. (The mic works fine when
attached to the onboard soundcard.)
Since I am getting some sort of input, I'm fairly sure that I haven't
muted any of the pertinent channels, but so far I haven't been able
to increase the input to acceptable levels. Any thoughts would be
appreciated.
Thanks,
Peter
>
> I assume that RME has developped their own protocols, which they don't
> want to share. And frankly I can understand their point of view, because
> I think an awfull lot of time (=money) must have been spent to develop
> an efficient protocol.
1. So they haven't invested the a comparable amount of time into
Hammerfall series?
2. I can only understand the point of view of open source developers
here, since they also invested an awfull lot of time (and money that
they didn't get back!) into developing linux audio applications, many of
which are state-of-art at least with respect to technology. And they're
free as in beer/speech.
That said i really don't understand the point of view of those few how
actually kindof defend the position of RME (or any other manufacturer in
a similar position), no offense intended.
> The RME story also goes for the firewire interface of M-Audio. They use
> a DM1000 based platform, so initially we thought the device could be
> supported by FreeBob. But apparently they modified the reference
> firmware, making it (possibly) non-conformant to the 1394TA specs. As
> such these devices cannot be supported by FreeBob directly. Maybe if we
> have a working driver, we can convince the M-Audio people to share the
> nescessary info so that we can support their devices also.
Which seems like it's the beginning of end for linux pro-audio hw
support if we don't fight for it. Right now it concerns just me, but it
might concern everyone in the near future.
Marek
As long as they don't wind up phasing out the PCMCIA cards in the near
future and go all firewire.
Also a person could theoretically build USB audio devices that just
strictly follow the USB standard, and they should work on linux, mac and
windows the same, Edirol seems to be perhaps the best bet for future audio
support simply because they strictly follow the USB audio standard.
If maudio is allowed to keep supporting linux and RME keeps making the
PCMCIA and PCI based systems then there's really no problem at all.
On Fri, 26 Nov 2004 linux-audio-user-request(a)music.columbia.edu wrote:
> Send linux-audio-user mailing list submissions to
> linux-audio-user(a)music.columbia.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://music.columbia.edu/mailman/listinfo/linux-audio-user
> or, via email, send a message with subject or body 'help' to
> linux-audio-user-request(a)music.columbia.edu
>
> You can reach the person managing the list at
> linux-audio-user-owner(a)music.columbia.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of linux-audio-user digest..."
>
>
> Today's Topics:
>
> 1. Re: Re: [linux-audio-dev] RME is no more (Georg Rudolph)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Nov 2004 19:36:48 +0100
> From: Georg Rudolph <georg.rudolph(a)schwaben.de>
> Subject: Re: [linux-audio-user] Re: [linux-audio-dev] RME is no more
> To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
> Message-ID: <41A777C0.2090400(a)schwaben.de>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Please, let's not be too harsh. I recently bought the pcmcia based
> multiface from RME, only because it has linux support, and it works
> great, on both kernels. Of course, firewire is cooler, but there is this
> way out. Glad that I didn't wait, at least. Firewire needs more time to
> be more legacy, hopefully not too long :)
>
> Regards,
> Georg.
>
>
> ------------------------------
>
> _______________________________________________
> linux-audio-user mailing list
> linux-audio-user(a)music.columbia.edu
> http://music.columbia.edu/mailman/listinfo/linux-audio-user
>
>
> End of linux-audio-user Digest, Vol 14, Issue 81
> ************************************************
>