Jon B wrote:
You're just running both devices off the same crystal. That's
certainly one way to do it, but wouldn't work with devices that use
different circuits or crystals, and I don't think it can be extended
to more than 2 or 3 cards.
sure it can.. just build a small timer circuit on a pro
> Hi. The only solution I saw to this problem was in a HOW-TO that a guy posted.
> Sadly I can't find it, but it was a soldering iron job on the soundcards.
Right here:
http://www.djcj.org/LAU/quicktoots/toots/el-cheapo/
You're just running both devices off the same crystal. That's
certainly on
Hi. The only solution I saw to this problem was in a HOW-TO that a guy posted.
Sadly I can't find it, but it was a soldering iron job on the soundcards. For
3 cards, disable the crystals on 2 cards, and link the crystal from the first
card to the 2 cards with the disabled crystals. this logically
On Saturday 31 December 2005 17:54, Jon B wrote:
> > I would've thought though that if you had a software buffer of X
> > milliseconds, then you should be sending that buffer to the card every X
> > milliseconds (according to some other timer in the system.) If it takes
> > longer before the card
> I would've thought though that if you had a software buffer of X
> milliseconds, then you should be sending that buffer to the card every X
> milliseconds (according to some other timer in the system.) If it takes
> longer before the card is ready for the next buffer then you need to
> drop some
> For starters, one may start measuring average frequency of interrupt
> requests generated by both cards provided both of the play the same
> length buffer.
>
> The measure of the average frequency will be the computers RTC.
>
> I am not saying that it is simple, and yes, prior knowledge, like NTP
