I'm working with Nebula in Pro Tools Native 10.3.5 and using the FXpansion VST to RTAS Adapter to wrap Nebula. It seems to be working well except for one issue - I cannot get Nebula's settings to save in Pro Tools after I've made my tweaks/adjustments. I've seen this topic previously covered on this forum, but I'm not sure if there was ever a definitive answer on whether there is a work-around for this. I would very much appreciate any help or advice from anyone working in similar fashion. Does anyone know if there a work-around?
Build 505 with VSTGUI4 is already reported but is a VSTGUI4 bug. We should release a need version with a workaround. About W7x64/PT 9/10 with VSTtoRTAS adapter that no recover Nebula values I'll report to FXPansion during this week. I hope the can find a solution, fix or workaround
Enrique Silveti. Acustica Audio customer and technical support.
enriquesilveti wrote:Build 505 with VSTGUI4 is already reported but is a VSTGUI4 bug. We should release a need version with a workaround. About W7x64/PT 9/10 with VSTtoRTAS adapter that no recover Nebula values I'll report to FXPansion during this week. I hope the can find a solution, fix or workaround
W7x64 and OS X 10.6 and OS X 10.7 PT 9/10. With that many variables it really sounds like the RTAS adapter.
Our temporary solution has been that as soon as we lock down a Nebula instance it gets saved as an in-session-folder preset; that way when someone receives a session with Nebula(s) in it, we just load the presets back for each instance and voila. The PT presets have an advantage over the Nebula browser: in our Lion setups Nebula gets crashy whenever you try to open an (already instantiated) instance or access the program browser; not that it crashes every time, but those are the two behaviors that cause the most crashes for us. However...switching Nebula programs using the PT presets has been seamless, I've yet to see even a single crash that way. So for me PT presets have not only helped us to work around this recall issue but also represents the most reliable way to switch Nebula programs inside an already instantiated Nebula instance.
But the obvious downside is that if someone forgets to manage the Nebula instances before laying the session back...it's a do-over.
I found solution for this 1.In MAST page set SCAN BOOT to 0 fast,press save,restart plug or session. 2.To load library first press LOAD in DISK page 3.To rescan new added library use instance with SCAN BOOT 1 recovery Now Pro Tools 10 save all settings My systems Windows 7 and 8