KVR Audio

noiseboyuk · Post by **noiseboyuk** » Fri Aug 31, 2018 8:29 am

andrew71 wrote:I'm also sitting on an upgrade to 9.5, hoping to delay activating it long enough so that I can take advantage of a potential grace period for Cubase 10 updates.

I'm in exactly the same boat! Hoping mine can hold it together for long enough...

Echoes in the Attic · Post by **Echoes in the Attic** » Fri Aug 31, 2018 1:31 pm

So is the idea with the shared signal path that it doesn’t matter which layer you are on, it’s filters and other shared controls act as one? So if you put the filter to max while on the layer a screen, then switch to b, the filter will be where you left it on a? Hopefully, otherwise it would be weird.

The shared shared signal path is great though, it actually handles one of my biggest complaints of Omnisphere prior to this version which is that you could not route the two layers through one filter.

And even though the granular is just a visual thing, I’ll be much more inclined to use it as it’s helpful to see where you are moving the playback position relative to transients and swells etc. I can’t believe bitwig is releasing their fixed midi channel stuff and the inproved sampler at the same time as Omnisphere is getting its update. Both while I don’t have my set up going.

As for a remaining wish for Omnisphere, I do believe now more than ever that they need a trilian like macro page for their new hardware profiles. Doesn’t have to look just like then hardware but a similar layout wth generic controls and background. It would be so much more useful for lots of people who don’t have the hardware as you would get the more immediate single screen layout like the hardware.

Oh one other wish would be a link feature for the parts just like it works for layers. It could be a main menu item. This would be useful if you copied the same patch across all parts and wanted your edits on one part to happen to all parts.

noiseboyuk · Post by **noiseboyuk** » Fri Aug 31, 2018 1:42 pm

Shared path - it does work as you say, except visually it doesn't keep up. Tweak the cutoff in A, it affects B-D. Switch to B and it looks like it hasn't been changed, but touch cutoff and the sound jumps from where it really was to where you've just turned the knob. So that's not ideal.

The macro controls would be great a la Trilian. They could either just offer a selection of the more unique controls, or spread it across a few tabs.

Kinh · Post by **Kinh** » Fri Aug 31, 2018 2:06 pm

F#ck!

iPlogger · Post by **iPlogger** » Fri Aug 31, 2018 3:48 pm

noiseboyuk wrote:
padillac wrote:Is there a way to easily see what those CC / NRPN messages are so we can start mapping our generic controllers?)
I think the only way really is to look up the midi implementation tables for the synths.

Exactly what Noiseboyuk mentioned. When I've done MIDI controller work in the past, I looked for manuals which have contained the keyboard's MIDI implementation.

The other day I was twisting random knobs on my controller, and they happened to map perfectly to some of the controls in Omnisphere. It was definitely nice to see the GUI immediately switch to the appropriate page.

Jeezo · Post by **Jeezo** » Fri Aug 31, 2018 3:52 pm

andrew71 wrote:Is anyone seeing long times for the user interface to reflect patch changes in Cubase? I'm finding that it is taking ten or more seconds when changing between patches for the new patch name and settings to be displayed. The patch is playable very quickly, but the GUI is very slow to show the new details. I took part in the beta and didn't notice this problem.

In the standalone application, the GUI updates immediately. This only seems to affect me inside Cubase, version 9.0.40.

exactly the same here with studio one 4 , it's runnng o on 3.5 and sonar platnum , something wrong with the graphcal engine versus asio engine priority or some lie that , even S1 meterng ect freeze durng this

don't mess you're cubase install , it's omnpshere

dreamkeeper · Post by **dreamkeeper** » Fri Aug 31, 2018 5:30 pm

Anyone else seeing high-ish CPU usage with the granular display?

Just load sample source and go to grain tab. In stand-alone I'm looking at ~15% - just sitting there, doing nothing. As plug-in, it's not as bad, but still around 4-5%. Adjusting any grain parameters doesn't change anything. Goes down again when leaving the grain tab.

XEON E3-1231v3, 3.4 Ghz - Win7 64bit - all readings from task manager

Funkybot's Evil Twin · Fri Aug 31, 2018 6:21 pm

iPlogger wrote:It was definitely nice to see the GUI immediately switch to the appropriate page.

