KVR Audio

recursive one · Post by **recursive one** » Thu Dec 29, 2016 7:36 am

Let’s say I have made a two bar clip at an instrument track EDIT: assinged to Spire VSTi, programmed some notes in it, then I copy this clip to next two bars on the same track (using either CtrlC or CtrlV or D) and change some notes in the new instance of my clip (the first one stays unchanged). Then I save the project and reopen it, and whoa! – the notes in the second clip are EXACTLY THE SAME as in the first one, despite I’ve changed them. This started to happen few days ago with no apparent cause and it always takes place both in old projects and new (blank) ones. If I merge the clips before saving, it re-opens normal.

EDIT: All other VSTis I've tested so far behave normal.

What can it be? Did I occasionally messed up something in global settings (no idea how and what EDIT: highly unlikely, as the problem happens only with Spire)?

Win 7, Studio One 2.6. 64 bit.

EDIT: was solved by upgrading to S1 v.3 Professional - I should have done this at some point anyway

Musical Gym · Post by **Musical Gym** » Thu Dec 29, 2016 8:08 am

If you click on the second instance of the clip and rename it, do you still have the problem?

Are you using shift-D (shared duplicate) or ctrl-drag by chance?

recursive one · Post by **recursive one** » Thu Dec 29, 2016 8:42 am

Musical Gym wrote:If you click on the second instance of the clip and rename it, do you still have the problem?

Didn't try this but I usually never renamed my clips before but everything was saved and re-opened normal.

Musical Gym wrote: Are you using shift-D (shared duplicate) or ctrl-drag by chance?

It was my thought too that I'm somehow making shared copies but wouldn't in such case the original clip be immediately changed too as I change the copy? It isn't.

Actually I'm using either Ctrl+C/Ctrl+V or D keycommands or copy/paste or duplicate from dropdown menu (and this happens in either of the above scenarios), don't touch the Shift button.

Musical Gym · Post by **Musical Gym** » Thu Dec 29, 2016 9:39 am

I don't rename midi clips ordinarily; I thought that might ensure it would be unique. Haven't really gotten into shared copies either, so am only guessing.
Maybe you can post at Presonus forum if you haven't yet or submit a ticket. Maybe it was a bug in your version of S1.
You could download S1 Prime free version and test that if you want.

recursive one · Post by **recursive one** » Thu Dec 29, 2016 9:58 am

Musical Gym wrote: Maybe you can post at Presonus forum if you haven't yet or submit a ticket.

I submitted a ticket already but I don't know how quick they are. This is the first major issue I ever had with S1 (after using it daily as my only DAW for almost 4 years).

Musical Gym · Post by **Musical Gym** » Thu Dec 29, 2016 10:01 am

Did you try in more than one song? Maybe there's something going on with the song? Far-fetched sounding, I know, but if it doesn't happen in other songs maybe you can isolate it to that one. Save as New Version?

recursive one · Post by **recursive one** » Thu Dec 29, 2016 10:08 am

Musical Gym wrote:Did you try in more than one song? Maybe there's something going on with the song? Far-fetched sounding, I know, but if it doesn't happen in other songs maybe you can isolate it to that one. Save as New Version?

I noticed it when working on a project, tried to save a new version, same thing. In this specific project I had already copied and modified some clips which were normally saved and reopened, it started to happen when I added some new synths.

Then I made a blank project, added a VSTi, repeated the above steps, saved it in a new folder, got the same results after opening it again

I believe there may be something stupid I've occasionally made but no idea what

Musical Gym · Post by **Musical Gym** » Thu Dec 29, 2016 10:22 am

I'd peruse the Presonus forums and maybe ask there.

recursive one · Post by **recursive one** » Thu Dec 29, 2016 10:45 am

Yeah, will do this if the support doesn't respond.
Thanks for your suggestions!

Musical Gym · Post by **Musical Gym** » Thu Dec 29, 2016 9:00 pm

Wish I had the answer. Post back when you find out the solution.

recursive one · Post by **recursive one** » Fri Dec 30, 2016 7:23 am

Narrowed this down to Spire, all the other synths I tried (Sylenth, Rapid, Virus TI plugin) behave normal, no matter if there is also Spire in the project or not. Spire has been my to-go softsynth for several years and for the first time ever it does me dirt

Well, at least it is a bug and not me having messed up the settings. Will report it to Reveal Sound too.

Musical Gym · Post by **Musical Gym** » Fri Dec 30, 2016 7:37 am

Interesting but weird, especially since it didn't give you trouble before.
If Studio One is causing Spire to misbehave, I'd try in S1 3 Prime just to see if the problem still exists.
Might be the problem was handled in an S1 update/upgrade.

recursive one · Post by **recursive one** » Fri Dec 30, 2016 8:07 am

It seems that S1 prime doesn't load VSTi

I have various reasons not to upgrade to S 1 v.3 (one of them is that I have S1 Producer, so the only option is upgrading to Professional which is not especially cheap). As for S1 v.2.6 I think I have the latest available version, Spire is also from the latest installer (reinstalled both yesterday, nothing changed).

recursive one · Post by **recursive one** » Fri Dec 30, 2016 8:07 am

Musical Gym · Post by **Musical Gym** » Fri Dec 30, 2016 8:46 am

Maybe try in S1 3 demo version unless that's the same as Prime.
As for Spire clips not saving midi, maybe add those parts with another vst, add Spire last into the placeholder track(s) after you duplicate those tracks, and render Spire to audio.
You should be able to get the midi back either from the combined audio/midi clip, the initial placeholder track, or with Melodyne.

Weird MIDI copying bug in Studio One (Spire related - Solved)