unearthed test track from a few years ago
-
@nnirror yeah it's way faster just working in Max - everything's right there, way lower CPU usage, no faffing between channels, and no overview so no losing the thread, can stay in the zone etc
but obvs in Live i can record to a timeline and do audio editing, which is something i'm prob never gonna add to the rig, so it's worth having but not ideal ykwim
i mean Max is a realtime environment, i know Live tries to be that but to me it's only realtime as far as clip triggering goes
@sean_ae fo sho, makes sense and easy to like, randomly drop in an effect device ontop of a chain while playing in live. definitely can see how both would have their benefits and worth exploring
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae love the way it floats away and then the beat comes back clanging on metal bars and wooden structures with that swelling pad underneath. the lead synth in the first half does sound similar to the "clarinet"-like bit in the 2024 live sets to me?
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae at least some peole still posting beautiful stuff
-
@sean_ae love the way it floats away and then the beat comes back clanging on metal bars and wooden structures with that swelling pad underneath. the lead synth in the first half does sound similar to the "clarinet"-like bit in the 2024 live sets to me?
@zweikreise yeah it's the same pipe sound, almost same drums as well on that bit
-
@sean_ae at least some peole still posting beautiful stuff
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae I'm so used to the live version of this material that hearing this is really screwing with my head. Everything's totally recontextualized. I feel like I'm hearing noises from later in the megaset too.
What's going on with that ambient coil-esque drone in the middle? It's so pretty.... was that made for this track specifically?
Side note love when you guys work with swing.
-
@sean_ae fo sho, makes sense and easy to like, randomly drop in an effect device ontop of a chain while playing in live. definitely can see how both would have their benefits and worth exploring
@nnirror esp useful for doing remixes
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
This post is deleted! -
@sean_ae I'm so used to the live version of this material that hearing this is really screwing with my head. Everything's totally recontextualized. I feel like I'm hearing noises from later in the megaset too.
What's going on with that ambient coil-esque drone in the middle? It's so pretty.... was that made for this track specifically?
Side note love when you guys work with swing.
@Galarem yeah the middle and end bits were just following the thread in Live and seeing where it went
didn't have a plan really it just happened that way
-
This post is deleted!
-
@sean_ae put up some shelving listening to this. the hihat made me think i'm in a restaurant with cutlery hitting the plate nearby..
@sean_ae also i cant not associate the scratch sound with the king's speech in katamari damacy
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae super funky 🤌
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae really love the snappy snare from 5:36-8:15ish - is that modalys? I just started trying to get it to work
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae Love it, thanks for sharing with us out here. With the rig modules, would you say that each of them holds various musical ideas (sounds, but also phrases and patterns) and that part of the larger music making process involves recombining ideas (current and previous) among them as new starting points? Sorry if that’s too abstract, but it’s an idea I keep rolling around in my head and wondering how much it plays in your process. You mentioned the term “dry technique” once in a message and I didn’t know what you meant, and interpreted it as “don’t repeat yourself” technique, like, maybe, avoid writing the same ideas over and over and rather save them, recall them, recombine them.
I wish you would teach a course! Ha
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae really beautiful, love that atmospheric section in the middle with the big chords coming in waves
-
@sean_ae really love the snappy snare from 5:36-8:15ish - is that modalys? I just started trying to get it to work
@zinn actually idk, i changed a bunch of stuff in the rig since i did this
i'm glad you asked though cos i can prob fix that issue by storing the patch name instead of the number (where it appears in the folder - and that was always a daft way to do it cos i change folder contents too often. too quick and dirty for my own good sometimes)
-
@Lime yeah basically it's just a patch which is a port of the global patch from the rig, and 3 different patches for each of the slot types i use (seq, synth, fx), and the patches all communicate at global/slot level via send/rcv pairs
they p much ignore Live's sequencing, and have to really cos i don't use note on/off
i did make a couple more patches to convert from our protocol to midi and back but i barely use them cos it's a bit awkward (out from the seqs is fine but back from Live's seq is a bit weird cos the synth/fx patches expect durations, so i have to fix the durations, which, yeah not great)
@sean_ae @Lime I'm kinda surprised you got the send/receive pairs working. What I found was that using sends on devices on the same track was fine, but sending/receiving across tracks resulted in jitter/latency. I made a simple patch pair to demo. One to send midi, one to receive. I added the send/receive patches to the same track and only the receiver to a 2nd track. I recorded an 8th note midi clip ouput from each of those. Screenshots will clarify hopefully-
-
@sean_ae Love it, thanks for sharing with us out here. With the rig modules, would you say that each of them holds various musical ideas (sounds, but also phrases and patterns) and that part of the larger music making process involves recombining ideas (current and previous) among them as new starting points? Sorry if that’s too abstract, but it’s an idea I keep rolling around in my head and wondering how much it plays in your process. You mentioned the term “dry technique” once in a message and I didn’t know what you meant, and interpreted it as “don’t repeat yourself” technique, like, maybe, avoid writing the same ideas over and over and rather save them, recall them, recombine them.
I wish you would teach a course! Ha
@chorist yeah i would say so, cos loads of them are doing more than you'd normally think of that type of module doing strictly (although it's a bit like how hardware synths might have some sequencing internally alongside whatever you're sending to them)
the way i do it is seq modules just do sequencing, synths do sequencing and synthesis, and fx do sequencing, synthesis and effect stuff
it gets more complex as you go down the chain basically, to the point where i can be doing whole tracks in one fx module (i do this cos my background is making one patch per track and i still like working that way sometimes cos it def has upsides)
i mean end of the day it's Max, and although i enjoy the rough formalism of hardware workflow i also like the weirder things you can do with hardware, and the near total connectivity you get in Max
-
@sean_ae @Lime I'm kinda surprised you got the send/receive pairs working. What I found was that using sends on devices on the same track was fine, but sending/receiving across tracks resulted in jitter/latency. I made a simple patch pair to demo. One to send midi, one to receive. I added the send/receive patches to the same track and only the receiver to a 2nd track. I recorded an 8th note midi clip ouput from each of those. Screenshots will clarify hopefully-
-
unearthed test track from a few years ago
was trying a new (at the time) m4l port of our rig - a lot closer to the way the rig works in Max than the older port we used on SIGN/PLUS
(so a good chunk of it was culled from the bit of the set i was working on then)
@sean_ae b sec at 5:37
