|
Technical assistance: Known problems and solutions
Hosts affected: All
Description: "I get clicks and audiodropouts"
Answer1: Increase the latency of your soundcard
Answer2: You caused a CPU overload. Reduce the number of plugins in your songs.
Answer3: Reduce the quality setting and number of voices.
Answer4: Reduce the release times.
Hosts affected: All
Description: "I get a high CPU load when i switch through patches during playback"
Answer: It is technically necessary to reset reverb/delay buffers on patch changes.
Hosts affected: Various
Description: "The host crashes when i switch trough presets"
Solution: Install the latest soundcard drivers and increase the latency setting of your soundcard.
Hosts affected: Sonar5, Sonar6, SaviHost, various others
Decription: "I get graphic errors when i resize the plugin interface"
Answer: The resizing routines of your host software is buggy. Please install a newer host version and refer to the host's company for a bugfix.
Hosts affected: Fruity Loops
Decription: "The first note in a song is not played"
Answer: This is a known problem in Fruity loops. It does also affect many other plugins, and has been reported to Imageline. Imageline ignores the compatibility problems.
Solution: Open Fruity loops, Go to audio settings, change "reset plugins on transport"
Hosts affected: Minihost
Description: "The presets/patch names are messed if i use the preset manager"
Answer: This is a Minihost problem which does also affect other plugins.
Hosts affected: Orion Platinum beta v7.5
Decription: "The automation parameters in song are in the wrong order"
Answer: Synapse has already fixed the problem. Please download a newer Orion version.
Hosts affected: Cubase3,4
Decription: "I get an audiodropout during playback"
Solution: Switch off autosaving
Hosts affected: Orion and some others
Description: "The efffect plugin does not respond to my Midi data"
Answer: Not all hosts are able to send midi data to effect plugins. You can also use automation instead of midi. Check your host configuration.
Hosts affected: Sonar 5/6
Description: "The CPU load is high when i open the editor"
Answer: The problem is caused by a bug in Sonar 5/6. Please update to a newer Sonar version. Download and install a graphics card driver.
Hosts affected: All
Description: "The gui response is slow when i change the mod in Gladiator", “It takes a second till i can hear someting after a patch change or loading in FireBird/Gladiator"
Answer: This is technically necessary to precalculate data for the HCM synthesis.
Hosts affected: All
Description: "Why does Gladiator/FireBird need so much CPU when i load it or swith presets"
Answer: This is technically necessary to precalculate data for the HCM synthesis. That's why the right panel says "Processing...". The CPU will drop down to a low value after a second. The method of preprocessing has the advantage that Gladiator needs lees CPU later.
Host affected: Cubase4
Description: "Cubase4 does not show some preset names properly"
Answer: This is a cosmetical Cubase4 problem which does also affect other company's plugins. Please refer to Steinberg for a bugfix.
Solution: Use the plugin's internal preset browser which works relieable.
Hosts affected: Sonar 5/Project 5
Plugin affected: Nearly all existing VST plugins with resizeable GUI
Description: "I can't see the plugin's GUI", "I can only see parts the plugin's GUI"
Answer: The problem is caused by a bug in VST adapter of Sonar 5/Project5. It can't handle GUI size changes properly.
Solution: Rescan your plugins in the host. We recommend to update to a newer Sonar version.
Host affected: Ableton Live 6
Plugin affected: Gladiator
Description: "Not all automation parameters are shown in the host"
Answer: Ableton 6 can only handle 128 parameters for Automation. Please refer to Ableton for a bugfix.
If your problem couldn’t be solved feel free to write a bug report.
|
