On Sat, Feb 14, 2009 at 9:08 PM, Robin Sheat <[email protected]> wrote:
> 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.
>
Currently it won't work, I remember forgetting to remove djconsole support a
couple of times (I also remember the Herc eng trying the current build
instructions on the wiki and getting screwed up by both methods trying to
grab the controller)... That's not to say we couldn't make it work, but it
takes effort that I think is better spent continuing to forge the new MIDI
code, write device scripts, etc.
I get the impression we will never have a time line until we set a
deadline. If we get to the point where the next release hits the first RC
test cycle we should give them a heads up. And then if the users have to
sit outside in the cold for a little bit, it will at least encourage them to
put it out more quickly. If it comes down to it we can also work with the
Herc team to make sure anyone complaining about drivers gets drivers ahead
of a GPA drivers release. I think the current Herc code does a diservice
to both Mixxx and Hercules... And even if we told users you are going to
have to wait some weeks/a month to get a real MIDI driver from Hercules, I
think they would be happier for it.
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?
>
The former is what we all want, but logistically it is going to be very very
difficult to do a joint release unless we set the date. Looking at how
long it takes us to get releases out. It's going to be hard for them to
justify releasing their driver ahead of us having a build that works with it
when we play the role of the major catalyst for adoption of the driver on
Linux (I think there are 2 other small fish).
Cheers,
-G
------------------------------------------------------------------------------
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
