Cannot save a play level preset on my receptor trio
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
Dear friends.
I don't know what is wrong here as I did it before and it worked.
Here are the steps I'm taking.
1, load the empty preset, open Omnisphere and choose a single patch.
2, close the Omnisphere window and go back to the presets level, click save as (using the GUI).
3, after I did this, the mouse freezes. I can move it anywhere but cannot click on anything, nore can I rename the preset with the keyboard or go any further whatsoever.
I did this a few times shutting down the receptor in between, same result.
Did I miss something?
Is there anything to check on the receptor itself?
Thanks for your help,
cheers,
JP are
I don't know what is wrong here as I did it before and it worked.
Here are the steps I'm taking.
1, load the empty preset, open Omnisphere and choose a single patch.
2, close the Omnisphere window and go back to the presets level, click save as (using the GUI).
3, after I did this, the mouse freezes. I can move it anywhere but cannot click on anything, nore can I rename the preset with the keyboard or go any further whatsoever.
I did this a few times shutting down the receptor in between, same result.
Did I miss something?
Is there anything to check on the receptor itself?
Thanks for your help,
cheers,
JP are
-
nathankingcole nathankingcole https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=107457
- KVRist
- 224 posts since 15 May, 2006
Did the omnisphere patch automatically load on restart? If so, try loading a blank patch then open omnisphere and attempt the preset save. I do not have omnisphere, but I am having similar issues with BFD Eco right now (which I just installed from the fxpansion windows installer). Maybe someone who uses omnisphere regularly could chime in. Is it an ompnisphere issue or receptor issue? Same question for BFD Eco if any of you have experience with it.
-
- KVRist
- Topic Starter
- 135 posts since 2 Mar, 2016 from Paris France
Dear Nathan, thank you for your reply.
[quote="nathankingcole"]Did the omnisphere patch automatically load on restart?
JP:
Oh, yes it did. I never thought it could be a plug-in issue, but as I said before, I already saved an Omnisphere patch on the receptor's play level successfully. I have no idea what goes wrong this time.
Unless I am missing one step in the procedure.
After opening Omnisphere, I'm speaking of the plug-in itself, and selecting the desired patch, is there something else to do on the receptor's synth level before going to the preset level?
The receptor's manual doesn't say much about resetting the unit, of course I wouldn't like to lose my data, but is there some kind of reset that would not araise everything? I saw something about "resetting the plug-in cash", but I don't know what it means.
Best,
JPR
[quote="nathankingcole"]Did the omnisphere patch automatically load on restart?
JP:
Oh, yes it did. I never thought it could be a plug-in issue, but as I said before, I already saved an Omnisphere patch on the receptor's play level successfully. I have no idea what goes wrong this time.
Unless I am missing one step in the procedure.
After opening Omnisphere, I'm speaking of the plug-in itself, and selecting the desired patch, is there something else to do on the receptor's synth level before going to the preset level?
The receptor's manual doesn't say much about resetting the unit, of course I wouldn't like to lose my data, but is there some kind of reset that would not araise everything? I saw something about "resetting the plug-in cash", but I don't know what it means.
Best,
JPR
-
- KVRist
- Topic Starter
- 135 posts since 2 Mar, 2016 from Paris France
Hi.
I partly solved my problem by loading an existing preset containing an Omnisphere patch, I was lucky enough to have one, and then clicking save as and renaming it.
So, the problem seems to occur only if I start from an empty preset. What could be the reason then?
Thanks for your help,
JPR
I partly solved my problem by loading an existing preset containing an Omnisphere patch, I was lucky enough to have one, and then clicking save as and renaming it.
So, the problem seems to occur only if I start from an empty preset. What could be the reason then?
Thanks for your help,
JPR
-
- KVRist
- Topic Starter
- 135 posts since 2 Mar, 2016 from Paris France
Hi all.
The more I understand the weirder it gets.
After starting up the receptor, if you click save as from an Omnisphere preset, the receptor crashes.
But, after starting up, if the first thing you do is click save as from a Kontakt preset, the save as dialogue box opens as expected, and if you then do the same from an Omnisphere preset, it works as expected as well.
Go figure it out.
Best,
JPR
The more I understand the weirder it gets.
After starting up the receptor, if you click save as from an Omnisphere preset, the receptor crashes.
But, after starting up, if the first thing you do is click save as from a Kontakt preset, the save as dialogue box opens as expected, and if you then do the same from an Omnisphere preset, it works as expected as well.
Go figure it out.
Best,
JPR
-
- KVRist
- 229 posts since 6 May, 2014 from New Mexico
Hey JPR,
I'm sorry I don't have anything actually helpful to say here, but my hope is to further this conversation to a resolution.
NI Komplete v10 and Omnisphere have been having similar issues. Apparently there is some ill translating the Windows version of these plugins through WINE. NI K10 is still locked out due to a .dll library for Kontact not able to load in rendering the whole update unusable. A post string you may have seen address this issue with Omnisphere 2.
I don't know which version of these plugins you have (I can assume NI K9 as you say it's working) but perhaps you may have stumbled across a potential fix for both regarding you most recent post.
Stuart
I'm sorry I don't have anything actually helpful to say here, but my hope is to further this conversation to a resolution.
NI Komplete v10 and Omnisphere have been having similar issues. Apparently there is some ill translating the Windows version of these plugins through WINE. NI K10 is still locked out due to a .dll library for Kontact not able to load in rendering the whole update unusable. A post string you may have seen address this issue with Omnisphere 2.
I don't know which version of these plugins you have (I can assume NI K9 as you say it's working) but perhaps you may have stumbled across a potential fix for both regarding you most recent post.
Stuart
Fish Out Of Water
Entune Productions
Entune Productions
-
- KVRist
- 229 posts since 6 May, 2014 from New Mexico
Fishoow wrote:Hey JPR,
I'm sorry I don't have anything actually helpful to say here, but my hope is to keep this conversation rolling in hopes someone with more background will be able to find a resolution.
NI Komplete v10 and Omnisphere have been having similar issues. Apparently there is some ill translating the Windows version of these plugins through WINE. NI K10 is still locked out due to a .dll library for Kontact not able to load in rendering the whole update unusable. A post string you may have seen address this issue with Omnisphere 2.
I don't know which version of these plugins you have (I can assume NI K9 as you say it's working) but perhaps you may have stumbled across a potential fix for both regarding you most recent post.
Stuart
Fish Out Of Water
Entune Productions
Entune Productions
-
- KVRist
- Topic Starter
- 135 posts since 2 Mar, 2016 from Paris France
Dear Stuart,
I'm using Komplete 9 and Omnisphere 1. Something, but prior to 2 anyway.
Cheers,
JPR
I'm using Komplete 9 and Omnisphere 1. Something, but prior to 2 anyway.
Cheers,
JPR
