Hi, My answers :
> the LV2 effects are listed in the "available synthesizers" window. > All of them? I know it's sometimes hard to know if a synth is really an effect. --> It's the windows "Muse settings.. Midi ports / soft synths" Yes, all of them. For example TAL-Reverb. And they are labeled LV2 (effects), so Muse knows they are effects :) > the Wine DSSI-VST synths and DSSI-synths are listed in the fx window. > Would also be good with a screenshot so we can be sure exactly which window you mean. --> It's the window that opens when you click in the fx rack of an audio track. All the DSSI synths and Wine DSSI synths are present. Not the LV2 synths. In the window displaying the plugins, the column AI (audio inputs) is at 0. If a plugin doesn't have inputs (AI=0), it's a synth not an fx ! > the first time I ran muse3, the path "VST_NATIVE_PATH" was not taken into account for the native vsts, the path "VST_PATH" was used instead. > I think it's by design that VST_PATH is used when there is no VST_NATIVE_PATH. Or are you saying that VST_NATIVE_PATH was set but MusE did not recognize it? --> yes VST_NATIVE_PATH was set. Best Regards, Jean-Pierre On 05/17/2016 01:00 PM, Robert Jonsson wrote: > Hello Jean-Pierre and thanks for the bug report. > > I'll reply here mostly to cc the devel mailinglist as I don't have much > time to look at this now. I see several issues that should be easy to fix. > > 2016-05-15 16:06 GMT+02:00 Jean-Pierre Haenlin <[email protected] > <mailto:[email protected]>>: > > Hi, > Thank you for this new version, the new mixer is nice. > I have worked a little with it, this is the list of bugs I've found : > > . nothing is written in the progress window that opens when loading > a project, the window is transparent > (XFCE/Fedora 23 - 64bit) > > > Okay, interesting, have not seen that one. > > > . in the mixer "show inputs" and "show outputs" do the inverse > > . moving the end of an event with crtl right clic doesn't work > anymore (while being in "pointer" mode) > > . right clic / popup menu in the arranger says pointer shortcut = U, > it is A (old bug) > > . when loading a project, the size of the mixer window is not always > restored, it remains the same of the previous project > > . in the mixer, the output track "Out 1" is sometimes duplicated n > times when loading a project B after a project A > > . doing 'functions/change note velocity' in the arranger window, on > a cloned part, results in notes being duplicated (n clones -> n notes) > ( error message : MusE error: PendingOperationList::add(): Double > DeleteEvent. Ignoring. ) > > . if 2 cloned parts are selected and then edited (ctrl-l), all the > cloned notes are displayed at the same tick > > . cloning a part (ctrl-c/ctrl-b) => error message : unexpected EOF > reading xml file at level 0, line 10, <event><part><> > > . in the drum editor, if only one note is selected, we cannot change > its pitch in the toolbox (old bug) > > > > Most of the above seems we should be able to reproduce, will hopefully > do some MusE testing later this week.. > > > > . the native vst fx are not loaded (native vst synth are ok), I > don't know if this is because they are 32bit, > error message : > Initializing Native VST support. Using VESTIGE compatibility > implementation. > scanVstNativeLib: > dlopen(/home/jph/Music/VST/NAT/destroyfx/buffer_override_stereo.so) > failed: /home/jph/Music/VST/NAT/destroyfx/buffer_override_stereo.so: > wrong ELF class: ELFCLASS32 > > > If your MusE version is compiled for 64bit you need to have the 64bit > version of the VST effect, we do not support loading 32bit plugins under > a 64bit host (atleast not yet). > The error seems to indicate this is the problem. > > > -- these are not really bugs, but... > > . the LV2 effects are listed in the "available synthesizers" window > > > All of them? I know it's sometimes hard to know if a synth is really an > effect. > Would be good with a screenshot. > > > . the Wine DSSI-VST synths and DSSI-synths are listed in the fx window > > > Would also be good with a screenshot so we can be sure exactly which > window you mean. > > > . the first time I ran muse3, the path "VST_NATIVE_PATH" was not > taken into account for the native vsts, the path "VST_PATH" was used > instead > > > I think it's by design that VST_PATH is used when there is no > VST_NATIVE_PATH. Or are you saying that VST_NATIVE_PATH was set but MusE > did not recognize it? > > > Regards, > Robert ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
