I mean,... the Ringmod in the Macro section doesn't count either, does it?loachm wrote: Sat Apr 24, 2021 11:58 am...I didn't count the preset name and the routing drop-down menu, which would route each engine to the filter or to the insert fx modules would just a be a logical consequence of that feature, that's why I wrote six in brackets. But you missed onegondii wrote: Sat Apr 24, 2021 11:41 am Hm, the insert FX, the ballsy filter, FX mix option...
Edit: utility source in filter section, second seq, preset name?![]()
![]()
Arturia Pigments 3 is out!
- KVRian
- 1113 posts since 8 Oct, 2019
-
- KVRAF
- 2209 posts since 2 Jan, 2003 from right here...
...just to prevent driving you mad - yup, I missed that one - it's from the original screenshot I took from the ring my bell preset. The quick changes I made are only in the upper half, so I only concentrated on that area. The one missing is probably too obvious (as if this wouldn't drive you madgondii wrote: Sat Apr 24, 2021 12:17 pm I mean,... the Ringmod in the Macro section doesn't count either, does it?
- Banned
- 2288 posts since 24 Mar, 2015 from Toronto, Canada
just want to put this out there. what sort of SR and buffer settings are you all using with VST and Arturia on your setups? I tried Pigments with 64 buffers and it goes nuts.
Gear & Setup: Windows 10, Dual Xeon, 32GB RAM, Cubase 10.5/9.5, NI Komplete Audio 6, NI Maschine, NI Jam, NI Kontakt
- KVRian
- 1113 posts since 8 Oct, 2019
ah - wave table edit(or)?loachm wrote: Sat Apr 24, 2021 12:29 pm ...just to prevent driving you mad - yup, I missed that one - it's from the original screenshot I took from the ring my bell preset. The quick changes I made are only in the upper half, so I only concentrated on that area. The one missing is probably too obvious (as if this wouldn't drive you mad)
- KVRAF
- 37411 posts since 14 Sep, 2002 from In teh net
128/48telecode wrote: Sat Apr 24, 2021 12:41 pm just want to put this out there. what sort of SR and buffer settings are you all using with VST and Arturia on your setups? I tried Pigments with 64 buffers and it goes nuts.
-
- KVRAF
- 9145 posts since 7 Oct, 2005
I use 128 in Cubase in 64bit/44.1Khz project. Most of the presets are fine (lower cpu than Zebra and Massive X a little), which is greattelecode wrote: Sat Apr 24, 2021 12:41 pm just want to put this out there. what sort of SR and buffer settings are you all using with VST and Arturia on your setups? I tried Pigments with 64 buffers and it goes nuts.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.
-
- KVRAF
- 2209 posts since 2 Jan, 2003 from right here...
...what's really great about Pigment, is the fact, that almost every parameter seems to enabled for host automation, which means, I could create comprehensive mapping templates for the plug-in in Maschine, so that I could jam with the synth and capture interesting settings with Maschine's lock states - something I can't do with the a different modern flagship synth, as, apparently, 16 automatable macro controls are supposed to be enough.
Sonically, MX is much more interesting, has better sounding modules and its sound quality is superior, but Pigment's graphic workflow is a lot better (wow, I can save and recall multistage envelope shapes - take that NI), it provides a better hardware access (host & midi automation) and with the wavetable import and granular sampler it has the better features to use your own sounds. So I'd probably end up using MX for the basic sound design to create samples and then continue with Pigments as the work horse...
Sonically, MX is much more interesting, has better sounding modules and its sound quality is superior, but Pigment's graphic workflow is a lot better (wow, I can save and recall multistage envelope shapes - take that NI), it provides a better hardware access (host & midi automation) and with the wavetable import and granular sampler it has the better features to use your own sounds. So I'd probably end up using MX for the basic sound design to create samples and then continue with Pigments as the work horse...
-
- KVRAF
- 2514 posts since 28 Sep, 2012
^ feel substantially the same about MX vs P3.
- KVRist
- 387 posts since 4 Apr, 2021
I'm still a bit confused why a brand new synth is doing it this way.Teksonik wrote: Sat Apr 24, 2021 12:15 amThere doesn't appear to be a separate release curve but the Link function does allow for a different curve:Bartone wrote: Fri Apr 23, 2021 8:49 pm No, I mean curve just for release. So the release curve can be independently modified. This option makes release slave to decay. Or am I doing something wrong here?
Pigments 042321-3.png
From the manual:
Release Link Buttons
There are two of these buttons: one by the Decay knob and another by the Release knob.
What they do is link the Decay time and the Release time to the Decay knob, which controls
them both. The Release is greyed out to indicate that it cannot be adjusted when the two
parameters are linked.
Also, when Release Link mode is active, the Decay curve knob also adjusts the Release
curve. Otherwise the Release curve is always exponential
20 seconds not enough ?![]()
Pigments 042321-2.png
Do you know is there benefits of doing it like this (= release doesn't have own individual curve)?
- KVRAF
- 6299 posts since 12 Jan, 2018
Massive X sounds better than Pigments for the most part without any doubt, but Pigments is slowly taking the game away from Massive X. I am saying this despite being a Massive X fanboy.
Two major drawbacks with Massive X compared to Pigments are GUI and types of presets.
Not saying Massive X GUI is bad, when I say GUI I mean preset browser, GUI animations, etc. I wish the team behind Pigments 3 could make presets for Massive X. Different synth, same approach (as applicable, of course).
Two major drawbacks with Massive X compared to Pigments are GUI and types of presets.
Not saying Massive X GUI is bad, when I say GUI I mean preset browser, GUI animations, etc. I wish the team behind Pigments 3 could make presets for Massive X. Different synth, same approach (as applicable, of course).
- KVRAF
- 19823 posts since 16 Sep, 2001 from Las Vegas,USA
Not if you use the Decay Link in the filter Envelope.chk071 wrote: Sat Apr 24, 2021 9:31 am It isn't that much with an exponential release stage slope (try a longer amp envelope release, like 7 or 8 seconds, and then set up the filter envelope as well, set the release to 20 secs, and you will have that rather ugly "the filter envelope closes before the amp envelope does").
In many cases I like "the filter envelope closes before the amp envelope does". It allows you to hear the full sweep.
I can't explain why Arturia didn't just make the curve adjustable for every segment of the envelopes. One could certainly argue that it's an odd omission in a synth that's otherwise very well thought out. I guess it's one of those things we'll have to accept until or if there is an update. I don't know if Arturia has a forum for feature requests but I doubt they'll see them here.
The problem is just like in Vital, Env 1 is hardwired to VCA. I'm trying it now and I'm able to get closer to the 20 second release time using a function generator set to envelope mode on an engine or osc output level. Without it the time to zero is closer to 15 or 16 seconds.chk071 wrote: Sat Apr 24, 2021 9:31 amStill gotta try out the function modulators though. They might work, if you set them up as an envelope (as far as I understand it, they work like MSEG's then).
Still that's a long time for release. It would be stealing notes like crazy even at max polyphony and I imagine the CPU demand would be much higher.
Edit: Here's a link to the Pigments feature request thread at the Arturia forums:
https://forum.arturia.com/index.php?board=334.0
You do not have the required permissions to view the files attached to this post.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
- Banned
- 995 posts since 4 Feb, 2021
I can not confirm the CPU overloads here. Macbook Air 1,8 gz i5, 8 gb ram DDR3, Big Sur, from 2017. Runs smoothly in Reason as VSTi and does not demand more power than Repro 5 or HIVE. There is probably not enough power to run 4-5 instances with heavy presets, but I'd render such tracks as audio before it come to such a load anyway. Generally, I am impressed with my Air as far as performance concerns. I can have a big load of Reason REs running and haven't run out of power yet. Sometimes I get tempted to buy an even stronger computer, but then grab myself in it with a big "Why?"
Tribe Of Hǫfuð https://soundcloud.com/user-228690154 "First rule: From one perfect consonance to another perfect consonance one must proceed in contrary or oblique motion." Johann Joseph Fux 1725.
