Pattern Event Vs. Per Note Automation-
Which is more Advanced and useful??
Pattern Event Vs. Per Note AutomationModerators: Christophe, Mark
16 posts
• Page 1 of 2 • 1, 2
Pattern Event Vs. Per Note AutomationYou do not have the required permissions to view the files attached to this post.
Re: Pattern Event Vs. Per Note Automation
What do YOU think? Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: Pattern Event Vs. Per Note Automationafaik, pattern automation per note is only for VST3 ?
Yamaha CS-30, Roland SH-1, Roland MKS70, Focusrite Scarlett 18i6, Yamaha FS1R, Oberheim Matrix 1000, Novation Remote 37SL, Korg Legacy, Alesis M1Active 520, Novation Launchpad Pro, Push2, Intel i7-7700HQ
Re: Pattern Event Vs. Per Note AutomationI can't see a lot of use for per-note automation and where you might need it there are simple ways to achieve the same result by other means. e.g. Multiple instances of an instrument and/or MIDI Machine with note ranges.
Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Pattern Event Vs. Per Note AutomationI could see automating for example the filter cutoff during a long note but for 16th notes? What would you automate in them? (serious question).
Re: Pattern Event Vs. Per Note AutomationIf you look at the example in the image, those splines could be pan automation, which might be kind of cool on pad sounds.
Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Pattern Event Vs. Per Note AutomationOh yes like I said for long notes automating Cutoff, Pan, etc makes sense but what would/could you automate on a 16th or 32nd note ( at a reasonably high BPM)? I'm not against per note automation and I believe that's one of Bitwig's main selling points but I'm not sure how much use it would get here. But hey bring it on if that's what people want........
Actually thinking out loud....looking at the example above you couldn't have per note panning in a chord unless the plugin supported it right?
Re: Pattern Event Vs. Per Note Automation
I thought along the similar lines the first time I read this thread. I don't know what new the VST3 standard brings, but seeing how things are in Orion, seems there's a tight relation between the UI controls and events as it is, so "per note" would seem rather impossible, unless you sever the said relation. Imagine you have a knob for Pan on the synth, and you do "per note" automation"... how will that knob behave exactly after that? Also, I think it would be too much of a drag if that would require to copy-paste the automation to all of the notes just to do what you already can right now. Apart from Velocity and the slide-type of automations, maybe even panning if it's made like velocities, everything else seems like it will just introduce a whole set of other problems. As for which one is more advanced, well "per note" definitely would have its unique uses, but current events just beats it to pulp with ease of use. SoundCloud ::: Facebook
Re: Pattern Event Vs. Per Note Automation
That's true, I didn't think that far through the issue. When you do think about it, there is probably very little that you could use it for at all. Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Pattern Event Vs. Per Note Automation
That's just what I was thinking. For example how would the cutoff of a single filter react to per note automation? You'd have to have a filter per voice for each note of polyphony. Could you even do that in DUNE? Assign each voice to a separate filter but then how to separate modulation? I suppose per note velocity would work and per note aftertouch if the plugin responds to poly aftertouch........
Re: Pattern Event Vs. Per Note Automation
I don't think it would get much if any use here. Unless for velocity or AT. But we can already do that.......(velocity at least)
Re: Pattern Event Vs. Per Note AutomationYeah, velocity and polyphonic aftertouch would be the only way to do this. The amount of MIDI data generated from the polyAT would be horrendous though!
You can do per note modulation in DUNE using note as source, but you can only do simple linear stuff with this, e.g., pan low MIDI note numbers so that they are to the left or have low cutoff frequencies and have high MIDI notes panned right or with high cutoffs, or the other way around if you use negative amounts.
Re: Pattern Event Vs. Per Note Automation
thats exactly what VST3 does Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: Pattern Event Vs. Per Note AutomationVST3 might support it but that doesn't mean it will suddenly start working for everything. Think about how SE handles data and there is just no way that this could work unless you made a synth with a signal path per note, which would be a huge clusterfuck.
Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Pattern Event Vs. Per Note Automation
Of course not, you have to code it to make it compliant. I was just pointing out that the new VST3 does exactly what the OP is talking about. Currently only cubase supports it. Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
16 posts
• Page 1 of 2 • 1, 2
Who is onlineUsers browsing this forum: No registered users and 393 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |