Sound IO run time

Hi,
I have a program which utilises the Sound I/O and Sound File functions from under the graphics and sound pallette.
I intend to build this into a distribution / installer.
When building it seems like I require the Sound and Vibration run-time engine.  I believe i am not using any components of the sound and vibration toolkit as the Sound vi's are available with the standard LabVIEW platform.  Also if this does need the sound and vibration run-time engine then it appears that there is a charge for S and V run time for each target machine.  If this is the case then this is completely unfeasable for my intentions.
Why do i need the sound and vibration run-time engine if I am not using the sound and vibration toolkit?
Do I need the run-time engine at all? (It appears that i do)
Will i have to purchase multiple run time engines if i Intend to distribute an application which uses these vi's ?
If i do have to purchase then i suppose all sound operations will have to be done third party
Craig
LabVIEW 2012

The sound card VIs are installed with Labview base. So they are not part of sound and vibration toolkit. Try to build an exe from one the sound IO examples. If this goes OK then you have a sound and vibration VI(s) some place else in the system. If you find such a VI. You may get around this by using copy the block diagram and paste into a new VI, and rebuild the connector pane. Do this also for the sub VIs.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Similar Messages

  • XFi Can't Handle more than one sound at a time?!?

    I bought an XFi Elite Pro and it was working great. Now, however, it will only handle one sound at a time. For example, if I'm playing a song in iTunes and windows makes a sound, the itunes song cuts out, the windows sound plays, then itunes abruptly cuts back in. Same thing in games. If I'm playing Warcraft the sound will cut out if Windows makes some kind of a sound.
    How do I get my card back to being able to play multiple sounds/music simultaneously? I'm running Vista Ultimate on a Quad Core system with 4 gigs of RAM.

    Sound like something messed up somehow. Maybe you can consider reinstalling the drivers again? @28.86.2.0

  • Unable to run vi with labview run time engine

    Hi All,
    I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
    When I make a call to it from Test Stand 4.1 it works lovely.
    When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
    I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
    I don't really understand! And am tearing my hair out.
    The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
    I have attached the problemVI.lvproj.
    Thanks for any advice or help.
    Matt
    Attachments:
    problem VI.lvproj ‏41 KB
    teststand.JPG ‏43 KB

    Matt,
    it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
    Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
    Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Include LabVIEW Run-Time Engine in C# Project Distribution

    I have written a software package in Visual Studio using C# which calls a number of functions from a dll which I have built in LabVIEW. I am now trying to produce an installation program for my C# package but can't quite work out how to include the LabVIEW Run-Time Engine in this installation.
    I am creating the installation program by defining a Visual Studio Deployment Project and I have added my LabVIEW dll to this. However, the dll requires the LabVIEW Run-Time Engine to also be installed on the target PC. I was hoping that there would be a set of files to implement the installation of the LabVIEW Run-Time Engine that I could include in my Visual Studio Deployment Project and do the installation of both my C# code and my LabVIEW dll (inc Engine) in one operation. Is this possible? Or do I need to produce a LabVIEW installation for my dll separately from the C# installation?
    Info:
    Development OS = Windows 2000
    Target OS = Windows XP
    C# Development Environment = Microsoft Visual Studio 2005 V8.0
    LabVIEW Version = 8.5
    Also, I am using the Order Analysis Toolkit and noticed that there seemed to be an 'Order Analysis Run-Time Engine' installed on my PC. Do I need this too?
    Thanks for any help.
    CAS

    Hi CAS,
    One way of automating the installation of the LabVIEW run-time engine is to use commands in a batch file (*.bat). These commands would be executed automatically at the same time as your distribution installer to install LVRT with your C# application. For more information on command line options, have a look at this KB. I don't have so much knowledge of C# distributions, though, so there may be a better way to approach this that someone else in the community could advise you on.
    With regard to the order analysis toolkit, you will also need this runtime engine installed. A point to note, though, is that the toolkit requires a run-time licence to be deployed in this fashion. It is now part of the Sound and Vibration Measurement Suite and needs to be licenced accordingly.
    I hope this helps!
    Best regards,
    Tom
    Applications Engineering, NI UK

  • Only one sound at a time work

    Hi
    Installed arch linux a couple of days ago and got most stuff up and running. Altho one problem I just noticed it that I can only play one sound at a time. For example, if I have music playing from mpd I don't get any sound from youtube or from urban terror only the sound from mpd will be played. I've googled some, but don't really know what to search for
    If you do have a explanation please keep the reply simple as I am still learning
    Thanks in advance
    Last edited by farner (2009-02-24 12:25:54)

    test1000 wrote:
    this might be obvious but are you using intel? the youtube and urban terror/any mmap based game is normal.see http://wiki.archlinux.org/index.php/All … nd_at_once. also from the urban terror webpage: "Urban Terror 4.1 can run on Quake 3 Arena or on the free ioUrbanTerror." if you switch to iourbanterror the alsa issue is fixed. or else you have to start any urban terror with et-sdl-sound which only works on i686.
    edit: if you check the wiki first for stuff like this you usually get a faster response and you get to use your brain as a bonus to
    I actually googled my a* of and searched the wiki, but was unable to find that site. And I do have intel, however after reading
    In Linux, only one program can play a sound at a time unless you have a soundcard that supports hardware mixing (all/most onboard soundchips don't.)
    I decided to use my pci card (a creative audigy 2 ZS). I have been having trouble before getting it to work so I thought I would use my onboard card instead. But it was fairly easy this time
    (had to disable the onboard card in the bios and change the module to snd-emu10k1) and woops it worked
    Thanks for all the help
    Last edited by farner (2009-02-24 22:33:57)

  • IMac won't boot if external hard drive running Time Machine powered on

    Upon rebooting, my iMac 3.06 GHz Intel Core 2 Duo with 4GB RAM, running OS X 10.5.4, locked up in a gray screen, the "gray screen of death."
    At the recommendation of the Apple Tech Support rep, I turned off the iMac using the power button, and rebooted with my USB and Firewire devices removed.
    The iMac boots fine with everything except my G-tech drive 1GB external hard drive running Time Machine with no partitions, attached using a Firewire 800 cable.
    If the external hard drive is on, I get the interminable gray screen.
    If I boot with the external hard drive powered off and then power it on after I'm at the Mac desktop, the disc image mounts normally on the desktop.
    I've already repaired all disc permissions and it doesn't help.
    My external hard drive has used 907 of the 931 GB true capacity. Supposedly, Time Machine removes the old files to make room for the new files.
    Time Machine itself is running properly once I get my iMac booted in this peculiar way.

    Raja,
    Do a SMC reset perhaps even a couple of times and see if that helps. Also in System Preferences + Startup Disk make sure the internal HD is selected.
    SMC RESET
    Shut down the computer.
    Unplug the computer's power cord and all peripherals.
    Press and hold the power button for 5 seconds.
    Release the power button.
    Attach the computers power cable.
    Press the power button to turn on the computer.
    PRAM RESET
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.
    Roger

  • Does labview run time engine 8.6 LVRTE86std​.exe supports DAQ?

    Due to the LONG TIME required to build an installer with exe, and this kind of DAQ issues http://forums.ni.com/ni/board/message?board.id=170​&message.id=324343&query.id=1071542#M324343
    I want to just give the user the Labview run time engine 8.6 LVRTE86std.exe  http://joule.ni.com/nidu/cds/view/p/id/1101/lang/e​n , and ask them to copy paste the exe.
    But does the LVRTE86std.exe contains all the necessary dependency for DAQ? Including the Sound and Vibration dependencies required for DAQ? Is there some document I can look up to see whether LVRTE86std.exe supports DAQ and I dont have to build an installer of my own?
    Solved!
    Go to Solution.

    No, the runtime does not include DAQmx. It does not include any hardware drivers. That is discussed in numerous posts.

  • Creating alert at run time

    Our current forms use the MESSAGE built-in to display
    error messages. When people are doing data entry and a message
    comes up, they might hit the enter key as part of their
    processing and never see the message. What we want is
    an alert-type screen that has more than one button so that
    we can place the focus on something other than OK in order
    to make it more difficult for them to miss the error message.
    Something like this:
    while key pressed != 'OK'
    loop
    display message
    end loop
    With this scheme they would have to change the focus from the
    non-OK button, ensuring that they have seen the message.
    An alert would work just fine for this. In order to make
    the integration of this new message processing easier we had hoped
    to put the creation of the alert and the loop in a .PLL file so
    the only change to the application would be to change MESSAGE to
    NEW_MESSAGE in the application's code.
    I can't find any documentation on creating alerts at run time.
    Is there a way to do that, or some other ideas on how to handle
    this situation?
    The applications run in a noisy environment, so having the
    application make a different sound might not work.
    null

    You just need one alert created in each form, rather you can reference one alert from a template and change the alert text runtime.
    Look at set_alert_property.

  • Run-time error calling TestComple​te

    Hi,
    I have a COM interface setup between TestStand and another software (TestComplete).  The two software were working and communicating well together for few month.  But yesterday I received an "error occurred calling TestComplete Library- Testcomplete in playing state."  Please see attachment.
    I have all the test scripts running on a network drive, never had a problem before.  What could be the cause of the problem?  Any help would be greatly appreciated!
    Best Regards,
    ph2
    Attachments:
    run-time error msg.doc ‏38 KB

    Hi Ph2,
    I hope you are doing well today!  As Ray has mentioned, it does seem that this error is being caused due to the current state that your TestComplete software is in when trying to communicate with it.  I am not familiar with TestComplete myself, but the specific dialog of the error, "An error occurred calling 'RunRoutineEx' in 'ItcIntegration' of 'TestCompleteLibrary'  TestComplete is already in the playing state," sounds like it might be trying to put the TestComplete program in the play state while it is already in this state. 
    The best bet would be to touch base with Smartbear as this does not look like a TestStand specific error.  I hope this helps, Ph2.  Have a great day!
    Taylor G.
    Product Support Engineer
    National Instruments
    www.ni.com/support

  • DSC 8.6.1 run-time and LV2009 executable are they working together ?

    Hi All,
    In my application  I first deploy shared variables and when they all have depleoyed the main application starts. My deployment procedure is something like that:
    0. Select first library
    1. check if  library is already running on SVE
    2. if not deploy it
    3. check next library
    Most of my variables in libraries are connected to OPC variables. OPC server is located in other computer and there is a LAN network between computers. I have noticed that when I execute my application exe only few of libraries are deployed to SVE. Eg. If I remove all processes(libraries) from SVE and start my application only 7/28 libraries are deployded. If I deploy those libraries manually from LV2009 project everything is okay. 
    On my computer is installed LV2009 development and DSC 8.6.1 run-time. Our target is remove LV2009 immediately after we have edited and tested  all our variables and libraries. Is there a potential risk that application which is made on LV2009 don't work with DSC run-time 8.6.1?  Have anyone else noticed problem when deploying variables from application exe? 
    BR, Jim 

    Meg K. B. , 
    It sounds like you are experiencing Time Stamp Counter (TSC) Drift as mentioned in the KB's for the AMD Multi-Core processors. However, according to this wikipedia article on TSC's, the Intel Core 2 Duo's "time-stamp counter increments at a constant rate.......Constant TSC behavior ensures that the duration of each clock tick is
    uniform and supports the use of the TSC as a wall clock timer even if
    the processor core changes frequency." This seems to suggest that it would be not be the case that you are seeing the issue mentioned in the KBs.
    Can you provide the exact modle of the Core 2 Duo processor that you are using?
    Ben Sisney
    FlexRIO V&V Engineer
    National Instruments

  • Enter run time in hours / mins / secs on the front pannel

    I am trying to get a pop up VI to run alongside my main program. While the measurment parts of my software run I want a VI to pop up and display the run time in hours / mins / secs. Once the main VI ends its sequence, I want the timer VI to close down again. It sounds easy and maybe it is, but can I get it to work ........... HELP !!

    I have created an example program for you (in LV 6.0). Basically a time window will popup at the start and show the runtime (calculated, so starts at 0 hours), and when you stop the Main vi the time window will close. The time is updated at every loop of the Main vi. All of this is achieved through VI server as you will see.
    I hope this helps you.
    Kim
    Attachments:
    Runtime_indicator.llb ‏39 KB

  • Missing vi.lib files in Run-Time LabVIEW 2012

    Hi
    I've got a problem executing VI's under RT in LabVIEW 2012.
    Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
    We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
    The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
    The RT Launcher is called from the CLI.
    "C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
    This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
    By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
    The system worked fine in LabVIEW 2010.
    The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
    I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
    Can anyone explain the difference and how to solve the problem ?
    Thanks
    Regards Kahr
    Certified LabVIEW Architect
    CIM A/S
    Solved!
    Go to Solution.
    Attachments:
    RT Launcher.png ‏68 KB
    Manager VI errors.png ‏35 KB

    Hi Kahr.
    It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption. 
    You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
    Separating Compiled Code from VIs and Other File Types
    The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
    With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
    The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
    The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
    1) Include the VI's in the EXE-file.
    When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change  something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
    Error 1003 When Using VI Server in a LabVIEW Application
    2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
    a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
    Go to Destinations ==> Destination Type ==> LLB.
    b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
    Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
    How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
    I have made a small example to demonstrate this:
    Example: Using vi.lib
    This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
    1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
    2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
    Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
    I hope this answers your question.
    Best Regards
    Alex E. Petersen
    Certified LabVIEW Developer (CLD)
    Application Engineer
    Image House PantoInspect
    Attachments:
    Using vi.lib.zip ‏83 KB

  • Run time engine 7.1

    I am trying to install the ELVIS system on multiple computers. LabVIEW 8.2 has already been installed on all of the computers. I am trying to install the CD that accompanied the ELVIS as well as the PCI card. However, when I install both of them and try to run ELVIS an error comes up on all the computers with "Unable to locate the LabVIEW Run-Time engine"
    please help, thanks

    When you tried to unistall LabVIEW and ELVIS in your Windows Control Panel, did you make sure to select the National Instruments folder under the list of programs first?  Also, do you have any other National Instruments software installed on your computer?  If you navigate to the National Instruments folder in Control Panel and still do not see your LabVIEW software, please e-mail or call into support.  We will be able to send you a special utility which will remove your software even if it doesn't show up in Control Panel.  It sounds like this issue would be fixed by a reinstallation.  Thanks!

  • How to drag and drop a picture at run time in a window displaying pictures?

    How to drag and drop a picture at run time in a window displaying pictures on the front panel. The main thing is that the window is displaying frames continuously?

    vivman,
    So from your description you have a picture control where you've already created an image and you'd like to drag an image around inside of the picture control. This can be done although it is going to take a significant amount of research and programming on your behalf. You can use the drag event in the event handler to find out when the drag occurs and where the cursor is. Then edit the picture as you move your mouse so that when you drop the picture gets updated.
    The even structure is a somewhat advanced topic and the drag and drop feature is one of the more advanced uses of this structure. I would search the example finder (help>>find examples) for "event" and "drag" to see how to use these events. Also you'll want to look at the examples for the picture control.
    Sounds like a cool project! Check out Darren's Weekly Nugget 10/30/2006 this topic (http://forums.ni.com/ni/board/message?board.id=170&message.id=212920). It might prove useful.
    Good luck!
    Chris C
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect

  • Adding DVM values at run time

    Hi,
    I am trying to adding domain values to DVM at run time,
    it is getting added to DVM at that movement ,bt
    when i redeploy the service I am not able to see the changes.
    so help required regarding this

    Hello
    That is the solution to his problem, by the sounds of it when he redploys his code he gets the old values (the one in his code) if he migrates it to the MDS when he redeploys it won't change. This will seperate his deployment from run time configuration values which is a good idea.
    Best Regards Tristan

Maybe you are looking for