On Sunday, May 22, 2016 12:30:44 PM EDT Robert Jonsson wrote: > Hello Jean-Pierre, > > . in the mixer "show inputs" and "show outputs" do the inverse > fixed in git > > > . moving the end of an event with crtl right clic doesn't work anymore > > (while being in "pointer" mode) > fixed in git > > > . right clic / popup menu in the arranger says pointer shortcut = U, it is > > A (old bug) > fixed in git > > > . 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 > > I'm not sure if I can reproduce this, it seems to work the same for both > copied and cloned parts and I think it looks right, the note events from > each part are at the same tick within the part. > Could you explain more what you think is wrong? > > > . cloning a part (ctrl-c/ctrl-b) => error message : unexpected EOF reading > > xml file at level 0, line 10, <event><part><> > > I've seen this before with certain xml interactions. It is a minor problem > with our xml implementation, the copy operation works correctly but the end > of the data is not handled correctly leading to this annoying print out. > I'm uncertain what would be the best way to improve it so I didn't do it > yet.
It is a benign error. I stepped through it a few times long ago and tried hard but could not think of a solution, but I was relieved that it was benign enough to ignore. > > . in the drum editor, if only one note is selected, we cannot change its > > pitch in the toolbox (old bug) > > 2016-05-17 21:01 GMT+02:00 Jean-Pierre Haenlin <[email protected]>: > > 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 :) > > I cannot reproduce this with the latest git, would it be possible for you > to try the latest git? Tim updated the LV2 support libs so I guess it is > possible this improved things. > > > > 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 ! > > > > Yeah, i see it now, i see some more problems with this when disabling > > certain plugin types with command line arguments. I'll see if I can improve > things. Yesterday I noticed we're missing even some simple installed examples such as the lv2 'metronome'. I can't seem to find it in plugins or synths lists anywhere. It has no inputs but only audio outputs. (Well, actually it has an atom:Sequence input. It demonstrates synchronization of a plugin with host timing using the LV2Time class, which looks verrrry interesting to me right now...) Upon further inspection I see none of the 'generator' style of plugins seems to be listed in the Add LV2 Effect or Synth popup menu. Such as white noise generators. Usually this is a familiar problem of simply not listing plugins which have zero inputs. Usually a straight forward fix. Also, mind zero-outputs as well, such as meters, we want them. What's weird is that we DO list generators in the rack plugin effect dialog, such as all the white noise generators, but I still can't find the lv2 metronome. Its ttl file says it's "a lv2:Plugin". (I'm in this exact lv2 code right now the last few days, I'll check.) Ahem... Mind you, with 22 <more...> listings in the Add LV2 Effect popup menu, AND a Midi Ports /Soft Synth synth list which is HUGE AND UNSORTED, it can be difficult for me to find the synth I want. What say we aim to sort that synth list. Shoulda been done long ago. And replace those popup menu Add Synth listings with something more akin to our rack plugin dialog or (the sorted) synth list ? It would be cool if we could use the lv2 class strings to provide categories listings. I'm looking at our code now where we read those class strings, too. (Although at first it was only to provide a better plugin name than just copying the description. You'll notice I just removed the <...> part from the Add Synth popup menu listings - for now. They are too long, and the name is just duplicated from the description when the LV2 synth is created.) Cheers. Tim. PS: Robert not sure if you're aware, but in the arranger track info mixer strips, you can right click, and the 'remove strip' and so on, are there and if you click on them bad things happen in the arranger. Tried to solve it earlier. Not sure what the best course is. Easy: Greying out those items if the strip is part of track info panel? Hard: Actually supporting the actions - such as deleting the track if 'remove strip' is clicked? > > > 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. > > Hmm, ok, haven't tested this yet, will try. > > 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
