KVR Audio

Cinebient · Post by **Cinebient** » Thu Mar 24, 2016 6:25 pm

With their latest easter deal i feel even more doomed to bee an early adopter of the Rise 25.......

Well, that´s life!

deastman · Post by **deastman** » Fri Mar 25, 2016 6:51 am

After further investigation, I'm convinced that my Seaboard RISE device drivers are not functioning correctly.

Watching the YouTube video they just posted on configuring the Seaboard with Bitwig, there are some discrepancies from what I've been experiencing. I cannot get Bitwig to automatically detect the Seaboard. It just won't find it, no matter what I do. I have to manually create the controller. And then I run into these mismatches that I've described with my pitch bend range. Like if I set the Equator VST to a bend range of 48, I have to lower the range in Dashboard to 24, or it won't track properly.

I've seen some occasional Windows 10 messages pop up warning that the last USB device I connected had failed, and to try reconnecting it. Looking in the Device Manager, there are two drivers listed for the Seaboad- one in Sound, video, and game controllers, which appears to have the correct driver, and another one in Software devices, which just has a generic Microsoft driver. Looking in the events list for both of these drivers, I see messages indicating the the "Device could not be migrated", whatever that means. I've tried uninstalling and reinstalling. I've tried just uninstalling the devices and deleting their drivers, and then doing a new installation. I've tried rolling back compatibility to Windows 8. I've tried running as an administrator. I've tried rebooting. I've tried using a different USB port- both USB 2 and USB 3. Nothing seems to make any difference. I did file support requests with both Roli and Bitwig today, so I guess I'll just have to wait and see what comes of it.

hyperscientist · Post by **hyperscientist** » Mon Apr 04, 2016 7:21 am

How stable Bluetooth MIDI is for you on OS X? For me it drops connection often. Sometimes I can play for 10 minutes straight without a drop and sometimes after reconnecting (which has to be done manually) it will drop connection again within few seconds or a minute and then it will be stable for a while it may be ok and after another 5-10 minutes it will drop. Every time I have to click "connect" manually in Audio MIDI Setup.

I have no problems with other Bluetooth devices (but I have no other MIDI Bluetooth devices to test) and I tried it in different rooms and apartments even - it's unstable like this all over.

How is it for you?

Cinebient · Post by **Cinebient** » Mon Apr 04, 2016 5:55 pm

hyperscientist wrote:How stable Bluetooth MIDI is for you on OS X? For me it drops connection often. Sometimes I can play for 10 minutes straight without a drop and sometimes after reconnecting (which has to be done manually) it will drop connection again within few seconds or a minute and then it will be stable for a while it may be ok and after another 5-10 minutes it will drop. Every time I have to click "connect" manually in Audio MIDI Setup.

I have no problems with other Bluetooth devices (but I have no other MIDI Bluetooth devices to test) and I tried it in different rooms and apartments even - it's unstable like this all over.

How is it for you?

Exactly like you described.

V0RT3X · Post by **V0RT3X** » Fri Apr 15, 2016 5:06 am

On OSX installation is pretty much plug'n'play and is recognized by bitwig. I had to manually add my Rise49 as a midi controller though before I could get it to work.

So far this thing is a blast, and once i get more time, i will do some more experiments.

tapper mike · Post by **tapper mike** » Fri Apr 15, 2016 4:32 pm

Just a quick not from a linnstrumentalist regarding polyphonic aftertouch and noteperchannel.

If your hosts supports different midi channel ins...
You can stack said synth on multiple channels That's how I handle poly AT and independent slides on my linnstrument.

Cinebient · Post by **Cinebient** » Sat Apr 16, 2016 9:59 am

tapper mike wrote:Just a quick not from a linnstrumentalist regarding polyphonic aftertouch and noteperchannel.

If your hosts supports different midi channel ins...
You can stack said synth on multiple channels That's how I handle poly AT and independent slides on my linnstrument.

But some plug-ins seems to listen to omni always. If every plug-in would offer a midi mono mode it would be great! So you can also play every monosynth/instrument polyphonic.... if the cpu and ram can handle it is another thing

Cinebient · Post by **Cinebient** » Sat Apr 16, 2016 3:53 pm

Now i experienced a problem with one keywave on my rise 25. The D# keywave on the right side doesn´t seems to work right. When i play and hit it exact in the middle it often plays by random D# and E at the same time or either of one. Also in piano mode where glide is turned off. So the midi triggering seems not accurate here. I hope it´s not a hardware fault. I can hit the D# keywave on the top and at the bottom without a problem but it doesn´t work in the middle. Vertikal slides for modulation also jump then often from D# to E, even with the finger exact in the middle or even more to the left. That make this note/keywave unusable.

