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.]
> 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?
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.
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.
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?
Tim.
>
>
>
> ---------- Forwarded message ----------
> From: Tim <[email protected]>
> Date: 2016-03-24 20:39 GMT+01:00
> Subject: Re: [muse] amsynth lv2 preset loading does wierd things (#491)
> To: muse-sequencer/muse <[email protected]>
> Cc: spamatica <[email protected]>
>
>
> Fixed now. The presets menu now uses our PopupMenu instead of QMenu.
> Go to Settings and choose either scroll or our normal PopupMenu behaviour.
> Although in the case of amsynth, either way it looks FUGLY - waaay too many
> items.
>
> I briefly looked at categorizing the items, just like the native UI does.
> I'm sure there's a way, but currently the items in our _presets list class
> member
> just hold one piece piece of text - the whole preset name.
>
> Regarding the support. It looks like we are already using that extension.
> Seems to work OK.
> IIRC on my older 32-bit 14.04 distro, these presets menus did not populate,
> I think.
> Here on newer 15.10 they are fine.
>
> Tim.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/muse-sequencer/muse/issues/491#issuecomment-200986396>
------------------------------------------------------------------------------
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
