May 24, 2016, 12:18:46 pm
Welcome, Guest. Please login or register.
Did you miss your activation email
News: Feel free to email any encountered problem at

Arturia Forums

Recent Posts

Pages: 1 [2] 3 4 ... 10
V-Collection / VCollection 5 and NI NKS integration.
« Last post by machinesworking on Today at 10:14:26 am »
 Hi I have both VCollection 5 and  Maschine Studio. A pleasant surprise about VCollection 4 is how well it integrates with Maschine. Word is VC5 also integrates but I'm not seeing it, no new plug ins show up after a rescan of plug ins in Maschine. The only Arturia products I see in Maschines NKS browsers are the v4 stuff.

  What exactly do we have to do to get the VCollection 5 plug ins in Maschine? I don't want to delete the V4 plug ins as I have a few presets waiting for Arturia to get finished with their 4 to 5 converter.
Hi Looneytunes,

This is by design. You can assign CC64 on release or Hold.
In the bottom toolbar you have a Sustain mode parameter when set on
- legacy : sustain control HOLD
- normal : sustain control Release
Having the same problem. I wonder if this is a general problem in this business. You buy various software and hardware, and since MIDI is a general language you trust that it will work. But generally there is some glitch, because manufacturers want everyone to buy the whole kit from them only. They apply some special solution, that disqualifies competitors. And it is a pity and very frustrating for consumers. You end up in browsing for hours for hours various foras and knowledge bases for answers. Baaaaah! 
...and there's a power switch bottom right that I can't click/turn off or on.
The CS80 panel UX.
1. The text labels on parameters do not render clearly, and even in larger resized windows they are very difficult to read. They are less clear than v2. Font needs to be crisper/clearer/more legible. Needs to render clearly even when small.

2. Not much contrast between the background colour and the font colour, makes labels harder to read. Perhaps darker panel, brighter font colour?

3. The parameter value is no longer displayed next to the control you are editing, it's now at the bottom window, which forces you to jump to the bottom of screen and back. In larger resized windows you sometimes lose the bottom of the app window frame off screen, and so the value is not visible. My preference is to have the value appear near the mouse arrow (like v2). If this is no longer feasible, make the value appear at the top of the app window frame as that's always visible.

4. Not enough contrast between push button states 'up' and 'down' e.g. ribbon 'pitch', 'midi sync' buttons. Would be good to have more visual feedback the button is 'down'.

5. Same as '4' for black rocker waveform switches. Not enough visual feedback to indicate states up, down, or midway.

6. VCO,VCF and VCA parameter/slider text labels in v2 took up entire width of slider size i.e. 'HIGH' was the width of slider.   In v3, the slider labels are now way smaller in comparison i.e. 'HIGH' is slimmer than the slider.
You could make each slider label/text larger width wise considering you have about 25% more horizontal room now. Touch Response labels use a different, large sized font than the rest (Brill, Level). Perhaps all values could use this size?

Panel 'Look and Feel'. These are totally subjective..
7. Some slider knobs are not aligned in centre, while some are e.g. channel I VCF sliders for AL, A, D, S and  R. Actually, it looks like those sliders' slots in the panel are out of whack. Looks unfinished.
8. Ribbon controller texture looks like no-dimensional rubber, not like the real world velvety thing. V2's looks better.
9. I get the super authentic look (beaten up) you're going for, but i'd prefer mine to look like 'Brand New Ultra Clean CS80'. Nice to have would be a selection of panel textures maybe?
10. It looks brown. Brown is the colour of sadness, decay. That may be authentic, but it's ....ugh. I prefer the v2 dark steel blue grey charcoal...

New style Application window UX
11. No indication if modulation is being used unless you open up the multi mode hatch. Would be nice if this was indicated without needing to look under hatch i.e. on a window bar?

12. Multi mode is indicated at the bottom of the application window (unless you open multi mode hatch) but in larger resizes the bottom goes off screen, and therefore cannot be seen. Nice if this indication was at the top of the app window, always visible.

13. Any bottom window bar info (parameter value, multi mode, midi ch ) is very hard to read, not enough contrast between text and background.i.e. just not clearly visible.

