On Mon, May 12, 2008 at 12:35 PM, Albert James Santoni <[EMAIL PROTECTED]> wrote: > Hi guys, > > > ----- Original Message ----- > From: Garth Dahlstrom <[EMAIL PROTECTED]> > Date: Monday, May 12, 2008 11:53 am > Subject: Re: [Mixxx-devel] loop tool > To: Nick Guenther <[EMAIL PROTECTED]> > Cc: mixxx-devel <[email protected]>, Felipe Machado <[EMAIL > PROTECTED]> > > > Hi Nick, > > > > I've seen it implemented a couple of ways: > > 1) Having loop in and loop out buttons (where the music between > > when you hit in and out is looped) > > 2) Having beat length select and a loop button > > > > > > Some of these use bpm detection to do it nicely (if your timing > > is a little off with the buttons).... I don't > > think our BPM detection is that granular though... > > so likely we'd have to go with 1 without the auto bpm > > alignment... > > This seems reasonable to me. I'd also be up for doing some brainstorming for > some unique way of implementing looping. I think simple loop-in and loop-out > is something we should start writing a spec for, and we can call it "Looping > 1.0". By sticking to this simple approach, we'll have functional looping > sooner rather than later. > > From there, we can build on the idea and come up with a spec for Looping > 2.0. One idea I have myself: > - Have a bank of loops that can be mixed in somehow. For example, when you > set the loop in/out markers, it would save that loop to a bank and you could > overlay it onto audio elsewhere in the song... something like this. > Stuff like this would take more effort and need way more thought put into > the design (and thus take longer to finish), which is why I'd like for > actually spec out and code Looping 1.0 first.
This is somewhat off topic, but I've been thinking about this sort of thing too. It would be really handy to also have not just a list of loops, but a list of cue points, each with an optional name the user can type in (and possibly some sort of wiring to hook it up to keyboard and midi control). Being able to overlay loops at random points *is* sampling, as Ben mentioned, and I think that should be something separate (though perhaps loops could have a "store in sampler" option). ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
