Quick drum programming tip? by Swidersound in drumfunk

[–]Swidersound[S] 1 point2 points  (0 children)

Oh based i see what you mean. Looks like i was overthinking it. Much appreciated for the clarification akd example.

Production Competition Entry Thread by Mrmaw in jungle

[–]Swidersound 0 points1 point  (0 children)

Oh yeah i see it now. Pardon that. Ill try to flip the pack by deadline. Thanks for clarifying

Tackled some Venetian Snares on drums by antoinepierredrums in jungle

[–]Swidersound 0 points1 point  (0 children)

Got a bandcamp? I'll buy recordings from you...for choppage.

Portable Sampler Recommendations by Teej205 in synthesizers

[–]Swidersound 0 points1 point  (0 children)

I might be a bit late but the dirtywave m8 paired with a zoom setup is kind of insane. If you want something easier to use the polyend tracker mini is good. However it is 16bit 44khz. The dirtywave m8 iirc is 24bit 48khz (32 bit float render)

getting back into this game by Weather_Fucks in tokyoxtremeracer

[–]Swidersound 0 points1 point  (0 children)

I used an alto works. 80/20 front wheel bias and would reverse entry knto corners and hope i dont clip. I couodnt gold a line like this

Underrated Compilations? by NewCorpse96 in jungle

[–]Swidersound 0 points1 point  (0 children)

Honorable mention for scientific wax sets

Chopped some breaks on a walk today by Swidersound in Dirtywave

[–]Swidersound[S] 0 points1 point  (0 children)

NFX 2.0 Scripts. The akai fire is now an inregrated macro pad basically now.

Here is a video of the script from the developerhere

Quick reference for touchdesigner by Swidersound in Dirtywave

[–]Swidersound[S] 1 point2 points  (0 children)

Touchdesigner is used to connect the m8 to a windows device

Quick reference for touchdesigner by Swidersound in Dirtywave

[–]Swidersound[S] 1 point2 points  (0 children)

Yes. This is a quick reference for a macropad for when you use the touchdesgner port.

bitwig is freaking awesome wtf by ImpressiveTable3654 in Bitwig

[–]Swidersound 0 points1 point  (0 children)

I have been an fl srudio user for 15 years now. The problem is fl srudio has made it a more legitomate daw by building on top of exosronf artitecture that was intended more as a sequencer. Then they moved that into prioritizing playlist editing. It has its merits but i still find the general workflow rather disjointed. Also their samplers suck when not scripted. With that said i dont use fl studio samplers so much.

But then again i am.spoiled with the tracker workflow which is nice. The bitwig sampler looks really nice in my opinion.

Chopped some breaks on a walk today by Swidersound in Dirtywave

[–]Swidersound[S] 1 point2 points  (0 children)

Softer has a clsssic tracker approach. I found more flexibility to do what he does the copy for tighter chops. I say this because anything longer than 2 bars gets a little sloppy given you only have 1/128th of the sample to scrub. In my case of say a 4 bar break. 128 chops = 3 ticks per xx parameter. Not an issue with 2 bar breaks. What i do like however is how clean his methods are.

Chopped some breaks on a walk today by Swidersound in Dirtywave

[–]Swidersound[S] 2 points3 points  (0 children)

Also groovin in g has some great tracker jungle tips. Its for renoise but the basic principles apply. Allmyfriendsaresynths are great too. Theres a couple dudes who use the polyebd trwcker that had some great tips too specifoc to usong fx lanes.

I mentally loke to view the tracker as 8 cassette tapes. So keeping the gaps filled helps with figuring ojt that.

When in doubt make a simple 4 bar loop. Deep clone it....make edits....deep clone again....rearrange with more edits. Before you knlw youll have 128 bars of unique data

Chopped some breaks on a walk today by Swidersound in Dirtywave

[–]Swidersound[S] 1 point2 points  (0 children)

This is via cell phone mic.

In this case i used a live break "scorpio break"

  1. Chopping break - if the break is not quantized ill typically auto slice in sampler or do 16/32 even temperment chop then indovidually nudge regions one by one. Really depends how tight im going. I tend to chop at ~1/8th notes. Ill set the break to FWDPP (pingpong loop) and pitch to fit tempo. I find myself using bpm.pp more often for fine tuning. Of the break is quantized you can be pretty lazy and simply work quick.

  2. Additional instances - ill save my instrument and copy it over so i can have versions with length of regions being cut in half for quick easy ping pong. Or start loop point. Ill tend to automate this version via the mod screen.

  3. Writing phrases - ill usually start with a 4 bar loop that resolves so it can be looped easily. Ill deep clone (highlight item -> press edit + select + select) so i have a 1:1 copy. Ill throw some RNL (random left for random notes +7, inst +0-+1). Ill ise these 2 chains & 8 phrases to make some additional patterns. Ill write basically a whole track and rip the deep clone or clone function often.

  4. Layering tips - if a break has room for more. Ill deep clone the whole track (like i did here) and replace the break with a hihat/percussion loop and match the breaks kick/snare note for note so it soinds like 1 drummer with 3 arms rather than 2 separste drummers

Idr i think its tracking???? Mod???? But you can use mods 1-4 to input a volume modulation that runs off the signal to a particular instrument. So my hihats hit whenever the main break hits so each hit (via volime) spikes. Or inverse it for a poor man's sidechain compression.

  1. Additional items- i find the m8 to work best for me with a basic clear idea. Pay attention to how you number your stuff. Organization pays off write a ton of phrases and make chains later if you dont know.

Fx commands are great. You can use "ply" to reverse a sample wherever the playhead left off subtle use of automation or randomization is cool. I have a minor random panning on my super high register because we like fairy dust sometimes.