> froze and I'm now waiting for it to wake up again (usually this takes > rewriting it at a resolution of 32 as opposed to 64. > problem I began editing the project file, clearing the automation and After finding out the name of the track that caused the > I took a look at the file and discovered a massive number of lines for one
#Automation track lmms Patch#
> Toby, please ignore my patch #47 in light of this and the vector > Matt, can you put the file (preferably from before your edits) somewhere > somewhere or is there something odd going on? You'd still need hundreds of > bars with an automation value for every 64th note. > A megabyte then contains 25,000 events, which is something like 400 4/4 > That's 25ish events in 1 kB, not quite 2 quarter beats at 1/64 resolution. one automation event would be under 40 bytes, to be generous. To one of your emails if you'd like - any takers? Parts before I send it (purely because I'd rather the project not beĪvailable to everyone and be kept somewhat private). I'd rather not send it through lmms-devel, and I will remove a few > think could be added to the program, I would also like to add a third Please let me know if I am on the right track > control points and a new mode which causes the value of the control to > Right now it allows people to choose between the default handling of > - add option for smooth lines and curves as opposed to sudden changes > I've been working on a new feature for the automation editor, this item On Sat, at 11:04 AM, Joel Muzzerall wrote: Values when the direction changes and still progresses smoothly when thereĪre several increasing or decreasing control points in a row. Kind of spline that qtractor and ardour are using that never overshoots I think this is most of what it would need to do, though there is another I found the discussion for thisįeature request on sourceforge so I have posted the new files there rather Splines with a configurable tension value. I have made a new version of this patch that implements Cubic Hermite Please consider fixing these burning issues ASAP. Repetitive boring stuff for us, not the opposite ) It's hard for new people to take LMMS seriously. To live with this, and people ask me "seriously?" when I say that you have Have now and we found our ways around, but it takes too much time and pain I think the above things were forgotten, because we got used to LMMS we lack of interpolated automation (vector-based instead of sample-based) lack of UNDO function (un-delete clips, instruments etc.) lack of basic editing capabilities (copy, delete, mute/unmute multiple (and ZynAddSubFX), but I feel obligated to mention LMMS' biggest flaws: I've been recently again teaching some grups of students how tu use LMMS
0 kommentar(er)
