blueveek
Comments
-
Well, it's the only one with such a jarring square format for displaying AUs. But if you resize windows in AUM for example, you'd get similar issues. But AUM doesn't use this square format as the default. Neither does Cubasis, BM3, Garageband or any other DAW.
-
Definitely a very small annoyance very low on the priority list :)
-
How about double tapping on a project's name to edit it? Much better :)
-
Save as doesn't delete the untitled project though. Any chance this could be added as an option?
-
That's great if you know beforehand that "obsidian programming" is what you're going to do. Generally other DAWs don't ask me to figure out a name before starting a track. I don't know what the proper solution is here, "untitled" isn't it IMHO.
-
I think this is a bug: pitch automation not working for Slate: https://www.youtube.com/watch?v=YP0omsPZjbY This is orthogonal to actually wanting to automate pitch for single pads, which doesn't seem possible regardless of whether or not this bug was fixed.
-
Here's a demo of it not working: https://youtu.be/YP0omsPZjbY Also, it seems that if it did work, it'd affect all pads. That's the complete opposite of what this is about.
-
+1 for this from me as well, NS2's approach of treating sampling and synthesising as different things is much better from an UX point of view.
-
Screen keyboards are useful for tweaking effect parameters while messing around live, before recording anything. It's the same reason why you'd want a keyboard while tweaking synth parameters.
-
Sometimes it's difficult to exactly define what a bug is :) Unexpected (or especially unintended) behaviour can be considered a bug in software development.
-
How about when I don't want to bake the effect into a sample? Suppose I want to automate that effect. Suppose that effect only exists as an AUfx?
-
Excellent!
-
Tangential before submitting a feature request: is there a way to link pads together? Suppose I want to tap a pad and have another one activate as well. (don't tell me to use layers, that's a different thing that solves a different problem)
-
What is the "logic and concept of slate"? Is this documented anywhere, or is it an opinion?
-
I've found this, but not entirely sure it's a bug, just unexpected behaviour since no other DAW does it: https://www.blipinteractive.co.uk/community/index.php?p=/discussion/77/aufx-are-affected-by-previous-aufx-that-emit-midi-in-the-chain#latest Of course, there's the issue of scaling AUfx (only effects, instruments scale…
-
Warp markers would be huge for me. It's something I always miss from desktop DAWs or Auria.
-
Yeah, I find the whole 4x FX bus + 1x output inserts + 1x Send FX needlessly complicated and confusing. I think it's all in the name of DSP efficiency, but at a great expense to simplicity and interop with external plugins. It'd be much simpler if each pad just had its effects chain, which allowed for the built-in effects…
-
Couldn't get that to actually do anything.
-
Automation, select all and changing velocities on many notes already exist in BM3 as well, so I'm not sure what you're referring to there exactly. Personally never got any crackling with AUs, but that's subjective. For me the biggest thing that I like is the piano roll. It's pretty freaking phenomenal.
-
I don't think there is one single AU which was designed for a square format on iOS. I don't think it's the AU developers's fault for not anticipating a new DAW with a new square format. Making AUs scale to any possible size requires time and money.
-
I think the point was that if the lane disappeared, adding back automation back later isn't instantaneous. Regardless of whether or not this workflow makes sense to us, the most common workflow shouldn't suffer because of these edge cases.
-
I really don't think switching to a different synth is something that most people care for. Lots of people buy NS2 as a DAW to use, not as a synth to use.
-
In my opinion, the best thing to do in this situation is just say 'use this space', but where the dimensions aren't surprising to any AU. AUM and Cubasis do this, on all iPad resolutions, and it works like a charm. It's precisely 1024x335 (after pixel ratio multiplication). NS2 does this for the AU instruments already. It…
-
BM3, just for sidechaining (you don't hear the source, you hear the ducking on the destination, which can then also be disabled). Alas, different expectations, so everyone is right in this thread :)
-
Use the standard size by default. Fill up the wasted space with knobs (macros maybe, for automation!), and a keyboard. Allow going full screen as opt-in.
-
What about AUs that legitimately have lots of params? Like modular synths. What about AUfx that can end up having hundreds of params as well? Like equalisers. This isn't a problem with the AUs. This is a problem with NS2's approach.
-
This "nightmare" can be looked at from the other perspective as well. See, we can both play this game :) "Do you think it would be intuitive UI/UX to be forced to go to outside of the plugin to a different view, pick a macro knob there, press some learn button hidden in some menu, go back to the plugin, turn the knob you…
-
I disagree. The problem is insisting on creating a layer of abstraction over AU params, in the name of uncluttering UI. This is a logical fallacy: presenting a solution to a problem created by the solution itself. In other words, this isn’t the only way of reducing clutter. Macros also are useful on their own, and that’s a…
-
Why have an extra layer of indirection with macros at all? You could add this ‘learn’ functionality for creating automation lanes instead of creating macros.
-
Out of curiosity, what are the features present in NS2 that you missed in BM3? (of course apart from Obsidian).