On Mon, 2008-06-30 at 23:19 +0400, Tuma wrote: > Hi! > I wanna ask if there is something new in MIDI controllers support?
I don't think so. You can view our full list of supported controllers here: http://www.mixxx.org/wiki/doku.php/hardware_compatibility > Last time i've built Mixxx MIDI Controller's signal support was really weak. > I think MIDI Support is really importrant fuctional. I wouldn't call what we have right now "weak", seeing as we support about a dozen controllers on three different platforms. (Show me another DJing application that does that.) :) We do think it could use improvement though, which is why one of our Google Summer of Code students is working on radically overhauling our MIDI system. If you're interested in seeing what he's working on, take a look at: http://www.mixxx.org/wiki/doku.php/gsoc2008_midi_control Thanks, Albert > > On Monday 30 June 2008 9:55 pm, Albert Santoni wrote: > > Hi everyone, > > > > We've made a great deal of progress in tackling the release-critical > > bugs for 1.6.0 over the last few weeks, and we're now closing in on > > the 1.6.0 final release. Adam and I are going to try to spend a few > > days working full-time on Mixxx at the end of July, and this is when > > we're planning to do the final release. I want to bring everyone up to > > speed with what needs to be done between now and then, to help give > > some perspective. > > > > For the next month, there will be a feature-freeze in effect for trunk > > in SVN. This will apply only to trunk with the default compile > > options. This means that Garth can continue working on iPod support, > > for example, since it must be explicitly turned on with ipod=1 and is > > not a supported feature yet. If there's something small/reasonable > > that you feel is worth adding to trunk within the next month, please > > email Adam or I first and we'll try to work it out. Branches (and GSoC > > students) should continue normal development. > > > > As for the work that needs doing before the 1.6.0 release, I'll try to > > break it down and try not to forget anything: > > > > Remaining Tasks > > ============= > > > > 1) Fixing bugs. Specifically, these three bugs need as much attention > > as we can give them: > > https://bugs.launchpad.net/mixxx/1.6/+bug/235807 > > https://bugs.launchpad.net/mixxx/1.6/+bug/223464 > > https://bugs.launchpad.net/mixxx/1.6/+bug/235479 > > > > We'll try our best to fix these bugs, but if the end of the month is > > reached before these are fixed, we'll likely decide to release 1.6.0 > > regardless. > > > > 2) Finishing the manual. The new manual has started to flourish, but > > there's probably still information that should be added that we > > haven't thought about. If you give it a quick glance and notice that > > we're missing something, please start a section on it or tell us. Our > > plan is to somehow dump the manual wiki page into a PDF to bundle with > > the 1.6.0 release, but we'll worry about this later. Lastly, someone > > will need to take a ton of screenshots to insert into corresponding > > parts of the manual. The screenshots should all be taken on a single > > OS (probably Windows or Linux) for consistency. > > Link to the manual: http://mixxx.org/wiki/doku.php/manual > > > > 3) Revamping the website. We had planned to have the website revamped > > months ago, but due to circumstances, nothing tangible has been done. > > If this situation is unchanged by about the middle of July, then we'll > > move forward with a less thorough revamp ourselves. > > > > How YOU can help > > =============== > > 1) Help us tackle the bugs we listed above! If there's any other bugs > > people feel like trying to fix, we'd also be happy to accept patches > > for those and grateful for your contribution. Other bugs: > > https://bugs.launchpad.net/mixxx/+bugs > > > > 2) Take a look at the manual and check if we forgot anything. > > http://mixxx.org/wiki/doku.php/manual Please feel free to add any content > > you feel is missing or let us know what we've missed. > > > > > > Mixxx 1.6.0 has been a long project with massive changes to many parts > > of our code-base. It's going to be incredibly satisfying for everyone > > involved when it's released, and I'm looking forward to that occasion > > myself very much. > > > > Thanks, > > Albert > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Mixxx-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
