XStudio has been designed to be as trouble-free as possible and has been thoroughly tested. However, not every usage scenario can be anticipated. This section is intended as a starting point for diagnosing and solving problems but should not be viewed as an all-encompassing source of problem resolution.
If the difficulty you’re experiencing is not covered here, contact the dealer who provided you with XStudio first. Alternatively, you can contact dcsTools.com - see the topic on Technical Support.
Application Bugs or Errors
Bugs and errors generally fall into one of two categories - a bug, which is the application not doing something as you might have predicted it would, or an error, which is the failure of the application to run or perform a specific task altogether.
If you find a bug, report it. Every effort is made to ensure XStudio performs as expected, but there may be circumstances that were not predicted in the development of the software. See the section on Technical Support for information on reporting a bug.
If you encounter an error, you will get an error message indicating a severe failure and XStudio may terminate. Provisions are made to "catch" such errors and log the error information to a file in the XStudio application directory. The filename is XStudio.elf. Again, report any application errors you encounter. You may be asked to send the appropriate log file for analysis.
Quick Links to Specific Problems & Troubleshooting Tools
Basic Troubleshooting Steps
Before getting too far down the road in trying to find your problem, check these items to be sure your environment for running XStudio is correct and functioning properly:
1.Make sure your PC (the one on which you are running XStudio) meets the minimum hardware requirements for this application. See the section on system requirements for more information.
2.Make sure your PC is functioning properly. This is a broad statement, but suffice it to say that if your PC is suffering from "blue-screens" or is "locking up" for no apparent reason, the PC may be a part of the problem.
3.Ensure that the pathways to retrieving log files, and, if applicable, inventory files and audio files, are correct and "reachable" from your PC. If you are retrieving files from a LAN (local area network), make sure you are correctly connected to the LAN and can "see" the host file server.
4.Make sure that XEngine is started and running if you are using XStudio as a stand-alone playback system. XEngine must be launched separate from XStudio and appears as a tray icon in the Windows task bar when running.
5.If you are using a host DCS or Maestro as the host audio engine, ensure that the host system is running.
6.Make sure that you have a default printer assigned in your operating system. Some functions in XStudio might fail if you have no printers defined. These problems may at first seem unrelated to printing. Some of the dialogs in XStudio offer print capability and automatically check for a printer when the dialog is opened. Log Validation and Log Printing are examples.
|
If you feel that the absence of a printer is causing your problem and do not have or do not want a printer assigned to the PC running XStudio, one solution is to add a standard file printing device to the system. This software-only solution ensures that XStudio finds a "printer" when needed. Refer to your Windows documentation for adding such a printer (actually, print driver) and configuring it properly. A commonly-used print driver is the Microsoft XPS Document Writer, which is available as a default on operating systems from Windows XP forward. |
7.Make sure that you have adequate hard disk storage for files XStudio generates. XStudio can generate a significant amount of event data as system performance and actions are tracked throughout the day. As a default, XStudio keeps 14 days worth of daily event logs (as does XEngine) and the files can approach 3 MB in size or larger for each day's event log. Database files can also be significant in size. Depending on the number and types of audio files you are playing and whether or not they are located on a local drive, you may find that you are running short of disk space.
