For anyone considering OB-Xd 3, be mindful of this ongoing major issue: In AUM, OB-Xd 3 currently circumvents AUM's MIDI data filtering mechanisms specifically regarding incoming MIDI data coming from wireless MIDI devices connected to your iPad using WI-FI (Network Session) or Bluetooth. AUM is in no way at fault in this. As a consequence of this situation, anyone using a wireless MIDI device to control AUM functionalities using CC data will not be able to prevent that MIDI data from reaching ALL AUv3 instances of OB-Xd 3 loaded in an AUM project. Since the MIDI CC parameter mapping is directly baked into OB-Xd 3 by the developer, every single instance of the synth loaded in your AUM project will respond to incoming MIDI CC data that is almost certainly not intended to control it (regardless of the MIDI channel), which will alter the synth sound in real time whenever a wireless MIDI controller device is used. I've contacted the developer about this 3 days ago but I haven't received a response since. I would highly recommend holding off until there's a confirmation in the patch notes that this has been fixed. For now, I've had no choice but to eject OB-Xd 3 from my projects completely because having my workflow disrupted by technical issues of this nature is just not viable, regardless of how good the synth sounds.
@@dr.rabbitfoot7421 I'm assuming you meant to reply to the other comment I wrote 🙂 I really hope my content makes its way to the ears and eyes of less experienced people interested in electronic music production/exploration as well. My take on the current state of things for now though is that due to the sheer amount of elements that need to come together to create a setup similar to mine plus all the troubleshooting skills that end up being needed due to the inherent complexity of it all, perhaps it's more realistic to envision a beginner starting on iPad with something like Groove Rider GR-16 (by Jim Audio) or essentially an app emphasizing more on a self contained groove box concept with a cohesive user interface rather than something more modular like what I use. When I started my channel I envisioned my content acting as a hub to enable users with preexisting knowledge regarding electronic music production technology to discover what's now possible on iPad as that info is not at all obvious to come by. Even though my core content is definitely emphasizing on the educational aspect, I think it's pretty safe to say a beginner would have to be extraordinarily motivated to be able to "digest" the core content I provide on this channel, considering the content's technical complexity baseline generally speaking. Everything is relative of course, and hopefully some might find it approachable... I tried my best to make my content approachable to the degree where it doesn't burden the efficient delivery of information for viewers that are familiar with this technology, but balancing all this is definitely not an easy thing.
Hey! Thanks for your comment :) The plugin I use on my phone is Surface Builder (by 4pockets) the probable reason it might not be easily recognizable is because Surface Builder allows users to create custom MIDI control surfaces, so the control surface you see on the phone has been designed by me and I can modify it on a per-project basis. This includes buttons position, size, color attributes, transparency, margin, background image, and of course customizing the CC data sent by each button. Surface builder is potentially a lot more powerful than the use case I've demonstrated throughout my videos so far. For instance, I could configure it so that I could switch between multiple pages of controls by tapping on tabs buttons that I could add to the control surface, and each page would have its own custom controls, dramatically expanding possibilities & flexibility. One very important key thing to be mindful of though is that if you're interested in using Surface Builder on your iPhone in a Portrait orientation, you will need to run an instance of AUM on your iPhone to host Surface Builder. In my experience, it's the most desirable configuration anyway for optimizing project saving logistics considerations, and being able to position the remote in Portrait orientation represents a major ergonomics improvement too. I mention Surface Builder extensively in my main guide video at these times: (the video is thoroughly structured with sections/chapters) 33:48 2.3 Surface Builder 37:17 3.1 Introduction to Controlling AUM With a Remote Control The video can be found here: ruclips.net/video/hU5tGoltlPk/видео.html Cheers! :D
For anyone considering OB-Xd 3, be mindful of this ongoing major issue: In AUM, OB-Xd 3 currently circumvents AUM's MIDI data filtering mechanisms specifically regarding incoming MIDI data coming from wireless MIDI devices connected to your iPad using WI-FI (Network Session) or Bluetooth. AUM is in no way at fault in this. As a consequence of this situation, anyone using a wireless MIDI device to control AUM functionalities using CC data will not be able to prevent that MIDI data from reaching ALL AUv3 instances of OB-Xd 3 loaded in an AUM project. Since the MIDI CC parameter mapping is directly baked into OB-Xd 3 by the developer, every single instance of the synth loaded in your AUM project will respond to incoming MIDI CC data that is almost certainly not intended to control it (regardless of the MIDI channel), which will alter the synth sound in real time whenever a wireless MIDI controller device is used. I've contacted the developer about this 3 days ago but I haven't received a response since. I would highly recommend holding off until there's a confirmation in the patch notes that this has been fixed.
For now, I've had no choice but to eject OB-Xd 3 from my projects completely because having my workflow disrupted by technical issues of this nature is just not viable, regardless of how good the synth sounds.
@@Silent_Stillness I’m watching now very detailed I hope this gets out to beginners to see what is possible
@@dr.rabbitfoot7421 I'm assuming you meant to reply to the other comment I wrote 🙂
I really hope my content makes its way to the ears and eyes of less experienced people interested in electronic music production/exploration as well. My take on the current state of things for now though is that due to the sheer amount of elements that need to come together to create a setup similar to mine plus all the troubleshooting skills that end up being needed due to the inherent complexity of it all, perhaps it's more realistic to envision a beginner starting on iPad with something like Groove Rider GR-16 (by Jim Audio) or essentially an app emphasizing more on a self contained groove box concept with a cohesive user interface rather than something more modular like what I use.
When I started my channel I envisioned my content acting as a hub to enable users with preexisting knowledge regarding electronic music production technology to discover what's now possible on iPad as that info is not at all obvious to come by. Even though my core content is definitely emphasizing on the educational aspect, I think it's pretty safe to say a beginner would have to be extraordinarily motivated to be able to "digest" the core content I provide on this channel, considering the content's technical complexity baseline generally speaking. Everything is relative of course, and hopefully some might find it approachable... I tried my best to make my content approachable to the degree where it doesn't burden the efficient delivery of information for viewers that are familiar with this technology, but balancing all this is definitely not an easy thing.
@@Silent_Stillness yes I did lol, and i think you do! Looking forward to seeing how this develops for you
These are well thought out and good fun to watch, thank you. Question what’s the program on the phone, I don’t recognize it? Appreciate you
Hey! Thanks for your comment :) The plugin I use on my phone is Surface Builder (by 4pockets) the probable reason it might not be easily recognizable is because Surface Builder allows users to create custom MIDI control surfaces, so the control surface you see on the phone has been designed by me and I can modify it on a per-project basis. This includes buttons position, size, color attributes, transparency, margin, background image, and of course customizing the CC data sent by each button.
Surface builder is potentially a lot more powerful than the use case I've demonstrated throughout my videos so far. For instance, I could configure it so that I could switch between multiple pages of controls by tapping on tabs buttons that I could add to the control surface, and each page would have its own custom controls, dramatically expanding possibilities & flexibility. One very important key thing to be mindful of though is that if you're interested in using Surface Builder on your iPhone in a Portrait orientation, you will need to run an instance of AUM on your iPhone to host Surface Builder. In my experience, it's the most desirable configuration anyway for optimizing project saving logistics considerations, and being able to position the remote in Portrait orientation represents a major ergonomics improvement too.
I mention Surface Builder extensively in my main guide video at these times:
(the video is thoroughly structured with sections/chapters)
33:48 2.3 Surface Builder
37:17 3.1 Introduction to Controlling AUM With a Remote Control
The video can be found here:
ruclips.net/video/hU5tGoltlPk/видео.html
Cheers! :D