|
Newbie
Total Posts: 5
Joined 2009-12-31
|
I'm not sure how long Roland have known about the problem, I can only base on my experience. I live in the US and when I tried to report the problem last year the support people did not even know there was a problem, they just kept quoting "it works with Sonar"
It was not until I saw this forum in the UK (towards end of last year) that it seemed to be acknowledged as a problem. John appeared to do a great job of articulating and passing the problem back through the channels but unfortunately it looks like that went to a black hole :-(
I really like the Roland sounds and if I just needed a sound module connected to my keyboard for live gigs then it would be perfect. However, for me, it is vital that my equipment works in my studio with my DAW (as it was advertised to). Unfortunately this is a *major* and the workflow to make it work are unacceptable.
On the positive, for anyone else in this situation, there is relief. I recently received my copy of Halion Sonic and this is an amazing software sound module that provides a great sound set and (very importantly) works with my DAW.
The sound set is very much like a motif and whilst I have a slight preference of Roland sounds, Halion Sonic has the edge, mostly because it works inside Cubase, but also because it has amazing sounds from a *software* module!
As I said, I really do love the Roland sounds but at the end of the day, if it does not work with my DAW then it's not much use :-(
So it looks like ebay will soon have another item on sale...
Finally, I really don't know if Roland actually pay much heed to these forums (their customers) but ignoring these kind of issues (because it means making things work with competitors) actually does far more harm in the long run than hoping everyone will convert completely to Roland gear. The reality is you can't pretend other DAWs, equipment, software, etc. does not exist.
|