!!!!!!!!! OS6.5 BUILD 352 !!!!!!!!!!!!!!!!!

[Mash-up]

apparantly another bug in the last one

[alekkh]

Hello everyone, here's my recent HC post about the 6.5:


...buid 352 is *definitely* not the last one....

-One prob I've had with build 350: filters in SPLIT mode generated awful noise from some patches.

- Build 351 fixed it. But now LFO3 assigns were no longer working! Reportedly, outputs 3&4 aren't working too.

- I downloaded 352 only to find out the LFO3 bug is still there! Waiting for build 353 already...

But the MOOG filter makes me forget about all these issues, it's soooo good!!

[udenjoe]

I already went from 350 to 351. I'm just going to wait until it's final.

[Hollowcell]

i went from 351 to 352 this morning before work...

i wanted to play around with the known bugs to see if 352 had fixed them...but i only had a short time so i decided to play around with new filter instead!!! :roll: this filter is really really good (to put it lightly! 8O )...

i cant wait to hear what people come out with using it!!

[Tom_1970]

LFO3 seems to works fine on my Virus.

Is it completely dead on yours?

[Aurora]

so i am going to have to upgrade the OS again!!!! that's the 3rd time this week!!!

Don't get me wrong.. The Virus is a great machine and the new features are excellent.. Part of the reason why i bought it was because of Access as a company and their development of the virus range via firmware upgrades..

Do Access not have a testing department? Upgrading firmware should not be taken lightly.. I only do it if it is completely necessary..(same as a pc!)If it goes wrong, from my understanding we are not covered by the warranty..

I think i'll hold off till they get the bugs ironed out!!

I am not slating Access here, i am a loyal fan.. but i would rather wait and get an OS that is stable and functions fully, rather than flashing my ROM every other day!!

When you spend alot of cash on a synth.. you dont want to be messing about flashing a chip.. that can go horribly wrong!!! (speaking form PC experience here!)

Quality definately seems to be slipping !!!

I had a Korg Triton, OS 2.0 took atleast 6 months to be released.. but when it was, it was stable and did exactly what Korg said..

Access seem to be very keen to enhance the Virus (not a bad thing)..but come on guys.. i am sure your users would rather wait until thorough testing is done..instead of a new buggy os every month...

On a side note.. it would have been nice to know that you only need to install the first midi file to update the OS..as installing the second one wipes all the presets from bank C upwards..

So if you are already on OS 5 or above (with the 1024 sound expansion).. you only need to load the first os midi file!!! (i know i should have backed up my presets :oops: )

well that's my tupence worth!!! I just dont need the hassle!!!

[Mash-up]

