John Bowen Synth Design

Hello, John

I met quite a recurring problem,
after a few hours often one or more display screens gets weird
like "# 73C] @ | [# # # @"
impossible to change presets or save: the only solution turn off

This happens to me very often like the frezze logo waldorf

Hmmm, is it consistently the same text displays? Like always the Oscs or LFO display?

I do not know, I remember the screen LCD filter
I take pictures the next time with my phone

Just happend to me. Took a picture:

Hmmm, also the Oscillator section. It seems that for those who are reporting this, it's only in the Oscillator text displays.

If you see it elsewhere, please let me know. We are investigating....

I've seen often, but only in the osc section.

I have seen it a couple of times, but only in the oscillator section.

Yes again for me last night ...Just oscillator screen

I wonder if all these bugs that were described in the last couple of weeks are just of the 2nd batch - or 1st one as well.
I've seen that the sample loop bug is only 2nd batch related.

The sample loop bug has to do with the new format we set up for the CF cards with v1.2. The old card format has the loop data where it can be read properly; the new format does not. The coder has to just update this portion of the sample loading code...it isn't related to the strange display characters.
HOWEVER...we didn't have reports of this at all in the first production run, so it's curious. It would be great if anyone experiencing this could determine if there's a repeatable series of steps to cause the strange displays, or if it's truly random behavior.

Just received my Solaris. This is happening to mine as well, just the oscillator display, just from browsing through presets. Away from home now for another week nowso won't be able to re-evaluate.

Very frustrating here, because I cannot get this to happen on my machine, and I'm running v1.2 OS like everyone else.

Sometimes it comes down to how some people use the synth - I've seen it before, where there was something obvious that I knew not to do, and went about it another way, but new users would not, making the problem show up.

If any of you experiencing this can find out a reason, or a certain procedure or number of steps that then cause this to happen, by all means, please post it here!

john b.

Sorry John, but it is a random bug :
I managed to obtain it today, deliberately, but one time only.
It occurs sometime when you change from a progrm to another with the arrows.
I was on program 2.73 and go to program 2.72 and i obtain the bug.
It was the second time i obtain it with this exact procedure.
But i was not able to reproduce it another time.

It would be good to know if this is happening in relation to a certain bank of presets as well.

Another picture : (I was send a private Message) : my Solaris don't work now