Multi sidechain inputs?

hello

the last mystery i have for building the tools i want is sidechain and that works nicely with 1 sidechain channel input

i tried having 3 coz i thought i could sidechain 2 nodes of an eq to 3 different channels so id end up having a ducker for kick snare and hat all in one i could drop on any channel

starting to think 3 channels for sidechain is not possible because the moment i add more than one it does not start showing 2 here

but will also cut out the first

am i missing something?

Hey Peter, exactly, right now the sidechain only accepts two inputs. I’ll make a note to add more inputs in the future.

hello i wonder where its at with multi inputs

cheers

thnx for the new sidechains, i already made my sidechain kick snare hat ducker for this day beforehand :slight_smile:

this works really nice thnx mario

a small example: yellow kick, green snare, blue hat

and ive found a way to make it as cpu friendly as my now mapping formulas template stuff by disabling all the visual stuff and pitch detection once your done setting it up so bye bye mapping formulas and hello mnodes :slight_smile: this is much easyer to setup

test

it has auto level finder for the envelopes, shows estimated pitch, has a button to transfer that as a starting point, adjustable analyser times and bypass for all parts visual or processing. oh and it can duck sideways aswell for a push pull effect or expand

ah never mind wont be uploading it to dannys ai generared hub you might just aswell call it danny’s place at this point

really bad idea giving some folks all this ai stuff while the rest has to watch the hub change into a ai slopfest

getting sick and tired of mnodes and the path it took now its all about graphics and their related bugs and the ai while the backend for audio has a long way to go still not to mention the incredible ammount of inconsistencies when you want to build a gui from basic controls ya know the thing that was advertized in the start > no code needed

clearly that is no longer true or even cared about

kinda amazing you managed to destroy the community and human aspect before you even released it…

Hey Peter,

Could you share a couple of examples of what felt inconsistent when you were building the GUI with the basic controls? What were you trying to do, and what happened instead?

MNodes is a big project, and some issues only show up when people start building their own patches. I’m still polishing it, and reports from the community help me find and fix things I’ve missed.

On audio, I see things differently. Giving you detailed control over routing and processing is a big part of what I’m building. The extra sidechain inputs you used for your ducker are one example of that work. If there’s a specific audio workflow where you’re still hitting a wall, I’d like to hear about it.

never mind mario this is the last i have to say

i love a lot about mnodes but some very basic stuff like latency reporting should be there long time ago and sidechain is very basic stuff imo. cpu use is a big concern aswell a few cv wires and up it goes. also when i build a gui every new project is a run around with workarounds and forced decisions because some element is not capable of fitting in style wise with the rest of my design and i am tired of coming with another list coz i could but i want to build and not build report wait and then the next i run into

i am also disappointed into the big sideturn mnodes took from soon export your own vst to now a few individuals flooding everything with ai an ai nobody else has while the claude doc is still stuck on 1.1.4… updates always have the potential of breakin things i had hoped to capture things as vst (an option someone you gave mnodes ai to build for himself based on your tools isnt that hilarious) untill i can capture a project as vst all i build is useless in a serious production due to updates potentially breaking things

ai is killing the community aspect as it does everywhere else most early birds are already gone havent you noticed but i sticked around because i love mnodes and want to seriously build my tools BY HAND with mnodes and did not buy it to code i bought it partly to escape the coding loop i was in for years working on my own software

but that is not to say i dont think you did not make something very cool here and i truly wish you and your family a good live coming from it but i am stepping back community wise and focus on my own creativity and just settle with what i have

Sorry to hear that, i assume this is your last message here or at least very soon you are leaving?

But i noticed the “some one you gave ai to build for himself” and now i only can assume, and of course correct me if you where not thinking about me. But none of my projects is build with MNode Assist. I was only beta testing a 2-3 weeks ago and like that golden dragon and pinball where created with MNode Assist. Just experiments, nothing more. almost a bit awkward to see or to be usable.**

