Quite interesting and IMO UX handy as reflects 1:1 the Ableton racks user interface:
Price:
param8 is available for 189€
2nd unit is 10% off (total 359.10 €)
3rd unit is 20% off (total 510.30 €)
4th unit is 30% off (total 642.60 €)
6 Likes
I think that’s the best thing, just start small and keep it simple at first 
1 Like
Super interesting. I got Push mainly for the encoders and screen; this little controller could save me a lot of space—I want to keep an eye on it.
1 Like
Really nice! I currently use a Move for this sort of thing, but I do always wish there was a screen for each knob, rather than the screen being at the side (basically the top quarter of a Push, as @DanHell says). I daydream of Ableton releasing a Move Pro (or whatever) with more screens, more channels, better i/o etc. But I digress…
I’ve tried using Knobbler on my iPad for Ableton control, and it is really nice, but in practice my fingers yearn for knobs.
3 Likes
Any Slink (from Hypnus Records) users here? Curious to get a read on something.
I’ve noticed the plug-in spikes my CPU (20%) on a mostly empty project.
Mind sharing your experience with it?
I just received mine ! Actually I originated the creation of Param8, and I’m stoked it turned into a product.
It feels great, homemade and 3D printed but great, super light, and honestly quite awesome for the price.
Latch and Revert modes are dead simple but powerful features for live !
5 Likes
I have some Slink devices. Any in particular that you use and/or notice being problematic?
I’m on a Macbook Pro with an M4 Pro. Still on Sequoia.
how would you compare it to the roto control? as they seem to be quite similar.
1 Like
Well, it started with me having issues with the RotoControl not being able to change its parameters names dynamically and me wanting a controller that controls stuff all across the Live Set, not just in one track like many remote scripts do, which I always found useless (or at least of a limited use) in a live situation.
In this regards, I find param8 much more suitable to use Midi Mapping to control parameters spread across the Live Set. You can even automate name changes with rack chains. It less direct than any automatic mapping, of course, it needs a tiny bit of preparation, but I find it much more useful and customizable.
Plus the revert and latch mode that I originally made for the expanded version of https://maxforlive.com/library/device/12707/16map for RotoControl.
2 Likes
I had something similar with a plugin-alliance plugin. Every 1 min or so there was a random cpu spike. It was only with 1 specific plugin.
To test it i made a completely empty set (i have a bunch of stuff in my default template), loaded only that plugin and made a screen recording with the cpu meter open.
I sent the recording to support and they refunded the plugin, nfi if they ever fixeded. I had a bunch of other PA plugins that were fine.
Theres a support channel on the hypnus discord, its quiet but the owner is around if people have questions.
1 Like
Pardon I should have mentioned, Slink Midi is the one I noticed. I’m running the latest Sequoia on an M4 MB Pro.
I dropped a Slink MIDI device into a default project and nothing seemed out of the ordinary. Now, I didn’t map anything but, at a glance, it seemed pretty normal. Not a device that I use though. I don’t know if there’s an updated version of the M4L device and I would’ve installed these no earlier than this time last year.
1 Like
Regarding Slink, has anyone tried the VST version?
Really feels like the absolute magic trick that is Link Audio has been sort of glossed over. Maybe because there was a lot of fanfare for it during the beta but not much when it came out. It’s incredible. Being able to natively pipe audio between apps, Max, Push, Live, with latency compensation and while everything is in time is amazing.
4 Likes
Is there any reason why I might have intermittent clips (more lkke transients)?
I’m using hardware on all of the tracks; nothing came in “hot.” I’m using Sequoia on an M4 (Big Six SSL mixer).
Diagnosis
-
For context, I found a bit of jitter / drift over a 16-bar kick recording. I’ve gone as far to copy and paste only two steps everywhere the kick is suppose to land. But there’s still an intermittent click.
-
I bypassed Ableton plug-ins on the drum group, as well as the kick track; there’s still what sounds like an intermittent phasing clipping (e.g., cut-off) that happens intermittently.
-
Because it’s intermittent, I’ve solo’d each track to find where it could be coming from. It seems to always happen at the top of a bar after a 16 bar sequence. Sometimes it happens during different aspects of the track, but it’s more consistently happening at the top of the bar.
This may not be an Ableton-specific issue, but it’s the only DAW I’ve tried. Appreciate any input.
Hopefully other companies will adapt to the Link Audio standard, so there is no need for aggregate audio interfaces or Overbridge anymore to combine multiple devices with usb audio.
2 Likes
Is it something you just hear but doesn’t actually appear if you export audio?
Where does the kick come from, what device? Bypass Ableton entirely, first check directly from the mixer if the click appears.
Is this recorded audio or is this monitored audio?
If it’s recorded then maybe the audio clip stopped recording at a non-zero crossing. Examine the clip and adjust the clip fades.
If this is during tracking then what is your sampling rate and buffer size?
Generally, people refer to this as ‘clicks’ and/or ‘pops’ vs ‘clipping’ where you’ve exceeded your available headroom. In the digital realm, this is very harsh and undesirable.
Please give a bit more context here.
To me it sounds much more like this, which is why I’d trace back the issue to the source. Buffering clicks are usually way more random and scattered.
1 Like
as other people have mentioned I just have a utility set to -6 on every channel so that the maximum output is 0db.
But the “mixing” in terms of actuallu balancing sounds was done in advance - I’m just dub mixing stems of already completed music when I’m performing like that - the faders really are just cutting stuff in and out. I generally have triggerable sections of the track set up with delay/reverb sends and a filter on each channel and that’s enough to get creative with.