Top window preset browser  UX
14.  Font is difficult to read at 100% e.g. 'a' looks like 'o', impossible at 60%. With all that new space devoted to label text areas, the text is scrunched up in the middle of the text area.

15. When a preset is selected, the right hand side shows features/meta data. There are drop down arrows left of the values, which only seem to do something when in User patch editing mode. They are visible for factory patches and template patch meta data yet they do nothing when clicked.  ideally you would not offer these drop downs if the user cannot use them e.g.grey them out or similar when not applicable.

16. When saving a patch in  'save as' and selecting the existing text to overwrite e.g. 'name' 'author' etc, the selected text disappears, meaning, when you select the text, the selection becomes a totally opaque blue blob. I have not ever seen this convention before. Would be more user friendly to highlight the selected text yet keep the text visible.

Multi Hatch - Multi mode UX
17. Circular pots are hard to see with only half the annulus width (the outside of the ring) changing colour, and not much contrast between value and background.

18. Circular pot value is displayed at the bottom of window, which may not be visible in larger resizes. Would be good if value appeared near mouse arrow, or if no longer feasible, at top (always visible) window bar.

19. The zone drop down is in French 'Affecte_Voie1'.

20. Legend font  hard to read. Values font as above for preset browser.

Multi Hatch - Modulation UX
21.Same font/text contrast and visibility as above.

New Application Window look and feel (preset browser, info bars, settings etc)
These are totally subjective..
It feels clunky, and looks like it was done without much visual or UX design input. The font sizes are inconsistent depending on the field, the highlighting is inconsistent depending on the field, and the contrast between the text and background is not friendly and is difficult to see clearly.There's wasted large spaces, then tiny little labels and values.

The dark colour scheme and low contrast makes it difficult to read.
I think there are many better fonts than this one. It is hard to read, it's too thin, and the round letters too fat and are confusable.

Sorry to go on, hope this is of help, looking forward to future revisions. I love how it sounds by the way, amazing synthesizer, one of my favourite plugins. I  have a bunch of your stuff. Eager to get CS80 as good as it can be.

cheers Jeff

How about  letting you just update the synths you want for say 10 euro each

Not sure, but I thought I had read that you could do that individually over at KVR?

Did you check what offers you may have?

When I checked my offers, updating individual synths was 150 bucks. :\
V-Collection / Re: V-Collection 4 versus V-Collection 5
« Last post by artao on Today at 05:59:13 am »
Spark 2 isn't listed in the V-Collection 5 any more. Will I loose Spark2 if I upgrade from v4 to v5?
No, you keep all the V4 instruments, including Spark2.

I'm very very curious what's up with Spark. They've been talking about updating it for quite awhile now.
Is it simply going to become its own product, no longer included in the V Collection? That would really be a shame, and IMHO a very poor decision.
I'm hoping it simply wasn't included because they're not done updating it yet ...... I also really hope they don't go charging us for the update.
V-Collection / Re: Where's the Sound Map function?
« Last post by artao on Today at 05:56:48 am »
That is exceedingly disappointing. I use that feature all the time. It's one of the most unique features of your synths.  :'(
You say, "Because of this redesign, if we wanted to keep the Sound Map, we would have had to rewrite its interface entirely. "
Well ... you already had to rewrite the interfaces for all the instruments, so I don't see how doing that with the Sound Map is any more of a hassle.

I urge you to seriously re-consider this decision, and once you fix up some of the bugs I'm reading about, get on with the business of putting the Sound Map back. :)
Presets are shared between Analog Lab 2 and the individual instruments.
You can make a Mini V single in Analog Lab 2 and then open it in the Mini V, and vice-versa.
The only presets that are exclusive to Analog Lab 2 are Multis.

Okay cool, thanks.
Just to be totally clear here:
I make a preset in, say, Mini V standalone. When I open Analog Lab 2, that preset will be there?
If so, that's excellent. It was the biggest thing that held me back from using Analog Lab for anything but browsing presets. :)
Pages: 1 [2] 3 4 ... 10
Carbonate design by Bloc
SMF 2.0.11 | SMF © 2015, Simple Machines