PlanetZ forums - scopeusers.com

Just emailed Ralf at Creamware about this, but in the meantime just wanted to check to see whether others can confirm, just in case it's a specific problem on my system (although this does seem unlikely as everything else is working fine):

In the mono version of the Graphic EQ, the Q control does not seem to be working correctly:

According to the manual, in both mono and stereo versions of the Graphic EQ, the Q frequency range should be continuously adjustable between 0.7 and 5.0 (and this works correctly in the stereo version).

However, in the mono version, the Q control only goes from 2.0 to 5.0. Double clicking the knob resets it at 2.9 (whereas in the stereo version it resets correctly at 2.0). I am not able to select values between 0.7 and 2.0 with the frequency range knob. However, double clicking in the numerical field does reset the range at 0.7 (but then turning the knob makes it immediately jump from 0.7 to 2.0 or above!).

Not a major deal, I know, but would be great if it were fixed.

Can anyone else confirm this?

Thanks.

you're right, same here!
a real bug!

Ha, never noticed that, prolly cos i tend to use the stereo version (which is rarely).

Thanks for confirming this, guys. Then it looks as though it is indeed a bug. Hope it will be fixed in due course...

All the best.

Hi, I found a lot of bugs in various modules, and the forum people told me to look out for alternatives... So - look out for an alternative

Are you saying that a fix is not likely, then?

Do you want me to count the actual bugs that have been confirmed here, with standard factory plugins - no 3rd party? They have been present since SFP3, and haven't been fixed 'till version 4.5 So - make a conclusion by yourself...

Cheerz

Hoi Badger,

Things don't get fixed that often, so don't get your hopes up too high. Of course, confirmation of a possible bug by other users filters out many other causes of the error, like a bad installation or a corrupt file or so. That confirmation, as you got in this topic, may save them some precious time...

Keep 'em coming,
at0m.

I see - didn't realise there were so many bugs. I suppose that perhaps Creamware could have lost many (all?) of their original development team during their rocky financial period. Since that came just after the version 3.1c release I suppose it would account for the lack of fixes since then...

That's one of the main reasons IMHO, that many of the original designers aren't around any more...

...and that ruins all the drivers / updates hope in the near future...

wrong. there are coders at work as we speak........

Working on next gen Scope OS/PCI Express HW Gary?

as to pci-e-
i don't know, but i wish they would. mackie style or similar automation too...

proper vista drivers for sure...

garyb wrote:wrong. there are coders at work as we speak........

That's encouraging to hear - do you think they'll be up for fixing some of these (admittedly minor) things?

maybe.
there is a lot of work to do. i'm not privy to the order of priority.

about saving time maybe could be useful to sum up those bugs in a dedicated topic; What do you think about this?