Spire: Problems and trouble shooting help
-
- KVRist
- Topic Starter
- 422 posts since 10 May, 2009
Problems and trouble shooting help
-
- KVRAF
- 2675 posts since 14 Jul, 2005 from Australia
As per my email discussions with you guys, I have found two bugs (as of Spire v1.0.6):
Computer Setup: Windows 8.1 (I have access to Dreamspark) with Cubase 6.5.5
* Opening the Spire interface on a track that uses Spire automation slows down the meters significantly in Cubase, especially on larger projects (video demonstration and test projects provided via email)
* Spire rarely but randomly crashes Cubase (crash logs sent via email)
Apart from those two problems, I think it's OK
Computer Setup: Windows 8.1 (I have access to Dreamspark) with Cubase 6.5.5
* Opening the Spire interface on a track that uses Spire automation slows down the meters significantly in Cubase, especially on larger projects (video demonstration and test projects provided via email)
* Spire rarely but randomly crashes Cubase (crash logs sent via email)
Apart from those two problems, I think it's OK
-
- KVRAF
- 2925 posts since 29 May, 2009 from New Zealand
I had massive graphical issues a while back in FL while using spire in an averagely CPU heavy project (was using 2 instances of Spire). For some reason the graphics would become VERY choppy, not respond to input and level meters on the mixer and main outs would freeze. The sound would be absolutely fine however. Ended up setting a fixed buffer for Spire and now all's well 
Just a tip in case you run into the same issue (i7 2600, Win x64 Ultimate).
Don't forget to hit "save now" on the settings page/tab once you've done this.
EDIT: Also seems to be a problem with threaded processing now and then. Disabling threaded processing (same page as the buffer editing above) solves random pops and click (and doesn't seem to affect CPU usage, stays as is).
Just a tip in case you run into the same issue (i7 2600, Win x64 Ultimate).Don't forget to hit "save now" on the settings page/tab once you've done this.
EDIT: Also seems to be a problem with threaded processing now and then. Disabling threaded processing (same page as the buffer editing above) solves random pops and click (and doesn't seem to affect CPU usage, stays as is).
-
- KVRist
- 45 posts since 15 Jun, 2013
We have found and fixed some issues like you've described, and we are planning to release them in the next version.soundpalace wrote:As per my email discussions with you guys, I have found two bugs (as of Spire v1.0.6):
Computer Setup: Windows 8.1 (I have access to Dreamspark) with Cubase 6.5.5
* Opening the Spire interface on a track that uses Spire automation slows down the meters significantly in Cubase, especially on larger projects (video demonstration and test projects provided via email)
* Spire rarely but randomly crashes Cubase (crash logs sent via email)
Apart from those two problems, I think it's OK
-
- Pick Me Pick me!
- 9687 posts since 12 Mar, 2002 from a state of confusion
I believe I have found a bug -- attempting to load a Patch Bank file when Single Preset menu option was selected causes crash to desktop. The opposite (selecting a single preset when Patch Bank menu option selected) behaves in the same manner.
-
- KVRAF
- 5678 posts since 25 Dec, 2004
I am unable to test this on OSX as the option is greyed out.VitaminD wrote:I believe I have found a bug -- attempting to load a Patch Bank file when Single Preset menu option was selected causes crash to desktop. The opposite (selecting a single preset when Patch Bank menu option selected) behaves in the same manner.
sketches... http://soundcloud.com/onesnzeros
some artists i support... https://bandcamp.com/spectraselecta
some artists i support... https://bandcamp.com/spectraselecta
-
- Pick Me Pick me!
- 9687 posts since 12 Mar, 2002 from a state of confusion
oksqigls wrote:I am unable to test this on OSX as the option is greyed out.VitaminD wrote:I believe I have found a bug -- attempting to load a Patch Bank file when Single Preset menu option was selected causes crash to desktop. The opposite (selecting a single preset when Patch Bank menu option selected) behaves in the same manner.
I'm still having the issue though.
-
- KVRAF
- 2675 posts since 14 Jul, 2005 from Australia
Just wanted to let everyone know that these issues both appear to be fixed in v1.0.8 which was just released. Well done guys!!sound_dev wrote:We have found and fixed some issues like you've described, and we are planning to release them in the next version.soundpalace wrote:As per my email discussions with you guys, I have found two bugs (as of Spire v1.0.6):
Computer Setup: Windows 8.1 (I have access to Dreamspark) with Cubase 6.5.5
* Opening the Spire interface on a track that uses Spire automation slows down the meters significantly in Cubase, especially on larger projects (video demonstration and test projects provided via email)
* Spire rarely but randomly crashes Cubase (crash logs sent via email)
Apart from those two problems, I think it's OK
-
- KVRAF
- 3817 posts since 8 Mar, 2006
small bug: v 1.0.8 Win, vst x86 version
resetting the osc fine parameter either via ctrl+click or double-click works but the GUI is showing the last value.
If trying to move the parameter again, it visually jumps to the actual value.
resetting the osc fine parameter either via ctrl+click or double-click works but the GUI is showing the last value.
If trying to move the parameter again, it visually jumps to the actual value.
-
- KVRAF
- 2675 posts since 14 Jul, 2005 from Australia
Confirmed here too on the VST2 x64 version in Cubase 6.5.5. The knob stays in its last position but the numeric value updates. I went ahead and tested every other knob on the plugin and can confirm that only the oscillator "fine" knob is affected.3ee wrote:small bug: v 1.0.8 Win, vst x86 version
resetting the osc fine parameter either via ctrl+click or double-click works but the GUI is showing the last value.
If trying to move the parameter again, it visually jumps to the actual value.
Well spotted!
-
- KVRian
- 910 posts since 21 Aug, 2011
New bug as of yesterday in Logic X / Mavericks. A new instance of Spire shows Init0-InitX as presets, as if the initial factory isn't found or isn't loading. Usually Cricket Bass of whatever is shows up here along with Bank 1.
-
- KVRist
- Topic Starter
- 422 posts since 10 May, 2009
Please, try reinstall Spire.Phase47 wrote:New bug as of yesterday in Logic X / Mavericks. A new instance of Spire shows Init0-InitX as presets, as if the initial factory isn't found or isn't loading. Usually Cricket Bass of whatever is shows up here along with Bank 1.
-
- KVRian
- 910 posts since 21 Aug, 2011
Just tried and the installer no longer works w/ Mavericks? Says it's from an unidentified developer?vega555 wrote:Please, try reinstall Spire.Phase47 wrote:New bug as of yesterday in Logic X / Mavericks. A new instance of Spire shows Init0-InitX as presets, as if the initial factory isn't found or isn't loading. Usually Cricket Bass of whatever is shows up here along with Bank 1.
