Easy text report in DLL causes LabVIEW crash

I was wondering if anyone else could shed some light on this problem (it's got tech support stumped).
To date I have two build machines and three target machines that have had the same problem. I build a DLL in LabVIEW that contains the Easy Text Report vi. I also create a VI that calls this DLL function to test it out. Everything works fine on my build machines. On my target machines, however...
On the target machine I put a call library function node on the block diagram and configure it for the LabVIEW DLL I created, select the function and setup the parameters to the function. Upon clicking on OK on the configuration window for the call library function node, my hard drive access spikes for some period of time (sometimes fractions of seconds, sometimes seconds); I assume the VI inside the DLL is being loaded into memory. I then get a Windows message stating that LabVIEW needs to be shut down at which point Windows terminates LabVIEW. Removing the Easy Text Report from the DLL VI eliminates the crash. Tech support has helped narrow this down a bit -- it seems to specifically be the print portion of the report generation VIs (they sent me a DLL that creates an HTML report which had no issues).
I'm doing this in LabVIEW 8.0. To make things more interesting, I have the same code in LabVIEW 7.0 and 7.1; neither of these have any problems. I've attached the code (LabVIEW 8.0) that tech support and I have been messing with.
Any thoughts or sugestions?
Tim Stahl
Attachments:
My DLL.zip ‏10 KB

Hi DougF,
It has been a while since I looked at this stuff in detail, so I will answer from memory.
There are a number of routines that must be present for the code to work correctly. The two I am thinking about are "CINDispose" and "CINUnload".
I suspect CINUnload is missing or buggy.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

Easy text Report.VI...not so easy

I'm using LV 7.0 and when I try to use the 'Easy Text Report.VI' I get this: Error -2147319779 occurred at library not registered. in font styoe.vi->set report font.vi->easy text report.vi->untitled 1. This error code is undefined. No one has provided a description for this code, or you migh have wired a number that is not an erro code to the error code input.
I would appreciate any help on this....tks

I am not positive what is causing the issue, but here is a list of things that may fix it. I understand some look strange, but I promise I have seen them fix issues.
1.Hit ctrl-shift-Run Arrow on the Top level VI to force a recompile of the hierarchy.
2.Open up the subVI (really a sub-subVI) called Font Style.vi. On the block diagram, in the upper left-hand corner, there is a property node. Change the property node to a different property, and then back to the original "TextFont" property. Save the VI.
3.Take a look at these links Error "-2147352573 Member not found in the xxx.vi" with NI Reports VIs in LabVIEW 6.0
f/websearch/2FCAAF080951FCAB86256982007AA16C?OpenDocument�> NI Reports Doesn't Seem to Be Working Pr...
4.Re-install LabVIEW
Evan

How can I add the number of columns/row starting with the build in "Text Report" example in the LabVIEW

Hi All,
I am wondering how can I add the numbers of row and column from the existing build-in "text report"
VI ? If possible, would you mind showing me step-by-step because I am a new user and I am not familiar with the labview software.
Thanks

Hi,
Easy text Report is for saving to a file. Do you mean you just want to add the totals of two arrays and write that? In that case I would just append the totals before writing to file.
Jeff | LabVIEW Software Engineer

Easy Text Report

Hello,
I try to print out a text with "Easy Text Report.vi".
After the "Set Report Margins.vi" there is an error: Menmber not found!
What´s wrong?
Thanks, Philipp

Hi Philipp,
I had the same problem, try this:
- In the Measurement System input of Set Report Margins vi connect a constant and set it to metric or US
- In the report margin cluster try to change the default values ( I set 10mm)
In my case this worked. This problem showed up only with LV6; LV5.1 worked fine.
Good luck,
Alberto

Executable and easy text report.vi

After reading some of the knowledgebase articles and the discussion grps it sounds like I am missing somethng when I create an exe and include "Easy Text Report.vi" in my LV2012 Project. If I run the exe in the admin window of Windows 7 the test results are printed out just fine. If I copy a shortcut of the exe file over to a user window on the same machine nothing is printed. Anyone know why????
Windows 7
LV2012
Thanks...
Solved!
Go to Solution.

Doing a quick search on the forums for that error gives a lot of information. I guess that error is what the print VI throws no matter what the problem is. You can try printing to pdf as the default printer and see if the error is still happening. Try changing the default printer to the one you are using. (Maybe the 2 logins have different printers selected as default). Someone who has experienced error -41002 might be able to explain more than I can... There is a knowledgebase that talks about issues with margins, but I don't know how much help that will be. -41002 KB A few other posts appear, but nothing that would explain the difference between administrator and users permissions.

Solenoid causing LabVIEW crash?

Hi
I am using LabVIEW 8.6 with an NI-9481, 4 channel relay module (amongst others) to control a solenoid valve which opens and closes a hydraulic circuit. The relay module controls a 24V DC supply to the solenoid.
The solenoid valve is opened and the hydraulic circuit operates. Once a condition is reached, the solenoid valve is closed by LabVIEW,shutting down the hydraulics. A few seconds later, the computer restarts. To try to remedy this problem a diode was fitted, parallel to the solenoid to protect the circuit from back EMF's generated by the collapsing magnetic field in the solenoid. This reduced the problem but has not solved it.
Can anyone suggest any remedies? Could the back EMF pulse be the reason for the computer resetting itself? Or could there be another reason?
Any help would be greatly appreciated.
Many thanks.
John
Solved!
Go to Solution.

Could you be having a "blue screen of death"? Just this morning I had to solve a problem with the PC restarting itself. The error messages when Windows restarted told me nothing. I found a tip on the forum how to turn on the blue screen message. Go to My Computer/Properties/Advanced/Startup and Recovery Settings, and uncheck the box that tells the PC to restart itself. Once I did that, I saw I had a blue screen related to the serial driver for a USB/Serial port converter. That led me down the path to updating the driver and all seems to be working fine for the moment. Now why the blue screen what able to know which driver caused the problem, but Windows didn't know when it restarted, that just shows the idiocy of windows.
If you have a blue screen, this will show it and maybe give a clue as to whether you have a crash due to a driver issue or some power failure.

Iisforward.dll causing IIS crash (IIS4 and IIS5)

After having discovered SP6 breaks iis proxying on IIS5 (unsupported, I
know), I began making test preparations on an IIS4 box. I am
encountering the same problems.
I install the iisforward.dll ISAPI filter.
I create the extension mappings, .jsp and .wlforward
(if there are special IIS settings on the "home directory" page it would
be nice if this was noted)
I create the iisproxy.ini:
WebLogicHost=jubjub
WebLogicPort=7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WlForwardPath=/weblogic (I have tried a PathTrim=/weblgic here as well)
Debug=on
DebugConfigInfo=on
I restart IIS Admin service and start the Web publishing service.
A request: http://webserver/weblogic/session causes an application
error on the webserver and the request to hang. Same thing I've
experienced on IIS5. If I use SP5, I see no errors.
Anyone else experiencing similar problems?
Jesse

Acknowleding that there is a bug that causes problems with IIS is on a
different box than WebLogic, I still have a problem getting proxing by path
to work when both are on the same machine. I followed the instructions for
installing the proxy, but have not been able to get it to work at all. Did
you find anything unclear in the instructions that you could provide clarity
to that would at least get me to the same "level of working" as you are?
Thanks,
Burke
"Diogo Lemos Pereira" <[email protected]> wrote in message
news:[email protected]...
YES, we are experiencing similar problems, on a similar configuration.
We do not suffer any problems when running IIS on the same box asweblogic,
i.e., setting "WebLogicHost=localhost" in the iisproxy.ini file.
Till the moment, we have found NO workaround for this problem - WLS seemsto
be ignoring the WebLogicHost and WebLogicPort parameters in iisproxy.ini,
other than localhost and 7001 (to which it defaults).
We have reported this situation to BEA Support, it has been assigned Ref#
200240.
Follow excerpts of our report, below:
Detailed Problem Description
======================
IIS breaks when forwarding requests to WebLogic Server
installed in a different box.
The problem seems to be wls ignoring WebLogicHost and
WebLogicPort parameters in iisproxy.ini other than localhost and 7001.
Error Message/Stack Trace
=====================
iisforward.log
Thu Oct 26 18:59:07 2000 LoadPropsFromFile:
D:\cemghb\IISProxy\iisproxy.ini
Thu Oct 26 18:59:07 2000 WLForwardPath: /weblogic
Thu Oct 26 18:59:07 2000 PathTrim: /weblogic
Thu Oct 26 18:59:17 2000 ====New
Request====/weblogic/FeedServlet
Thu Oct 26 18:59:17 2000 After PathTrim, url is
'/FeedServlet'
iisproxy.ini
WebLogicHost=10.100.21.91
WebLogicPort=7001
WlForwardPath=/weblogic
PathTrim=/weblogic
Debug=ON.
Good luck
Diogo
=====================
Diogo Lemos Pereira
Java Systems Architect
WhatEverNet Computing, S.A.
Portugal
=====================
Jesse E Tilly wrote:
After having discovered SP6 breaks iis proxying on IIS5 (unsupported, I
know), I began making test preparations on an IIS4 box. I am
encountering the same problems.
I install the iisforward.dll ISAPI filter.
I create the extension mappings, .jsp and .wlforward
(if there are special IIS settings on the "home directory" page it would
be nice if this was noted)
I create the iisproxy.ini:
WebLogicHost=jubjub
WebLogicPort=7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WlForwardPath=/weblogic (I have tried a PathTrim=/weblgic here as well)
Debug=on
DebugConfigInfo=on
I restart IIS Admin service and start the Web publishing service.
A request: http://webserver/weblogic/session causes an application
error on the webserver and the request to hang. Same thing I've
experienced on IIS5. If I use SP5, I see no errors.
Anyone else experiencing similar problems?
Jesse

Pasting text into indesign CS5 causes constant crashing

We have a problem with one of our computers and indesign CS5. When they paste text from any other program into indesign it crashes. It may be OK for 10 minutes or so but then crashes. This is a big job with lots of business cards and they need to copy and paste text from excel and then into indesign. She gets through 4 or 5 and then it crashes. We have deleted preferences a few times and tried pasting into text edit first but it always ends up crashing indesign. It happens when text is pasted from a pdf or word also.
Any ideas?
TR

Not a very timely reply but, I was being vexed as well with copying from one InDesign document to another. The original and the destination were both two color newsletters. I would copy an entire page and switch to the destination document to paste it. Unfortunately, once the Command-C was initiated, the swirling ball of death eventually resulted in a crash. After three attempts and restarting my computer, I tried it again but, same result.
Then, I copied only one element at a time (graphic, then a text box, grouped text and graphic...etc.) Not until I came to a single Placed EPS graphic (Illustrator EPS) did it initiate the death spiral. (I'd previously deleted all unused colors just in case)
I opened the offending file and noticed that a radial gradient contained a spot color and a CMYK mix (instead of a percentage of the same spot color). That was all it appeared to be... so far. A bit odd that THAT would hang such a powerful suite of software.
I plan to try a full page copy/paste to see if that was indeed the problem.
Computer Info: 2009 MAC Tower, 2.66 GHz Quad-Core Intel Xeon, 8GB RAM, OS 10.6.8, CS6. (and I was completely sober)
PS: I tried the full page copy/paste and, it worked without a hiccup.
Message was edited by: SlamDesi

Crash Report [@ npswf32.dll@0xd856b ]

Hello Adobe Team
can you confirm, that it is fixed with the latest dev build (11.0.1.145 or higher) ?
Crash Report [@ npswf32.dll@0xd856b ]
Thanks

64-bit:
Firefox 9.0a1 Crash Report [@ npswf64_11_0_1.dll@0x18dba1 ]
https://crash-stats.mozilla.com/report/index/bp-9e7ffe10-d31c-4b7b-abb2-ca11d2110901
I hope the next update will fix both.

Print easy text.vi doesnt work in executable

I have 3 target machines running labview 2012 on a PXIe8101controller. In my statemachine the vi prints out a report using easy text report vi ( on report generation pallet) at the end of the test. Its an executable vi on all 3 machines. On 2 of the machines it works fine. On the 3rd it hangs up when I'm logged in as a standard user. If I log in as administrator it works fine. The thing I noticed is that on the 2 machines it works on, the image is "factory..1.2.1f6" (under control panel>systems).
On the test equipment that it only works in admin mode the factory image is 1.2.4.f1. Also MAX is 5.3.1 on the one that runs fine and 5.5.0 f1 on the one that it doesn't work on. Anything I'm mssing?
Thanks.
Solved!
Go to Solution.

Maybe you can enlighten us with your solution so others may benefit. Unless it was just something silly. Then just say it was something silly.
Myself, I'd probably go ahead and post it, even if it was silly little mistake. At worst, it's a laugh on me - at best, someone else made the same boneheaded mistake I lived through and they don't have to walk in my footsteps.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

I can't append control image to report on 1 page with appended text report

I am attempting to create a report which is simply header, experiment information, and two graphs of data. I am using a Easy Text Report and Append Control Image to Report. I have successfully printed out this report, but on two separate pages. The header info is on the first page, and the graphs on the second page. This doesn't seem to be a margins problem, as the header is very brief and the graphs aren't that large either. I would like to make this into a one page report. Any help is greatly appreciated.
Message Edited by csmrunman on 01-15-2010 10:18 AM

Nevermind. I neglected to see the Append Report Text.vi. That solved everything.

Calling a DLL from LabVIEW causes crash

Okay, this is an odd one. I have searched through various posts and have found several things that were close but not quite the same.
I have a DLL. I pass to the function in the DLL two strings, each one representing an absolute path to a pair of files. I use a path control to get the paths and then convert those paths to strings. The function also has about 13 other parameters, each of which are U8's passed by reference. I have attached my VI and the DLL. I had to zip the DLL to get it a valid extension.
The function opens the file pointed to by the first string and parses information out of it. It then tries to create some temporary files in a folder that W7 considers to be a safe temporary folder. The problem is that when I run this VI, LabVIEW crashes...hard. I get the message that LV needs to close. However, before it crashes, it successfully opens the file, parses the info out of it and creates one new file in the temp folder. So, the issue seems to happen after the function mostly finishes with everything it needs to do.
One interesting note: I replaced the outputs of the path2string conversions with string constants pointing to the exact same files. Now LV doesn't crash. Instead I get an unhandled exception error in the DLL.
Next interesting note: This same procedure called from another application written in C (on another system) works fine.
Finally, I do have one advantage that most others don't: the developer of the DLL is a coworker of mine. So I have access to the source code.
My coworker feels that the function is failing "between the lines" of code. He thinks it is some type of stack overrun but can't place it.
Any thoughts?
Thanks,
Joe
Attachments:
dll_LoadConstantsFile.vi ‏15 KB
gui_confread_dll.zip ‏40 KB

Rolf, if I understood you correctly, here is the portion of the header file that declares the function:
#define
DLL_EXPORT __declspec(dllexport)
BOOL WINAPI DLLMain(HINSTANCE hinstDLL,DWORD,LPVOID);
extern
"C" DLL_EXPORT void__cdecl LoadConstantsFile(char*filename,
char*patch,
uInt8 *load_status,
uInt8 *device_type,
uInt8 *multi_bom_available,
uInt8 *hires_gain_available,
uInt8 *dcdc_bom_option,
uInt8 *bat_rail_type,
uInt8 *num_mb_genconf,
uInt8 *num_ring_presets,
uInt8 *num_dcfeed_presets,
uInt8 *num_impedance_presets,
uInt8 *num_fsk_presets,
uInt8 *num_tone_presets,
uInt8 *num_pcm_presets);
Here is a description of the function:
Constants File Reader
This is the main function that parses the constants files, collects information, and creates temporary script files. Run this FIRST.
void LoadConstantsFile(char *filename,
char *patch,
uInt8 *load_status,
uInt8 *device_type,
uInt8 *multi_bom_available,
uInt8 *hires_gain_available,
uInt8 *dcdc_bom_option,
uInt8 *bat_rail_type,
uInt8 *num_mb_genconf,
uInt8 *num_ring_presets,
uInt8 *num_dcfeed_presets,
uInt8 *num_impedance_presets,
uInt8 *num_fsk_presets,
uInt8 *num_tone_presets,
uInt8 *num_pcm_presets);
Inputs
filename
Full path and filename of constants file to be read
patch
Full path and filename of patch file to be loaded
I/O
load_status
Updated with 0 if load successful, non-zero if unsuccessful (see codes table)
device_type
Updated with value representing device supported by the configuration file (see codes table)
multi_bom_available
Updated with 1 if configuration file supports the multi-bom format, 0 otherwise
hires_gain_available
Updated with 1 if configuration file supports the hires gain format, 0 otherwise
dcdc_bom_option
Updated with DCDC BOM Option of
default General Configuration detected (see codes table)
bat_rail_type
Updated with Battery Rail Type of
default General Configuration detected (see codes table)
num_mb_genconf
Number of general configuration presets detected (if multi-bom is supported)
The items marked as "inputs" are meant to have something passed in as a value. The parameters marked as I/O are meant to have a pointer to them passed so the function can modify the values (passed as reference).
The function simply opens the file at "filename" and parses out the info to update the other U8 parameters. The file pointed to by "patch" is simply opened to verify it exists and then closed.

Deny Access function with invalid file refnum causes LabVIEW to crash

Hi folks,
I have LabVIEW 8.5, and today encountered something interesting that consistently causes LabVIEW to crash. Essentially, if you find the "Deny Access" function under the advanced file IO palette and wire up an invalid refnum, Windows (XP in my case) reports that LabVIEW has to close. I checked in task manager, and the LabVIEW process is still active and using a disproportionate amount of the CPU.
To reproduce the issue, simply drop the function on your block diagram, create a constant from the refnum input terminal, and run the VI. Has anyone else seen this behavior?
Thanks,
Jim

Hi Carla,
I'm glad to help, and thanks for looking into it. The way I ran into the bug was while I was working on an action engine VI to log certain text values (see attached picture). While logging, I didn't want other programs to access the file. When a new file had to be generated, I wanted to stop denying access and close the reference. However, if the value on the shift register was invalid, LabVIEW crashed instead of throwing an error (I guess a crash qualifies as an error).
If you look at the attached picture, my workaround was to use the "Not A Number/Path/Refnum?" function. If the reference is bad, I don't try to use the "Deny Access" funtion or close the file. That worked just fine and seems like a good solution for now.
Jim
Attachments:
Logger.png ‏6 KB

Labview crash on lvdaq.dll

Labview 7.1 crashes when dropping any Traditional Daq on diagram. Traditional daq version 7.3.
Mass compile crashes when lvdaq.dll is displayed, have removed and reloaded traditional daq
Any ideas ?
thanks
Mike

Hi Mike,
Thank you for posting to the NI Forums! I have searched out database and have not found any reported issues with Traditional DAQ causing LabVIEW 7.1 to crash. Traditional DAQ version 7.4.4 is the latest version that is compatible with LabVIEW 7.1 I would recommend upgrading to this version to see if this fixes the problem. Be sure to read the readme for this version of Traditional DAQ as there are some specific installation instructions. Hope this helps! Let me know!
Regards,
Margaret Barrett
National Instruments
Applications Engineer
Digital Multimeters and LCR Meters

ImageRenderer.dll Causing PP CS5.5 to crash.

I'm working on a project that is starting to make me think maybe it wasnt worth buying PP CS5.5 The most Important project of my life and it keeps crashing. I shall explain more.
Im working with footage taken on a ProHD camera Info below:
Type: QuickTime Movie
File Size: 3.5 GB
Image Size: 1920 x 1080
Frame Rate: 25.00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:13:53:19
Average Data Rate: 4.2 MB / second
Pixel Aspect Ratio: 1.0
QuickTime Details:
Movie contains 1 video track(s), 1 audio track(s) and 1 timecode track(s).
Video:
There are 20844 frames with a duration of 1/25th.
Video track 1:
Duration is 0:13:53:19
Average frame rate is 25.00 fps
Video track 1 contains 1 type(s) of video data:
Video data block #1:
Frame Size = 1920 x 1080
Compressor = XDCAM EX 1080i50 (35 Mb/s VBR)
Quality = Normal (3.00)
Temporal = Normal (3.00)
Audio:
Audio track 1 contains 1 type(s) of audio data:
Audio data block #1:
Format = 16 bit - Stereo
Rate = 48000 Hz
Compressor = 16-bit Big EndianC
Timecode:
Timecode track 1 contains 1 type(s) of data:
Timecode data block #1:
Start Time = 09:37:17:07
Reel name =
When playing back this footage on VLC it works fine and there are no obvious errors or anything strange going on. Playing back in PP was fine when I started the project however once I had aligned 3 cameras, nested them and made a new sequence, dragged the nest across so I could use MultiCam I got my first crash; So I decided to restart the project and just import the one video file which you see above. I cannot play back this file without PP crashing. It crashes generally around the same time code each time. Crash details below:
Faulting application name: Adobe Premiere Pro.exe, version: 5.5.2.0, time stamp: 0x4e960e56
Faulting module name: ImageRenderer.dll, version: 5.5.2.0, time stamp: 0x4e95f50d
Exception code: 0xc0000005
Fault offset: 0x000000000014c59d
Faulting process id: 0x1918
Faulting application start time: 0x01cd094fe9a5fad9
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5.5\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CS5.5\ImageRenderer.dll
Report Id: 38e19277-7545-11e1-8746-bcaec52105c2
Fault bucket 48268580, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Adobe Premiere Pro.exe
P2: 5.5.2.0
P3: 4e960e56
P4: ImageRenderer.dll
P5: 5.5.2.0
P6: 4e95f50d
P7: c0000005
P8: 000000000014c59d
P9:
P10:
Now, I have other footage shot with the same camera, same memory card in the same location and this footage works fine in PP.
I cannot even scrub through the video slowlty as this also causes a crash. The only way I have found to solve the issue is to cut out the video at that time stamp and the video seems to play past the affected part. This obviously will not do as my entire project will have to be shot again and considering the fact that the people I was shooting will probably never return to the Uk means I cannot re shoot the video.
There is nothing wrong with the footage. So if anyone knows how tofix this or if you need more information pease let me know
PC Specs:
ACPI X64
Processor: Intel(R) Core(TM) i7 960 @ 3.20GHz 3.60GHz (Watercooled)
RAM: Corsair i7 DDR3 2GB PC12800 1600MHz (x3 or 6GB)
HDD: Samsung 1TB 32MB Spinpoint F3 HD103SJ ATA
GPU: Nvidia GeForce GTX 580 (Watercooled)
Motherboard: ASUS P6X58D-E X58 DDR3 LGA1366
Audio Nvidia HD

More information on the file. I have just downloaded MediaInfo and taken a look at the file. I hope this helps in the quest for a crash free PP.
General
Complete name                            : F:\Burp.MOV
Format                                   : MPEG-4
Commercial name                          : XDCAM EX 35
Format profile                           : QuickTime
Codec ID                                 : qt
File size                                : 3.45 GiB
Duration                                 : 13mn 53s
Overall bit rate mode                    : Variable
Overall bit rate                         : 35.6 Mbps
Encoded date                             : UTC 2012-03-22 22:50:56
Tagged date                              : UTC 2012-03-24 01:11:43
©TSC                                     : 2500
©TSZ                                     : 100
Video
ID                                       : 1
Format                                   : MPEG Video
Commercial name                          : XDCAM EX 35
Format version                           : Version 2
Format profile                           : Main@High
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Custom
Format settings, GOP                     : M=3, N=12
Codec ID                                 : xdvc
Duration                                 : 13mn 53s
Bit rate mode                            : Variable
Bit rate                                 : 34.0 Mbps
Maximum bit rate                         : 35.0 Mbps
Width                                    : 1 888 pixels
Original width                           : 1 920 pixels
Height                                   : 1 062 pixels
Original height                          : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 25.000 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Top Field First
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.678
Stream size                              : 3.30 GiB (96%)
Language                                 : English
Encoded date                             : UTC 2012-03-22 22:50:56
Tagged date                              : UTC 2012-03-22 22:50:56
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Audio
ID                                       : 2
Format                                   : PCM
Format settings, Endianness              : Big
Format settings, Sign                    : Signed
Codec ID                                 : twos
Duration                                 : 13mn 53s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 Kbps
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Stream size                              : 153 MiB (4%)
Language                                 : English
Encoded date                             : UTC 2012-03-22 22:50:56
Tagged date                              : UTC 2012-03-22 22:50:56
Menu
ID                                       : 3
Language                                 : English
Encoded date                             : UTC 2012-03-22 22:50:56
Tagged date                              : UTC 2012-03-22 22:50:56
Bit rate mode                            : CBR

Easy text report in DLL causes LabVIEW crash

Similar Messages

Maybe you are looking for