Thats because it's not there anymore. You can use the SEQ section to produce chords.ezelkow1 wrote:Im still not seeing 'Chrd' as an option in the Order section
-Arto
Thats because it's not there anymore. You can use the SEQ section to produce chords.ezelkow1 wrote:Im still not seeing 'Chrd' as an option in the Order section
Ok, just wanted to bring it up since its still in the manualKirnu wrote:Thats because it's not there anymore. You can use the SEQ section to produce chords.ezelkow1 wrote:Im still not seeing 'Chrd' as an option in the Order section
-Arto
i think i like it the other way? anyway, what i want is to produce the input chord at any point in the arpeggiation note order.Kirnu wrote:Thats because it's not there anymore. You can use the SEQ section to produce chords.ezelkow1 wrote:Im still not seeing 'Chrd' as an option in the Order section
-Arto
Yes that's correct.nexussynth wrote:wait..i think i get it now..SEQ has boxes for selecting how many notes of the chord will be sounded at each step?
Thanks man. It's very nice to hear you like Cream because at this point the only feedback we get is bug reports and feature requestsnexussynth wrote:i am very much enjoying this plugin. so far it is the best arpeggiator yet..and i have them all.
this version is also more stable in energyXT 1.41 than the previous.
Which Cream version are you using? I hope prerelease version 1 because it had problems with access rights to data folder.giftculture wrote:Cream or Cream64 both crash ableton 9 beta 64-bit or 32-bit, live 8.2.4, and reaper when I scan the VST plugins
I went into the VST folder in MacHD/Library/Audio/Plugins and I created a "disabled VST" folder and moved all of the VST plugins except for Cream and Cream64 into it. This should have disabled all VST plugins except for those two. Ableton 9 beta and Ableton 8.2.4 still crash upon scanning it. I downloaded Reaper, and it crashed as well upon scanning the plug - so something is definitely hoarqued up somewhere... The fact that two different DAWs crash when loading it seems to point to a more fundamental problem somewhere...
I'm running 10.8.2
I would be happy to provide a stack trace or run an instrumented version of the plugin if it would be helpful to the developers to track down what might be going wrong.
Well, then I'd say it's a local problem. First, Live9 is still closed beta and we can't provide support for that, BUT we're in contact with Ableton so we'll have a look into v9 next week (I hope).giftculture wrote:Cream or Cream64 both crash ableton 9 beta 64-bit or 32-bit, live 8.2.4, and reaper when I scan the VST plugins
(...) Ableton 8.2.4 still crash upon scanning it. I downloaded Reaper, and it crashed as well upon scanning the plug - so something is definitely hoarqued up somewhere... (...)
I registered yesterday or the day before and downloaded the version that was linked in my registration email. However, it appears according to the info window to be version 1.0.0. Is it possible that my registration email had a stale link?Kirnu wrote:Which Cream version are you using? I hope prerelease version 1 because it had problems with access rights to data folder.giftculture wrote:Cream or Cream64 both crash ableton 9 beta 64-bit or 32-bit, live 8.2.4, and reaper when I scan the VST plugins
I went into the VST folder in MacHD/Library/Audio/Plugins and I created a "disabled VST" folder and moved all of the VST plugins except for Cream and Cream64 into it. This should have disabled all VST plugins except for those two. Ableton 9 beta and Ableton 8.2.4 still crash upon scanning it. I downloaded Reaper, and it crashed as well upon scanning the plug - so something is definitely hoarqued up somewhere... The fact that two different DAWs crash when loading it seems to point to a more fundamental problem somewhere...
I'm running 10.8.2
I would be happy to provide a stack trace or run an instrumented version of the plugin if it would be helpful to the developers to track down what might be going wrong.
If you are using version 2 please send the crash log to us and we'll investigate the problem.
-Arto
I understand about not supporting Live 9 - I'm also having issues in Live 8 and Reaper.PepeLopez wrote:Well, then I'd say it's a local problem. First, Live9 is still closed beta and we can't provide support for that, BUT we're in contact with Ableton so we'll have a look into v9 next week (I hope).giftculture wrote:Cream or Cream64 both crash ableton 9 beta 64-bit or 32-bit, live 8.2.4, and reaper when I scan the VST plugins
(...) Ableton 8.2.4 still crash upon scanning it. I downloaded Reaper, and it crashed as well upon scanning the plug - so something is definitely hoarqued up somewhere... (...)
Arto and me are using Reaper as first choice daw when testing, so I can assure Cream has no general problem while scanning vst folder or using Cream. You can also see that all Cream related videos are made with Reaper, either on WIn or OSX. However, we're using 10.7.5 and I have no problems. Maybe it's a 10.8 related problems... does anyone else has problems with Cream on OSX 10.8.x and Live/Reaper?
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement