On Sunday 15 February 2009 15:02:56 Garth Dahlstrom wrote: > * IMO, the MIDI based support via the alpha driver is already better then > the Herc code we have.
Completely agree, however noone else has it yet :) > * It's a bit chicken and egg... if we don't remove the Herc stuff when we > build next release, that driver can't work (and we have to release again). Hmm. That's a good point. What loads first? Could we check for any MIDI devices, and only if it doesn't show any, do scans for herc devices. I'm just thinking that, until we have a real timeline for the MIDI driver the users will be left out in the cold. > * By the time we do the next release, that driver should be good enough... I hope so. > releasing without the hacked up Herc support will clear the way for them to > put it out in the wild. If it was a choice between 'release without herc code, and working MIDI when the driver comes out' vs. 'release with herc code, but have no MIDI support for it later' I agree, go with the former. But is it perhaps a false dichotomy? -- Robin <[email protected]> JabberID: <[email protected]> http://www.kallisti.net.nz/blog ||| http://identi.ca/eythian PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
_______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
