22 Oct
2005
22 Oct
'05
9:55 p.m.
On 10/22/05, Martin Wohlleben <Martin.Wohlleben(a)gmx.de> wrote:
Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark
Knecht:
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
On 10/21/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
Hi Marc,
I got the same failure with wine20050930. I downgraded wine to wine20050830
and xfst-0.3 compiled cleanly.
You also have to change the vst header as for jack_fst. Otherwise you get some
error messages and make will "fail". I don't know exactly what I changed
exactly, but you can find the headers which I used attached to this e-mail.
I still got a failure message, during compilation but xfst works.
good luck,
Martin
On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector
Centeno-Garcia wrote:
Hi all,
I just got a few minutes to try xfst on my AMD64 machine. Did
anyone else run into this:
mark@lightning ~/CODE/xfst-0.3 $ make
winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
winebuild: unrecognized option `--debug'
Usage: winebuild [OPTIONS] [FILES]
<SNIP>
make: *** [xfst.exe.dbg.c] Error 1
mark@lightning ~/CODE/xfst-0.3 $
I hope I'm doing this correctly. I put the Steinberg headers in the
vst directory and then ran make. That seems to be what the README file
suggests. There is also a file called readme.jack-fst which seems ot
be leftover from the older Jack_fst. Is that correct?
Make does seem to want to run winebuild, and winebuild on my system
doesn't support an option called debug.
mark@lightning ~/CODE/xfst-0.3 $ wine --version
Wine 20050930
mark@lightning ~/CODE/xfst-0.3 $
Did I miss some conversation about this?
Thanks,
Mark Thanks! We help ourselves... that's the nice
thing about open source.
With the -r option Crystal works for me now. What is this option for?
One plugin that I can't get working is the SRI_1010. It would be very
nice to have this one unless you know of any other free convolution
plugin. I tried with and without the -r option and I get:
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of this
midi device. Assuming FM Synth
gui_thread_id = 10
could not post message to gui thread
cannot create editor
hmmm... this looks like the plugin is trying to open a midi port by
itself. try to configure wine so that it does not see any alsa midiport.
Have any of you tried to use this one?
cheers!
Hector.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language 
22 Oct
22 Oct
11:56 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
On 10/22/05, Martin Wohlleben
<Martin.Wohlleben(a)gmx.de> wrote:
Hi guys:
Yes, I'm having the same problem with winebuild. The trouble is that
the syntax for winebuild's options has changed from what Torben has in
the Makefile. Unfortunately I haven't yet figured out the new magic
incantation, but I did spend an hour or so on it this afternoon. Got no
joy, same as you. :(
Best,
dp
Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark
Knecht:
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
On 10/21/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Hi Marc,
I got the same failure with wine20050930. I downgraded wine to wine20050830
and xfst-0.3 compiled cleanly.
You also have to change the vst header as for jack_fst. Otherwise you get some
error messages and make will "fail". I don't know exactly what I changed
exactly, but you can find the headers which I used attached to this e-mail.
I still got a failure message, during compilation but xfst works.
good luck,
Martin
On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector
Centeno-Garcia wrote:
>Thanks! We help ourselves... that's the nice thing about open source.
>With the -r option Crystal works for me now. What is this option for?
>One plugin that I can't get working is the SRI_1010. It would be very
>nice to have this one unless you know of any other free convolution
>plugin. I tried with and without the -r option and I get:
>
>err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of this
>midi device. Assuming FM Synth
>gui_thread_id = 10
>could not post message to gui thread
>cannot create editor
>
>
hmmm... this looks like the plugin is trying to open a midi port by
itself. try to configure wine so that it does not see any alsa midiport.
>Have any of you tried to use this one?
>
>cheers!
>
>
>Hector.
>
>
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
Hi all,
I just got a few minutes to try xfst on my AMD64 machine. Did
anyone else run into this:
mark@lightning ~/CODE/xfst-0.3 $ make
winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
winebuild: unrecognized option `--debug'
Usage: winebuild [OPTIONS] [FILES]
<SNIP>
make: *** [xfst.exe.dbg.c] Error 1
mark@lightning ~/CODE/xfst-0.3 $
I hope I'm doing this correctly. I put the Steinberg headers in the
vst directory and then ran make. That seems to be what the README file
suggests. There is also a file called readme.jack-fst which seems ot
be leftover from the older Jack_fst. Is that correct?
Make does seem to want to run winebuild, and winebuild on my system
doesn't support an option called debug.
mark@lightning ~/CODE/xfst-0.3 $ wine --version
Wine 20050930
mark@lightning ~/CODE/xfst-0.3 $
Did I miss some conversation about this?
Thanks,
Mark
23 Oct
23 Oct
12:57 a.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/22/05, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Mark Knecht wrote:
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
On 10/22/05, Martin Wohlleben
<Martin.Wohlleben(a)gmx.de> wrote:
Hi guys:
Yes, I'm having the same problem with winebuild. The trouble is that
the syntax for winebuild's options has changed from what Torben has in
the Makefile. Unfortunately I haven't yet figured out the new magic
incantation, but I did spend an hour or so on it this afternoon. Got no
joy, same as you. :(
Best,
dp Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark
Knecht:
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
On 10/21/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
>On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector Centeno-Garcia wrote:
>
>
>>Thanks! We help ourselves... that's the nice thing about open source.
>>With the -r option Crystal works for me now. What is this option for?
>>One plugin that I can't get working is the SRI_1010. It would be very
>>nice to have this one unless you know of any other free convolution
>>plugin. I tried with and without the -r option and I get:
>>
>>err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of this
>>midi device. Assuming FM Synth
>>gui_thread_id = 10
>>could not post message to gui thread
>>cannot create editor
>>
>>
>hmmm... this looks like the plugin is trying to open a midi port by
>itself. try to configure wine so that it does not see any alsa midiport.
>
>
>
>>Have any of you tried to use this one?
>>
>>cheers!
>>
>>
>>Hector.
>>
>>
>--
>torben Hohn
>http://galan.sourceforge.net -- The graphical Audio language
>
>
Hi all,
I just got a few minutes to try xfst on my AMD64 machine. Did
anyone else run into this:
mark@lightning ~/CODE/xfst-0.3 $ make
winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
winebuild: unrecognized option `--debug'
Usage: winebuild [OPTIONS] [FILES]
<SNIP>
make: *** [xfst.exe.dbg.c] Error 1
mark@lightning ~/CODE/xfst-0.3 $
I hope I'm doing this correctly. I put the Steinberg headers in the
vst directory and then ran make. That seems to be what the README file
suggests. There is also a file called readme.jack-fst which seems ot
be leftover from the older Jack_fst. Is that correct?
Make does seem to want to run winebuild, and winebuild on my system
doesn't support an option called debug.
mark@lightning ~/CODE/xfst-0.3 $ wine --version
Wine 20050930
mark@lightning ~/CODE/xfst-0.3 $
Did I miss some conversation about this?
Thanks,
Mark
Hi Marc,
I got the same failure with wine20050930. I downgraded wine to wine20050830
and xfst-0.3 compiled cleanly.
You also have to change the vst header as for jack_fst. Otherwise you get some
error messages and make will "fail". I don't know exactly what I changed
exactly, but you can find the headers which I used attached to this e-mail.
I still got a failure message, during compilation but xfst works.
good luck,
Martin
9:23 a.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
On 10/22/05, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file that's
not present in the xfst package. The --exe mode requires no spec file,
but either it's not working as advertised or I'm still missing something
about it. One of those modes is supposed to be used when winebuild
creates a .c file.
Btw, this is wine-20050930, I think you're on the same version, yes ?
We should also be sure to test DSSI. As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
Also, I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Best,
dp
Mark Knecht wrote:
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
On 10/22/05, Martin Wohlleben
<Martin.Wohlleben(a)gmx.de> wrote:
Hi guys:
Yes, I'm having the same problem with winebuild. The trouble is that
the syntax for winebuild's options has changed from what Torben has in
the Makefile. Unfortunately I haven't yet figured out the new magic
incantation, but I did spend an hour or so on it this afternoon. Got no
joy, same as you. :(
Best,
dp
Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark
Knecht:
>On 10/21/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>
>
>
>
>>On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector Centeno-Garcia wrote:
>>
>>
>>
>>
>>>Thanks! We help ourselves... that's the nice thing about open source.
>>>With the -r option Crystal works for me now. What is this option for?
>>>One plugin that I can't get working is the SRI_1010. It would be very
>>>nice to have this one unless you know of any other free convolution
>>>plugin. I tried with and without the -r option and I get:
>>>
>>>err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of this
>>>midi device. Assuming FM Synth
>>>gui_thread_id = 10
>>>could not post message to gui thread
>>>cannot create editor
>>>
>>>
>>>
>>>
>>hmmm... this looks like the plugin is trying to open a midi port by
>>itself. try to configure wine so that it does not see any alsa midiport.
>>
>>
>>
>>
>>
>>>Have any of you tried to use this one?
>>>
>>>cheers!
>>>
>>>
>>>Hector.
>>>
>>>
>>>
>>>
>>--
>>torben Hohn
>>http://galan.sourceforge.net -- The graphical Audio language
>>
>>
>>
>>
>Hi all,
> I just got a few minutes to try xfst on my AMD64 machine. Did
>anyone else run into this:
>
>mark@lightning ~/CODE/xfst-0.3 $ make
>winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
>fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
>winebuild: unrecognized option `--debug'
>Usage: winebuild [OPTIONS] [FILES]
>
><SNIP>
>
>make: *** [xfst.exe.dbg.c] Error 1
>mark@lightning ~/CODE/xfst-0.3 $
>
>I hope I'm doing this correctly. I put the Steinberg headers in the
>vst directory and then ran make. That seems to be what the README file
>suggests. There is also a file called readme.jack-fst which seems ot
>be leftover from the older Jack_fst. Is that correct?
>
>Make does seem to want to run winebuild, and winebuild on my system
>doesn't support an option called debug.
>
>mark@lightning ~/CODE/xfst-0.3 $ wine --version
>Wine 20050930
>mark@lightning ~/CODE/xfst-0.3 $
>
> Did I miss some conversation about this?
>
>Thanks,
>Mark
>
>
>
>
Hi Marc,
I got the same failure with wine20050930. I downgraded wine to wine20050830
and xfst-0.3 compiled cleanly.
You also have to change the vst header as for jack_fst. Otherwise you get some
error messages and make will "fail". I don't know exactly what I changed
exactly, but you can find the headers which I used attached to this e-mail.
I still got a failure message, during compilation but xfst works.
good luck,
Martin
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
11:57 a.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file that's
not present in the xfst package. The --exe mode requires no spec file,
but either it's not working as advertised or I'm still missing something
about it. One of those modes is supposed to be used when winebuild
creates a .c file.
I wonder if I might find some help on one of theWine lists. I'll try
there and let you know if I discover anything.
Mark Knecht wrote:
Btw, this is wine-20050930, I think you're on the same version, yes ?
Yes.
We should also be sure to test DSSI.
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run
commercial VST's? Not
clear. Seems like something homegrown that competes.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything.
Also, I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
I certainly agree that any writing you do will be helpful.
Cheers,
Mark
1:41 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sunday 23 October 2005 13:57, Mark Knecht wrote:
Incidentally I'm following this thread with the greatest interest, as I've all
about given up on wine running anything "I" want to run on it, and am looking
forward to Dave's tutorial. Waiting in anticipation. Nigel.
On 10/23/05, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
Hi Mark.
Theres a bit about it on the DSSI home page, that I accessed from DSSI on
planetccrma audio software list.
Mark Knecht wrote:
I wonder if I might find some help on one of theWine lists. I'll try
there and let you know if I discover anything.
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file that's
not present in the xfst package. The --exe mode requires no spec file,
but either it's not working as advertised or I'm still missing something
about it. One of those modes is supposed to be used when winebuild
creates a .c file. Btw, this is wine-20050930, I think you're
on the same version, yes ?
Yes.
We should also be sure to test DSSI.
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run
commercial VST's? Not
clear. Seems like something homegrown that competes.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything. Also, I'm in the process of rewriting the
VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
I certainly agree that any writing you do will be helpful.
Cheers,
Mark
2:21 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sunday 23 October 2005 07:40, Nigel Henry wrote:
On Sunday 23 October 2005 13:57, Mark Knecht wrote:
Incidentally I'm following this thread with the greatest interest, as I've
all about given up on wine running anything "I" want to run on it, and am
looking forward to Dave's tutorial. Waiting in anticipation. Nigel.
Hi Mark. Sorry about the last post. There are about 2 lines of info. Tried to
progress to sourceforge to download dssi-vst, but konqueror suddenly starting
using 100%+ cpu. Don't know if some disgruntled windows user has knobbled the
sourceforge dssi-vst page. I was going to DL dssi-vst and see if there was
anymore info about it in the README. Doh. Nigel.
On 10/23/05, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
Hi Mark.
Theres a bit about it on the DSSI home page, that I accessed from DSSI on
planetccrma audio software list.
Mark Knecht wrote:
I wonder if I might find some help on one of theWine lists. I'll try
there and let you know if I discover anything.
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file
that's not present in the xfst package. The --exe mode requires no spec
file, but either it's not working as advertised or I'm still missing
something about it. One of those modes is supposed to be used when
winebuild creates a .c file. Btw, this is wine-20050930, I think you're
on the same version, yes ?
Yes.
We should also be sure to test DSSI.
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run
commercial VST's? Not
clear. Seems like something homegrown that competes.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything. Also,
I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
I certainly agree that any writing you do will be helpful.
Cheers,
Mark
3:20 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Nigel Henry <cave.dnb(a)tiscali.fr> wrote:
Nigel,
I don't know the status of dssi-vst, but it sticks in my mind (and
this was quite some time ago) that it didn't handle GUIs at all. It
only worked with VSts that ran in the backgorund or could run without
a GUI. I was surprised that this was useful, but I was told on the
Rosegarden list that there were numerous VSTs that worked this way.
Anyway, I've not used it and up until now thought that it was a
pretty specialized piece of software. I could be very wrong about
everything above.
From my POV, all Windows VST's of interest to me includes some part
of a GUI for control. It has been my thought that to get this GUI I
must run Wine, in one form or another. Possibly I'm wrong about that
or possibly DSSI has new capabilities.
Let us know what you find out.
Cheers,
Mark
Incidentally I'm following this thread with the greatest interest, as I've
all about given up on wine running anything "I" want to run on it, and am
looking forward to Dave's tutorial. Waiting in anticipation. Nigel.
Hi Mark. Sorry about the last post. There are about 2 lines of info. Tried to
progress to sourceforge to download dssi-vst, but konqueror suddenly starting
using 100%+ cpu. Don't know if some disgruntled windows user has knobbled the
sourceforge dssi-vst page. I was going to DL dssi-vst and see if there was
anymore info about it in the README. Doh. Nigel.
3:25 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
I'm not going to put up a revised edition until I resolve the winebuild
issues with Torben's Makefile. The only problem appears to be a syntax
issue, hopefully I can resolve it within a few days.
Best,
dp
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run commercial VST's? Not
clear. Seems like something homegrown that competes.
Sorry about the typo, it should have read dssi-vst. But I think that's
been made clear by some other posts to this thread.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything.
Also, I'm
in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
3:47 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Dave Phillips wrote:
Mark Knecht wrote:
I'm not going to put up a revised edition until I resolve the
winebuild issues with Torben's Makefile. The only problem appears to
be a syntax issue, hopefully I can resolve it within a few days.
Best,
dp
Not to muddy the waters guys but Mark, you quoted "Going back to a
previous Wine version was Not an option". Just curious why...
Thac, whom packages now primarily for PClinuxOS, has recently packaged
Xfst againts 20050830 (two months old) and it appears to work fine.
Including HyperCanvas synth which I know I have Dave hooked on for life! :)
Is the latest Wine version doing some cool stuff with other M$ based
audio apps? Or are you simply remaining vigilant to promote forward
growth? Not that I'd disagree with that concept but its ironic we have
lived with using a Wine version , indeed, the ONLY reliable version that
jack_fst or dssi would work against for the mass's that was quite old.
Cheers,
R~
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run commercial VST's? Not
clear. Seems like something homegrown that competes.
Sorry about the typo, it should have read dssi-vst. But I think that's
been made clear by some other posts to this thread.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything.
Also,
I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
4:11 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Russell Hanaghan <hanaghan(a)starband.net> wrote:
Not to muddy the waters guys but Mark, you quoted
"Going back to a
previous Wine version was Not an option". Just curious why...
Hi Russel,
Because going backward does not meet my view of "a supported
environment". I think that Dave and I are very much approaching this
from the POV that whatever way we work out to really use VSTs needs to
live into the future. We have two different environments on the table
at the moment:
1) A linux-based platform that holds the VST and talks to Wine & Jack
as required. This was jack_fst and is now xfst.
2) A Windows-based platform that holds the VST and talks to Jack.
Right now we're sort of intersted in Savihost, but there are likely
others.
My understanding of status an issues:
a) Of the two above #1 requires a developer (Torben) agree to maintain
xfst into the future or we get stranded again some time out there.
b) #2 above doesn't have the complication of a Linux app but adds the
complication of a second Windows app, as well as requiring Wine to do
a good job talking to Jack. At this time it appears Wine is broken for
Jack >0.99 so that doesn't work right now.
Of the two above I prefer #1 in the short term, and #2 in the long
term. I think #2 can be done, eventually, as long as the Jack
developers don't break Wine audio support, as they did with
Jack-0.100.+, the way the Wine developers broke jack_fst memory
mapping.
Anyway, I'm looking for a solution that works and allows me ot move
forward with Wine.
There are good reasons to use the newest Wine. They have greatly
reduced the number of install problems and more apps are working now.
Cheers,
Mark
4:37 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Russell Hanaghan skrev:
Dave Phillips wrote:
upgrade i have just packaged wine-20050930 and xfst-0.4 for pclo
available now
im rebuilding them for mandriva 2006.0 now
/Torbjörn Turpeinen (Thac)
Mark Knecht wrote:
I'm not going to put up a revised edition until I resolve the
winebuild issues with Torben's Makefile. The only problem appears to
be a syntax issue, hopefully I can resolve it within a few days.
Best,
dp
Not to muddy the waters guys but Mark, you quoted "Going back to a
previous Wine version was Not an option". Just curious why...
Thac, whom packages now primarily for PClinuxOS, has recently packaged
Xfst againts 20050830 (two months old) and it appears to work fine.
Including HyperCanvas synth which I know I have Dave hooked on for
life! :)
Is the latest Wine version doing some cool stuff with other M$ based
audio apps? Or are you simply remaining vigilant to promote forward
growth? Not that I'd disagree with that concept but its ironic we have
lived with using a Wine version , indeed, the ONLY reliable version
that jack_fst or dssi would work against for the mass's that was quite
old.
Cheers,
R~
What's DSSI? Answering self:
http://dssi.sourceforge.net/
From a quick read, how does DSSI allow me to run commercial VST's? Not
clear. Seems like something homegrown that competes.
Sorry about the typo, it should have read dssi-vst. But I think
that's been made clear by some other posts to this thread.
As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so
perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
xfst & latest Wine - definitely yes. What's dss-vst? Google didn't
tell me anything.
Also,
I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Seems possibly a bit premature based on these results but I probably
don't have a good view. Clearly the jack_fst stuff that's been there
for the last year or more is probably no longer helpful to many. It
seems like xfst and at least last months Wine is probably a better
solution, but has it been tested with enough VST's to think it works
well? Performance? xruns? All the messy stuff of real life? ;-)
1:18 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Dave Phillips wrote:
Mark Knecht wrote:
seems a little emvarrissing that all the talented linux programmers are
concentrating their efforts on running M$ based plugins. should be a
slew of dssi's by now, or maybe a reaktor killer...
On 10/22/05, Dave Phillips
<dlphillips(a)woh.rr.com> wrote:
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file
that's not present in the xfst package. The --exe mode requires no
spec file, but either it's not working as advertised or I'm still
missing something about it. One of those modes is supposed to be used
when winebuild creates a .c file.
Btw, this is wine-20050930, I think you're on the same version, yes ?
We should also be sure to test DSSI. As far as I can tell, the
vstserver project is dead, and the fst project is on a back-burner, so
perhaps we should concentrate on xfst and dss-vst with the latest WINE
releases ?
Also, I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Best,
dp
Mark Knecht wrote:
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
On 10/22/05, Martin Wohlleben
<Martin.Wohlleben(a)gmx.de> wrote:
> Am Sonntag, 23. Oktober 2005 00:02 schrieb Mark Knecht:
>
>
>
>
>> On 10/21/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>>
>>
>>
>>
>>> On Fri, Oct 21, 2005 at 08:33:55PM -0400, Hector Centeno-Garcia
>>> wrote:
>>>
>>>
>>>
>>>
>>>> Thanks! We help ourselves... that's the nice thing about open
>>>> source.
>>>> With the -r option Crystal works for me now. What is this
>>>> option for?
>>>> One plugin that I can't get working is the SRI_1010. It would
>>>> be very
>>>> nice to have this one unless you know of any other free
>>>> convolution
>>>> plugin. I tried with and without the -r option and I get:
>>>>
>>>> err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type
>>>> of this
>>>> midi device. Assuming FM Synth
>>>> gui_thread_id = 10
>>>> could not post message to gui thread
>>>> cannot create editor
>>>>
>>>>
>>>>
>>>
>>> hmmm... this looks like the plugin is trying to open a midi port by
>>> itself. try to configure wine so that it does not see any alsa
>>> midiport.
>>>
>>>
>>>
>>>
>>>
>>>> Have any of you tried to use this one?
>>>>
>>>> cheers!
>>>>
>>>>
>>>> Hector.
>>>>
>>>>
>>>>
>>>
>>> --
>>> torben Hohn
>>> http://galan.sourceforge.net -- The graphical Audio language
>>>
>>>
>>>
>>
>> Hi all,
>> I just got a few minutes to try xfst on my AMD64 machine. Did
>> anyone else run into this:
>>
>> mark@lightning ~/CODE/xfst-0.3 $ make
>> winebuild -o xfst.exe.dbg.c --debug -C. audiomaster.c fst.c
>> fstinfofile.c gtk.c jfst.c vsti.c vstwin.c
>> winebuild: unrecognized option `--debug'
>> Usage: winebuild [OPTIONS] [FILES]
>>
>> <SNIP>
>>
>> make: *** [xfst.exe.dbg.c] Error 1
>> mark@lightning ~/CODE/xfst-0.3 $
>>
>> I hope I'm doing this correctly. I put the Steinberg headers in the
>> vst directory and then ran make. That seems to be what the README
>> file
>> suggests. There is also a file called readme.jack-fst which seems ot
>> be leftover from the older Jack_fst. Is that correct?
>>
>> Make does seem to want to run winebuild, and winebuild on my system
>> doesn't support an option called debug.
>>
>> mark@lightning ~/CODE/xfst-0.3 $ wine --version
>> Wine 20050930
>> mark@lightning ~/CODE/xfst-0.3 $
>>
>> Did I miss some conversation about this?
>>
>> Thanks,
>> Mark
>>
>>
>>
>
> Hi Marc,
>
> I got the same failure with wine20050930. I downgraded wine to
> wine20050830
> and xfst-0.3 compiled cleanly.
> You also have to change the vst header as for jack_fst. Otherwise
> you get some
> error messages and make will "fail". I don't know exactly what I
> changed
> exactly, but you can find the headers which I used attached to
> this e-mail.
> I still got a failure message, during compilation but xfst works.
>
> good luck,
> Martin
>
>
>
>
Thanks for the confirmation Martin. Backing down on Wine is not an
option. I'll wait and hope Torben will update the files to fix it.
Cheers,
Mark
Hi guys:
Yes, I'm having the same problem with winebuild. The trouble is that
the syntax for winebuild's options has changed from what Torben has in
the Makefile. Unfortunately I haven't yet figured out the new magic
incantation, but I did spend an hour or so on it this afternoon. Got no
joy, same as you. :(
Best,
dp
2 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Ken <renueden(a)earthlink.net> wrote:
seems a
little emvarrissing that all the talented linux programmers are
concentrating their efforts on running M$ based plugins. should be a
slew of dssi's by now, or maybe a reaktor killer...
Personally I don't see it this way at all, at least form a user's
point of view. I write music. I want sounds. I use whatever tools are
available to me to do it. If I have Reaktor, which I do, but I don't
want to run it on Win XP for either stability or licensing reasons,
then running it Linux is a sensible thing to look into. When Dave,
myself and others discuss this topic I don't think that any of us are
speaking as developers. I'm certainly not one.
If the folks writing Wine are doing the tasks they want to accomplish
then we are doing them a service in testing Wine. (Whether through
xfst or Wine/Savihost/etc.) I am served if I can run Reaktor.
I have little patience for the idea of *waiting* for first 'a Reaktor
Killer' and then later a set of instruments programmed into that
killer that allow me the breadth and depth of sound I get from Reaktor
today. I'll be happy to use them if and when they appear. A very good
example (IMO) is ZynAddSubFx. Good synth. Very usable. Very limited
preprogrammed libray of sounds for a casual user to start with.
Compared to Reaktor Session, where you start with 100's of interesting
preprogrammed sounds for the cost of $200 I saved at least weeks of
time, most probably months of time over the last few years.
Just my 2.5 cents,
Mark
3:02 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
On 10/23/05, Ken <renueden(a)earthlink.net> wrote:
good points, thanks for the info.
seems a little emvarrissing that all the talented
linux programmers are
concentrating their efforts on running M$ based plugins. should be a
slew of dssi's by now, or maybe a reaktor killer...
Personally I don't see it this way at all, at least form a user's
point of view. I write music. I want sounds. I use whatever tools are
available to me to do it. If I have Reaktor, which I do, but I don't
want to run it on Win XP for either stability or licensing reasons,
then running it Linux is a sensible thing to look into. When Dave,
myself and others discuss this topic I don't think that any of us are
speaking as developers. I'm certainly not one.
If the folks writing Wine are doing the tasks they want to accomplish
then we are doing them a service in testing Wine. (Whether through
xfst or Wine/Savihost/etc.) I am served if I can run Reaktor.
I have little patience for the idea of *waiting* for first 'a Reaktor
Killer' and then later a set of instruments programmed into that
killer that allow me the breadth and depth of sound I get from Reaktor
today. I'll be happy to use them if and when they appear. A very good
example (IMO) is ZynAddSubFx. Good synth. Very usable. Very limited
preprogrammed libray of sounds for a casual user to start with.
Compared to Reaktor Session, where you start with 100's of interesting
preprogrammed sounds for the cost of $200 I saved at least weeks of
time, most probably months of time over the last few years.
Just my 2.5 cents,
Mark
3:45 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sun, Oct 23, 2005 at 07:32:57AM -0400, Dave Phillips wrote:
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
Dave,
I'm only here for a few minutes this evening. In the make file
there seems to be more or less a a single invocation of winebuild that
has 'debug' in it. Can we just remove it?
Since the option isn't supported, and wasn't in the man page, I
don't know what Torben intended in it's use.
Anyway, part of this exercise, in my mind, is finding a solution
that works AND is maintainable out into the future. I suspect that
when we get past this we will see it as our first, small maintainance
patch. What's important is that we don't go backward with old Wine,
but always forward with new Wine.
Cheers,
Mark
Hi Mark:
Unfortunately merely removing the --debug option doesn't resolve the
options problem. Winebuild now uses "modes" to define its actions, and
those modes are further defined by a set of options pertaining to that
mode. The problem now is that I can't figure out the right combination
of mode + option(s). The --dll mode requires a .spec or .def file that's
not present in the xfst package. The --exe mode requires no spec file,
but either it's not working as advertised or I'm still missing something
about it. One of those modes is supposed to be used when winebuild
creates a .c file.
Btw, this is wine-20050930, I think you're on the same version, yes ?
We should also be sure to test DSSI. As far as I can tell, the vstserver
project is dead, and the fst project is on a back-burner, so perhaps we
should concentrate on xfst and dss-vst with the latest WINE releases ?
Also, I'm in the process of rewriting the VST+Linux tutorial, I'm
displacing the vstserver and fst material and putting up front new
material regarding my experience with xfst and DSSI. It should be
completed tomorrow (I'm not at my Demudi machine).
Best,
dp
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
4:23 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
Hi Torben,
0.4 gets farther but still has problems for me. I commented out two
functions in aeffectx.h to get this far. Unfortunately this looks like
mostly an AMD64 problem:
mark@lightning ~/CODE/xfst-0.4 $ make
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o audiomaster.o audiomaster.c
In file included from ./fst.h:26,
from jackvst.h:8,
from audiomaster.c:23:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
In file included from audiomaster.c:24:
./vst/aeffectx.h:21: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/aeffectx.h:1000: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o fst.o fst.c
In file included from fst.h:26,
from fst.c:4:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o fstinfofile.o fstinfofile.c
In file included from fst.h:26,
from fstinfofile.c:2:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
In file included from fstinfofile.c:3:
vst/aeffectx.h:21: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
vst/aeffectx.h:1000: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o gtk.o gtk.c
In file included from ./fst.h:26,
from jackvst.h:8,
from gtk.c:20:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
gtk.c: In function `bypass_handler':
gtk.c:34: warning: cast to pointer from integer of different size
gtk.c: In function `mute_handler':
gtk.c:42: warning: cast to pointer from integer of different size
gtk.c: In function `remove_handler':
gtk.c:49: warning: cast to pointer from integer of different size
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o jfst.o jfst.c
In file included from ./fst.h:26,
from jfst.c:23:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
In file included from jfst.c:25:
./vst/aeffectx.h:21: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/aeffectx.h:1000: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o vsti.o vsti.c
In file included from ./fst.h:26,
from ./jackvst.h:8,
from vsti.c:32:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
In file included from vsti.c:33:
./vst/aeffectx.h:21: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/aeffectx.h:1000: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vsti.c: In function `queue_midi':
vsti.c:77: warning: assignment from incompatible pointer type
winegcc -c `pkg-config --cflags gtk+-2.0` `pkg-config --cflags jack`
`pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:49: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:70: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:72: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:74: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:75: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:100: warning: `__cdecl__' attribute ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c:56: warning: `__stdcall__' attribute ignored
vstwin.c:153: warning: `__stdcall__' attribute ignored
vstwin.c: In function `fst_create_editor':
vstwin.c:381: warning: cast from pointer to integer of different size
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
winebuild: ld -m elf_i386 -r failed with status 256
winegcc: winebuild failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
I will try it on a 32-bit machine later today or tomorrow.
Thanks,
Mark
6 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht wrote:
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
Hi Torben,
0.4 gets farther but still has problems for me. I commented out two
functions in aeffectx.h to get this far. Unfortunately this looks like
mostly an AMD64 problem:
6:18 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht wrote:
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...)
- Mark
On 10/23/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
Hi Torben,
0.4 gets farther but still has problems for me. I commented out two
functions in aeffectx.h to get this far. Unfortunately this looks like
mostly an AMD64 problem:
7:28 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark Knecht wrote:
On 10/23/05, Lee Revell <rlrevell(a)joe-job.com>
wrote:
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make
On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht
wrote:
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...) On 10/23/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
Hi Torben,
0.4 gets farther but still has problems for me. I commented out two
functions in aeffectx.h to get this far. Unfortunately this looks like
mostly an AMD64 problem:
- Mark
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
8 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark Knecht
wrote:
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
Thanks,
Mark
On 10/23/05, Lee Revell
<rlrevell(a)joe-job.com> wrote:
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht
wrote:
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...) On 10/23/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
>
> xfst IS fst. i just removed the hacky stuff.
> i removed the debug stuff from the makefile and it still works with my
> wine version.
>
> Wine 20050111
>
> i uploaded to
> http://galan.sf.net/xfst-0.4.tar.gz
>
> please report back.
Hi Torben,
0.4 gets farther but still has problems for me. I commented out two
functions in aeffectx.h to get this far. Unfortunately this looks like
mostly an AMD64 problem:
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
8:13 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sun, Oct 23, 2005 at 03:00:24PM -0700, Mark Knecht wrote:
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
hmmm... try to give the link call -m32 also...
bedtime....
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark
Knecht wrote:
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $ On 10/23/05, Lee Revell
<rlrevell(a)joe-job.com> wrote:
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht
wrote:
> On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
> >
> > xfst IS fst. i just removed the hacky stuff.
> > i removed the debug stuff from the makefile and it still works with my
> > wine version.
> >
> > Wine 20050111
> >
> > i uploaded to
> > http://galan.sf.net/xfst-0.4.tar.gz
> >
> > please report back.
>
> Hi Torben,
> 0.4 gets farther but still has problems for me. I commented out two
> functions in aeffectx.h to get this far. Unfortunately this looks like
> mostly an AMD64 problem:
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...)
Thanks,
Mark
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
24 Oct
24 Oct
4:40 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Mark,
Perhaps we can ask Thac what "magic" he did to get this to compile; I
have just updated to his recent build of Xfst on Wine 20050930 and it
works like a trooper on my 64 bit box and an old SBlive 5.1. It runs all
my regular suite of Vst's and they are operational with no obvious GUI
bugs. Mind you, I have not put them through the paces on any recording
but they do fire up and work.
Russell
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark
Knecht wrote:
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id], <n>)' -
ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
Thanks,
Mark
On 10/23/05, Lee Revell
<rlrevell(a)joe-job.com> wrote:
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make
On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht
wrote:
>On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>
>
>>xfst IS fst. i just removed the hacky stuff.
>>i removed the debug stuff from the makefile and it still works with my
>>wine version.
>>
>>Wine 20050111
>>
>>i uploaded to
>>http://galan.sf.net/xfst-0.4.tar.gz
>>
>>please report back.
>>
>>
>Hi Torben,
> 0.4 gets farther but still has problems for me. I commented out two
>functions in aeffectx.h to get this far. Unfortunately this looks like
>mostly an AMD64 problem:
>
>
Is even theoretically possible to run 32 bit VST plugins in a pure 64
bit environment?
Lee
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...)
7:25 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Russell Hanaghan skrev:
Mark Knecht wrote:
First of all i have built almost all critical dependencys also to ahve
full control.
Then there is a very straight forward spec nothing magic about that.
On 10/23/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
Mark,
Perhaps we can ask Thac what "magic" he did to get this to compile; I
have just updated to his recent build of Xfst on Wine 20050930 and it
works like a trooper on my 64 bit box and an old SBlive 5.1. It runs
all my regular suite of Vst's and they are operational with no obvious
GUI bugs. Mind you, I have not put them through the paces on any
recording but they do fire up and work.
Russell
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark
Knecht wrote:
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
Thanks,
Mark
On 10/23/05, Lee Revell
<rlrevell(a)joe-job.com> wrote:
> On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht wrote:
>
>
>> On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>>
>>
>>> xfst IS fst. i just removed the hacky stuff.
>>> i removed the debug stuff from the makefile and it still works
>>> with my
>>> wine version.
>>>
>>> Wine 20050111
>>>
>>> i uploaded to
>>> http://galan.sf.net/xfst-0.4.tar.gz
>>>
>>> please report back.
>>>
>>
>> Hi Torben,
>> 0.4 gets farther but still has problems for me. I commented out
>> two
>> functions in aeffectx.h to get this far. Unfortunately this looks
>> like
>> mostly an AMD64 problem:
>>
>
> Is even theoretically possible to run 32 bit VST plugins in a pure 64
> bit environment?
>
> Lee
>
Good question. Problem is I don't know if I'm truly pure 64-bit here.
I have a pure 64-bit kernel, I think, but I also have emulation IA32
libraries installed which I'm pretty sure Wine is using.
I'm doing apples as much as possible. Using the Crystal VST I can get
sound using Savihost under Wine and the Alsa driver. Latency is bad,
etc., and I want to run Jack, but I have Jack-0.100.5 installed and
Wine doesn't seem to talk to that version of Jack.
On the same machine xfst doesn't link. Notice the message:
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
ld: Relocatable linking with relocations from format elf64-x86-64
(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
So I suspect that when Torben gets a chance to look at this he'll find
a way to make it work. (I hope...)
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make
8:06 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
tobbe(a)nyvalls.se wrote:
Russell Hanaghan skrev:
I wonder....aren't we using Gcc 3.4 or somehting ancient like that
Thac? I noticed the subject line after sending mail. Maybe it's relevant.
R~
Mark Knecht wrote:
First of all i have built almost all critical dependencys also to ahve
full control.
Then there is a very straight forward spec nothing magic about that.
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Mark,
Perhaps we can ask Thac what "magic" he did to get this to compile; I
have just updated to his recent build of Xfst on Wine 20050930 and it
works like a trooper on my 64 bit box and an old SBlive 5.1. It runs
all my regular suite of Vst's and they are operational with no obvious
GUI bugs. Mind you, I have not put them through the paces on any
recording but they do fire up and work.
Russell
On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark
Knecht wrote:
>On 10/23/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
>
>
>
>
>>On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht wrote:
>>
>>
>>
>>
>>>On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>>>
>>>
>>>
>>>
>>>>xfst IS fst. i just removed the hacky stuff.
>>>>i removed the debug stuff from the makefile and it still works
>>>>with my
>>>>wine version.
>>>>
>>>>Wine 20050111
>>>>
>>>>i uploaded to
>>>>http://galan.sf.net/xfst-0.4.tar.gz
>>>>
>>>>please report back.
>>>>
>>>>
>>>>
>>>Hi Torben,
>>> 0.4 gets farther but still has problems for me. I commented out
>>>two
>>>functions in aeffectx.h to get this far. Unfortunately this looks
>>>like
>>>mostly an AMD64 problem:
>>>
>>>
>>>
>>Is even theoretically possible to run 32 bit VST plugins in a pure 64
>>bit environment?
>>
>>Lee
>>
>>
>>
>Good question. Problem is I don't know if I'm truly pure 64-bit here.
>I have a pure 64-bit kernel, I think, but I also have emulation IA32
>libraries installed which I'm pretty sure Wine is using.
>
>I'm doing apples as much as possible. Using the Crystal VST I can get
>sound using Savihost under Wine and the Alsa driver. Latency is bad,
>etc., and I want to run Jack, but I have Jack-0.100.5 installed and
>Wine doesn't seem to talk to that version of Jack.
>
>On the same machine xfst doesn't link. Notice the message:
>
>winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
>jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
>--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
>ld: Relocatable linking with relocations from format elf64-x86-64
>(audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not supported
>
>So I suspect that when Torben gets a chance to look at this he'll find
>a way to make it work. (I hope...)
>
>
>
hmm... i dont have x86-64 here.
but try
CFLAGS=-m32 make
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
Thanks,
Mark
25 Oct
25 Oct
3:36 a.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Russell Hanaghan skrev:
tobbe(a)nyvalls.se wrote:
yes but i have built it for mandriva 2006 with gcc-4.0.1 also and it
works just fine.
but when you look at this line
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
it is clear that the wine he is using is compiled 32bit and that he is
trying to compile xfst 64bit
so either he should use a 64bit wine or compile xfst 32bit
Russell Hanaghan skrev:
I wonder....aren't we using Gcc 3.4 or somehting ancient like that
Thac? I noticed the subject line after sending mail. Maybe it's
relevant.
R~
Mark Knecht wrote:
First of all i have built almost all critical dependencys also to ahve
full control.
Then there is a very straight forward spec nothing magic about that.
On 10/23/05, torbenh(a)gmx.de
<torbenh(a)gmx.de> wrote:
> On Sun, Oct 23, 2005 at 01:18:00PM -0700, Mark Knecht wrote:
>
>
>
>
>> On 10/23/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
>>
>>
>>
>>> On Sun, 2005-10-23 at 11:23 -0700, Mark Knecht wrote:
>>>
>>>
>>>
>>>> On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
>>>>
>>>>
>>>>
>>>>> xfst IS fst. i just removed the hacky stuff.
>>>>> i removed the debug stuff from the makefile and it still works
>>>>> with my
>>>>> wine version.
>>>>>
>>>>> Wine 20050111
>>>>>
>>>>> i uploaded to
>>>>> http://galan.sf.net/xfst-0.4.tar.gz
>>>>>
>>>>> please report back.
>>>>>
>>>>
>>>> Hi Torben,
>>>> 0.4 gets farther but still has problems for me. I commented out
>>>> two
>>>> functions in aeffectx.h to get this far. Unfortunately this looks
>>>> like
>>>> mostly an AMD64 problem:
>>>>
>>>
>>> Is even theoretically possible to run 32 bit VST plugins in a
>>> pure 64
>>> bit environment?
>>>
>>> Lee
>>>
>>
>> Good question. Problem is I don't know if I'm truly pure 64-bit
>> here.
>> I have a pure 64-bit kernel, I think, but I also have emulation IA32
>> libraries installed which I'm pretty sure Wine is using.
>>
>> I'm doing apples as much as possible. Using the Crystal VST I can
>> get
>> sound using Savihost under Wine and the Alsa driver. Latency is bad,
>> etc., and I want to run Jack, but I have Jack-0.100.5 installed and
>> Wine doesn't seem to talk to that version of Jack.
>>
>> On the same machine xfst doesn't link. Notice the message:
>>
>> winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o
>> gtk.o
>> jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
>> --libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11
>> -luuid
>> ld: Relocatable linking with relocations from format elf64-x86-64
>> (audiomaster.o) to format elf32-i386 (xfst.qiWLmx.o) is not
>> supported
>>
>> So I suspect that when Torben gets a chance to look at this he'll
>> find
>> a way to make it work. (I hope...)
>>
>
> hmm... i dont have x86-64 here.
> but try
> CFLAGS=-m32 make
>
>
Hi Torben,
It changed the message a bit but it's still not happy:
winegcc -c -m32 `pkg-config --cflags gtk+-2.0` `pkg-config --cflags
jack` `pkg-config --cflags jack` -I. -o vstwin.o vstwin.c
In file included from fst.h:26,
from vstwin.c:14:
./vst/AEffect.h:35: warning: malformed '#pragma pack(push[, id],
<n>)' - ignored
./vst/AEffect.h:191: warning: #pragma pack (pop) encountered without
matching #pragma pack (push, <n>)
vstwin.c: In function `fst_load':
vstwin.c:514: warning: assignment from incompatible pointer type
winegcc -mwindows -o xfst.exe audiomaster.o fst.o fstinfofile.o gtk.o
jfst.o vsti.o vstwin.o `pkg-config --libs gtk+-2.0` `pkg-config
--libs jack` `pkg-config --libs alsa` -L/usr/X11R6/lib -lX11 -luuid
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible /usr/lib32/libwine.so when searching for -lwine
/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lwine
collect2: ld returned 1 exit status
winegcc: x86_64-pc-linux-gnu-gcc failed.
make: *** [xfst.exe] Error 2
mark@lightning ~/CODE/xfst-0.4 $
Thanks,
Mark
Mark,
Perhaps we can ask Thac what "magic" he did to get this to compile; I
have just updated to his recent build of Xfst on Wine 20050930 and it
works like a trooper on my 64 bit box and an old SBlive 5.1. It runs
all my regular suite of Vst's and they are operational with no obvious
GUI bugs. Mind you, I have not put them through the paces on any
recording but they do fire up and work.
Russell
24 Oct
24 Oct
1:24 p.m.
New subject: [linux-audio-user] multiple simultaneous instances of xmms (or other graphical app) w/JACK?
Hi all,
I would like to simultaneously play 2 audio files and mix their output
via JACK. I want a JACK solution because I also have BruteFIR in the
workflow. I can play a single instance of xmms through JACK without
problem and I can open multiple instances of xmms without problem - once
enabling that option. Here's the hitch: when I try to play audio files
with the two xmms instances, the first works fine, but the second gives
an error complaining that it can't open the output device and to check
that another program isn't blocking it.
I'm using xmms-jack-0.14 as the output from xmms into JACK, but it
doesn't seem to handle multiple instances. Am I correct and is there a
workaround? Is there another/better (lightweight w/GUI) jack-aware
audio player that I could use instead of/in addition to xmms? I'm
primarily playing .mp3 & .wav audio files.
Distro is a fairly stock FC4 (with FC4 kernel slightly massaged &
rebuilt to use realtime-lsm module)
JACK 0.100.6
QJackCtl 0.2.18
Thanks in advance,
Rick
3:09 p.m.
New subject: [linux-audio-user] multiple simultaneous instances of xmms (or other graphical app) w/JACK?
On Mon, 2005-10-24 at 11:24 -0400, Rick Wright wrote:
Hi all,
I would like to simultaneously play 2 audio files and mix their output
via JACK. I want a JACK solution because I also have BruteFIR in the
workflow. I can play a single instance of xmms through JACK without
problem and I can open multiple instances of xmms without problem - once
enabling that option. Here's the hitch: when I try to play audio files
with the two xmms instances, the first works fine, but the second gives
an error complaining that it can't open the output device and to check
that another program isn't blocking it.
This is an XMMS bug. Please report it to the XMMS developers.
Lee
3:20 p.m.
New subject: [linux-audio-user] multiple simultaneous instances of xmms (or other graphical app) w/JACK?
On Mon, 2005-10-24 at 11:24 -0400, Rick Wright wrote:
> Hi all,
> I would like to simultaneously play 2 audio files and mix their output
> via JACK. I want a JACK solution because I also have BruteFIR in the
> workflow. I can play a single instance of xmms through JACK without
> problem and I can open multiple instances of xmms without problem - once
> enabling that option. Here's the hitch: when I try to play audio files
> with the two xmms instances, the first works fine, but the second gives
> an error complaining that it can't open the output device and to check
> that another program isn't blocking it.
Did you try running xmms in oss mode but through jacklaunch?
That works fine for me.
You can also play the file with a PureData object.
MB
3:34 p.m.
New subject: [linux-audio-user] multiple simultaneous instances of xmms (or other graphical app) w/JACK?
On 10/24/05, Rick Wright <riwright(a)vt.edu> wrote:
Is there another/better (lightweight w/GUI)
jack-aware
audio player that I could use instead of/in addition to xmms? I'm
primarily playing .mp3 & .wav audio files.
alsaplayer will do this.
- Mark
23 Oct
23 Oct
4:38 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On Sun, Oct 23, 2005 at 08:03:12PM +0200, torbenh(a)gmx.de wrote:
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
ok... thac just built rpms. it works.
go xfst. go.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
5:05 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de> wrote:
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
OK, on one of my 32-bit systems I got much further. The GUI comes up
and Crystal is visible in QJC's connection windows. However almost
immediately I see this in the terminal where I'm running:
mark@gigastudio ~/CODE/xfst-0.4 $ ./xfst ~/VSTs/Crystal.dll
gui_thread_id = 10
Got the focus
zombified - exiting from JACK
lost focus
Got the focus
lost focus
The GUI is still up but the VST is gone from QJC. I exit Crystal and see this:
Got the focus
lost focus
Got the focus
wtf.
lost focus
quit........
mark@gigastudio ~/CODE/xfst-0.4 $
mark@gigastudio ~/CODE/xfst-0.4 $ wine --version
Wine 20050930
mark@gigastudio ~/CODE/xfst-0.4 $ uname -a
Linux gigastudio 2.6.12-gentoo-r10 #1 Thu Sep 8 02:09:54 PDT 2005 i686
AMD Athlon(TM) XP1600+ AuthenticAMD GNU/Linux
mark@gigastudio ~/CODE/xfst-0.4 $
NOTE: If anythign about xfst require Wine work with Jack then it may
be a problem for this version of Wine.
Thanks,
Mark
5:34 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
Mark Knecht wrote:
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Mark,
Did you try running xfst with the -r flag? ./xfst -r ~/VSTs/Crystal.dll
That solved the same problem for me with Crystal. If that doesn't work
try changing the timeout parameter in jack to at least 1000msec.
Hector
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
OK, on one of my 32-bit systems I got much further. The GUI comes up
and Crystal is visible in QJC's connection windows. However almost
immediately I see this in the terminal where I'm running:
mark@gigastudio ~/CODE/xfst-0.4 $ ./xfst ~/VSTs/Crystal.dll
gui_thread_id = 10
Got the focus
zombified - exiting from JACK
lost focus
Got the focus
lost focus
The GUI is still up but the VST is gone from QJC. I exit Crystal and see this:
Got the focus
lost focus
Got the focus
wtf.
lost focus
quit........
mark@gigastudio ~/CODE/xfst-0.4 $
mark@gigastudio ~/CODE/xfst-0.4 $ wine --version
Wine 20050930
mark@gigastudio ~/CODE/xfst-0.4 $ uname -a
Linux gigastudio 2.6.12-gentoo-r10 #1 Thu Sep 8 02:09:54 PDT 2005 i686
AMD Athlon(TM) XP1600+ AuthenticAMD GNU/Linux
mark@gigastudio ~/CODE/xfst-0.4 $
NOTE: If anythign about xfst require Wine work with Jack then it may
be a problem for this version of Wine.
Thanks,
Mark
6:01 p.m.
New subject: [linux-audio-user] Re: [ardour-users] jack_fst and gcc4
On 10/23/05, Hector Centeno-Garcia <h.centeno(a)sympatico.ca> wrote:
Mark Knecht wrote:
Hector,
Yes, I tried it with and without the -r. At that time it was
failing. However this machine is a little bit out of date and the card
setup is a bit complex so I'm doing some fiddling with everything to
see if it helps. It seems it might as now it seems to be running, at
least with some sound cards and at some sample rates.
mark@gigastudio ~ $ cat /proc/asound/cards
0 [M2496 ]: ICE1712 - M Audio Audiophile 24/96
M Audio Audiophile 24/96 at 0xa400, irq 10
1 [R15 ]: RME9636 - RME Digi9636 (Rev 1.5)
RME Digi9636 (Rev 1.5) at 0xe2000000, irq 9
2 [CMI8738MC6 ]: CMI8738-MC6 - C-Media PCI CMI8738-MC6
C-Media PCI CMI8738-MC6 (model 55) at 0xd800, irq 11
mark@gigastudio ~ $
I'll report back more later if I figure out any real problems, but
I think it possibly is working.
Cheers,
Mark
On 10/23/05, torbenh(a)gmx.de <torbenh(a)gmx.de>
wrote:
Mark,
Did you try running xfst with the -r flag? ./xfst -r ~/VSTs/Crystal.dll
That solved the same problem for me with Crystal. If that doesn't work
try changing the timeout parameter in jack to at least 1000msec.
Hector
xfst IS fst. i just removed the hacky stuff.
i removed the debug stuff from the makefile and it still works with my
wine version.
Wine 20050111
i uploaded to
http://galan.sf.net/xfst-0.4.tar.gz
please report back.
OK, on one of my 32-bit systems I got much further. The GUI comes up
and Crystal is visible in QJC's connection windows. However almost
immediately I see this in the terminal where I'm running:
mark@gigastudio ~/CODE/xfst-0.4 $ ./xfst ~/VSTs/Crystal.dll
gui_thread_id = 10
Got the focus
zombified - exiting from JACK
lost focus
Got the focus
lost focus
The GUI is still up but the VST is gone from QJC. I exit Crystal and see this:
Got the focus
lost focus
Got the focus
wtf.
lost focus
quit........
mark@gigastudio ~/CODE/xfst-0.4 $
mark@gigastudio ~/CODE/xfst-0.4 $ wine --version
Wine 20050930
mark@gigastudio ~/CODE/xfst-0.4 $ uname -a
Linux gigastudio 2.6.12-gentoo-r10 #1 Thu Sep 8 02:09:54 PDT 2005 i686
AMD Athlon(TM) XP1600+ AuthenticAMD GNU/Linux
mark@gigastudio ~/CODE/xfst-0.4 $
NOTE: If anythign about xfst require Wine work with Jack then it may
be a problem for this version of Wine.
Thanks,
Mark
7027
days inactive
7030
days old
linux-audio-user@lists.linuxaudio.org
33 comments
11 participants
participants (11)
-
Dave Phillips -
Hector Centeno-Garcia -
Ken -
Lee Revell -
Marcus Alessi Bittencourt -
Mark Knecht -
Nigel Henry -
Rick Wright -
Russell Hanaghan -
tobbe＠nyvalls.se -
torbenh＠gmx.de