Log in

View Full Version : [solved] single mode bugs


grs
23.10.2005, 02:16 PM
[edit: some parameters are not meant for mid note tweeking. see Bens end comments]

Forget all this USB / Virus Control / Arp bugs.
I get 'Single' Patch edit bugs. Some times you will be tweeking a parrameter and then suddenly it stops having any effect. Mainly only if you are playing one note or chord and holding it or using an arp and having 'hold' on. Sometimes is hangs there forever without knobs or buttons doing anything. Then if you play new notes on the keyboard the new notes have all the parrameter changes you made in silence.

I haven't found one knob or button which triggers it, I just know that it will happen but you wont know it happened unless your holding keys down. Some richer sounds are more prone to it (more voices? more chances?)

Anyone else had the 'loose tweeking control of long notes' bug?

note: No usb cable involved.

MADSTATION
23.10.2005, 03:21 PM
Yes I can reproduce this!

grs
24.10.2005, 08:26 AM
So it's proven that the TI even without integration has gremlins in the system.

blay
26.10.2005, 08:47 AM
the title of this thread alone scares me...

im buying tomoro and now im not so sure - i thought the ti would be fine avoiding the usb/vc - and how many times were we told the hardware was working perfectly but it was just the software that remained to be finalised for release?

:(

cheers

pete

ben crosland
26.10.2005, 09:04 AM
Yes I can reproduce this!

You mean reliably, or accidentally?

If you can reproduce it reliably, please detail the exact patch and steps to do so, as I have never encountered this bug.

grs
26.10.2005, 09:52 AM
Any patch, any amount of time from 20seconds to 2 or 3 minutes. Hint: play a chord with 4 notes and hold it DO NOT play the chord again just hold down the keys of your first chord. If you can tweek away with your free hand, I believe the unresponsiveness is provoked more so if you can tweek two knobs or more together and choose different knobs all over the virus - filter section, amp env, fx, semitone, value 1 2 and 3, just go a bit nuts, don't be to slow about it either just twist away rapidly. I can get it to happen around 80% if the time, the longest I went was about 5 minutes but it did eventually do it.

When it happens; keep the initial chord held, set osc balance to middle, filter balance to middle then rake the cutoff 1 and 2. You should hear some changes, but nothing.

I could take a video of me doing it but my canon camera just got an e18 error. Apperently fatal! :(

DIGITAL SCREAMS
26.10.2005, 10:10 AM
grs.....plz try it out on my patches i made for the Virus KC some time ago. I experienced no probs with these. Id be interested to know what happens...

DS

grs
26.10.2005, 11:15 AM
DS: I've got pleanty of patches to try, thanks.

I've been trying to reproduce the bug now for 1/2 hour now and managed to do so 50% of the time. I must say Ben your patches are harder to knock over due to the unison factor being low. But results are below.

Rom A17 - 2 mins. 5 note chord held. No response until new notes played.
Rom A17 - 1 mins. 5 note chord held. no response lasted only 10 seconds then snapped back.
Rom A 120 - 4 mins. 5 note chord held. no response until new notes played. high pitch note lasting for ever, even when new patch selection. I think that was a feedback loop in the reverb or delay. panic did not reset it had to power off.
Rom B 111 - 5 seconds. 5 notes held (with shift 'hold') I only tweeked cutoff 1 while turning the master volume knob. panic did not work 'arp on' pressing did not work. only stopped when playing new notes.

I found a bizare screachy spazim bug a few times. The BPM light would go fast, crazy on, off for a second then splutter gasp - CHARRRZZZZZ... forever until hard power off. It was encouraged by the same tweeking as the 'long note, no response after tweeking madly' bug attempts but not as often. It only happend twice in half an hour.

ben crosland
26.10.2005, 11:39 AM
OK - I think I know what causes this:

The Virus TI has certain parameters that have been programmed to only change once a new voice is played. This is to avoid unwanted artefacts in the sound. Specifically, these are

Delay Patterns

Reverb Room Types

Oscillator modes.

Since these are not 'performance' parameters, realtime control is not normally required.

However, once you have changed one of these parameters without triggering a new voice, the sound will stop responding to any other controllers as well, it seems.

I guess for now, the answer would be to avoid changing these parameter values on sustained voices, if you wish to do lengthy, live tweaks to a note/chord, or simply remember to retrigger the notes if you change these parameters.

I suspect that in most cases, in this situation, you will be messing about with a patch, experimenting with all sorts of different parameters, as opposed to actually performing something?

grs
26.10.2005, 11:48 AM
Gothca. Now I can replicate this in 2 seconds. Understandable once you know what is happening.

I did for a second suspect changing the oscilator was in on it.

I'm even 'down' with the reason now.

blay
26.10.2005, 12:40 PM
Thanks for clearing this up Ben.

cheers

blay