Sean M. Pappalardo wrote: > Hello. > > Andreas Pflug wrote: > > >> - I didn't succeed in getting the scripting engine to do work. As a >> regression from 1.6.1, my Hercules RMX doesn't work, and the js >> functions just return nothing. >> > > There is tangible proof that the scripting system works, is powerful, > and well-received: > http://mixxxblog.blogspot.com/2009/02/midi-scripting-and-stanton-scs3d-videos.html > Maybe, but neither svn-trunk nor 1.7 Beta did any scripting for me. Which renders both versions useless for my RMX.
> > > In addition, Garth (jumpkick on IRC,) has been steadily working on > fixing the Hercules regressions as well as adding useful new features > via scripting to the Hercules controllers he has access to, which > include the RMX. The latest versions of the RMX mapping and scripts can > be found in the 1.7 branch. You're encouraged to try them and discuss > your reactions and/or suggestions here or in IRC. And/or offer patches. > http://mixxx.org/wiki/doku.php/hercules#hercules_rmx_tested > Actually I've been getting tired lurking around to find a workable configuration; that url doesn't help either. The documentation/wiki is a total mess regarding where to find "The Real Version". This includes the fact that people are still directed towards the dead svn! >> I can't see where I should start now, >> apparently the best candidate would be 1.6.1 (for me). And a prolonged >> migration period from svn to bzr is plain horrible. Apparently I >> invested time in a dead trunk, following the official instructions. >> > So right now, the rule of thumb is as follows: bug fixes go in the 1.7 > BZR branch, new features go in SVN trunk, since the 1.7 branch has been > feature-frozen since its creation. (After the merge, SVN trunk & > branches will be migrated to BZR and SVN will be decommissioned.) > Ah well. Frankly that doesn't inspire too much confidence for me.... Nightmare to clean up. >>> Next, the control creation code should be refactored ... > And you are enthusiastically encouraged to begin that process in trunk! The currently disorganized repositories keeps me refraining from that. > And you are of course welcome to continue to use 1.6.1 if that suits you > better. > I'm usually willing to use trunk versions in real life, and contribute stuff to it. But currently V1.7 appears unusable for me, which kind of forces me to continue with 1.6.1, which in turn would make that a personal branch with no chance to contribute to the main project. ---------------------------------------- To make up the depressing result of this thread for me: The Mixx project is currently in a state that makes it daunting for me to contribute. There have been decisions in the near past that I find highly fatal: announcing a beta of a software state that's known to be broken (IMHO beta should be mostly working, to the best knowledge of the releaser), and stretching a source repository migration over a prolonged, undetermined time. I'll do a little tweaking on my personal 1.6.1, and maybe I come back in a year or so when 1.7 has settled, maybe not. Sigh. Regards, Andreas ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
