The PC was not the source of timecode but part of the timcode chain. Hey, and this is the NORMAL way you have it. Timecode generated by external source, decoded by TC2000 or similar, delivered to the PC via RS232, feed into the QM2000 over Windows/OS COM Port driver. If the OS crashes, COM port data are no langer transmitted to the QM2000 and that is why it stops. If you call this way inside the PC not part of the QM2000, it is a cheesy assumption as I cannot feed timecode a different way except transformin the QM2000 into a CD2000. And that would be excactly in the way of my argument. Dedicated hardware and operation system for maximum reliablility. And the old myth of a crashing PC would not stop a show...it is a myth. A lot of crashes lead to a reboot incl. PCI device reset. Once this happens, the QM2000 will stop. Even a lame network connection can cause problems to the QM2000 show stability causing dropouts, jumps and jitters if you have the preview window open. From my point of view, the system can only by as stable as the basis. And Windows or better general purpose Operation Systems are not the best ground to build it on...and we are talking about the best in here, arent we? So the really best system for show playback would be something simple and reliable...like ADAT.



Reply With Quote
buffo
That's why I think the CD-2000 is the ultimate solution.
