I have looked at this in some detail in the past as I design LED based solar charged lights and am generally interested in LEDs.
Firstly, human perception at constant power and variable duty cycle pulses. A say 10% duty cycle would result in 10 x the current at the same voltage for this to hold. Real LEDs will have somewhat higher forward voltages when current is increased by 10x but not greatly so. A fair test is probably Ipeak x time on = constant.
In the distant past it was alleged that the human eye response was such that pulsing LEDs at constant power but at low duty cycles resulted in greater apparent brightness. AFAIR the reference was in an HP document.
Quite recently I have read just the opposite from a moderately authoritative but unremembered source.
I can probably find the recent document, but the HP one will be lost in the mists of time. However, I believe that any physiological effect ether way is small. Given that you need about a 2:1 change in LED brightness for it to be noticeable when LEDs are viewed separately (one or other but not both together), small differences will certainly not be noticeable. Where eg two flashlights are shone side by side on a general scene so that direct comparison can be made you may need about 1.5:1+ difference before the difference is noticeable - this depends somewhat on the observer. When two lights are used in "wall washing" on a smooth wall, side by side differences of down to about 20% may be discernible.
Secondly - actual brightness.
Using constant mean current, total light output falls for pulsed operation and is lower for increasingly low duty cycle! The effect is even worse for constant mean power !!
Both of these effects can be clearly seen by examining the data sheets of target LEDs. Luminous output per current curves are close to straight lines but curve towards decreasing output per mA as current increases. ie doubling current does not quite double luminous output. This decreasing rate of return accelerates as current increases. ie an LED operated at well below its rated current produces more lumen/mA than at rated current with increasing efficiency with decreasing mA.
Output (lumen) per Watt is even worse than lumen per mA. As mA increase Vf also increases so the Vf x I product increases at a faster rate per lumen than just I does. So, again, maximum lumen/Watt is achieved at low mA compared to rated mA and lumen/Watt efficiency improves with decreasing current.
Both these effects can be seen in the following graphs.
These curves are for the utterly marvellous [tm] Nichia NSPWR70CSS-K1 LED mentioned below. Even though this LED is rated at 60 mA absolute maximum and 50 mA continuous max Nichia have kindly specified it's performance up to 150 mA. Longevity at these current is "not guaranteed". This is about the most efficient <= 50 mA LED available. If anyone knows of any with a superior l/W at 50 mA and in the same price range, please advise!
I use the Nichia "Raijin" NSPWR70CSS-K1 LED in several products. This started life as an 30 mA LED but was uprated to 50 mA by Nichia after testing (with reduced lifetime of 14,000 hours). At 50 mA it delivers about 120 l/W and at 20 mA about 165 l/W. The latter figure puts it amongst the very best real world products available, although recent offerings are now exceeding this value at well below rated currents.
A complicating factor is that modern high power LEDs are often rated for Iabsolute_max values perhaps 20% above Imax_operating. ie it is not possible to operate them in a pulsed mode at less than about 90% duty cycle and constant mean current without exceeding their rated absolute maximum currents. This does not means that they cannot be pulsed at many times their rated maximum continuous currents (ask me how I know :-) ) just that the manufacturer does not certify the results. The Raijin LED is VERY bright at 100 mA.
Special case.
One area where pulsing at very high currents and low duty cycles may make sense is where the LED is rated for this sort of duty and the instantaneous luminous output (brightness) is of more importance than the mean brightness. A commonly encountered example is in Infra Red (IR) controllers where the brightness of each individual pulse is important as individual pulses are detected and the mean level is irrelevant In such cases pulses of 1 amp plus may be used. The limiting current in such cases may be the bond wire fusing currents. The effect on the LED die will be a shortening of lifetime but thi is (presumably) allowed for by th manufacturer in the specification - and required total operating lifetime is usually low. (eg a TV remote control which is used for 0.1 seconds x say 50 pulses per hour for 4 hours per day gets about2 hours of on time per year.
Effective illuminance improvement of a light source by using pulse modulation and its psychophysical effect on the human eye. EHIME university 2008
Enddolith cited a paper that claimed a substantial true visual gain under certain conditions. Here's a full version of the Jinno Motomura paper cited
[link updated 1/2016]
They are claiming an up to ~ 2:1 true lumen gain (as lumens relate to eye response) at 5% duty cycle but despite the great care they have taken there are some major uncertainties when translating this to real world applications.
They seem to place very high emphasis on fast rise and fall times. Are these met when illuminating real world scenes, does it matter? and are there selected examples where it will work better than others?
This is looking at LEDs directly (with remaining good eye?) and comparing apparent brightness. How does this translate to light levels reaching observer after scene reflection.
How does this apply when the LEDs are used to illuminate targets. Are the average luminance levels from a target compared to direct LED observation going to affect results? By how much?
As modern eg White LEDs have Imax_max ~= 110% of I_max_ continuous, and as this effect seems to depend on ~5% duty cycle, has this got any implications for similar real world LEDs at large percentages of rated current?
The simplest circuit is to separately feed the sound and light sensor signals into a microcontroller with a A/D, compute the desired LED brightnesses, then output the results as PWM.
There are many micros that have at least two A/D inputs and two PWM outputs. If this were a volume product, I'd probably start by looking at the PIC 16 line. If this is a one-off, use whatver you have lying around or are comfortable with. This would be very easy to do on one of the 16 bit PICs or dsPICs, like a 24F. You'll have a hard time finding one that can't run from its internal oscillator, has two or more A/D inputs, and at least two basic PWM outputs (called Output Compare on these parts).
The parameters of your algorithm that you mention about would be build-time constants in the main include file. Changing them would as simple as changing the values in the include file, then ree-building and re-flashing the code into the micro. If you want to get more sophisticated, you could implement a UART protocol that allows changing the parameters on the fly.
Best Answer
This multivibrator circuit of yours has only two states. In order to get what you ask for, you need more states. You likely will have to build it using several monostable multvibrators, and have each one trigger the next, in a loop.
Edit: Since you posted a photo, I see it is a purchased item. Nonetheless, you can modify it to be monostable, and you can buy several boards to achieve your goal.
The standard answer is to use a microcontroller to do this instead, but I generally believe in answering the original question and letting you decide.
Details: With this two transistor circuit, there are three ways to wire it:
In this circuit, either the left transistor is on, or the right one is. When the left side turns off, the right side turns on. The corresponding LED's indicate this. It's really flashing one LED, and the second one can be added, but it will always be in the opposite state from the first. These things happen together, so it isn't possible to have both off at the same time. That would require third state--and more parts.
Let's say you could build a three-state circuit. You'd have these states:
Question: When both lights are off, which one is going to come on next? Your desired circuit has two places where one of the LED's go off without the other coming on. So, really, you need four states to produce this effect:
You can use a 555 in place of the multivibrator. And it can be wired to be astable, bistable or monostable. But, you still would need four of them. Both kinds of circuits can provide a pulse to trigger the next circuit, and both have an input where the trigger can be fed in.
I suggest looking at the diagram in the Wikipedia article on multivibrators (or maybe you got a schematic with the board?), and find all the like parts on your board. If you didn't get a schematic, you should try to draw one.