On March 26, 2016 05:39:03 PM Robert Jonsson wrote: > 2016-03-25 19:24 GMT+01:00 Tim E. Real <[email protected]>: > > On March 25, 2016 11:43:50 AM Robert Jonsson wrote: > > > Awesome Tim, you're on fire! :) > > > > "You're on fire, Donkey! No really, you're on fire!" > > > > [Shrek II, Far Far Away Idol.] > > hehe > > > > Unfortunately I seem to have an unrelated problem and can't verify right > > > now. > > > > > > I don't get any lv2 synths into MusE at all, I see the effects however. > > > I've got a rather recent 32-bit install here.. > > > The problem looks suspiciously similar to what funcmuscle has reported > > > recently. > > > I will dig deeper into this shortly. > > > > > > /Robert > > > > Hm, wonder what's up there... Maybe trying to load 64-bit synths? > > No, I think it was working just before. Could be that the build is just > borked but I'll try to get to the bottom of it. > > > Speaking of which... > > > > I wonder if you might offer some tips: > > I installed Airwave but am having trouble getting it to run. > > Confused by the several path entry boxes and terminology > > > > like "path to all your native VSTs" - do they mean native > > Linux VSTs or Windows VSTs? (Admittedly I used similar > > confusing terminology when adding Linux VST support.) > > > > I can seem to get our Linux VST to open the Airwave .so file > > > > but it crashes. I wonder if that's what I'm supposed to be loading. > > Yeah the airwave gui is a bit confusing and I have a feeling it is fuzzy > about which wine version you have referenced also. > > I can't check at the moment but as I recall the 'path to all your native > VSTs' means just that. > > In one of the other path boxes you will point to a specific vst dll. > > What will happen is that airwave will create a specific *.so in the native > VST dir which contains bootstraping code for exposing the VST dll as a > native VST (using Wine of course) > > > Related: > > Also, yesterday I copied all my Windows and Linux VSTs from my > > > > 32-bit system over to this new 64-bit system. > > > > And MusE refused to load any of them, of course, being 32-bit. > > Yeah, this part of how they designed the 32/64 bit support in Linux is a > bit unforgiving. In Windows I believe it is much easier to use 32-bit dlls > though the program is 64-bit (though do treat this as hearsay, I'm not > really that knowledgeable about it) > > > And that's when I got a real sinking feeling, you know? > > In a cruel ironic twist, I suddenly realized that after all the work > > > > embedding various plugin architectures support, we may have > > to rip it out and let a 32/64-bit BRIDGE do all the loading for us ! > > > > I mean bridges for all the LADSPA, DSSI, VST, and LV2 plugins. > > > > How ironic that we may have to let a Linux VST bridge do the work > > > > for us, eh? > > > > What do you think? Possible? A multi-architecture 32/64 bridge? > > Hehe, well, it is annoying that we can't just allow 32-bit plugins but I > don't think this is a big issue.
Yeah, I was a bit hyper there. Our code can remain the same and a bridge can be external and just do its thing. But it'd be nice to actually /embed/ the bridge into the app. I understand that's what you were looking into, with the AW code. > All the open source synths have 64-bit builds (I've resolved to using most > synths from falktx marvelous kxstudio, where all softwares are built for > both 32- and 64-bit) and in the case of closed source linux VSTs I haven't > come across any yet that doesn't exist in both 32 and 64 bit. > The expection is old closed source VST dlls, but as airwave is just such a > 32/64 bit bridge, old 32-bit Win VSTs can be run under 64-bit MusE. > > Also, I should note that for the time being I'm back to using dssi-vst and > a 32-bit OS for my actual music making. For starters, chunk support doesn't > seem to work correctly with airwave + muse (this could simply be a timing > issue, I've added some experimental delays to the dssi-vst chunk support > also, since I was experiencing sporadic load failures). > I also get rather frequent xruns using airwave, haven't tried to dig deeper > into this but it is possible that the IPC mechanism that it currently uses > isn't as reliable as the old/correct solution. I think I've mentioned > before about dssi-vst stopped working with recent kernels in a 64/32-bit > scenario due to some change in the kernel or libc, Absolutely. Yeah I know. I just finished a major investigation myself, why 64-bit dssi-vst is broken. Sucks. That's why I turned to Airwave to see what it's all about. I will try to help with supporting it for sure. One way to look at it, is dssi-vst is kinda old. There are some broken things that will probably never be fixed. (Closing windows. Controller ranges. etc.) Maybe it's time to retire it in favour of somethng else that can support more features? NOTE: I mentioned that the last time I went through this with dssi-vst, I simply installed an older dssi-vst-64-bit package and it worked ! I have that package here, will try and report back. Might be too old by now... > which is the main reason > why I now use a 32-bit OS for music making. airwave worked around this by > using some low-level ipc mechanism that I forget the name of, Futex? I read some of those threads :-) > from some > forum threads I've gotten the feeling this might not be a viable long term > solution though, possibly due to worse ipc performance (again, heresay). > > /Robert T. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
