I disagree with this statement. It's not a waste of development to make the Flex software deal with this issue smoothly.
Flex is a commercial product that has to live in the real world of mainstream, Windows based computers, all their faults included. Besides, being cutting edge and somewhat experimental, Flex Radio Systems is a business that has to sell radios to remain in business and pay its employees. Luckily have they several volunteers that keep the costs lower, but ultimately they have to sell more hams on the concept. My system is on the high end of what most hams have in their shacks. (Win7, 64 bit, 8 gig RAM, AMD 965 Quad core, dedicated $125 Firewire 800 card with a high-end TI XIO chipset on the PCIe 1x "short socket" slot). Even if there is a problem with my system, the Flex software needs to have some mechanism to alert me to it, or reduce its performance in a way that gracefully degrades. -----Original Message----- But it is a classical high-DPC event. They probably could cause PowerSDR to resync but that would be spending valuable development time to fix a problem that only occurs on computers that aren't working properly. _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
