LabVIEW
3d sound example
The link you provided explains the problem:
"If the function(s) you wish to call contains complex data types, you need to manually use a Call Library Function Node function in LabVIEW to directly call the DLL, defining the prototype within the configuration dialog (if the DLL has been compiled with a Type Library, parameter data and return types will be defined automatically). Note that if your complex data type is a struct with more than primitive data types (int, double, char), it is easiest to create a wrapper DLL from a C-based language. Since C/C++ constructs do not always directly correlate to LabVIEW data types, a wrapper DLL can appropriately extract the contents of the complex structure and translate them to primitive terms. For instance, if you have a struct in C which contains a char * (a string or character array), you can create a wrapper function which LabVIEW will call that takes in a char * type directly, puts that into a structure, and then in turn calls the DLL. Note that if you have the DLL source code, you can directly modify the DLL so that it takes in a char * instead of the struct.
Note: There is a very helpful example in the Labview Example finder that explains how to handle several different data types to be used with the Call Library Function Node. The example is named Call DLL.vi. Refer to this example when dealing with complex data types such as arrays or strucs. To Find this example go to the LabView Example Finder (Help»Find Examples) and select the Directory Structure radio button. In the directories list, select dll and then data passing then Call Native Code.llb. The Call DLL.vi example is under that directory"
C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\OpenAL32
Parsing header file warnings:
No errors/warnings occurred when parsing the header file.
The following errors/warnings occurred when generating the wrapper VIs for this shared library.
VI Not Executable
The VI is not executable because of one of the following reasons:
1. The shared library or a dependent file is not installed. To make the VI executable, you must install the shared library and all support files on the computer on which you run the VI.
2. A required custom control might be empty or cannot be found. To make the VI executable, update the custom control manually.
3. The VI contains a parameter with an unsupported data type. To make the VI executable, you must replace the empty cluster that the wizard generates with a control or indicator that uses supported data types.
alc Capture Close Device.vi
alc Capture Samples.vi
alc Capture Start.vi
alc Capture Stop.vi
alc Close Device.vi
alc Create Context.vi
alc Destroy Context.vi
alc Get Contexts Device.vi
alc Get Enum Value.vi
alc Get Error.vi
alc Get Integerv.vi
alc Get Proc Address.vi
alc Get String.vi
alc Is Extension Present.vi
alc Make Context Current.vi
alc Process Context.vi
alc Suspend Context.vi
Jennifer_R,
I see the custom controls you are talking about. Unfortunately I have no idea how to add elements or what I would add? Sorry I just never made custom controls before.
Maybe someone could help me out in this respect.
Regards,
-SS
Thank you for explaining this a different way. I did find the files that correspond to ALCdevice and ALCcontext, or at least the files I suspect Labview is using.
I also decided to include the source provided direct from OpenAL.org if you would like to help, or at least continue to point me in the right direction.
I believe they are openal-0.0.8\src\al, alc_device.h, alc_device.c, alc_context.h, and alc_context.h.
Regards,
-SS
