Still confused by Cream
-
- KVRAF
- 1924 posts since 15 Oct, 2008 from Germany
If you have a specific question, ask away. I'm sure you'll get an answer. Did you read the manual?
-
- KVRian
- Topic Starter
- 730 posts since 13 Apr, 2002 from Terra Australis
Thanks pinki! And I would ask specific questions except that I have lots of questions and asking one or two won't get me that far. The videos just give the bare outline and the manual is, frankly, rubbish.
Seems odd that the dev is determined to make people work hard to understand the functionality. This sort of plugin needs a series of videos to explain all the functions. There are parts of this plugin that simply aren't even mentioned either in the short videos or the manual!
Seems odd that the dev is determined to make people work hard to understand the functionality. This sort of plugin needs a series of videos to explain all the functions. There are parts of this plugin that simply aren't even mentioned either in the short videos or the manual!
-
- KVRer
- 16 posts since 16 Jul, 2008
It would be very useful for the developer to post some Video tutorials to show some of the concepts not explained at all in the manual. Still loving this plug 
-
- KVRist
- 126 posts since 4 Feb, 2013
In fact, Cream is extremely complex under the hood. And it's also not that easy to explain the basics without beeing boring :/
On the other hand I gave a look into a track of mine (Upperclass) where Cream was heavily used on the bass track. It seems confusing, and it took some time to reach that - but for me it was fun to play around
I'm not sure how to help you out now :/
The main idea is an arpeggiator with kinda step sequencer to control midi relevant actions like step-based gate, transpose etc. and the possibility to place parts out of the (input) chord wherever you want on the SEQ tab.
All in 12 different patterns (per track). You also have a chordmemory functionality, which is pretty flexible, because you can use more than one chordmem presets on a pattern, in fact, one preset per step if you need it
To make it more flexible, there are loops/loop points for every action, if you need it.
However, at the end it's just an arpeggiator - but a good and complex one
On the other hand I gave a look into a track of mine (Upperclass) where Cream was heavily used on the bass track. It seems confusing, and it took some time to reach that - but for me it was fun to play around
I'm not sure how to help you out now :/
The main idea is an arpeggiator with kinda step sequencer to control midi relevant actions like step-based gate, transpose etc. and the possibility to place parts out of the (input) chord wherever you want on the SEQ tab.
All in 12 different patterns (per track). You also have a chordmemory functionality, which is pretty flexible, because you can use more than one chordmem presets on a pattern, in fact, one preset per step if you need it
To make it more flexible, there are loops/loop points for every action, if you need it.
However, at the end it's just an arpeggiator - but a good and complex one