From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple bugs in AVI Codec Comparison example

Environment:
Windows 8.1
LabVIEW 2018 SP1 f4 - 2020
Vision Development Module 2018 SP1 - 2020

 

Steps to Reproduce:

  1. Launch LabVIEW, open Help menu and select Find Examples...;
  2. In Example Finder navigate to Toolkits and Modules > Vision > Files;
  3. Open AVI Codec Comparison example and run the VI.

Expected Results:

  1. In a Results table:
    1. Codec column contains actual codec names as returned by IMAQ AVI2 Get Codec Names VI;
    2. Avg Write Time (ms) column contains frame write times expressed in milliseconds;
    3. File Size (KB) column contains AVI file sizes expressed in KB (base 2 customary historical unit).
      KB has traditionally been used as a convenient way to refer to 1024 (210) bytes and this definition is still prevalent in software world:
      FileSizeWin.png
      If you wanna meet the current standards and make it less ambiguous to engineers, you can replace the KB unit with KiB (it will be more ambiguous to other Windows users, though).
      The same applies to your 2 GB size limit as well;
  2. Example runs without errors.

Actual Results:

  1. In a Results table:
    AVIComp.png
    1. Codec column contains filtered codec names used for file creation;
    2. Avg Write Time (ms) column contains frame write times expressed in seconds;
    3. File Size (KB) column contains AVI file sizes expressed in kB (base 10 unit as defined by SI);
  2. If an x264vfw codec is installed in a system, example fails with an error -1074395992 File access denied, because it tries to create a file with a name containing one of restricted characters, namely "/".
    I understand that it's just an example and doesn't account for everything, but it already has name filtering in place and could easily filter all restricted characters.

Fixed version is attached below.

 

Reported to NI with SR #7811774.

0 Kudos
Message 1 of 2
(1,314 Views)

NI Technical Support wrote:

CAR #1084594.


 

0 Kudos
Message 2 of 2
(1,239 Views)