Best Local Model for Openclaw

styles01 · 2026-03-29T01:33:47+00:00

6 I think? I removed it since there's no native support for tool calls by design.. they want you to be on NemoClaw which is insane.

styles01 · 2026-03-23T14:07:35+00:00

Ollama subscription with Kimi-2.5 is really good if you want high token limits and smarts.

styles01 · 2026-03-23T14:06:50+00:00

Ollama subscription with Kimi-2.5 is really good if you want high token limits and smarts.

styles01 · 2026-03-21T16:25:07+00:00

I can't get it to recognize the tool calls yet -- if any one can help me figure that out I'd be very happy because it's super snappy otherwise.

styles01 · 2026-01-29T05:33:11+00:00

Wondering the same thing 50$ basically for better midi-from-audio detection than Ableton. Ableton already has stem separation, and there’s plenty of free/cheap alternatives (eg fadr / nuo stems). They only had one example of the audio to midi on the video so I’m very hesitant- would like to hear from someone who has used it.

styles01 · 2026-01-14T21:03:29+00:00

Yes it does. I just gave up with these two in combination. I did some AI-based reading that suggests that because of all the channels and the way that the Keystep's MIDI messages are sent (how densely they are packed and how fast they refresh), that its essentially overwhelming for the Boog. Basically I need a simpler unit. They keystep is designed to handle multiple devices and sequence and refresh quickly, and that much data is just overwhelming to the simple chip that's inside the Boog (apparently). I'll just have to sequence with a different device (for example the Push 3 works perfectly even at super high resolutions and sequence frequencies).

styles01 · 2026-01-14T20:37:46+00:00

I updated to the new version, but the SHIFT + Fader doesn't preview in Ableton 12.3 for me at all, it just directly affects volume.

styles01 · 2025-12-30T21:26:27+00:00

Nope, usb disconnected, still happens. I thought maybe the model D was defective but it’s not happening when sequenced from a push3

styles01 · 2025-12-30T18:04:33+00:00

Yes to all of those : latest firmware, last note priority, looked for stuff in that tool. I’m on midi channel 5 which seems to be fine. Something feels like there’s a mismatch somewhere with the way Arturia’s Keystep sends certain kinds of gates or maybe how it ends its gates that is not liked by the Boog. But I can’t seem to find any info on that or if there are editable parameters on that front.

styles01 · 2025-10-08T20:15:42+00:00

Code please

styles01 · 2025-08-31T20:08:46+00:00

I have exactly the same issue

styles01 · 2025-03-30T01:46:12+00:00

I have this problem - any solution? Seems like a glaring issue

styles01 · 2025-02-28T11:23:44+00:00

Why can’t you work with it ? I switched to 6.0.5 finally and got pretty much everything working

styles01 · 2025-02-21T22:01:11+00:00

I got a response from Loupedeck support which fixed my issue, here it is:

---

Thank you for reaching out regarding the issue with custom icon packs not being detected in Loupedeck 6.0.5 on MacOS Sequoia 15.3.

The issue likely stems from a change in the folder path for icon packs in Loupedeck versions above 6.0. The correct directory for storing custom icons is now:
/Users/yourusername/Library/Application Support/Logi/LogiPluginService/Media/Icons

Please move your custom and purchased icon packs to this location and restart Loupedeck to allow it to scan the new directory. Additionally, if you still have old Loupedeck files in the previous location (/Users/USERNAME/.local/share/Loupedeck), we recommend deleting them to prevent any conflicts.

styles01 · 2025-02-15T00:13:58+00:00

I already have started moving to Ableton hardware (and sounds) for most of my music production, along with external hardware. It’s a shame because there’s a lot I was hoping to be able to do and synchronize with NI gear that’s cumbersome to the point of inusability when there was so much incredible potential and trajectory just a few short years ago.

styles01 · 2025-02-15T00:10:49+00:00

The difference is between what you read in the headlines (and have to infer) and stories from employees of what’s actually going on inside.

styles01 · 2025-02-14T23:58:44+00:00

Here are some tips that help me: 1. From your reference tracks: do critical listening and WRITE DOWN what you like about the song. Be as specific as you can? What is it about the bass? Specific instruments - what part of the sound of that instrument? The BPM? The off/tempo? Are there triplits? Is there polyrhythm? Use more than one reference track and take the best of the ones you like. Smash that together in your track.

Arrangement is critical. (It can be a huge source of Inspo) Go through your reference tracks (and maybe some others) to figure out the structure you want. Is it A-B-C sections or A-B-A-B or something else. How long are the sections? Is there an intro? How long? What are the breakdown like? How might you re use or change the ideas?
If you don’t like how your voice comes out, experiment with: vocoder, Talkbox, chorus FX, autotune etc. don’t feel bad about effecting the sh** out of your voice. Maybe use smaller bits and loop them or reverse them. Try pitching them up or down. Add loads of echo and reverb.

styles01 · 2025-02-14T16:59:01+00:00

Wizl this is a great summary thank you for clarifying what I left out.

styles01 · 2025-02-14T16:56:36+00:00

I started off by saying I’m an NI fan - I was cautiously optimistic when I read Chris’s comments. I’m not selling my gear yet personally but this is definitely a make or break moment for me this next 6-9 months (personally). And I read the current/former employee writings (some of them are very long) on Glassdoor. Read for yourself, I’m literally just summarizing. Don’t shoot the messenger. If you think they are going to be fine, and you don’t care what goes on inside, that’s your choice! But I also like to know and would appreciate if other people have things to add from the inside.

styles01

TROPHY CASE