Hi Albert
Thank you for detailed answer.

I think I'd go with improving the Mk2 support at first. I've managed to
compile 1.7 version from the bzr repository and played around with my
console. The support isn't as smooth as in Virtual DJ. Basically I miss the
smooth scratching capability of the VDJ,  effects/cue/looping controls(I've
read that looping isn't finished yet and will be one of the "feature of
interest" for the 1.8), and smart use of joystick for fast track
navigation/insertion. If someone could explain me where to start
hacking(scripting?) I would be very grateful.

Best Regards, Siarhei Rachytski

On Mon, May 18, 2009 at 7:53 PM, Albert Santoni <[email protected]> wrote:

> Hi Siarhei,
>
> A few of us also came from OpenGL/C++ backgrounds before we started
> working on Mixxx, without any prior sound processing knowledge, so that
> definitely shouldn't be a problem. (Heck, most of us didn't know
> anything about Qt either!)
>
> A good place to start would be to build Mixxx on your respective
> platform. There's documentation on the wiki for this under "Build
> Mixxx": http://www.mixxx.org/wiki/doku.php
>
> It's also worth taking a quick peek at our development roadmap to see
> our main design principles and where we're going:
> http://www.mixxx.org/wiki/doku.php/development_roadmap
>
> You're basically free to work on whatever you want, but keep in mind
> that we're "feature frozen" for 1.7, and we're just picked our feature
> targets for 1.8:
> http://www.mixxx.org/wiki/doku.php/5_17_2009_developer_meeting_minutes
>
> If you want to work on improving support for your Hercules MK2, you
> might want to play around with MIDI scripting.
> http://www.mixxx.org/wiki/doku.php/midi_scripting
> I'm not entirely sure what the state of the Hercules MK2 controller is
> at the moment, but perhaps Garth could better advise you on where to
> start hacking that stuff.
>
> Otherwise, we're looking for someone to work on finishing up LADSPA
> support:
> http://www.mixxx.org/wiki/doku.php/ladspa
>
> The good news is that all of the audio processing and a large part of
> the GUI are done. There's just quirks here and there in the GUI that
> need fixing, and a the odd deployment issue here and there. If you're
> interested in working on it, get in touch and I'll advise you in more
> detail.
>
> Thanks, and feel free to ask for help if you need it!
> Albert
>
> P.S. Many of our developers and contributors hang out on IRC in #mixxx
> on Freenode, and we can help you get started hacking Mixxx from there
> too.
>
> On Sun, 2009-05-17 at 13:54 +0300, Grayyoga wrote:
> > Hi
> >
> > I want to participate in Mixxx developement. I'm totally new to the
> > sound processing applications, but have a good expertise in
> > OpenGL and C++ is my primary programming language. I also own a
> > Hercules DJ Mk2 console and could perform some of the related work and
> > testing. Could you give me some insights on where to start?
> >
> >
> > Best regards, Siarhei Rachytski
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensing option that enables
> > unlimited royalty-free distribution of the report engine
> > for externally facing server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________ Mixxx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
>
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to