User guide

TROUBLESHOOTING & KNOWN ISSUES
These issues apply to Bit-100 v2 version 1.1 and may be resolved in subsequent
versions.
Defaulting to Patch 1, u pon start - up:
With some VST host programs, when you reopen a song which contains an instance of the Bit-100 v2 , for
some reason the host software tell s the Bit-100 v2 to default to the first patch. So, for example, if you ’ r e
working on a song which includes the Bit-100 v2 set at patch number forty ( which has been tweaked to
your liking ) , upon saving and reopening the song, the Bit-100 v2 is not set as it was when you saved, but
instead is set at patch number one. This is a serious irritant because the recall o f all settings within a
particular song is one of the best features of virtual studio technology .
This problem is not unique to Manx Synths and only occurs under certain conditions with particular
hosts . None the less, we will look at resolving th is issu e in future updates .
If you experience this problem, please note that the settings you applied to the patch you were
working with will have been properly saved with the song , so there should be no problem if your song
includes several Bit-100 v2 patches, c ontrolled by program change events .
Setting a program change key in your host program will ensure that the Bit-100 v2 returns to where you left it.
Alternatively , you can apply the following work around:
1 ʹ copy the patch you are working with into patch#1 memory slot using the Bit-100 v2 ͛s ‘patch menu’ button.
2 - Save your song. When you reopen it later, if the Bit-100 v2 d efaults to patch 1 , its no longer a
problem and everything will be just as it was when you saved.
Hanging CPU use :
With the complexity of audio processing under the Bit 100s skin, it was always going to be an animal for CPU
cycles. However , in some circumstances, the Bit 100 v2 appears to retain CPU use even when naturally silent.
This should definitely NOT be happening; silence should be achievable with no CPU cycle at all, obviously.
It’s a bug which we are anxious to locate and resolve. If you find this happening, please note that,
temporarily switching to default program #1 may stem the CPU use.
Appendix Three
File Menu buttons not working properly
People may find that on some systems, the buttons which increase and decrease the numbers in the
data fields presented in the file menu do not respond properly. If this is the case, simply fill the data fields
in manually.
If you click ‘load patch’ and nothing happens, just click ‘load bank’, than hit ‘cancel’ and then return to
load patch again.
26 Appendix Two - Troubleshooting