I think Taylor might be less inclined to implement that since it’s something you can do with the Audulus nodes you’re given and wouldn’t be much more efficient if it were to be implemented at a lower level. The other stuff is something that wouldn’t be user-buildable with the nodes available. Good thought - just don’t want to explode the number of functions you can do in the expression node past a certain point - you’ll start to get into cryptic Max/Pd ~abbreviatedCommands
Had this idea today. Sometimes I want to copy groups of patches to a certain multiplicity. Instead of copy/pasting manually, which is tedious, I have three ideas:
- A copy menu option with a number input (not sure how the input would work)
or
- a special Copy Node with an output where you set the multiplicity (default 1) and connect its output to any input of a patch you want to copy. It copies and disconnects immediately.
Or
- A button as part of the interface. You can change the number on the button. Select what you want to copy, then tap the button.
Have you tried copy, paste, move, group, copy, paste? You can get an exponential number going pretty quickly. I suggested to Taylor a while back a method for creating knobs and lights where you could create them in groups by dragging them in rows/columns to make an array. Can you give me an example of what you’re copy/pasting so I can visualize what you’re doing?
That’s what I do usually. Unless I need a power of 2 I have to use extra brain power to figure out what to group. Its not overly difficult but could be easier. If I could get 12 copies at once in a neat column I think thats considerably easier.
1 Like
Please please please (if it isn’t too difficult), make there a way to make patches read-only. Sometimes I just want to open a patch to view or identify what it does. Then I lose track of where I was or what I was doing due to distractions, and when I come back, sometimes I have ended up wiping the slate clean to start a new patch over what was a experiment that started in the one and only copy I had of certain patches I had not shared (there is no backup in these cases). So by the time I realize I have patched over what should be a hard copy, I am unable to ‘undo’ the changes made to revert back to the blank slate and then bring back the copy I didn’t mean to kill. I think that would be useful, and I know it would save me from myself, quite a bit. Thanks! 
4 Likes
I would second that. I’ve gotten in the habit of duplicating patches before I start editing them and then working on the copy.
3 Likes
This might be a pretty significant request, but has the subject of integrating PD into Audulus come up before? Maybe a module that implements an interface to pdlib or something similar?
It would be great to be able to integrate PD patches into Audulus, or maybe use Audulus input for PD patches.
2 Likes
I would think that the simplest approach to integrating PD and Audulus would be through a shared audio/MIDI stream. On macOS Soundflower should allow at least audio to pass from one app to the other. I think the ideal approach would be using an AU version of each running in a host. Doing a quick Google search it looks like there is a project that is intended to allow PD to run as an AU on macOS but it hasn’t been updated in 3 years so I don’t know if it is still useable. Apparently pdlib isn’t thread-safe so the developer had to build his own wrapper for PD. There is also the PDParty app which allows PD patches to run on iOS, but I wasn’t able to determine if it supported AUv3, IAA or Audiobus. The Audulus AU available for macOS is currently somewhat limited, but should be significantly improved with V4 and an AUv3 version is also planned for iOS. Ultimately I think that this will be the best approach to integrating the two apps. I believe that writing a specific interface from PD to Audulus would be a significant piece of programming and would probably only be feasible on the Mac in any case. iOS is pretty restrictive about the types of inter-app communication allowed and IAA, Audiobus or AUv3 are probably the only practical approaches.
2 Likes
MobMuPlat is an IAA app with Audiobus support. The Pd patches need to be written in Pd Vanilla. They can run either in native mode or you can build a custom GUI for the patch on a PC and transfer it to your iOS device.
zMors Modular is an app that can run Pd patches and host AU or IAA apps. It hasn’t been updated in 10 months and the AU window support isn’t always very functional.
PdParty can’t be hosted as an AU, IAA or in Audiobus.
3 Likes
How about UNgroup?? You could convert all inputs and outputs to vias, converting i/o names to expr-legal variable names if necessary. Exposed elements could stay exposed
Just a thought. I’ve needed it from time to time.
I’d like to request a ‘snap to grid’ and/or ‘align modules.’ I’m imagining the ‘snap to grid’ would work very similarly to the existing lock/unlock UI feature. The ‘align modules’ would work similarly to the align feature in the microsoft office suite, where you have Alight Left, Center, Right, Top, Middle, Bottom as well as distribute horizontally and vertical.
As I mentioned elsewhere on this forum, foregoing an official ‘snap to grid’ feature, I’d be happy to write a little python script and/or iOS ‘shortcut’ to parse an audulus save file for module XY coordinates and round them to a user definable increment.
4 Likes
Snap to grid is definitely happening
4 Likes
If anyone is familiar with quartz composer the short cut system is pretty smooth.
Hit cmd + return and a library panel pops up that starts a new search.
Do a search for something like “LFO”
Then you can click on or navigate to the Wave generator with the keyboard arrows and the module will pop up in your modal workspace.
I immediately started trying to find a keyboard search function and was a little disappointed that I had to navigate so many menus to find modules in Audulus.
Still it is sooooo coool!
Thanks for a great app.
3 Likes
I have been mulling over the MIDI Fighter twister. When I saw the Hydra synthesizer knob/screen design I was reminded of how I wish the Twister had a small screen just to display text below each knob. This would, hopefully, lessen that feeling of separation you can get from hardware controlling software.
That ain’t happening. But, the twister does have programable colour coding. So, I am hoping Audulus 4 can allow for some sort of knob/button colour coding for hardware controllers. I think that would be enough of a visual cue to keep things fluid.
The second thought has to do with focusing. What if when you zoom in on a section of a large patch, the knobs that are currently on the screen are the ones that light up on the Twister. Then when you move to another section, different knobs light up and there is a one to one colour match?
It would also be nice to be able to save screen locations that can be snapped to. So you could have maybe 3 or 4 locked screen zoom points that you can flip between without needing to drag the screen and resize it.
I have been thinking about some sort of Make Noise Rene sequencer the using the Twister, or both the Midi Fighter and the MF Twister.
I have to say though, I have done stuff like this in the past and have found that while it may be challenging and fun to setup, quite often the fact that it is not dedicated like a Rene would be, means it might not get used.
2 Likes
I’m also hoping that A4 will have the ability to send some MIDI feedback to the Twister.
Firstly I think that the knobs and triggers in Audulus should be channel specific. As it stands, it doesn’t matter which channel a CC message is received on which limits the ability to use multiple banks on the Twister or even different controllers.
Secondly I believe that knobs and triggers should send MIDI feedback back to the controller. This would allow the Twister and similar devices to track a knob position instead of the knob only tracking the Twister. When you opened a patch, mapped knobs would send their position to the Twister, which would set itself to match.
Thirdly I think we need the ability to send an arbitrary MIDI message. You could use this to switch banks on the Twister, or change the knob color etc.
That is a major topic.
If this can’t be a two way street I will be very sad.
1 Like
I know that @taylor intends to expand the MIDI capabilities available in Audulus version 4. Exactly what form that will take and when various features might be available is still TBD. He has made some fundamental changes to the underlying architecture of the app which will provide a sound platform for future development, and at this point getting all of the basic functionality debugged is taking priority over new features. I guess we’ll just have to wait and see.
1 Like
Hey! I’ve tried to search this question in this topic before posting, but nothing useful has come up.
I know that auv3 is coming with Audulus 4, but what about having multiply, separate IAA ports like Patterning 2 or Reason Compact?
Auv3 would be useful for having separate instrument roles on different channels in AUM or Audiobus, but it would be great to be able to use lets say half of ES-8 for audio and effects, and the other half - for modulation and / or sequencing.
P. S. I guess this won’t happen due to iaa being soon deprecated by apple, so hopefully multichannel support for au is coming sometime in not too distant and not too bleak future)))
3 Likes
As you pointed out IAA has been deprecated by Apple, with AUv3 intended as its replacement. Because of this I would expect that there will be no additional IAA development for Audulus. I have advocated strongly for multichannel support in the forthcoming version 4 AUv3 on both iOS and macOS and hopefully that will be the case.
3 Likes
Just to confirm: I’m going for multichannel AUv3 support in A4. No IAA though because it’s deprecated.
7 Likes