FAQ

General questions

If these common questions do not resolve your problems, please contact us via our tech support area.

You can buy the DELTACAST OEM products directly from us. Please do not hesitate to fill-in our price request form to receive a quote or tell us more about your application needs.

Please fill in a price request form to receive a quote for one of the DELTACAST OEM products.

At DELTACAST, we know that providing high-quality products is not enough. First-rate customer service and high quality technical support are just as important.

When using support@deltacast.tv for your technical questions, your email gets directly into our system and visible for the key members of our team working on this. This avoids your email of getting in a personal mailbox and not be threaten right away by the right person.

Yes and probably quicker than you might expect. Our hardware and software design teams have many years of experience in designing and developing products for the digital video and broadcast field. Contact us to discuss your application/specific needs.

We aim to repair your DELTACAST board in the briefest delays. Please submit your RMA request online.

Hardware questions

If these common questions do not resolve your problems, please contact us via our tech support area.

If you are installing your DELTACAST OEM board in a new PC, PCI slots may present some mechanical resistance as the board slides into the slot. Press the board strongly but carefully into the slot.

The first issue could be that your DELTACAST OEM board is not correctly positioned into its PCI slot. In this case, turn off all power supplies and ensure that the board properly fits into the slot.

Another possible issue is that a cable (IDE cable) or PC component (RAM module) has been accidentally moved and not correctly repositioned during the installation.

The boot failure might be due to a system incompatibility. The DELTACAST OEM board has been tested on a wide range of up-to-date PCs. Make sure that your BIOS version is the latest available.

Software questions

If these common questions do not resolve your problems, please contact us via our tech support area.

As in the name, the DELTACAST products are really OEM oriented, and therefore regardless from a Demo application, no end user software is included. The SDK contains a Driver & an easy to interface API on which you can connect your application. So for running one of our OEM boards you will need to write your application yourself (helped by source code application delivered with the SDK), or use one of the software packages of one of our OEM customers.

No, the DELTACAST products are really OEM oriented for Windows applications. We decided therefore to write an appropriate Driver & an easy to interface API to propose all the standard and specific functions of our DELTACAST OEM boards. Although not having the ‘Video for Windows’ driver, for more generic Windows applications in SDI and HD we’ve a direct show filters who can run on our SDK.

No, the DELTACAST products are really OEM oriented for Linux applications. We decided therefore to write an appropriate Driver & an easy to interface API to propose all the standard and specific functions of our DELTACAST OEM boards. Although not having the V4L driver, please do contact us since we might have an alternative solution available.

The filters and documentation can be found on the download center.

Please send us an e-mail to get the latest info on this.

Please send us an e-mail to get the latest info on this.

The first issue could be that your DELTACAST OEM board is not correctly positioned into its PCI slot. In this case, turn off all power supplies and ensure that the board properly fits into the slot.

If the board is correctly positioned into its slot, please ensure that it has been at least detected by the Plug and Play of Windows. To achieve this, right-click the My Computer icon, select Properties, go to the Hardware tab and click Device Manager. There should be a Other PCI bridge entry in the device tree. Right-click this item and select Install.

Another possible cause is that you did not log-on properly to Windows. Installing a driver requires Administrator privileges. Please log-on using an appropriate account.

There could be a conflict with another board (such as a network controller). Try re-installing the driver after having removed all other non-essential boards and, once installed, re-install the removed boards.

The driver requires the presence of a specific file – *.bin - in the system32\drivers subdirectory of Windows. Please ensure that this file is present. If not, proceed with a re-installation of the driver, or copy the file from the installation CD-ROM.

The driver also requires an important amount of physical memory. The minimal memory requirement is 128Mb of physical RAM per installed DELTACAST OEM board.

If you are running over/underruns, appropriate error status are latched and are also reported by the channels status LEDs located on the bracket of the board. If this is the case, please read carefully the corresponding topics in the SDK documentation. Please also check that your PC is equipped with enough physcial RAM, fast enough storage solutions and that no other significant resource consumer application is running.

If your video channels on the DELTACAST OEM boards are locked on external reference clocks, please verify the integrity of these clocks.

Some components on the DELTA-asi board require an adequate ventilation (see the Board Operating Environment chapter). Please ensure that your PC is correctly ventilated.

If your DELTA-asi boards are well-ventilated, please browse the DELTACAST web site and check for any driver or StreamMaster updates.

DELTACAST drivers install themselves into the Other Devices category, identified by a question mark icon. This is normal and with no consequence on the actual functionalities and behaviour.

The DELTACAST drivers allocate memory buffer in the context of stream start-up. They need a special memory type suitable for DMA transfers from and to the card. Memory fragmentation may prevent Windows from providing the requested memory buffers. The solution to that problem consist in pre-allocating memory buffers during driver loading at Windows start-up. Please consult the Memory Preallocation topic of the SDK documentation for details on how to integrate that functionality.