|
From: <car...@gm...> - 2013-07-02 12:25:13
|
Actually, i got very weird behavior. First, i thought that it started working because of compiling with --enable-optimizations=no option because that was the moment it began to work. However, i tried installing with different options and even debian binary (which wasn't working initially) and they all work now. I can try later on another setup, maybe it will appear again. On Tuesday, July 02, 2013 08:55:23 AM Ryan Billing wrote: > Also read PACKAGERS.README. > > There are other optimizations that are platform dependent. It seems > that some of the "magic" choices when > > --enable-optimizations=yes > > are not necessarily complete checks, since the script must be enabling > certain options on hardware that either does not completely support the > options. > > Particularly, try --enable-vectorize=no > > That option maybe is the problem for some CPU's. It does not appear to > be validated in the configure script, only whether or not the user > enabled/disabled it. The default appears to be yes. > > Try these options: > ./configure --enable-optimizations=no --enable-vectorize=no > --enable-sse2=yes > > (sse2 option with either sse or sse2, whichever is appropriate). > > See if the problem goes away with disabling vectorize, then I will know > which compiler option causes the problem, and perhaps there can be some > better checks put in place to prevent this from being enabled on > hardware that does not support it. Then a note in PACKAGERS.README to > warn about it. > > Thanks > > On 07/01/2013 03:04 PM, car...@gm... wrote: > > Hello, > > > > I've just encountered the same problem and solved it by compiling with > > --enable-optimizations=no option. That included disabling sse2 which > > however should be supported on my computer. So either this option > > disables something else as well (and not showing it in Optimizations > > table later) or sse2 'engine' doesn't always work correct. > > > > I hope this will be helpful if you still have this problem or anybody > > else searching like i was doing before... > > > >> Hello, > >> > >> This is my first post to the list, I'm here because I'm having the exact > >> same problem. FX like chorus, delay and such work fine, but nothing > >> with distortion, as soon as I enable distortion or overdrive, the > >> output goes null. So all the presets that involve them doesn't work. > >> > >> I also noticed a glitch on the GUI, in the input/output levels (more to > >> the output) but this is probably unrelated. > >> > >> Unfortunately for me, compiling from git didn't fix the problem. > >> > >> My OS is slackware 14, 64 bits, there are not pre-build packages, so > >> this has been tested with the official 0.6.1 tarball as well as git's > >> head. > >> > >> However, 0.3.0 works perfectly. > >> > >> My cpu supports sse and sse2 and I can see that at the end of > >> configure's script sse2 seems to be used. > >> > >> Please let me know what else can I provide to help debugging this. > >> > >> Best Regards > > > > ------------------------------------------------------------------------- > > ----- This SF.net email is sponsored by Windows: > > > > Build for Windows Store. > > > > http://p.sf.net/sfu/windows-dev2dev > > _______________________________________________ > > Rakarrack-users mailing list > > Rak...@li... > > https://lists.sourceforge.net/lists/listinfo/rakarrack-users > > --------------------------------------------------------------------------- > --- This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Rakarrack-users mailing list > Rak...@li... > https://lists.sourceforge.net/lists/listinfo/rakarrack-users |