![]() It works as-is but is not as seamless as I would like. there is no way to send any information from Audulus back to TouchOSC, but I’m hoping that with two way MIDI support the integration between TouchOSC and Audulus will become seamless enough to allow it to become a practical performance surface for Audulus. The UI design process is a bit cumbersome and does require a Mac or PC, but it does allow you to separate the performance UI from the Audulus engine. It fully supports multi-touch which I regard as essential for a practical performance environment. It also allows you to define the size of touchable UI elements, and has a wider selection of control types. It uses tabbed screens rather than icons to switch views, but it also supports multiple displays. Have you looked at TouchOSC? Using it as a control surface for Audulus provides many of the same features as your proposal. I like the idea of being able to switch views, and on-screen help would be very useful.The SVG icons allow for a compact display, but sometimes can be a bit obscure. Some interesting ideas, and a good presentation. Ideally people can take the patches and use them in ways that go beyond what you’d originally envisioned as they make them part of their own creative process. In patch design, as with music, it is great to be able to create something others can engage with versus being limited to a small audience because they can’t relate to what you’re trying to accomplish. Patches could be enhanced by users who are able to apply their graphic and GUI design talents to create polished intuitive patches. People who already use Audulus would no longer need to encourage people to get over the programming hump to use Audulus and the complexities of patches would not interfere with the ability to use them as a sophisticated GUI approach would allow the patch user to focus on understanding how to use it within the context of what they already know. The vector based nodes/modules with nested patch levels is unparalleled on iOS so the ability to establish GUI relationships using similar tools for traditional app usage people are familiar with could leverage the existing tools and bring things to another level. These conditions along with the already planned improvements in functionality for Audulus 3 and Audulus 4 along with the increased capacity of iOS devices and the Files app can all contribute to the synergy of what improved GUI functionality and flexibility can bring to the table. ![]() AU is much more reliable than IAA, remembers your setup, and can use more than one instance of an app. Audulus as a visual programming language is great and magnitudes more accessible to new users than traditional text based programming environments. What I would like to have in Audulus might not match up with their road map for the future but I certainly don’t see my desire to have a deep and user friendly GUI and audio programming environment on iOS going away either. I have no interest in defending my proposal to the Audulus developers as they’re either willing to broaden their market or believe they need to focus on the market they currently have. My impression is that the Audulus development team is focused on a programmer oriented market and will not be willing to invest in the GUI support needed to make the patches accessible to the general iOS musician. Given the tepid response by I didn’t want to waste my time on such an effort as it seems there’s probably zero chance of something like my proposal becoming a reality in Audulus as all of the demos seem more focused on complex patches with lots of wires and collections of modules strung together which are overwhelming to many potential new users or to users who just want to create music with patches with minimal time invested in learning how to use patches. Rather than nodes exclusively focused on audio processing, there’d also be nodes to facilitate linking controls together in a relational structure for a GUI.Ī video isn’t the best way to demonstrate such a proposal and perhaps an html structure which is more interactive would be. My motivation is to be able to create patches in Audulus that are able to appear similar to conventional music creation apps so that users who aren’t into programming will be able to easily use the Audulus patch as they would any other app they’re used to using.Ĭurrently, Audulus seems more oriented towards people who are more interested in the audio programming side of app development whereas I would like to have a platform on iOS where the GUI could be equally sophisticated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |