Hi Tim! 2014-05-04 18:39 GMT+02:00 Tim E. Real <[email protected]>: > > Hello Robert, and Florian, I'm still here. > > Robert, I've spent the last several MONTHS fixing the master here. > The master as it stands now is just not ready for prime-time > and it would NOT be good release.
Why is that, I think it works quite nicely, or are you aware of glaring bugs? I mean, the stuff you are building will probably add lots of neat enhancements but HEAD is working nicely for me, except for the two mentioned problems. If you know of problems with HEAD my argument is void but otherwise I think we can release a maintenance release soon and then in a month or two we can release your stuff. That would be more alinged with our intentions to release more often. Which seldom happens ;) > But my fixes are not quite ready for commit yet. > There was a lot of stuff that needed (needs) fixing. > I estimate maybe a week before I have something, I really am working > very hard to get something ready because I knew that soon others > may have commits of their own, as is the case here, possibly > wanting to overlap some of the fixes I am doing. > > The first problem you mention above is likely due to these bugs > and may be fixed by my fixes. > > The second problem you mention, well, I guess that's up for debate. > I'd prefer to keep the Jack midi thing... I have no problems with having jack-midi as default if they were functionaly equal but I have had quite a few problems with the jack-midi solution lately. Best would be to fix it but until that can be done I think we should fall back on a working solution. I'll try to elaborate on the problems I have had in a bug soon. > > I hate to discuss what I'm doing for fear of jinxing my work, it has > a habit of doing that, sometimes I discover a stumbling block that > shoots down everything I have tried and it's back to the drawing board. > > So briefly, I have fixed things that Flo and I discussed (every event gets > a unique ID, problems with selections etc), and I have implemented what > we discussed about operations: Operations are now 'collected' beforehand > in the non-realtime stage and executed VERY FAST in the realtime stage > with very simple instructions. It doesn't get much faster than that. > Previously the realtime stage was doing all the 'collecting' and wasting > a lot of time, doing a lot of searching and even mem allocation - a no-no. > > There are, and have been, a lot of challenges and snags along the way. > For example I've found the tempo, signature, and key lists have a design flaw > that prevents them from working with undo, at tick = 0. > So I'm fixing that right now. > > It's been very intense and complex fixing these bugs. > Yes, it has taken THIS long, but I hope to have something soon, because it > is finally coming together and showing signs that it WILL work. Sounds cool! Does this have any impact on the song file format? Regards, Robert ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
