I recently ran into an issue on a system that uses the comma "," as decimal instead of "."
Apparently, this is common in some parts of Europe and especially in France.
The solution is to simply change Windows' region setting and choose "." as a decimal separator.
There are 2 distinct issues:
The first will mainly impact you if you try to capture NTSC with any capture card using AmarecTV on comma-region system,
The second if you try to use IO-data gv usb2 with any software to capture NTSC with a windows that uses comma, and ofc if you use both together.
The reason why everything works fine with PAL is probably because PAL fps is not a fraction it is 25/50, but NTSC is 29.97
The error on AmarecTV may look like this
Quote:
return: HRESULT=80004005 (
code: pConfig-> SetFormat(pamt)
|
Another reason behind this error is if you manually modified the suggestions to some unsupported format (unsoprted color space, or dimensions).
VirtualDub, despite its massive list of things I don't like, handles this particular kind of error reporting better
Some programmers are really bad at understanding there are different countries and languages, and I have suffered from this stupid thing a lot, but in this very particular instance, you can't blame I-O data. Please note that their product only OFFICIALLY supports windows in Japanese and the device is not officially sold outside Japan.
Also, note that they no longer officially support Windows versions prior to 10.
Hope that helps people who may run into these issues too!