KVR Audio

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

I have a workaround to merge all clips into one before saving, then it opens normal.

Or I'll also try freezing the Spire tracks before saving.

I guess, it's just my Virus being jealous and wanting me to switch back to it, so it does some voodoo

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

I think I can also try this out in Reaper Evaluation.

Are there any other DAW demos allowing saving and opening projects?

woggle · Post by **woggle** » Fri Dec 30, 2016 9:47 am

recursive one wrote:I think I can also try this out in Reaper Evaluation.

Are there any other DAW demos allowing saving and opening projects?

Samplitude I think.

Musical Gym · Post by **Musical Gym** » Fri Dec 30, 2016 9:58 am

FL Studio up to a point...
maybe search for top ten DAWs, visit their sites, and check out demo limitations
also free DAWs

recursive one · Post by **recursive one** » Fri Dec 30, 2016 10:06 am

Musical Gym wrote:FL Studio up to a point...

I think the demo can save projects but doesn't open them.

Will try Reaper and Samplitutde, I think this will be enough to indentify is the problem is DAW specific or related to Spire in general.

recursive one · Post by **recursive one** » Fri Dec 30, 2016 2:08 pm

Maybe full deinstalling S1 and Spire with manual register edit and fresh installation may help?

A bit afraid to do this though as I may lose some settings/presets/whatever.

Musical Gym · Post by **Musical Gym** » Fri Dec 30, 2016 9:21 pm

Maybe reinstall Spire only. I wouldn't reinstall S1 until/unless you fully research what gets changed.

Drogers · Post by **Drogers** » Wed Jan 04, 2017 8:11 pm

I had something similar. Try inserting a new Instrument track. Then set the MIDI channel to a different channel than your first instance of Spire. Now copy your MIDI sequence to the new track and edit. If this does not work, save the MIDI sequence as a file using export, then drag and drop it on the second channel.

recursive one · Post by **recursive one** » Wed Jan 04, 2017 11:32 pm

Drogers wrote:I had something similar. Try inserting a new Instrument track. Then set the MIDI channel to a different channel than your first instance of Spire. Now copy your MIDI sequence to the new track and edit. If this does not work, save the MIDI sequence as a file using export, then drag and drop it on the second channel.

Thanks for your input! Was it ever solved at your end and did it happen to Spire or some other plugins?

I discovered that if I freeze the Spire instrument tracks before saving and then unfreeze them after opening the project again, everything saves normal, so I use this as a workaround. Much better than nothing, at least I can continue working on my projects.

Also I found out that it there are no similar problems in Reaper, but when I use my notebook to open the S1 projects created on my main DAW computer the same thing happens.

Presonus suggested me to reinstall S1 having removed the settings files beforehand but it didn't help.

recursive one · Post by **recursive one** » Thu Feb 09, 2017 8:14 am

The problem was solved by upgrading my Studio One to v.3 professional.

For the record, Reveal Sound genuinely tried to help but weren't able to recreate the bug.

Musical Gym · Post by **Musical Gym** » Thu Feb 09, 2017 9:14 am

excellent

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