Cherry Audio Forums

When input 1 is connected to the Mini LFO, it is alternating between (0V / 'Off' / Logic Low) and (+5V / 'On' / Logic High) on a regular basis, as shown by the red Multi-Oscilloscope trace in my most recent post. Exactly, that's more or less what I said about the LFO inverting the signal and not th...

Still doesn't add up. The way I see it is this: Looking at the 3 pictures on my first post above: 'And' works as expected as input 1 is on and input 2 is off. 'Nor' and 'Xnor' don't work as expected as 1 is on , 2 is off and according to truth tables in this state the output should be off. When inp...

The inversion is caused by the NOR or XNOR gates. Now I'm more confused. If this is so it sounds to me like they are doing what they shouldn't be. :?: I give up, lol. No, they're working fine. It's the fact that there is no signal connected to the right-hand input of the logic gates which explains ...

There is no contest here... what is seriously needed is a full blown recereation of the EMS VCS 3 . And yes I know about free Cynthia, however the VCS 3 is ripe for a make-over with all the added bells and whistles that Cherry Audio can bring. On the plus side, it should be a relatively simple proj...

To add to the pendantry, a signal is something that conveys information. The phrase "gate signal" doesn't indicate any particular value for the signal other than implied by the type constraint of "gate". So say on or off, high or low, 1 or 0, 5 V or 0 V, true or false etc. All t...

Should this be: 'While both or one input signals are "off" a gate signal will be sent to the output.' as this is the way NAND works. Yes, I agree with your definition. The terminology seems to jump around when they are describing the different logic functions. I think this may have trippe...

Okay, here's the relevant code, trimmed down to essentials: private double inputMeterValueL; // new value for input meter private double outputMeterValueL; // new value for output meter private double inputMeterLastL; // last value for input meter private double outputMeterLastL; // last value for ...

The variables in question are [...] are properly set in ProcessSample() , but are set to 0.0 in Initialize() and at the top of the first run through ProcessSample() OK, it's difficult to debug what's happening without seeing the actual code, or at least the appropriate snippets that are causing pro...

The variables that evoke this error are all user-defined members of the main class, and I initialize them both in the Initialize() method and in a one-time-only method I run at the top of ProcessSample() . I'd still be tempted to perform an explicit initialization of the variable values at the poin...

The error message is particularly galling, since the variable is always initialized, just in another part of the program, and there's no way to initialize it in the location where it's being used. Earlier versions of Java apparently weren't so picky. Are you using multiple modules/classes in your p...