Hi Tim!
I've done a clean checkout and it seems you've removed vestige support for
the moment so running the compile script now generates a native VST-less
build. I hope we can see both Vestige and VST support in the next rc. I'd
prefer to use the SDK but it still isn't building here. I should note that
I have used these exact same headers to compile qtractor and the DISTRHO
VST plugs so its not a prob with my headers.
Deb Wheezy amd64 w/ VST 2.4:
[ 51%] Building CXX object
muse/widgets/CMakeFiles/widgets.dir/vst_native_editor.o
In file included from
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffectx.h:17:0,
from /home/dan/src/lmuse/muse2/muse/vst_native.h:45,
from
/home/dan/src/lmuse/muse2/muse/widgets/vst_native_editor.cpp:25:
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:125:32: error:
expected ‘)’ before ‘*’ token
In file included from
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffectx.h:17:0,
from /home/dan/src/lmuse/muse2/muse/vst_native.h:45,
from
/home/dan/src/lmuse/muse2/muse/widgets/vst_native_editor.cpp:25:
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:126:32: error:
expected ‘)’ before ‘*’ token
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:127:27: error:
expected ‘)’ before ‘*’ token
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:128:27: error:
expected ‘)’ before ‘*’ token
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:129:27: error:
expected ‘)’ before ‘*’ token
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:130:28: error:
expected ‘)’ before ‘*’ token
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:149:2: error:
‘AEffectDispatcherProc’ does not name a type
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:152:2: error:
‘AEffectProcessProc’ does not name a type
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:155:2: error:
‘AEffectSetParameterProc’ does not name a type
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:158:2: error:
‘AEffectGetParameterProc’ does not name a type
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:183:2: error:
‘AEffectProcessProc’ does not name a type
/home/dan/src/vstsdk2.4/pluginterfaces/vst2.x/aeffect.h:187:2: error:
‘AEffectProcessDoubleProc’ does not name a type
In file included from
/home/dan/src/lmuse/muse2/muse/widgets/vst_native_editor.cpp:25:0:
/home/dan/src/lmuse/muse2/muse/vst_native.h: In member function ‘VstIntPtr
MusECore::VstNativeSynthIF::dispatch(VstInt32, VstInt32, VstIntPtr, void*,
float) const’:
/home/dan/src/lmuse/muse2/muse/vst_native.h:187:47: error: ‘struct AEffect’
has no member named ‘dispatcher’
make[2]: *** [muse/widgets/CMakeFiles/widgets.dir/vst_native_editor.o]
Error 1
make[1]: *** [muse/widgets/CMakeFiles/widgets.dir/all] Error 2
make: *** [all] Error 2
On Sat, Dec 8, 2012 at 8:37 AM, Tim E. Real <[email protected]> wrote:
> On December 7, 2012 08:07:12 PM Dan MacDonald wrote:
>
> > Its true!!!
> >
> > Tim you generous genius you and just in time for xmas too! Thanks so much
> > for sorting this out! :)
> >
> > Muse svn complies fine if you just stick to using compile_muse.sh ie
> Vestige
> > headers and although I've only done the most bare minimum of testing so
> far,
> > Aspect seems to work so thats a huge win right there but so far I'm not
> > having any luck getting any usable sound out of TAL-Noisemaker yet
> > unfortunately - this is under Deb Wheezy amd64. I'll try Deb squeeze x86
> > soon.
> >
> >
>
> --------------
> Try it now.
>
> - Native VST fixes and changes.
>
> Redid cmake options. Please do 'prune' and carefully reconfigure.
>
> (Dan can you please try the sdk again? Would help.
> Currently the only real benefit is Chunks, otherwise most of the
> native VSTs seem to mostly function fine with without it.
> Maybe not surprising considering the target users?)
>
> Fixed track info banks and patch popup list bank issues.
>
> Fixed plugins such as NoizeMaker: Kill harmful redundancies -
> call getParameter before setParameter.
>
> Fixed crash reloading song with huge-chunk plugin like NoizeMaker:
> Stack overflow in processEvent().
> TODO: Fix all other such sysex stack buffer usages like possibly in DSSI.
>
> --------------------
>
> > Another prob I have with Noisemaker is I was unable to see where I might
> be
> > able to select one of its integrated presets or is this not supported yet
> > Tim?
>
> Create a midi track and select the synth as it's output device, then
> operate
> the trackinfo bankH, bankL, and program boxes, or simply choose the patch
> from the instrument patch list popup button (above the boxes), which I
> just fixed.
>
> Now, if you are referring to the /generic/ GUIs, the non-'native' ones,
> yes I'm keenly aware that our generic GUI windows do not have a program
> box.
> This problem hit me straight on when I added DSSI synth plugins (opposite
> of
> effect plugins), as rack effects. No mechanism to set program! Such as
> with
> several of the Calf DSSI plugins. Also no mechanism to direct midi to the
> effect plugin, which might use it.
>
> And so here this problem has come around again with the vst, been thinking
> about it a lot lately because we will need to add vsts and lv2s as rack
> plugins soon. It involves changes to our Plugin classes, been studying it.
>
> >
> > My biggest problem right now with the newly born plugin support is I
> don't
> > see any other way of opening any of the VST plugins windows other than
> > clicking the GUI column for the plugin under the MIDI ports / soft synths
> > window which seems a bit awkward to me.
>
> Agreed.
>
> Bit of an oversight. Normally the other MESS synths open automatically
> right away. But DSSI-VST support presented a problem: When you close
> a DSSI-VST 'native' GUI window via the window's 'X', you cannot open it
> again. Same behaviour as in Rosegarden.
> However in MusE if you stick using to the popup 'show generic/native GUI'
> menu, it works every time !
>
> Em, thus I wanted to kinda force users to learn that poup menu, so I
> kept 'em closed at creation. Well, that and the GUIs can be complicated
> and take time and some may want to work strictly with the generic GUI
> (which... again... has no program box... sigh). And so on.
>
> Here with Native VSTs, we needn't worry too much about all that,
> so it's do-able.
>
> >
> > There are 3/4 ways I'd expect/like to be able to open the VST etc.
> plugins
> > GUI window:
> >
> > 1 - When a VST plugin 'track'/object is selected in the arranger you
> should
> > be able to either double-click on the plugin name/ title at the top of
> the
> > plugins column on the left or right click and select 'Edit'.
> >
> > 2 - Double-clicking on any of the synth / VST plugin icons in the
> arrangers
> > 'Track Type' column
> >
> > 3 - As 1 but in the Mixer window columns too
>
> Agreed it should be better. Been studying those columns some more.
> I have always kinda hated that left-click ports popup menu versus the
> right-click 'show gui' menu.
>
> I think we should unify the two onto the right click menu.
> Thus it would clear the way to use left-click or double-left-click as
> 'show native gui', or the fall-back 'show gui'.
>
> Also would like to unify several other kinda sloppy menu arrangements.
>
> Tim.
>
> >
> > If you can get at least one of those in Tim I'll be even happier!
> >
> > Well done Tim! You've made my Christmas!
> >
> > :D
> >
>
> > > On Fri, Dec 7, 2012 at 8:02 AM, Tim E. Real <[email protected]>
> wrote:
> > >
> > > Feature: Native VST instruments support.
> > > Now in the SVN trunk.
> > >
> > > Here's what I got so far. Try er' out. Remember things may
> > > change slightly (or wholly?) so let's give a thorough workout
> > > to weed out any bugs.
> > >
> > > Best results are from compiling with the vst sdk.
> > >
> > > Featuring:
> > > True sample-accurate parameter automation!
> > > Full native GUI support for TOUCH, WRITE modes!
> > >
> > > New cmake options for:
> > > Enabling native vst.
> > > Enabling true sdk support .
> > > The vst header path.
> > >
> > > Plugins environment variable is currently VST_NATIVE_PATH
> > > else "/usr/lib/vst:/usr/local/lib/vst".
> > >
> > > What should we do there for paths and env var, eh folks?
> > >
> > > TODOs: Parameter ranges: fixed at linear 0.0 - 1.0 for now.
> > > Program categories. Dynamic port changes.
> > > Plugins correct path and env var?
> > > No rack effect plugins yet.
> > >
> > > And so on...
> > >
> > > ---------------------------------
> > > NOTICE: Plugins vary widely in quality. Some may crash MusE upon
> startup,
> > > while using MusE, or particularly most common
> -
> > > upon closing MusE.
> > > Be careful what you put in the plugin
> directory!
> > > Advice is to try one-at-a-time, or use the -D
> > > switch to see what plugin
> > > might be crashing MusE at startup.
> > > ---------------------------------
> > >
> > > Lemme know if any of them cause trouble.
> > > I'll take them out back and have a stern talk with them...
> > >
> > > Tim.
> > >
>
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
