Running StreamPix/Hermes API/TroublePix under Windows 64 bit.
It's possible to run the 32 bit version of
under a 64 bit OS.
Both 32 and 64 bit versions of
can be installed and run on a 64 bit Windows.
needs to connect to a camera or frame grabber for acquiring images,
more considerations have to be taken into account:
32 bit edition, you have to make sure that the 32 bit driver for
the specific camera or frame grabber is installed and able to run in 32 bit mode under a 64 bit OS. Not all camera /
frame grabber drivers support this mode. Typically, running the 32 bit application provided with the camera will
help you figure that out. If the application cannot connect and capture from the camera,
will not work either.
32 bit edition, if the 64 bit version of the camera driver is
32 bit edition will not recognize the camera. Rather use
64 bit edition in this case.
Typically, you cannot have both 32 bit and 64 bit camera / frame
grabber drivers installed simultaneously.
Both Version of StreamPix/Hermes API/ TroublePix 32 bit and 64 bit can be installed in a 64 bit OS, since files are in separate folders.
The camera/frame grabber is not in the Grabber Selection list.
: The driver for your camera/frame grabber is not installed on the computer or is not a version
for the driver compatibility list for our latest releases.
Or consult the "changes.txt" file, located in C:\Program Files\Common Files\Norpix, to find out which camera driver
versions are supported with your current version of the software.
was installed before the camera/frame grabber driver and libraries were installed on the computer.
Because of DLL dependencies, the driver must be there before
is installed. Simply use the
application to register the device. If you are not sure what is the name of the file that needs to be registered, simply try to register all the devices. If this doesn't fix the problem, re-installing
(only Prosilica Firewire): There is a problem with one of the SDK dependencies for the Prosilica firewire.
On some computers, it freezes the installation when trying to register it. So, for the moment, our Prosilica firewire is not
registered by default. Please use the
(NpxRegMan.exe) to register it after the installation. The name of the file to be
registered is NpxProsilica.
: There could be some incompatibilities between older and newer NorPix files or between NorPix products.
should fix this.
The camera/frame grabber won't start.
Cause 1 : The camera/frame grabber is not correctly configured. Test the camera/frame grabber with its own software
before trying in
. If it doesn't work with its software, it won't work with our product either.
Cause 2 : The version of the camera/frame grabber driver is not compatible with your current version of
Consult the "changes.txt" file, located in C:\Program Files\Common Files\Norpix, to find out which camera driver
versions are supported. Also, you can see
the driver compatibility list for our latest releases.
: There could be some incompatibilities between older and newer NorPix files or between NorPix products.
A clean installation
should fix this.
How is the GPS data saved in StreamPix?
The GPS Positioning module can be used to view the GPS data, to overlay it on the image or to burn it into the image.
Also, it allows saving the selected GPS data to a text file (comma separated values), when recording.
This is detailed in the StreamPix manual, under the GPS Positioning module section.
Also, StreamPix has the option to save the GPS information as metadata, along with the sequence file.
The metadata recording can be enabled from StreamPix settings->Metadata page->Save metadata option.
There is also a module called Metadata Display, that can be loaded to see the current metadata.
The GPS metadata can be overlaid on the image in live mode, when recording or even burnt on export.
This is detailed in the StreamPix user manual, under the Metadata Overlay module.
If loop recording with metadata is needed, there is one more thing that has to be done:
set the metadata constant size to a certain value, not zero.
This is detailed in the StreamPix user manual, under the Metadata Spy module.
Furthermore, when exporting to JPEG, using a sequence file that was recorded with GPS metadata,
the GPS info can be burnt into the image EXIF properties.
The camera/frame grabber is not working anymore.
You can reset StreamPix/TroublePix
to reload camera factory defaults values.
StreamPix: For each workspace, in Camera ribbon, select Load. In the dialog, check "Reset grabber settings", and then select OK.
TroublePix: Select Tools | TroublePix Settings -> Advanced and press "Reset grabber settings to their default values".
Then, quit and restart StreamPix/TroublePix
. It's recommended to also power cycle the camera, to have it reset to its default boot up profile and settings.
Where can I find the user manual?
The manual for
can be accessed from Help | User manual.
The documentation for
can be found under
Start menu | All Programs | NorPix | Hermes | Hermes Documentation
or using the Windows Explorer, in
C:\Program Files\Common Files\NorPix\Hermes\docs\Hermes.pdf
All our products have also a Camera installation manual that gives details about the supported devices and their features.
It can be found under
Start menu | All Programs | NorPix | Tools | Camera installation manual
or using the Windows Explorer,
C:\Program Files\Common Files\NorPix\help\Grabbers.pdf
Adobe Reader or any other PDF viewer needs to be installed to open the manuals.
How can I import the sequence files in Matlab?
The sequence files can be imported in
using a macro file.
engineers helped us develop a
for uncompressed sequence files of 640 x 480 pixels, 8 or 16 bits.
Based on this demo, other macros can be created, for different image sizes and formats.
More details about the NorPix sequence format can be found in the
Help menu, under the Sequence File Format manual.
In case of compressed sequences, the images don't have a constant size inside the sequence, so it's very difficult to
write a macro to read them properly in Matlab.
The macro file is provided as is. NorPix does not guarantee that this macro is suitable for all usage.
It is the user responsability to test the code and eventually adapt it to his needs.
Entry point not found - dll error
The procedure entry point X
could not be located in the dynamic link library DLLFile
Our products are linked with some third party dlls. Usually these are low level libraries that are needed for software performance optimization.
can be any of these third party dll files.
These 3rd party libraries are installed with our products and they can be found in the Norpix common folder.
Depending on the version of Windows (32/64 bit) and the version of our products (32/64 bit) this common folder can be one of the following:
- C:\Program Files\Common Files\Norpix
- C:\Program Files(x86)\Common Files\Norpix
It's possible that another application (let's call it AppX
) installs another version of the DLLFile
If the AppX
installer did not comply with Microsoft recommended best practice for software deployment, the file was probably installed in the c:\Windows\System32 folder. This prevents our products from loading the right DLLFile
from the Norpix common folder.
To fix this you can do a search on your computer for the DLLFile
. Rename the other DLLFile(s)
(there may be more than one) that you find besides the one located in the Norpix common folder.
Note: After renaming the other DLLFile(s)
, most probably AppX
will not work properly, reporting the same kind of error message on startup.
Possible work around:
- You might need to rename the file back before running the AppX. This would mean that you cannot run both our products and AppX in the same time.
- You might want to move the DLLFile from C:\Windows\System32 to the AppX folder where the launched exe file is located.
StreamPix freezes when launched.
This might happen with frame grabbers if the current configuration file doesn't work with the current camera.
To fix this, activate the "Scroll Lock" function of your keyboard. Start
won't connect to the
camera while Scroll Lock is on. Open "File | Hardware Settings" and go to the configuration file tab.
Replace the current file by the one made for your camera.
Click "OK". Disable "Scroll Lock" and click the "Live" button to connect the camera using the new file.
On the sequence bar, I can go past the last image (ex : 51/50).
You can always advance one image past the end. The current frame number tells what will be the ID of the next
image to be captured. So when you create a new sequence, you are at position 1/0 meaning that the sequence currently
contains no images and that the next image to be captured will be labeled "1". Pressing record or snap will always
capture at the current image position. So if you want to append more images to an existing sequence
(containing 123 frames), you would place the cursor at image 124/123 (so you aren't overwriting existing images).
Sending a Crash Report.
There are a lot of factors that can make StreamPix/TroublePix unstable. In most cases,
hardware or driver compatibility issues may crash the application. In case of a crash,
a report is built containing general information about the operating system version, processor
type and loaded modules. To help us identify the cause and fix the error, send the crash report to our
Technical Support department for further analysis and investigations.
To send us a crash report, please follow the procedure below:
1. When the crash dialog shows up, fill in the form and click Save & Send ( see picture ).
The crash report will be automatically saved in
%AppData%\Norpix\CrashReports and then sent to .
Note: please provide a valid email address.
2. If your computer is not connected to the Internet, you'll have to send us the report manually to
including a short description of what you were doing when the application crashed.
What is the hardware trigger mode and how to set it up ?
Hardware triggering means that each image exposure is triggered using a TTL trigger pulse.
The trigger pulse can be used in 2 ways, both having the same performance:
- trigger the camera directly, if the camera includes a trigger input line
- trigger the frame grabber, which will trigger the camera
If you need to synchronize multiple cameras, to acquire and expose at the exact same time, they will need to be set up in hardware trigger mode.
This will guarantee that each camera will receive the start exposure signal at the same time. Hardware triggering is usually achieved using an external pulse generator. The pulse signal is split and sent to each camera.
To set up the hardware trigger mode on the hardware side:
- Connect the external trigger source to the camera/frame grabber trigger input pin, using a cable or a wire
- Make sure the physical trigger input pin matches the Trigger Input selected in the software(consult the camera/frame grabber manual)
- Make sure the external trigger source is running at a frame rate supported by the camera/frame grabber
To set up the hardware trigger mode on the software side:
- Open the camera/frame grabber Hardware Properties->Settings page
- Look for the Trigger Mode setting and enable it
- Depending on the camera/frame grabber, you might also need to specify the Trigger Input/Source
- Make sure the Trigger Input/Source matches the physical trigger input pin that receives the external trigger pulse (consult the camera/frame grabber manual)
- For frame grabbers, you might need to use a different configuration file, which is specifically designed for trigger mode
If the camera/frame grabber is properly set up in trigger mode, its frame rate should match the frequency of the external pulse generator.
Any change in the external trigger source frequency should reflect in the camera/frame grabber frame rate.
Also, if the external pulse generator is stopped, the camera/frame grabber should display no image.
Some frame grabbers (BitFlow, Solios, Radient, ImperX, Xcelera) have support for an internal pulse generator, which can be used to trigger one or more cameras. In this case, no external trigger device is needed. Check with NorPix for more details on this configuration.
: The hardware trigger doesn't trigger events in the software, like the start and stop of the recording
(for this see the software trigger
What is the software trigger and how to set it up ?
The software or computer trigger gives the opportunity to control some events like the start and stop of a recording.
The software monitors the state of various TTL input lines and, if a certain condition is met, it triggers the corresponding event.
For example, if the computer trigger is used to start and stop the recording, the camera will send images continuously to the computer, but the software will only record those images received between the start and stop recording conditions. These conditions are managed directly by the software. The response time depends on the performance of the monitored input devices and it's usually between 1 and 5 ms.
When using this method with multiple cameras, they will start recording at almost the same time, and there could be a difference of plus or minus 1 frame in the number of recorded images. As the cameras are free running, this cannot guarantee that all cameras capture at the exact same time.
The software trigger can be set up in 2 ways:
To set up the software trigger on the hardware side:
- When using one of the compatible I/O external devices, make sure the device is connected to the computer and properly installed.
- If you are using the camera/frame grabber TTL input lines, you will also need an external device (any device) that can change the state of the TTL input line (usually a switch between 0 and 5V). This has to be physically connected to the TTL input pin of the camera/frame grabber (with a cable or a wire).
- Make sure the physical TTL input pin matches the event input line that is monitored in the software
To set up the software trigger on the software side:
- Enable the input control and set up the event (check the software manual on this)
- Make sure the event input line matches the physical TTL input
- Make sure the camera/frame grabber is in free run, which means that the trigger mode is disabled (there are special cases when the camera/frame grabber can be set in trigger mode on a separate trigger input line)
The software trigger doesn't trigger the exposure for each image sent by the camera/frame grabber
(for this see the hardware trigger