totally agree with you here.
i haven`t even upgraded from os 6 yet, due to this problem.

good point also about the second file, i actually posted a message about this, as it seemed as clear as mud on the instructions.

[ben crosland]

- Build 351 fixed it. But now LFO3 assigns were no longer working! Reportedly, outputs 3&4 aren't working too.

- I downloaded 352 only to find out the LFO3 bug is still there! Waiting for build 353 already...

nonsense - LFO3 is working fine. You were either using a much earlier build before, or you just haven't noticed until now how LFO3 works.

The LEDs only light up once you change the Amount to above +0. They do not behave like LFO1 and 2, because you can only send LFO3 Amount to *one* of the available parameters.

So, now you can relax and get on with enjoying build 352 :wink:

[ben crosland]

[quote="Aurora"]so i am going to have to upgrade the OS again!!!! that's the 3rd time this week!!!

All part of the fun :wink:

Upgrading firmware should not be taken lightly..If it goes wrong, from my understanding we are not covered by the warranty..

I'm sure Access will see you alright if the worst should happen - I've yet to hear of anyone having to pay for this problem to be sorted out. It's really a very simple proceedure to replace the ROM chip.

I think i'll hold off till they get the bugs ironed out!!

Suit yourself - I think you'll find that 352 is pretty stable now..

i would rather wait and get an OS that is stable and functions fully, rather than flashing my ROM every other day!!

Don't worry about it so much - the ROM chips are guaranteed by the manufacturer to withstand a few thousand flashes. The instances of Flash ROM failure is really very rare.

[Aurora]

fair points Ben!! :wink:

i'll give 352 a go!!!

Hopefully with this one all is well!!

my experience with flashroms hasn't been good..which added to my frustration..

i had problems with OS5, which i upgraded to just after buying my Virus..
I really thought that my virus was knackered..(didn't have much experience of the synth).. I really could have done without the panic..(luckily there was a post regarding the problem here otherwise i would have been sending it back to the shop)

i still feel that Access could put a definitive tested os upgrade on there site rather than their current batch of offerings..

Not all users are experienced.. the difference between a shaky os and a hardware failure could be difficult to spot by someone who does not know what they are looking for..

They have set such high standards with their products and OS's that i can't help but feel dissappointed..

Maybe i'm just having a bad day 8O

[alekkh]

LFO3 seems to works fine on my Virus.

Is it completely dead on yours?

Can you assign *different* values of LFO3 to: Osc1 and to PW1 ? Or, to PW1 and Sync Phase? Can you make all 5 LFO3 red LEDs light up (to indicate they have data stored), like with LFO1&2 and with Assignables? - I can't...

[hatembr]

NO

thats the difference between LFO3 and LFO1&2
with LFO3 you can assign one destination at a time:
so only one of these LEDs can be lit:
- OSC1 OR
- OSC2 OR
- OSC1 + OSC2 OR
- PW1 OR
- PW2 OR
- PW1 + PW2 OR
- SYNC PHASE

[alekkh]

NO

thats the difference between LFO3 and LFO1&2
with LFO3 you can assign one destination at a time:
so only one of these LEDs can be lit:
- OSC1 OR
- OSC2 OR
- OSC1 + OSC2 OR
- PW1 OR
- PW2 OR
- PW1 + PW2 OR
- SYNC PHASE

I don't remember myself being limited by the LFO3 assigns before (2 years already). But maybe you are right - It does look like LFO3 is meant to be limited. Strange, that I noticed that only after upgrading to 6.5 - maybe became too peaky :)

[Hollowcell]

im not sure what u r talking about wiht the lfo3 there alekkh, but i had a chance to play around a little more with 352 last night and the "known bugs" seem to be ironed out.....

now back to this brilliant filter 8O

[udenjoe]

LFO3 seems to works fine on my Virus.

Is it completely dead on yours?

Can you assign *different* values of LFO3 to: Osc1 and to PW1 ? Or, to PW1 and Sync Phase? Can you make all 5 LFO3 red LEDs light up (to indicate they have data stored), like with LFO1&2 and with Assignables? - I can't...

As far as I know you can use the modulation matrix for these other destinations with an LFO 3 source.

[marc]

i still feel that Access could put a definitive tested os upgrade on there site rather than their current batch of offerings..
...
They have set such high standards with their products and OS's that i can't help but feel dissappointed.

Although we're certainly open minded for suggestions to improve the stability and quality of the virus OS builds it's not like we don't test at all and you our users as beta testers. in fact we test a lot but unfortunately finding bugs also means that you need to be a little lucky sometimes.

i give you an example: the first build os OS6.5 contained a bug which enabled the individual outs 3-6 in the multi mode. sure you'll think now - "yeah, that's really obvious, why didn't they find this?". unfortunately the multi outs worked on part one and when we tested this OS build we haven't tested the outs on every part.

don't get me wrong - we care about bugs and we try to fix them as fast as possible. that's why you have been supplied with 3 OS version in such a short while.

somebody mentioned that it would help to know that the second1024.mid installs the 1024 sounds (and therefore can delete what you have stored in banks e-h). let me quote from the readme file which comes with every OS update:

"...
Load SECOND1024.mid into your Virus. Proceed as stated in the display.
This file contains the ROM sounds."

we will ammend that this file can possibly overwrite existing ROM sounds. we though that this would be pretty obvioous.

as for the LFO3 bug - we haven't had any bug report so far and in case you believe you've found a new bug, please contact us at: support@access-music.de

best, marc

[Aurora]

thanks for the reply Marc..

I have since installed the latest os and all is well..

I am a loyal fan of Access products and hope you don't feel i was slating..

I had a number of fears regarding flash upgrading my unit..(seem to be unwarranted!)

It's refreshing to get a reply form a synth manufacturer..

PS you put me in my place..i am eating humble pie here :oops:

[alekkh]

[quote=Aurora]

1) we will ammend that this file can possibly overwrite existing ROM sounds. we though that this would be pretty obvioous.

2) as for the LFO3 bug - we haven't had any bug report so far and in case you believe you've found a new bug, please contact us at: support@access-music.de

best, marc

2) OS 6.5 is terrific indeed, and the LFO3 bug is probably not a bug, as LFO3 supposedly had two assignables maximum even in older OS.

1) I had the 1024 patches before OS6.5. After using the 1024 update file, I didn't hear any difference. Unless I'm again missing something, did I need the second file at all?

thaNKS!

:D

[marc]

I had a number of fears regarding flash upgrading my unit..(seem to be unwarranted!)


i guess nobody _likes_ to update the flash ROM. many horror stories have been told and keeping in mind that once the flash is broke, it needs to be replaced i can understand your fears.

but: we never had an incident at access R&D where a flash actually broke while being updated. i'm not aware that one single beta tester we have broke a flash ever. maybe these components are better than we think they are? the flashs we're using "guarantee" ten thousands of write cycles.

marc