Sample Chains on MD?

virtual_flannel · 2014-03-02T19:20:39.000Z

Used to do this when I had an MD, but didn’t know it was called sample chaining. Just P-lock those start points for a lot of fun! As was mentioned, no slice, so its not quite as nice, but still a great way to flex the MD!

void · 2014-03-02T19:55:56.000Z

ok just tried to do this systematically for the first time… filling up a track with trigs and locking STRT + END in increments of 8. pretty cool!

this needs to be automated.

void · 2014-03-02T21:28:55.000Z

stay tuned & dust off your TM-1’s guys

void · 2014-03-03T02:39:25.000Z

Okay…

MDice is a loop slicer for the Machinedrum running on Mac OS X 10.9.

Screen%20Shot%202014-03-03%20at%2003.08.35.png897×541 48.9 KB

Download: http://cl.ly/3u2O2c061T0f

What you need:

an MDUW with latest OS
a TM-1 MIDI interface.
a Mac with OS X 10.9

Connect your MDUW two-ways, the app needs MIDI in- and output.

MDice generates trigs in the currently selected track. The trigs’ STRT & END params are locked to slice up loops. So load a ROM or RAM machine containing a nice loop into a track, and make sure you’re in EXTENDED mode.

First Step (1-64): where in the pattern should the loop begin.

Length (1-64): how long should the loop be.

Skip (1-16): Space between trigs. In other words, slice width.

Sample Length (1-64): The length of your original sample measured in steps. A 1-bar sample is 16 steps.

Forward/Backward: General slice order.

Generate Locks: Whether STRT/END params should be p-locked. For ROM/RAM slicing, you want to keep this enabled.

Reverse: chance of slices playing backwards.

Shuffle: chance of slices being out of order.

When you’re happy with the parameters, press the Slice button.
this will generate trigs in an additive way… it never deletes trigs, only adds. so you can layer slices with different settings.

If you want to start fresh, clear the track on the MDUW.

IMPORTANT: when you hit the Slice button, the current pattern will be modified by the app, and will automatically be reloaded by the MDUW. This means the KIT will be reloaded too. Save your Kit before slicing. Also, it’s a good idea to keep a copy of the track/pattern in the copy buffers.

MOKA · 2014-03-03T12:36:01.000Z

possible to post your souce code to port this for Win?

void · 2014-03-03T12:45:30.000Z

here’s the code which does the slicing, which is trivial:

gist.github.com

https://gist.github.com/jpenca/9324287

MDice slicer

//
//  MDSampleSlicer.m
//  MachineDrumFramework
//
//  Created by Jakob Penca on 02/03/14.
//  Copyright (c) 2014 Jakob Penca. All rights reserved.
//

#import "MDSampleSlicer.h"
#import "MDMath.h"

This file has been truncated. show original

not going to show my code for manipulating sysex at this point… maybe later.

MOKA · 2014-03-03T12:54:24.000Z

Great, very apprecciate

void · 2014-03-03T13:16:33.000Z

here’s the method which gets called when you press the slice button:

gist.github.com

https://gist.github.com/jpenca/9324621

MDSlicer request

- (void) doIt
{
	[self.sliceApplyButton setEnabled:NO];
	
	int offset = self.firstStepSlider.intValue - 1;
	int length = self.lengthSlider.intValue;
	int skip = self.skipSlider.intValue;
	int sampleLength = self.sampleLengthSlider.intValue;
	float reverseAmt = self.reverseRandAmountSlider.intValue / 1000.0;
	float shuffleAmt = self.shuffleRandAmountSlider.intValue / 1000.0;

This file has been truncated. show original

There’s a system for asynchronous requests of SysEx data…
In the method above, there’s 2 nested requests.

first i’m asking for the current track number, then getting the current pattern. then apply the slicing and send the pattern back to the MD.

MOKA · 2014-03-03T13:23:38.000Z

Really thank you, a question …
you regenerate the checksum or not when you send the pattern?

void · 2014-03-03T13:25:58.000Z

yes… without correct checksum the MD will not accept the pattern

MOKA · 2014-03-03T13:30:03.000Z

thanks for all the info

void · 2014-03-03T16:07:33.000Z

is there any interest in a thing like this?
wondering if it’s worth putting more work in it.

Accent · 2014-03-03T16:24:06.000Z

Haven’t had a chance to even use it yet, but yes, I’m interested.

FreeFall · 2014-03-03T17:03:40.000Z

Damn VOID, you are so hired!

I haven’t had a chance to play with the MDice app yet (just downloaded it) but I’m excited to play with it. This is a great tool for exploring sections of a loop, without having to do all the tedium of setting START/END points. Very very cool.

It may be a day or three before I can dig into this thing, but I’ll report back once I do.

Thanks VOID!

void · 2014-03-03T18:32:06.000Z

having good results with Amen-Break autojungle & other drumloops.

but also, short chains of 4 or 8 one-shots work well…
recording a chain via RAM machine, then slice&dice…

i don’t have an OT and am not really familiar with that sample-chain concept, but it works very well… basically storing a mini-drumkit in a sample

what’s cool is that you can pitch the individual hits without messing up timing.
also, you can change the MD master tempo and the sliced stuff stays synced.

void · 2014-03-03T18:38:47.000Z

updated the app with the following functionality:

can now optionally auto-save the current Kit. This is a workaround for the MD-behaviour of reloading the kit when receiving a pattern, so you don’t have to save it manually if you make a tweak.
has an option for locking the pitch-parameter of all generated trigs to the value that’s currently in the kit. this only works when kit-auto-save is enabled.

Silverfish · 2014-03-03T19:54:02.000Z

This is a fantastic idea!

I don’t have Mavericks installed yet, so I can’t give it a shot. I’m seriously considering upgrading just for this.

I can’t wait to try it!

Accent · 2014-03-03T20:06:49.000Z

Damn, must have missed it was only for Mavericks. I’m still on ML and don’t plan to update any time soon, since Live 8 is buggy on 10.9 from what I understand. Bummer. If it is compatible with any previous versions at some point, I’m all in.

void · 2014-03-03T21:43:22.000Z

dunno, there is something in my framework code which seems to make my stuff fail to run on older OSX versions… hard to find out sans an older Mac to properly debug this.

here’s a build which should run on 10.7:

can anyone try? if it fails, can you send me the log?
(open /Applications/Utilities/Console.app, there should be some info in there)

PeterHanes · 2014-03-04T01:10:57.000Z

""void"":

is there any interest in a thing like this?
wondering if it’s worth putting more work in it.

Yes, I’m very interested in this kind of thing. I just downloaded and will get to playing with it in the next few days.
Thanks for taking the time to make it available.