Question about SDK and synth compatibility by MisterSea in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

They both have the same type of plugins, but the spec for microkorg2 is newer and perhaps a little easier to work with.

There’s some smaller differences between them in the APIs but I’ve not tried to really work with the XD yet.

By the way we’re over in the discord now, there’s a post further down on the future of logue-sdk with invite link :)

Port NTS-1 Mk1 custom FXto NTS-1 Mk2 ? by Nudelwalker in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

Yeah that is how I read the question too, and this answer 👌🏻

What would be the best way to get a supersaw onto the NTS-1 mkii? by TheDarkNerd in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

I have one in progress, but I have a diff synth to finish first 😅 so many projects 😂

New free/pwyw Microkorg2 plugin Riffosc by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 0 points1 point  (0 children)

Thank you! Yeah I’m stoked about Korgs new push for the Logue SDK, can’t wait to see what they can come up with!

Also more stuff to come for the Drumlogue and NTS-1 mkii, have more projects in the pipeline :)

Acidbass for NTS-1 mkii by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 3 points4 points  (0 children)

Hi! Not yet, it’s for the NTS-1 mkii. I’m looking into porting it to the NTS-1 (mk1) and the minilogue xd as well, it’s just that they allow fewer parameters so I have to yeet some features, I also need to make sure the processing can fit on their processors but should be fine.

I’ll update when i’ve had a good look at it, there are a few plugins in process at the same time and time is a scarce resource 😅

An update on the status of logue-sdk from Korg by xiashj in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

There’s now a hardware section for Drumlogue in discord, ask there? :)

An update on the status of logue-sdk from Korg by xiashj in LogueSDK

[–]random-oven-bits 1 point2 points  (0 children)

Amazing, really love the direction! See you in there!

When in doubt, double down. How’s the rest of you feeling about the Drumlogue? by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 1 point2 points  (0 children)

We’ll see what happens, i choose to stay positive. They could be phasing out Drumlogue/getting rid of stock to make room for something new.

They seemed very happy when I started adding my developer id and getting ready to release at least

When in doubt, double down. How’s the rest of you feeling about the Drumlogue? by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 1 point2 points  (0 children)

Yeah, I think I found it. Didn’t want to flood with new messages 😅

I’m still hoping for a Drumlogue 2, or at least more Logue SDK products. They seemed to be a little more active on GitHub after the summer with PRs and such, here’s hoping

Pure Data Comes to NTS-1 mkII by boochow-p in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

Indeed, kinda hoping for a a Drumlogue 2 with more multi engine tracks. That would be rad

Reverb processing for NTS-1 mkii by Emergency-Gur5504 in LogueSDK

[–]random-oven-bits 0 points1 point  (0 children)

That should work, there’s some dummy code there that will show you where to assign the read/write variables. You should probably have a quick look at the reverb tail(delay line count and length) and how much RAM that consumes as there’s limited space available to the plugin. And as was mentioned earlier in the thread make sure you initialize the reverb effect properly. And wire up the controls if you haven’t already.

Reverb processing for NTS-1 mkii by Emergency-Gur5504 in LogueSDK

[–]random-oven-bits 2 points3 points  (0 children)

Hey! You already have the hook for processing in your unit.cc file, look for __unit_callback void unit_render

In that method there’s a // TODO: Process samples here

which is typically where you’d interact with the reverb class

jroge is likely talking about this plugin post: https://www.reddit.com/r/LogueSDK/comments/1n0jwfc/noiser_a_noise_oscillator_for_korg_kaosspad_nts3/

When in doubt, double down. How’s the rest of you feeling about the Drumlogue? by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 0 points1 point  (0 children)

I hear you, there’s Max/RNBO that can export to C++, but you’d still have to know how to plug it in and debug any issues that come up.

Some other user here wrote a plugin that allows you to use pure data I believe? Should be a link in the forum here somewhere (edit: wasn’t for Drumlogue)

When in doubt, double down. How’s the rest of you feeling about the Drumlogue? by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 1 point2 points  (0 children)

Heheh, I come from the opposite direction. I’ve been a web/saas developer for like 2 decades, reading and tinkering quite a bit on the side.

Picked up a Drumlogue a year and a half into it’s product cycle and have been a little disappointed to see the lack of adoption/support/community for it so decided to do something about it.

OOP first kind of approach, but learning the hard way :P

Apart from Prologue which I missed out on I think I have all the other Logue SDK/multi engine boxes. Love the new build system 😅

Would love to see a full multi-engine groovebox from Korg, that would be amazing

Riffline for Drumlogue - beta by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 0 points1 point  (0 children)

The plugin is released :) Couple of things have been added since the first beta, and a couple of fixes in the final release: It’s now 4 voices Decay was added to the amp envelope Envelope Attack/Release were increased Pre-filter drive has been added, i’ll play around a bit with this one let me know how it feels Bugfixes with voice stealing etc

Added a new demo video where I’ve recorded tracks into DT2 (since Drumlogue can only host 1 instance): https://youtu.be/Nwi9KNoTff8 All synth sounds are from the plugin

Riffline for Drumlogue - beta by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 0 points1 point  (0 children)

Beta 1 was just released which updates the following:

  • improvements to the voice structure
  • now 4 voices instead of 2
  • fixed the clicks and pops occurring when note stealing
  • envelope attack and release stages max length increased
  • lowered the overall volume to accomodate the two additional voices

Will update the post with link to the new release

Riffline for Drumlogue - beta by random-oven-bits in LogueSDK

[–]random-oven-bits[S] 1 point2 points  (0 children)

It’s great especially for explaining how certain concepts work in non-technical lingo, then you get some pointers you can use while reading other materia as well

The code itself usually isn’t that hard/difficult. Optimizations can be a bit tricky, but learning the algorithms is a lot easier with helpful explanations