Your favorite beat mangling tool
-
- Posts: 187
- Joined: Fri Aug 01, 2008 10:32 am
- Location: Bristol
- Contact:
+1duluxdog wrote:I don't do much of beat mangling but I tried Supatrigga a few times and thought it was alright. The thing is, it sounds so obvious. You can hear it all over some tracks, used to excess.
Can't be some hands on manual-mangling; traditional cut paste, re-sample, re-verse and some individual external sample editing/processing.
Pretty sure the man Richard D James got the best part of his sound this way, don't think he would use many if any 'auto-glitchers'.
Allows for more precision imo.
Live (yoghurt) - MBP- Circuit Bent Rampant Rabbit - Mongolian Nose Flute - 'The Marvelous Mechanical Mouse Organ' (on loan from Bagpuss) and a Swanee Whistle made from a used heroin syringe.
Well, yes and no - I also feel inspired after a getting good Blow Job... but I'm not sure it counts as a "beat-mangling tool" in itself - so I'm not sure it counts.mike@TrackTeam Audio wrote: A nice BJ will prob get you mangling beats like no other...
MBP 2.4GHz, 4Gb RAM, OSX 10.5.5, Live7Suite, Motu Ultralite Mk3, ADAM p11A
-
- Posts: 2122
- Joined: Tue Aug 07, 2007 9:57 pm
Thats why I want a tool that on one hand spits out nasty tunes but on the other is well controllable. I guess most of the glitch-tool users put the sound into the glitch-tool, see what comes out and then begin to edit.Low Frequency Obstinator wrote: Can't be some hands on manual-mangling; traditional cut paste, re-sample, re-verse and some individual external sample editing/processing.
Pretty sure the man Richard D James got the best part of his sound this way, don't think he would use many if any 'auto-glitchers'.
Allows for more precision imo.
-
- Posts: 2122
- Joined: Tue Aug 07, 2007 9:57 pm
-
- Posts: 1965
- Joined: Fri Oct 26, 2007 3:58 pm
- Location: Nottingham, UK
I use CList's BeatLookup (various versions), a couple of tools by a chap named Sowari; one called 4techre in perticular. There's some ncie things in the 'jambient' series of ensembles.Grappadura wrote:Mike & other Reaktor users: What ensembles do you use? I´ve listened to the demos of drumcrate & was impressed!
From the stock library, there's various sample-manglers, too. I'll be jiggered if I can remember what they're called though!
Macbook | Live 7.0.18 |
-
- Posts: 986
- Joined: Wed Apr 09, 2008 8:02 pm
- Contact:
I build my own ensembles.Grappadura wrote:Mike & other Reaktor users: What ensembles do you use? I´ve listened to the demos of drumcrate & was impressed!
3.6 GHz i7-9700K 8-Core|Win 10 64|MOTU 16a|Push 2|Live 10.1.15 Suite|Komplete12|Studio One V4|Reason 11|Zebra 2|Omnisphere 2||
--------------------------------------------------------------------------
http://soundcloud.com/nomar161
--------------------------------------------------------------------------
http://soundcloud.com/nomar161
-
- Posts: 986
- Joined: Wed Apr 09, 2008 8:02 pm
- Contact:
Right on. I do indeed mean using the RAM/ROM machines. Do you have the UW version? If so, I HIGHLY recommend getting to know your MD better. UW-specific stuff follows, so disregard if you don't have this option on your machinedrum.4am wrote:ops... forgot to say i already have one
but i don't use it so much for beat mangling... do you mean with the ram machines?
Assuming you have the UW, check through the manual regarding the differences between the two types of ROM locations in the MD. The last few ROM slots behave somewhat differently with modulating the sample start and end times, optimized for rearranging loops. This is just the ticket for beat mangling.
I say give this a shot before plonking down more of your money for new shit. I always say that the MD is one of only three pieces of hardware (out of probably a hundred or so) that I will never sell. Give it love! In fact, I am heavily considering doing a free series of tutorial videos on sound design with the MD-UW once I am done with my current series.
- Nick
-
- Posts: 1279
- Joined: Wed Nov 02, 2005 5:31 pm
- Location: leadville, CO
the manual provides little to no help on how to use the UW, took me a bit to get it sorted out, but once i did, love it, because i can do dbglitch/beat repeat type stuff, but actually control it. (using parameter locks so that each step plays from exactly where i want gives great results, but i also like just noodling by randomly moving around the steps i've placed (via function/arrow), and putting LFOs on sample start/end.)
back to your question, i doubt it's because the memory is full. but i'm doing this with RAM machines sampling the external input, then playing it back, rather than loading samples into ROM (which seems like more trouble than it's worth, though YMMV).
back to your question, i doubt it's because the memory is full. but i'm doing this with RAM machines sampling the external input, then playing it back, rather than loading samples into ROM (which seems like more trouble than it's worth, though YMMV).
-
- Posts: 2122
- Joined: Tue Aug 07, 2007 9:57 pm
-
- Posts: 986
- Joined: Wed Apr 09, 2008 8:02 pm
- Contact:
IMO, this is the one part of the MDUW that is less than obvious in terms of ease of use. It's a little weird. If you are sampling into the inputs, make sure you set up a RAM record machine on a track. Go to your RAM record machine parameters and set your "ILEV" to 64, "MLEV" to 0. Now insert a trig for the RAM machine at the beginning of your pattern. Next, play the pattern and immediately delete the trig for the RAM machine. You should now have something in memory to play with.
At this point you COULD mess around with the RAM play machine, but I always copy what's in the RAM record machine into one of the ROM memory slots so I can work with something that won't accidentally get erased. Do this by going into your global menu, hit enter to choose 1 (out of 8 choices for global setups). From here, you should have an option for "sample manager," so go there. Now scroll down to your R1 machine and you should have a number displayed there which shows that something is in RAM. With R1 highlighted, hold down function+copy (I think copy = record button). Now move up to ROM slot 48, for instance, and hold function+paste (I think paste = play button). It will ask you if you want to carry out the copy operation, so hit enter. You might have to hit enter a couple of times, but it will copy. Now it asks you if you want to reload, so hit enter again and the RAM location will automatically clear out and you are left with your loop in the ROM location. Now set your ROM machine up on a track and choose that sample.
This looks like a long process in writing, but I only had to do it a few times before I got it down to 30 seconds or so. It's well worth it. I hope I haven't confused you, and good luck!
- Nick
At this point you COULD mess around with the RAM play machine, but I always copy what's in the RAM record machine into one of the ROM memory slots so I can work with something that won't accidentally get erased. Do this by going into your global menu, hit enter to choose 1 (out of 8 choices for global setups). From here, you should have an option for "sample manager," so go there. Now scroll down to your R1 machine and you should have a number displayed there which shows that something is in RAM. With R1 highlighted, hold down function+copy (I think copy = record button). Now move up to ROM slot 48, for instance, and hold function+paste (I think paste = play button). It will ask you if you want to carry out the copy operation, so hit enter. You might have to hit enter a couple of times, but it will copy. Now it asks you if you want to reload, so hit enter again and the RAM location will automatically clear out and you are left with your loop in the ROM location. Now set your ROM machine up on a track and choose that sample.
This looks like a long process in writing, but I only had to do it a few times before I got it down to 30 seconds or so. It's well worth it. I hope I haven't confused you, and good luck!
- Nick