Damn, after many months i wish i hadn´t bought the Rise 25 since it runs never without a problem or bug for longer time since i bought it. And i use it not often. Even my touchscreen on my iPhone works more accurate in this case.
Has/had anyone maybe such a problem? Or did i bought a lemon

tapper mike · Post by **tapper mike** » Sat Apr 16, 2016 4:35 pm

Cinebient wrote:
tapper mike wrote:Just a quick not from a linnstrumentalist regarding polyphonic aftertouch and noteperchannel.

If your hosts supports different midi channel ins...
You can stack said synth on multiple channels That's how I handle poly AT and independent slides on my linnstrument.
But some plug-ins seems to listen to omni always. If every plug-in would offer a midi mono mode it would be great! So you can also play every monosynth/instrument polyphonic.... if the cpu and ram can handle it is another thing

I've yet to experience that on my old vista AMD quad core using cantabile as a host. I simply assign each rack (not track)
Have you tried freezing tracks to reduce cpu load?

Vintage73 · Post by **Vintage73** » Sat Apr 16, 2016 4:40 pm

I guess I need to ask...is the RISE not quite ready for Primetime? Should I hold off until they work out some of the bugs? I'd really like to get one if they work as-advertised, but it sounds like there are a few problems with them, still.

hyperscientist · Post by **hyperscientist** » Sat Apr 16, 2016 5:26 pm

Cinebient wrote:Has/had anyone maybe such a problem? Or did i bought a lemon

Key to pitch tracking seems to work fine on mine - I think I would notice such problem. What pains me is impossibly inconsistent velocity response and bluetooth midi connection that is not reliable at all (with OS X).

What other issues were you referring to?

tapper mike · Post by **tapper mike** » Sat Apr 16, 2016 5:34 pm

Bluetooth is a terrible way to transmit midi data. It's basically a gizmo of an idea that marketers told us we needed in our lives.

hyperscientist · Post by **hyperscientist** » Sat Apr 16, 2016 5:37 pm

Blue Phase Music wrote:I guess I need to ask...is the RISE not quite ready for Primetime?

Tough call, depends on the person.

It's not perfect yet (also because of environment for example Live not supporting aftertouch or most plugins not being compatible out of the box), but it goes a long way already. Also for me the feeling of keywaves is not there yet - a bit too stiff, but I am confident that it's different for every other person and for you it may be great (many people are praising it). If you look at the demos post on YouTube by ROLI than you can clearly see it's very much capable. What those demos don't show is that it takes a significant amount of effort to play it well which may or may not kill your excitement and pleasure of playing it. I know that I was pushing it aside many times cursing that it's not worth it, but then always I would come back. You have to be this kind of a person that enjoys being no the bleeding edge of technology despite numerous drawbacks. Some are, but are you?

Cinebient · Post by **Cinebient** » Sat Apr 16, 2016 5:47 pm

hyperscientist wrote:
Cinebient wrote:Has/had anyone maybe such a problem? Or did i bought a lemon
Key to pitch tracking seems to work fine on mine - I think I would notice such problem. What pains me is impossibly inconsistent velocity response and bluetooth midi connection that is not reliable at all (with OS X).

What other issues were you referring to?

In general the software (Dashboard and Equator) was from the beginning very buggy. This seems to be better now and works good so far.
But after a while i think it's not really ready to replace a touch screen for me. The tactile feedback is nice but it doesn't work as accurate as it should in terms of triggering the right midi notes in a certain area where i touch.
The XY pad and the sliders are nice but i find them also not working accurate always.
I really love Equator but the hardware just don't cut it for me. I tryed to sell mine but even for 300 bucks less for a nearly unused device no one will buy it.
The 3D touch on my iPhone can do the same and more and works even better (beside the tactile feedback of course) than the Seaboard surface... sadly

So i think i stay with "normal" keys and flat touch screens (hope for 3D touch iPads in near future) until there comes hardware which works better for me and comes with more flexible software (dashboard).

V0RT3X · Post by **V0RT3X** » Sat Apr 16, 2016 5:59 pm

I am more than pleased with my Rise 49 so far, and even with the little niggles in it i can still see it being very useful. It does take a bit of getting used to, but so far I can't see myself parting with this anytime soon.

I imagine once more major developers provide MPE support for their synthesizers that the Rise will be more sought after.

Either way I'm happy!

Roli Seaboard RISE