Scratch Ableton clips in Traktor

Scratch Ableton clips in Traktor

You should be able to scratch ableton clips in almost any DVS with a little prep work.

have the clips all recorded on one audio file in the DVS with loopcues at the beginning of each clip, sync a muted DVS to ableton and map a button to mute the ableton clip and jump to the clip in the DVS and unmute in the DVS. If the levels are right this should "activate" scratch mode on the clip. Then map a bunch for all your clips and have them also toggle back to ableton on a second press.*

you could also use the midi output to cycle the DVS clip back into sync while you scratched it. This means being able to scratch a track anywhere but have it be in prefect sync when you release on the beat.

Ideally, you would have the scratch-clip looping via a beatsynced modifier countdown to re-cue because you could retain the looping function in traktor that way.

Ok, keep the hotcues open, and do the Traktor clip switching with a modifier system and beatjumps using midi-masher or midi-loop automation. That way you can set hotcues inside the clip and cue-juggle the clip on the fly.

Yes I have heard that also, but so far I can find nothing on ms pinky's stability in gig situations. While it isn't ideal to use a DVS as a dedicated live clip play-head, It should be stable and add some features that ms pinky doesn't have like: better hotcue juggling, colored waveforms, and the ability to scratch while quantized and probably more...

The quantized scratching is kind of hard to imagine but it should operate like this...

Have midi-masher take the beat phase output from another deck in Traktor (synced to live) and use that to trigger beat jumps in the Traktor clip. If you were to hold the control vinyl still, the clip would still jump to each beat of the clip while not playing, and if you scratch, the clip would track the scratching but also play the clip beat by beat under the scratch pattern. Sound interesting?

 

Was this ever attempted ... or successful ?

 

https://mspinky.com/ms-pinky-max-for-live/

Also


Join the latest "attempt" to get NI involved someday at this topic...
https://www.native-instruments.com/forum/threads/suggestions-for-traktor.419459/#post-1981485

... but aside those "alternative" don't hold your breath waiting for something like this. The result of these times come in the form of Remix Decks with in my opinion (aside automation lack) is far better than any of them for Ableton-like-with-turntables set.
Just use loop recorder to get material into the remix cells and that's it. NI could improve the workflow (check that topic for details) but the software even being long not so updated (minor things and new TDJ2) it's still the most advanced in the market for certain things...

 

Appreciate the response. Both ms.poinky pinky stinky and Scratch Track appear to be a viable "link" between the two worlds. Wonder if it will record a "performance" in Live per other plugins etc? Ie record a scratch routine using my TKS3 within live without touching Traktor ... ? Which is really the use case in which I'm interested. (Yes, it does. Yay.)

In further review, both tools only mention "timecoded vinyl" ... Is anyone aware the reasoning behind this ... They haven't been updated to include language for something like a Traktor Kontrol, or is it because they only support DVS?

Found Vinyl Lab as well. Going to try both Scratch Track (ST) and Vinyl Lab trial versions and see if I can get my use case to work. Doesn't appear ms.pinkystinkyfuiddnkhfy has a trial version, else that would be my preference.

12:55 - Pretty impressed w/ ST so far. Launched my TKS3 in MIDI mode and have it almost feeling like vinyl. Ability to map MIDI to just about anything on a turntable + mixer setup is something I've always wanted. Vinyl Lab is doo doo. I'd like to try ms.pinky before I make the purchase.

1:40 - With regard to the future, Allen & Heath's recent announcement surrounding Traktor will likely have a positive impact on quicker feature development, once operationally implemented. I perceive Native Instruments as having more of a bespoke, high-end, electronic and symphonic instrument focus, and less on the DJ end of the spectrum.

20:31 - Implemented the techniques in this tutorial, but it's nothing more than messing with pitch filters and sample trigger points. Not a true scratch methodology, though I will likely use it in performance along with real scratching.

20:35 - Conclusion for today is that while ST is quite close to what I'm looking for, it hasn't been developed in over 4 years, and my main concern is its processor spike issues when my audio buffer is larger than 256. This is likely a deal breaker for any serious use, as I need my latency to be sub 3ms. I'd like to get ms.pinky working as I suspect it's light on the processor. I've reached out to the authors.

 

Scratch track plugin has full automation and midi controller support so no need for DVS and you can just use it drawing lines on a DAW. I believe it's what you try to do...?

Hope it helps.

 

Yes - thanks. Please see my previous post. Was editing as I was going about the day.

 

Ms Pinky is abandonware ar this moment. No development seems going on. Also the maxfoelive patch has some “lacks” and nobody with enough knowledge was working on it too far (reach mr satkumi for the latest person working on patching).
Things like automation need to be implemented to name one example. Warped material recording could be “faked” by sampling on send channel but it adds extra step and still not true warping (if you change the tempo and the warp markers aren’t right set with the automatic algo... ) so I will recommend you reach Aaron Lesse (stagecraft owner and developer) for news on ST plug. He’s active at tweeter posting upgrades to other soft he made (synths) so maybe ST and other dj apps are just on halt due to low sales or so.

Best,
D.

 

That's great insight, Mutis. I've reached out to ms.pinky, but not Aaron, and as Aaron appears to be more active, will connect w/ him and see if I can incentivize him to update ST. It needs just a bit of refining and bug squashing. The processor jump issue is the only potential black hole I can see ...

 

Great. Please share here your findings...