FoxBurner SDK is a CD, DVD and Blu-ray burning and recording software development kit. FoxBurner SDK is cross-platform, and offers a well-rounded and flexible API for fast and easy implementation of different burning and recording solutions. If you are looking for burning or recording SDK to be added in your application, you are at the right place. Since 2000 we offer with the FoxBurner SDK a wide API to C++ (MSVC, QT, Eclipse, GCC) as well as an Delphi API and an API to the new FireMonkey framework for Windows and Mac. Today the FoxBurner SDK powers many applications within the health, goverment, law enforcement, data security and other industries.

Features:

Widely used premiere burning / recording engine that has been developed and optimized since 2000.
Trusted by established leaders in major industries and across the world like Microsoft, Bitdefender, Mercedes Benz, Bosch, General Electric, Orion Health and many more.
Burns M-Disc
Burns High capacity Blu-ray (BD-XL) media
Burns standard Blu-ray Disc (BD-R, BD-RE, BD-R DL, BD-RE DL)
Burns Double Layer DVD media (DVD+R DL and DVD-R DL)
Burns standard DVD media (DVD-R, DVD+R, DVD-RW, DVD+R, DVD-RAM)
Burns standard CD media (CD-R and CD-RW)
Managed API for Microsoft .NET Framework 4.5, 4.0, 3.5, 3.0
Native C++ UNICODE/UTF-16/UTF-8 API
Native 64Bit / 32Bit API
FireMonkey and VCL API
Runs on Mac OS X 10.5 and above
Runs on Windows (8, 7, Vista, XP, Server, CE)
Runs on Ubuntu, Suse, Debian (and more) Linux
Runs on Unix
Runs on Android 4.2 and above

Changes in 6.8.2:

Added GetFileAllocationTable to .Net component and sample.
Fixed the bug in .NET wrapper when CompareFilesForArrangementEvent is invoked with wrong arguments.
Fixed the issue in COM object that causes a memory leak and may cause a crash in an application that uses FoxBurner COM object.
Fixed the issue when an attempt to burn on a rewritable medium with auto-erase enabled results in “Selected project type is incompatible with session being imported” error, if the RW medium is not empty and already contains a file system different from the file system being burned.
Use direct disc reading for verification of the burned files instead of OS file I/O functions. This lets us to not release the disc to operating system prematurely after a burn, thus preventing conflicts.
Set maximum value of “Retry Count” spin controls in Utilities sample to 300, because the default value of 100 is less than returned by default by some drives.
Fixed the issue when not all burned files are reported by BurnFileEvent and VerifyFileEvent.

Home:

http://www.ifoerster.com

ONLY for V.I.P