I think it makes more sense to at least leave flexible stubs lying around (in the style of djDecks) so that in the future if Mixxx grows more Decks we're not trapped into a toggling model.
And I do have a good reason for controlling multiple decks at once: suppose you've locked together two tracks but want to rewind or slow down or speed up one without losing the beatmatch? On Tue, Sep 23, 2008 at 12:38 AM, Josh Matthews <[EMAIL PROTECTED]> wrote: > > Well, with only one button, then a deck is always receiving vinyl control > input. I'd be happy with a button per deck, with only one depressed at any > given moment, or neither. However, I doubt it would be a huge issue if it > was there was just a single toggle for deck 1/deck 2. > > On Tue, Sep 23, 2008 at 12:18 AM, Albert Santoni <[EMAIL PROTECTED]> wrote: >> >> On Mon, 2008-09-22 at 11:57 -0400, Josh Matthews wrote: >> > The way djDecks handled which decks received vinyl control was via a >> > button on each player that toggled it on or off. In the preferences >> > you could set the input channel for each deck, so you could specify >> > that all three players would be controlled through the same input >> > channel, and it worked without problems. >> >> When would you want to control more than one deck simultaneously with >> one turntable? If there's a good reason, sure, but for simplicity it >> might be better to just make a single button that toggles between the >> two decks. (Less buttons is better for MIDI controllers, easier to code, >> etc.) :) >> >> Thoughts? >> >> Thanks, >> Albert >> >> > >> > On Mon, Sep 22, 2008 at 12:37 AM, Albert Santoni <[EMAIL PROTECTED]> >> > wrote: >> > Hi Josh, >> > >> > I started hacking Mixxx as I was moving out of rez too. :) >> > >> > I wrote most of the vinyl control code, and I'd be happy to >> > give you as >> > much guidance as possible on this. To get you started, I've >> > written a >> > feature specification on our wiki outlining the work that >> > needs to be >> > done for it: >> > http://www.mixxx.org/wiki/doku.php/single-deck_vinyl_control >> > >> > In the Design section, I briefly introduce some of the vinyl >> > control >> > code before I realized the easy way to code this (which I also >> > documented on that page). >> > >> > Mixxx's vinyl control works by getting input audio from a >> > soundcard and >> > passing it to a VinylControlProxy object, which then adjusts >> > the >> > playback rate/position. The easy way to hack single-deck vinyl >> > control >> > in is to simply reroute which VinylControlProxy object >> > receives the >> > audio from the soundcard. (There are two of these objects, one >> > for each >> > player/channel.) I go over this in more detail in the wiki >> > article. >> > >> > My big question is how is control supposed to be switched from >> > one deck >> > to another? Is it by looking at the crossfader position or >> > something? >> > >> > Don't let the specification wiki page scare you - it's just >> > there to >> > outline the work, and when you're in doubt, code! Get >> > accustomed with >> > the code base (specifically soundmanager.cpp) and worry about >> > doing it >> > "right" later. >> > >> > I hope this gives you the end of the string. If you have >> > questions, >> > please don't be afraid to ask! I'm also available on our IRC >> > channel >> > (#mixxx on Freenode) quite a bit (my nick is asantoni), so >> > feel free to >> > bug me when I'm around there too. >> > >> > Thanks! >> > Albert >> > >> > >> > >> > On Sun, 2008-09-21 at 18:07 -0400, Josh Matthews wrote: >> > > Hi everyone, >> > > I discovered Mixxx just before I had to pack up my residence >> > room and >> > > move out, and I still don't have anything plugged in in my >> > new house. >> > > Anyways, I really like what I saw, but it seems to be >> > missing single >> > > turntable vinyl control. This is something that the djDecks >> > program >> > > has, which I've been using up until now, and it is >> > indispensable to me >> > > as my soundcard only has enough in/out plugs to let me use a >> > single >> > > deck. What's the status of this feature? If someone can >> > give me an >> > > overview of the work required, I could probably whip it into >> > shape if >> > > need be. I'm bilingual in English and C++, so give me a >> > holler. >> > > >> > > Cheers, >> > > Josh >> > > >> > >> > > >> > >> > ------------------------------------------------------------------------- >> > > This SF.Net email is sponsored by the Moblin Your Move >> > Developer's challenge >> > > Build the coolest Linux based applications with Moblin SDK & >> > win great prizes >> > > Grand prize is a trip for two to an Open Source event >> > anywhere in the world >> > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> > > _______________________________________________ Mixxx-devel >> > mailing list [email protected] >> > https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> > >> > >> > >> > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
