On 10/23/05, Russell Hanaghan <hanaghan@email-addr-hidden> 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
Received on Mon Oct 24 00:15:08 2005
This archive was generated by hypermail 2.1.8 : Mon Oct 24 2005 - 00:15:09 EEST