--
** added this later : I mean Assist is very usable, you can create projects but i also would suggest to see it as an helping aid. get examples, get a solution for a question. But it is not to be used like “lets create 20 large projects” and give it away for free. i mean you are spending money on it. unless you are motivated to give back to the world on your behave, nothing wrong about that also.

I think a community will always change, you got a lot of hyped people that at some point figure out that also this takes time away from creating music. There can be a lot of reasons why things shift. difficulty, limits , ai versus non-ai.

I mean i have Autism, This brings some exclusive skills. I remember a lot, i got a creative mind, perfectionism, wanting to learn what i create.

We are all different, a community does not exist from a singular point of view on the matter and even that singular point will shift influenced by changes.

But thanks for being here, and i still hope you find a way to still be here. i mean, not everyone is like me or Mario with AI. For sure, even Mario is still typing code till this day as am i.

Never stop learning, never stop enjoying things in life what matters to you!.

Wish you the best, if you are leaving. thanks for being here!

I get where you’re coming from.

MNodes has reported latency to the DAW for some time. In my experience, it runs smoothly, though CPU use depends on how the graph is built. Optimizing the graph is part of developing a patch. VST export is still planned, and I have a few things to resolve before releasing it. Keeping existing projects working across updates is a priority for me.

I want people to be free to build by hand or use Assist as much as they like. I also enjoy seeing new projects on the Hub, where many users go to find instruments and effects for their music. I’m not sure how much of the change you’re seeing in the community is related to AI. I still see people sharing projects and talking about MNodes both here on the forum and on Discord. If you ever feel like revisiting the conversation, I’d like to understand whether your concern is about Assist itself.

Thanks for everything you’ve contributed. I respect your decision to step back.

I’m with you Peter. I have held back writing a similar post. It seems MNodes has gone past the “sweet spot” with regard to music production using the node building blocks. With its recent focus on AI and graphics and sometimes seemingly esoteric nodes, I am less clear on Mario’s vision. Or perhaps that direction makes it more clear. I don’t know. But that’s just me. But my opinion is 1 of about 10,000 out there so in the end, what I think is meaningless. But I wanted to share it anyway. Don’t get me wrong - MNodes is AMAZING and I’ll certainly continue to use it. But I absolutely understand where you are coming from.

I’m still trying to understand what you feel has changed in MNodes’ direction.

My vision has always been to create an environment where people can develop audio and MIDI projects, or use projects made by others. Visual tools such as shaders, 3D objects and lighting, alongside Nucli, Racks and new audio effects, expand what people can build within that environment. To me, these additions are part of that vision.

Assist adds another tool to that workspace. Some people will enjoy connecting every node themselves, others will use AI for parts of the process, and others will use it more extensively. My goal is to give people a versatile environment for developing audio and MIDI apps, with room for those different ways of working.

I understand that some additions may be more relevant to you than others. What I’m still unclear about is which changes make MNodes less suited to what you want to do. Is it becoming harder to use, are there particular audio or MIDI features you feel need more attention, or is it the balance of development priorities that concerns you? What would you like to see change?

its also this kind of stuff mario i dont know what to trust now see

notice how it is disabled for a moment and then just picks up again

temp

Thanks for pointing it out. It’s completely normal for bugs to keep turning up. One thing I learned a long time ago is that however confident you are in your software, there’s always an unexpected issue waiting to appear. Unfortunately, that happens with any software, however mature it is.

I’ve already fixed this issue and others you’ve mentioned. Thanks again for your keen eye and for helping me improve MNodes.

i know and i dont hold it against you, you work very hard and in many ways you do not deserve that but for me being able to use my tools consistently in my own music i need to be able to capture them in a state that can not be changed by updates i hope you understand because ultimately i make them to use in my music and not just for the fun of it

Mario,

I’m an older guy that probably doesn’t yet know enough about AI to fully appreciate its utility and position as a tool in MNodes. Don’t change anything with what you are doing and where you are going. I am just used to more hand built patches given what I’ve seen in other modular software communities. Who knows, even other tool’s users may be creating patches with AI.

So rather than you changing anything, I’m the one that probably needs to change and modernize my perspective. :blush: