Your title is confusing to me... and probably others.
I read it as there's an issue with the 'native' Arpeggiator in Studio One.

What your video shows is that you're having issues with the Arp built into Omnisphere... correct?

markrobotham wroteIs anyone else having issues with the arp speed in studio one. As you can see from the video the arp is playing twice as fast. Eg: set to 1/4 plays 8ths - 8ths plays 16ths etc In order to play 1/4 I have to set it to 1/2.

phpBB [video]

Omnisphere's arp in Studio One working perfectly for me here. I'm on mac.
No issues at all. Never used it, but just tested it for you.

Played a chord for 1 bar, set studio one's tempo to 120. Tested Omnisphere triggering 1/2, 1/4, 1/8, 1/16 note pattern and all is working correctly.

Best
Scott

Thanks for checking, I haven't found any particular steps to reproduce as yet, just seems to happen randomly, although consistently once saved in a studio one song project.

Still waiting for a fix for Omnisphere reverb issue in studio one, spectrasonics are aware of that one though. very annoying when using the pro verb inside of Omnisphere.

Corrected post title.

markrobotham wroteThanks for checking, I haven't found any particular steps to reproduce as yet, just seems to happen randomly, although consistently once saved in a studio one song project.

Still waiting for a fix for Omnisphere reverb issue in studio one, spectrasonics are aware of that one though. very annoying when using the pro verb inside of Omnisphere.

Corrected post title.

I just tested it on Windows and it works for me. So what's the issue with the pro verb effect?

Thanks, pro verb issue was first reported back in December 2018 was hoping to have to have sorted by the 2.6 update but it still exists.

I did email them again and they said "We are aware of this issue and know that this is important to get resolved.
Our FX units, including Pro-Verb were developed with 3rd party companies. Because of this, it’s doubly complicated to fix."

Video here https://www.youtube.com/watch?v=hCUHLOHgdRw steps to reproduce in the description

The arp and pro-verb issues appear to fixed in the latest Omnisphere 2.6.1e update.

Another issue, this time the Mod Envelope Timing. Omnisphere 2.6.1e & Studio One 4.5 Mod Envelope Timing Issues works fine in Cakewalk by Bandlab, but not in Studio One 4.5

EDIT 23rd May 2019: It only happens when dropout protection is set to "maximum" in Studio One.

Just updated to Omni 2.6.1e and I'm getting similar issues when loading a project with Omnisphere instruments, but if I reload the patch from scratch, the issue seems to go away. The other issue I'm having is switch patches now seems to trigger a random note. If that's a new feature, I'd like to turn it off, lol.

Dan

Just curios, are you also getting broken glide settings with custom patches prior to 2.6? I say broken in the sense they don`t load how they were originally programmed, the glide seems more prominent, to the point of making the patch unusable.

I have made spectrasonics aware of this and the other issue of the mod envelope timing issue in studio one when when dropout protection is set to "maximum" However the latter could be Studio One issue.

Either way if you have issues please also report them to spectrasonics so they can get fixed

markrobotham wroteJust curios, are you also getting broken glide settings with custom patches prior to 2.6? I say broken in the sense they don`t load how they were originally programmed, the glide seems more prominent, to the point of making the patch unusable.

I haven't run into this as of yet, but I'll keep an ear out for it.

Dan

dcumpian wroteThe other issue I'm having is switch patches now seems to trigger a random note. If that's a new feature, I'd like to turn it off, lol.

I think it's a new 'Omnisphere' feature to rival Komplete. Haven't found a way to turn it off yet, and it also seems to trigger at max velocity as well...

chrismarshall2 wrote

dcumpian wroteThe other issue I'm having is switch patches now seems to trigger a random note. If that's a new feature, I'd like to turn it off, lol.

I think it's a new 'Omnisphere' feature to rival Komplete. Haven't found a way to turn it off yet, and it also seems to trigger at max velocity as well...

Here it is: https://support.spectrasonics.net/manua ... on-page05a

dcumpian wrote

markrobotham wroteJust curios, are you also getting broken glide settings with custom patches prior to 2.6? I say broken in the sense they don`t load how they were originally programmed, the glide seems more prominent, to the point of making the patch unusable.

I haven't run into this as of yet, but I'll keep an ear out for it.

Dan

On a lark, I loaded a patch with Glide enabled and, you're right, the Glide time parameter has changed. It appears that the Glide parameter is now longer than it used to be. Pulling the slider down just a bit shortens the glide back to where my ears tell me it should be.

Dan

chrismarshall2 wrote

chrismarshall2 wrote

dcumpian wroteThe other issue I'm having is switch patches now seems to trigger a random note. If that's a new feature, I'd like to turn it off, lol.

I think it's a new 'Omnisphere' feature to rival Komplete. Haven't found a way to turn it off yet, and it also seems to trigger at max velocity as well...

Here it is: https://support.spectrasonics.net/manua ... on-page05a

Thanks for this! It was driving me crazy...

Dan