Improvements/Wishes for the patcher


#154

heres a little one, but it would make patching much faster; on osx, when i pull up the object window i need to select an object from the list and THEN im able to arrow up and down. it would be great if i could type an object name and then arrow down to the one i want.

in other words its mouse, type, mouse, type. instead of mouse, type, type, type. .

like i said, just a small annoyance, but it would make patching alot smoother and faster for me :hamburger:


#155

Press tab to move focus from the object name field to the list,
shift-tab to move focus back.


#156

oh nice - sorry i missed that - thanks!


#157

The ability to convert a subpatch into a patcher object version of the subpatch.

This would be very handy if you load a subpatch from the browser in Axoloti and then still want to edit the subpatch from patch to patch. The you could just push the "convert to patcher object" button and Axoloti converts the subpatch to a patcher object, which can then be edited, without worrying about messing up other songs or patches.


#158

you can already do this in 1.0.8, context menu, convert to patcher object.


#159

10 posts were split to a new topic: Sub patch - bypass/processing


#167

The Object Browser is the single item most in need of some attention in the current Patcher, I'd say.
It at the Least needs to be resizable, but having it constantly visible, or even docked to one side of the Patch window, would in my view be a great improvement.

a|x


#168

Also, I don't think the width of an object should be determined purely by the length of the title string.

I don't think we need any part of the file path of the object in the title- just the object name should be sufficient.

The path could be displayed in a tooltip when rolling over the title.

Personally, I think it would look much neater if the widths of all objects conformed to the same grid used to snap their positions.

a|x


#169

Yes just tried it. Nice. But it is not possible to edit the patch afterwards, besides form the code editor. Would be awesome if it was just another regular patcher object that you can edit as others.

Anyway, happy to finally be onboard the "new school" Axoloti :smile:


#170

Object layout, adding the ability to customize the position of different controls within the frame is certainly something I want to improve, and yes object type name or instance name should not affect size.

Hmmm but it is sometimes used to differentiate: osc/sine versus lfo/sine versus math/sine
I did not like the max/pd style ~ suffix, the tilde character is hard to reach on many keyboard layouts.

But that is already the case, no?


#171

A keyboard shortcut for reloading objects would be nice.....


#172

+1 for that. Would be very handy.

a|x


#173

Fair points. I don't see the problem with having a truncated name in the titlebar, and a more specific path in a tooltip that appears when you roll over the titlebar.

a|x


#174

there is an 'ideal' that you can reproduce a patch from a screenshot...so that might be slightly hindered by using tooltips. though, id say most of the time, the end part of the name is likely to be enough.
I think this ideal does have merits... here on the forum, when explaining things, you can simply post a screenshot, or even part of a screen, to give the idea of whats happening in the patch.

... but as i said, perhaps the end part is enough for this purpose.


#175

That's interesting. It IS one of the merits of an object-based editor that it's by nature 'self-documenting', so I do see your point here.

You can upload a .axp file to the forum though (and it will take up less space on the server, too, probably).

Maybe you could have a keyboard shortcut to toggle all tooltips on/off.

a|x


#176

Is there a way too start the patcher without automatically connecting?
I have a few axoloti's, and I wouldn't mind choosing which one to interact with before connecting (as some may be running in autonomous mode)


#177

not as far as Im aware... but I do want to do something similar....(same reason, many axoloti's to control)
Im thinking perhaps something like a command line interface, that can just upload a patch and get it to execute, disconnected.

what you can do temporarily at the moment (apart from sdcard and using program change events or similar) is use the fact that if you disconnect a board it continues to run the patch.

so what I do is...
select board 1 - connect, go live
disconnect (on console window)
select board 2 - connect, (possibly change patch) , go live
disconnect (on console window)
select board 3 - connect, (possibly change patch) , go live
disconnect (on console window)
etc

one thing you can't do currently... is reconnect to a running patch... as soon as you connect to a board, it will automatically stop the current patch.
(would be nice, if it would allow reconnect, you get the logging ... and something like if you had the same patch loaded, you could reconnect it ... obviously needs to be the same patch, for controls to match)

its not ideal buts works for now.. well that and using the SD Card, and load the patches via program change events.


#178

You might consider adding a couple more XML tags (or additional properties for existing tags) to be used in the Parameter section of the object definition.
Taken some cues from HTML/CSS, how about

float left
float right
clear

Using these tags/properties, you could arrange controls in horizontal rows and specify where to start the next row. It would be a start, in terms of allowing more controls over object layout.
Note: you'd have to move the parameter label above or underneath the control, for this to work (but to be honest, I think it would look neater here, anyway).

I used to be involved in the development of a video performance software, that had a plugin format based on Quartz Composer. At one time, they experimented with a method to allow plugin developers to customise the layout of their plugins, and even add their own background image. Adding the ability for Axoloti custom object developers to add their own logo or branded background image might encourage more established programmers (i.e. those who already have an established brand) to get involved.

a|x


#179

It gonna look like nightmare IMO. Reminds me Jeskola Buzz in skinned mode:


#180

How about reserving a small area at one corner of an object for logo or something similar, as a compromise?

a|x