Speaking of this feature, is there any way to shut it off? I don't recall this happening in the beta but I found it very annoying yesterday. Just because I'm twisting the oscillators waveform knob doesn't mean I actually need or even want to go to the oscillator magnify page.

andrew71 · Post by **andrew71** » Fri Aug 31, 2018 6:22 pm

Jeezo wrote:
andrew71 wrote:Is anyone seeing long times for the user interface to reflect patch changes in Cubase? I'm finding that it is taking ten or more seconds when changing between patches for the new patch name and settings to be displayed. The patch is playable very quickly, but the GUI is very slow to show the new details. I took part in the beta and didn't notice this problem.

In the standalone application, the GUI updates immediately. This only seems to affect me inside Cubase, version 9.0.40.
exactly the same here with studio one 4 , it's runnng o on 3.5 and sonar platnum , something wrong with the graphcal engine versus asio engine priority or some lie that , even S1 meterng ect freeze durng this

don't mess you're cubase install , it's omnpshere

Sorry to hear that you are having problems too. After checking my laptop with Cubase 9.0.40, where everything ran as normal, I appear to have got to the bottom of my problem.

A while ago Cubase was freezing for me quite regularly, the user interface became completely unresponsive but audio would continue playing. The only way out of this problem was to kill the Cubase process and restart. The recommendation that I found was to set Cubase to run in compatibility mode with Windows 8 or earlier, which I did and the problem seemed to happen much less after that.

I just removed the compatibility option from Cubase and Omnisphere 2.5's performance is back to normal. Time will tell whether my Cubase freezing issue will return...

zvenx · Post by **zvenx** » Fri Aug 31, 2018 6:26 pm

Thanks for sharing the update.
rsp

Echoes in the Attic · Post by **Echoes in the Attic** » Fri Aug 31, 2018 7:07 pm

noiseboyuk wrote:Shared path - it does work as you say, except visually it doesn't keep up. Tweak the cutoff in A, it affects B-D. Switch to B and it looks like it hasn't been changed, but touch cutoff and the sound jumps from where it really was to where you've just turned the knob. So that's not ideal.

This seems like a huge oversight. So making small adjustments means you constantly have to go back to the same layer to adjust the shared settings. Really surprised by this. Definitely worth reporting.

iPlogger · Post by **iPlogger** » Fri Aug 31, 2018 7:52 pm

Funkybot's Evil Twin wrote:
iPlogger wrote:It was definitely nice to see the GUI immediately switch to the appropriate page.
Speaking of this feature, is there any way to shut it off? I don't recall this happening in the beta but I found it very annoying yesterday.

I don't recall it being in the beta either. I think it was a surprise announcement for the official release. I don't know if you can turn off the feature.

zvenx · Post by **zvenx** » Fri Aug 31, 2018 8:01 pm

There is a link something or other in the hw menu. I don't have a hardware to test but maybe that?

@echoes, I thought it was filters in series, which would affect the sound but not the parameters of the next filter in the chain. I assume u tested that.

Rsp

Echoes in the Attic · Post by **Echoes in the Attic** » Fri Aug 31, 2018 8:04 pm

zvenx wrote:There is a link something or other in the hw menu. I don't have a hardware to test but maybe that?

@echoes, I thought it was filters in serious, which would affect the sound but not the parameters of the next filter in the chain. I assume u tested that.

Rsp

As mentioned above it isn’t separate filters in series. It makes there be only one filter and other shared elements. Having different visual knob positions for what is the same filter doesnt make sense though.

dreamkeeper · Post by **dreamkeeper** » Fri Aug 31, 2018 8:22 pm

zvenx wrote:@echoes, I thought it was filters in serious, which would affect the sound but not the parameters of the next filter in the chain. I assume u tested that.
That is, say in A I have a lowpass and I filter off everything above 12khz, if B also has a lowpass, it anychanges I make with its cutoff above 12khz would have as much effect audible unless I move it below 12khz.
Rsp

As far as I can tell, there is no filter chain in shared mode - just one (dual-)filter. Adjusting parameters on any layer page only ever affects the same (shared) filter. They should really prevent switching to the filter pages of the layers B to D - at least make sure that the other layers' displays update properly.

edit: yeah - echoes beat me...

Omnisphere 2.5 Released