Hi guys, I have already started working on Master Sync in my own branch: lp:~ywwg/mixxx/master_sync. While work is still very preliminary, I think we should decide how to organize this before we have two completely different implementations. I'm still at the point where I wouldn't be totally opposed to throwing out what I have, but I'd prefer not to unless there's a major problem with the approach.
I forsee several sources for a master sync clock: * A specific deck * A specific bpm * Midi / JACK clock To start with I've been implementing deck sync -- a specific deck is designated as the master deck, and the slaves adjust their speed to match. For this first round I'm not worrying about /2, x2 bpm issues or even phase checking. Eventually there will need to be bpm pulses that slaves listen for so they can determine if they are out of sync, and if necessary, tweak their own playback rate to get back in sync. Since this is a big, important feature, it might be worth sketching out the whole thing ahead of time so we know it's theoretically robust. I'd also like to make sure it can scale significantly, to 16 or 24 decks for ableton-like performances. Owen On Mon, 2012-03-19 at 14:19 +0530, Gayan Dhanushka wrote: > Hi William, > > I am a lot familiar with DJ softwares for a few years now. During my > leisure time I use virtual DJ Pro and play around with it. I am the > official DJ of my batch and whenever there is a function which needs > music I am the guy that they always turn to. I love listening to > hiphop, rock and trance music and most of the songs that I play fall > into those categories. I'm not a professional I did those for fun and > I learned DJ'ing all by myself. I really love it that is why I was > really happy to see that a DJ software has been accepted by GSoC and I > decided to make some contribution. > > First of all thank you very much for the detailed information. I am > happy to say that I understood the things that you've mentioned here. > > Instead of the SYNC button in virtual DJ they have what they call a > beat lock. When a track is added to deck 1 and before you add a track > to deck 2 you can hit the beat lock button and then add it. The > playing speed of the track on deck 2 changes accordingly to the BPM of > deck 1. But even there the decks do not check always with one another > and try to adjust the beats. The scenario that you've mentioned > through (1), (2) and (3) is correct. Those can take place practically. > But there might be a little problem. If this feature is implemented > say that the two tracks dynamically check for each others BPM and try > to synchronize the playing speeds of the songs can go horribly fast or > slow and it can jeopardize the whole DJ session. > > The master clock concept is more or less the same. instead of > synchronizing with the other deck this time the tracks are > synchronized to a BPM set as the master clock. > > > Thanks for the youtube link. I watched it and yes it will be a cool > function for a DJ to have. He/She will be able to sync the two tracks > very easily with it. When you said that the music was so loud I > thought it is a joke while listening to the guy who speaks in a very > low voice but when the song came up I came to know what you meant :). > > I'm happy to tell you that I'm very much interested in this idea and > the project. I understand major requirements of this project and I > pretty much like to do this as a GSoC project. > > I'm a final year student of department of computer science and > engineering, university of Moratuwa, Srilanka. I'll be downloading the > code base and try to build it. I will update you about the progress. I > don't have prior knowledge of Bazaar and building code from it. But > I'm familiar with maven and ant builds. I hope that bazaar would be > the same. > > Thanks! > Gayan > > > > > -- > Gayan Dhanushka > Undergraduate > Computer Science & Engineering > University of Moratuwa > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
