2012/12/10 Tim E. Real <[email protected]>: <...> > Thanks for the pass, been neglecting that list for a few days. > > Try it now: > > - Fix VST names: Use filename if effect name or product name blank. > > - Fix bug 3594221: End-to-end midi notes don't retrigger. My bad. > In my MEvent::sortingWeight(): Note-ons with zero velocity are > really note-offs. > > Yes, it was broken recently with my sorting weight thingy.
Great! > NOTE: For this to be, or ever have been, correct we need to ensure > in a few key places that the length of a note is never allowed to > be zero, else that's a note-on and off at the same time and > MPEventList will put the note-on last and will have no corresponding > note-off thus a stuck note. > The places I think some are already thoughtfully taken care of, > one example to check is the piano roll note length - is it allowed to > be zero? Tested: Thankfully someone enforced it to 1. > Another would be in the function buildMidiEventList. > > ----------- > Now, about /overlapping/ notes: I tested several synths and > incredibly (hearteningly ?) Deicsonze was the only one that > handled note situations like this: > > X X X X X XYXYXYXYXYXY Y Y Y Y Y Y Y > or > X X X X X XYXYXYXYXYXY X X X X X X X > > Amazing but it must be awfully arbitrary since it could not possibly > know which note-off goes with which note-on. > It's a real tricky subject, one that I think Dennis or the LMS plugins guy > brought up, and I kind of jokingly said maybe we ought to 'bump' other > notes out of the way when moving notes around. > One really wants to allow this kind of thing for ease of editing while > moving notes around - you know move this one here on top of this one > then move the other one somewhere else kind of thing. > (In case that person missed my response in the noise, we have translucent > note drawing, it may have been a bit hard to notice at the time so I > recently lowered the default setting a bit. Still slightly hard to notice > without vertical expansion.) > > Anyway I agree that only MusE knows for sure which note-off belongs > with which note-on and that only MusE has a chance to correct it > before it gets out to the device. > But how? > I'm thinking it involves arbitrary blocking of note-ons. > For the extreme example two notes same length on top of each other > but with different velocities: Who do we block and who do we allow? > Easy? Send only one note-on and one-note off and SUM the velocities? > > But then there's note-offs that come after each other... > > And then, what of synths that actually /support/ this kind of > two note-ons in a row stuff? Deicsonze starts a new oscillator > and you'll notice depending on where the second note is placed, > the waves may CONSTRUCTIVELY or DESTRUCTIVELY sum. > i.e. it /can/ go to twice the volume - or very little volume. > Of course, that's a synth function and could (maybe already) be made > to 'sync up' the oscillators starting... > > Hm, let us ponder some more. I hope there's a logical way to > deal with this. More input welcome on this of course. I'm not the expert but it seems to me there is no "right way", with midi it's impossible to describe which note ends where. > >> I saw the report for Euphoria but don't have it installed so haven't >> checked. > > And speaking of the LMS plugins guy, bada boom boom, hey if > you're out there Euphoria and pretty much the rest of the suite > crashes with illegal instruction. I compiled it myself. > I'd say usually that's either 32/64 bit stuff or AMD/Intel stuff. > At the moment I'm running AMD64 box, but with 32-bit Lubuntu. > > I built the deb package. > Later the package manager (Synaptic) said it's a broken package and > removed it on me! > >> >Also: >> > >> >Within the simpledrums window between the channel on/off and note on/off >> >check boxes there are supposed 'Volume' buttons that don't do anything. I >> >think they should be rotary dials but they're not. >> Dan, could you supply a screenshot, for me it's a slider and it works fine. >> >> >There is a unneeded slider on the right that doesn't slide anything. >> > > All features tested OK here channel volume OK. > And right-side master volume worked, live in real-time too. > > You guys getting this multiple annoying terminal message with SimpleSynth? > QGradient::setColorAt: Color position must be specified in the range 0 to 1 > I tried to look before but didn't have much time. Indeed I do! I'll take another look at that. Dan, not sure if you did another bug report for the non functioning stuff in SimpleDrums? As I said it works here but we need to ensure it works everywhere.. Regards, Robert ------------------------------------------------------------------------------ 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
