Nothing is more important to us than making a product that everyone enjoys. We use only the best commercial codecs and stable development platforms to ensure that users have a good experience.
In rare cases, user computers are configured in a way that prevents DashWare (and similar video publishing applications) from operating well. Below are steps that have been used by customers to resolve their issues. The most common fixes are listed first. Please contact Support if they do not resolve yours.
- Use the video file created by your camera. If you want to use another video editor, please do it after adding the gauges.
- Install the latest version of DashWare. It can be found and installed for free from our Download page.
- Update your video drivers.
- Run Windows Update. If you choose to not install all available updates, please install any related to .NET and video display.
- Uninstall QuickTime and then install the latest version. We don’t know why this works but it does. Make sure to uninstall instead of just performing an update.
- Update the software that came with your camera. Uninstalling first is not necessary.
- Run the Windows Media FixIt http://support2.microsoft.com/mats/windows_media_player_diagnostic/.
- Install the Full version of the K-Lite codec pack. NOTE: There are ads for other software on this page that look like download links. Please only download using the link that says Download@MajorGeeks. Once it is installed, please run the Windows Fixit listed above again.
Many customers run DashWare on their Mac using Boot Camp, Parallels or VMWare. Boot Camp is the most popular because it free with recent Mac OS versions.
Apple provides very good instructions at http://support.apple.com/kb/ht1461. DashWare runs on all versions of Windows from XP through Windows 8.1. If you do not already own a copy of Windows, your friends or IT guys at your office probably have extra copies laying around.
Please know that we understand that having a native Mac version would be preferable. At this point, our company is not big enough to support two operating systems. If we ever release a Mac version, we will make sure that any DashWare licenses that you own are transferable.
We hope you enjoy DashWare and look forward to seeing your videos.
Yes. This may sound a overly confident but we have two things on our side. One, logger software and hardware vendors need their customers to be able to use the data they create in order to be valuable. Two, we have been doing this for over five years. There are times that we needed to be creative like with ContourGPS when we had to pull the data out its video stream but these are exceptions.
We recommend saving data from your logger into one of these popular formats: GPX, TCX, FIT or NMEA.
If these are not an option, export your data as a CSV file. From within DashWare, you can easily open the CSV and tell DashWare about the data and save a profile for future imports.
Below is a sample of loggers that we support. The full list of loggers and software that customers use with DashWare would fill our entire website.
APM 2.5/2.6 (using Flytrex)
Blade 350 QX (using Flytrex)
ChaseCam (we auto-extract data from their video files)
ContourGPS, Contour+, Contour+2 (we auto-extract data from their video files)
DashWare iOS Logger
DJI Naza (using Flytrex)
DJI Phantoms (using Flytrex or Vision Plus Utility iOS/Android apps)
DL1 – Race Technology
Garmin VIRB Camera
G2X – Racepak
GoBandit (we don’t auto-extract their data, but we support their NMEA data
Harry’s Lap Timer
Sony Action Cam GPS — HDR-AS30V/B
Suunto Ambit Watch, Foot Pod, and Heart Rate Monitor
Ultra GPS Logger
Vision Plus Utility iOS/Android apps
Here are some notes on making a DashWare-friendly CSV data file:
-It’s good to have a static line of text at the top declaring that it is your data format. Something like “Some Cool Logger Data File”. The DashWare Data Profile for your format can then be easily set up to automatically detect one of your data files.
-We require a CSV header line: A line of text containing the column headers/names.
-Then the raw data lines would follow after that.
-There should be a Time column (full timestamps work great, e.g. “2011/08/07 20:10:02.200”, or the total running time in seconds e.g. “1.1”)
-Latitude and Longitude should be in +/- decimal degrees
-Be consistent with your data units, or at least change the column name when you use different units. DashWare can be used to create calculated data columns for other units.
You will then need to make a Data Profile that understands your format. Bring up the Data Profile Editor (File Menu > Edit Data Profiles…) and press F1 for detailed help. Tips:
-The column mappings (bottom right area of dialog) are used to map your column names to known DashWare data types. Set up the mapping for your time column first, so you can use the “Test File / View Data…” button. It is very handy. “
-To get a map to show up, you need to use our “Degrees to Cartesian Converter” (calculators/converters are in the bottom left area of dialog) to create X and Y units in feet. You must map these new X and Y output columns to our “Positional \ Longitude / X Position (Feet)” and “Positional \ Latitude / Y Position (Feet)” data types.
Have a look at an existing data profile, such as the GPX one, as an example.
For the DashWare community, we have a Facebook page:
And there is an unofficial Google+ community:
Changing DashWare to handle arbitrary text fields is actually a very big change. All of the code is optimized for handling, and storing numbers.
Here is a way you can work around it:
We have a component type called “Digit”. The Digit component is really meant for letting you make your own numerical digits in image files, then using the Digit type to display them.
You get to specify an image file for every digit, 0 through 9. Normally your image files would show digits, but they can really show anything you want. What you can try is… instead of using text values in your CSV file like “motor burn-out”, you can use a number to specify the state.
0 –> motor burn-out
1 –> parachute deployment
2 –> landing
Create an image file for each state that shows the state’s text value. The appropriate one will be displayed by the Digit component, depending on the numerical state value.
If you have more than 10 states, you can use 2 digit components placed over top of each other. One will handle the 0000001.0000000 digit position, the other can handle 0000010.0000000.
In your first Digit component, 0 would be a blank/fully transparent image, 1 through 9 would handle the first 9 states.
In the second Digit component, 0 would again be blank, and 1 through 9 would handle 9 more states.
And so on.
So state 00 in the CSV would mean nothing is shown.
State 01 would mean Digit component 1’s first state would be shown, 09 would be the last.
State 10 would mean Digit component 2’s first state would be shown, 90 would be the last.
The Google/Bing Maps license pricing makes it impossible for small companies to use their maps API in a pay-for PC application. Hardware manufacturers can get around it by having free software to go with their hardware.
However, as a workaround, you can take a screen capture of a Google/Bing map. Then add it as an Image Component behind a Map Component. It takes a little tweaking to size it properly, and line it up. But the result is cool. Here’s an example:
Double click on the NAME of the gauge (in the project tab) that and this will bring up the Gauge Input Mapper dialog. Here you can manually assign data file channels to gauge inputs.
How to make ground based altitude–it will be a single step at the start of every project for you:
-Figure out what the ground altitude is (for example, 750 meters)
-Make a clone of the data profile you are using, so that you can edit it. This can be done in the Data Profile Editor (File Menu > Edit Data Profiles…)
-In this clone add a Math Calculator (bottom left area) that takes the Altitude in meters and subtracts 750. Call this new channel “Ground Based Altitude”, or whatever you want.
-Map your new channel to our appropriate “Positional \ Ground-Based Altitude” type, based on your desired units.
-Save the new data profile.
Every time you make a change to a data profile, or want to use a different data profile in a project, you need to remove then re-add your data file to the project. So re-add your data file to your project and select your new cloned data profile.
Add a gauge to your project that shows ground based altitude, or edit an existing gauge and change the gauge’s input data type to ground based.
How to make blue/green screen, gauge-only videos with DashWare:
-Add your video and data files to the DashWare project like usual: synchronize, set up your gauges how you like, etc
-Once you are ready to export, create a new “Green Screen” gauge. In this new, empty gauge add a Filled Rectangle component with the dimensions of your video (e.g. 1920 by 1080). I use a bright, neon green color for the fill. You want to pick a color that you are not using in any of your other gauges.
-Put this new gauge behind all the other gauges in your project and it will cover up your source video.
-Export and now you will have a green screen video with only gauges.
-In your favorite video editor use a chroma key filter to turn the green screen parts of the video transparent and presto you have a transparent video with your gauges.
To synchronize, locate a spot in the video that corresponds to a spot in the data. The slider below the video moves through video time, the slider in the Synchronization tab moves through the data time. I find the easiest is to look for where you first start moving in the video. Then locate where the speed first starts going up in the data. Click the “Sync with video” checkbox in the Sync tab to sync them together. Playback your video. If the data looks a little off, uncheck “Sync with video”, adjust, and then recheck “Sync with video”. You can make fine adjustments with the < and > buttons on either side of the play button (below video or in sync tab). By default they move by 0.1 seconds. Holding Alt makes them move by 1 second.
You have a camera, now you just need a data logger to gather data to power the gauges. We support data from smartphones and almost every logger on the market.
We have a free iPhone data logger app you can get here:
Have you tried uninstalling and reinstalling? Are you installing as one user and running as another? If you right click on the DashWare shortcut and run as Administrator, does that make it work?
For m2ts support often times you need to install a directshow filter to decode the audio. I use ac3filter (http://www.ac3filter.net/). Exit DashWare, install the ac3 filter and then use mp4 output.