[crosspatch] orientation...

Brian H.'s icon

Hi,

Does this object have a way to make a matrix with a vertical orientation– meaning outputs on top, inputs on bottom, like a conventional studio patchbay? Seems like it would, but I couldn't find anything in the help file.

Thanks,
Brian

Wil's icon

If you don’t mind coding it look at this thread

But thats not what you are asking is it? You want the actual [matrix] to plug into the bottom and exit the top?

That’s confusing and just weird because everything in max flows down.

You can easily build the [matrix] to do that.

I don’t know about [matrix~], I very explicitly do NOT use AI for any audio coding.

Brian H.'s icon

What the robot coded is what I was asking for (except outputs on the top), although I need to understand it better to use it in this case and it does need to work with [matrix~]. The position of the actual Max inlets/outlets doesn't matter. Sounds like it will be a feature request.

Wil's icon

Hi. if we are splitting hairs and updating the traditional definition of robot to include AI, then it follows that Max is a robot as well.

As far as matrix~ , crosspatch works with that as well . There is a one minor difference how the crosspatch adapts to matrix vs matrix~ when seeing the connections that ere made using x y value messages directly.

if you dont want to change the matrix object and just change visual layout of crosspatch, just take the code from the shared link , drop it into any free AI model , and tell it to switch the inlets and outlets.

Not saying you are lazy just saying anyone cannot be lazy with AI. It will give you a completely positive 100% guaranteed to work answer that isn’t even close. It was trained to do that. The bosses in the industry are slowly working to untrain or retrain all the bad training they did a few years ago. It will take a few more years to fix.

In the meantime lyou can you use prompts like “be critical in your assessment “ to help it look at itself and impossible things people ask of it.

Until regular folks start dong that, we are going to go through a few years of building mostly Homer Simpson barbecue S10E19 (with a really nice birdcage at the end)

It is very doubtful c74 is going to update the crosspatch object to have left/right , right/left , top/bottom , bottom /top configuration. Maybe?

Roman Thilenius's icon

the main difference between using crosspatch in your patch and using custom crosspatch patchers in your patch is that your custom crosspatch patcher was available 15 years before crosspatch and you can easily change its direction, color, or size.

Brian H.'s icon

Heh, well I have been waiting almost 15 years! But in those 15 years I had other things to do with my life than learning JS, so this option in [crosspatch] matters to me.

Roman Thilenius's icon

homer simpson would have used [lcd], [mgraphics] or [jit.pwindow].
it is drawing a few lines (without fancy curves) and getting the idle mouse and click postion after all.

Wil's icon

Haha. Because he was a 90’s/00’s kind of guy !

I 100% think there is lot to be said in favor of the legacy folks vs ‘updated system’ folks.

There is a massive amount of folks and work done around max 4-5 that should never change. I find a lot of post from 2010 to 2015 is that are absolutely gems.

As well, I found one last night that was never solved (with Roman in it) from 2010 and I solved it last night using AI and V8.

So there’s nothing wrong with being right at the front edge as well.

Besides, Honers car NEEDED all those cup holders.

Roman Thilenius's icon

if cycling would add vertical mode tomorrow, we all know what would happen next: people would ask for diagonal orientation of crosspatch´s IOs to be added.

becoming dependent on third party tech is one thing, becoming dependent on something you only hope might come somewhen in the future is the worst you can do.

while it is great that max now has "crosspatch", i wouldnt like to wait for someone else to build exactly what i need. (or learn java only for a single task, i am with him there.)

it should be easy to decompile the object using CC 5.5 and build an alternate version, but then how you are going to call the new object? :)

weird enough that since this month you can run powercore plug-in for windows natively on mac-arm using DSP emulators.
but when you have 30 different crosspatch object versions floating around the net, that is the definition of slop.

accept what is there and fill the subjective gaps with custom code.