Hi Shayne, I've had problems with my serial codes for Absynth, I wanted to know if you experienced something similar. I used my second authorization from the website to activate Absynth on linux, since the codes for windows did not work. Then I did an update of wine, and it asks me for new codes, and neither of my other two codes work. Has this happened to you? I am on PlanetCCRMA (FC1) wine 20041019. Andr?s Shayne O'Connor wrote: > >i've got absynth, vokator, b4, pro-52 working on the latest version of >wine with jack_fst (unfortunately i have to enable "no memory lock" in >qjackctl to get any to work). > >fm7.dll segfaults but the fm7.exe launches with no output available (i >do remember being able to get sound out of the standalone at one stage, >but maybe with different version of wine, and not very useful, cos you >could only use the on-screen keyboard). > >i have been able to get the xpress keyboards version of fm7 working >(along with the b4, pro-53 versions), albeit without being able to >change any of the settings from the gui (so stuck with the default >preset). > >absynth works beautifully, such a great sounding synth to have access to >on linux ... also, you should make sure you have "Managed" = "N" in your >wine config, otherwise it's impossible to enter serial codes ... > >ps - i've got a whole bunch of other vsti's working (i'll head on over >to the vst compatibility page soon), such as plasticz, slayer2, t-racks >plugin suite, edirol superquartet and orchestral, grm classic bundle etc > >shayne > > > > > >
