OS2 using audio track locators for live fun.

i don't know if this has been covered, but i've been getting some interesting results creating a dummy audio track (just record nothing for the length of the sequence) and putting locate points in different spots (usually like 1 and 4 [a kick and a snare] or whatever...) to do some very interesting live stuff by just popping in and out of different points in my entire sequence (since everything goes to the locator point instantly). its like having the jumping around functionality in seq change but WITHIN a sequence. thought someone might find this of use.

edit: turns out you don't even need to record a dummy track, just put points in the empty audio grid.

this is SUCH a powerful features for live use, maybe the single most potentially awesome live feature in jjos

can someone explain this feature?

is this the same as the audiotrack thing in the 2500 where you can start playin anywhere in the seq?

or is this different?

boxtones wrote:boxtones

Post subject: Re: OS2 using audio track locators for live fun.

not sure about the 2500, but it sounds the same.... except, that not only can you START playing from anywhere in the sequence, but you can jump to any part in the sequence while its already playing

boxtones wrote:can someone explain this feature?

is this the same as the audiotrack thing in the 2500 where you can start playin anywhere in the seq?

or is this different?

it's like setting setting 'chop' points on the timeline of an audio track, assiging these regions to the pads, and then using the pads to jump in between points of your entire sequence

this sounds cool

does anyone have any music that would display how it works?

or any vids?

and is this only available in OS2 cuz i have os1 4.99

os 2 only im afraid unless you use an old version of os1 with the pad mode functions. your far better getting os2 if you want to do this type of stuff because in the old pad mode the pad was permanently assigned to that function, no matter what bank or program you were using- not good for live stuff at all. with os2 this locate feature will only kick in when you select an audio track from the main screen, meaning that drum programs and instruments will play back as originally intended pad for pad.
os2 is great for other stuff too (adsr, loop edit and ndc to name a few)

it cool how its instant, like random access.

truly fly, not used it to its full yet either, just waiting for the ideal project - to enable this scenario fully.

just flicked about in it up till now.

but fly suggestion of putting them into a track/seq. and dipping in frequently.

i did this a while back in slightly diff ways, in the PC to seq#, using a SS, set a blank seq up (say #99 for simplicity), put loads of PC>Seq# events in it...all yer best seq's.

use it as the SS (simult seq), so it will always be running, yet flipping all the other seq's around according to the PC>Seq# events.

Will this effect midi as well?

midi, indeed. simult sequence your drums and watch your hardware get wild with just midi on your main sequence. i like putting a lot of random frequency sweeps all over a midi track and then jumping around, b/c your filters jump all over the place which can get really glitchy. i wish there were a way to sample the audio coming out while jumping around inside the box, but don't think it'll work.

I don't know how I missed this feature... yikes!

Curious though, why so many pre-assigned features. Anybody know why we've got a stop/play pad assignment when we've already got them on the MPC? Back Forward I'd think is already kind of be bar buttons.

good point. the more pads that point to locations the better. all the other functions (start/stop etc...) are redundant. time-based (.5 seconds forward/backward) are generally useless with the bar >/< step >/< like you said. 1.2: free 'em up.

NearTao wrote:I don't know how I missed this feature... yikes!

Curious though, why so many pre-assigned features. Anybody know why we've got a stop/play pad assignment when we've already got them on the MPC? Back Forward I'd think is already kind of be bar buttons.

yeah true, BUT , mbe its so that if any pad hits are recorded using these jump markers into the sequencer, they WOULD need to be pad based events .....but sayin that, the mpc couldn't 'use' a 'play' event from a recorded pad event if its stopped. but i sure could use a 'stop' pad event when its playing.

i first thought that they were a waste of pad use - these 'start/stop' functions when there's already dedicated buttons for this, but mbe JJ has a plan.

imagine being able to set the amount of time in bars/beats before the locator makes the jump after you press the pad. itd be all abletoney.

I would love to be able to record these changes into the mpc with a MIDI track that will trigger these recorded markers.

Also it would be super if the markers triggered to a "lock" of some sort so that the transitions can be super smooth when triggering the markers so there is no timing issues, the event will move to the marker on the next 1/4 or 1/8 beat for example.