#1 Burning Software

Hi,
I'm just starting to use StarBurn. We need to integrate CD/DVD/Blue Ray writing capability into our java application.
We use StarBurn SDK Enterprise EDITION Version 12.0.

I manage to use the JStarBurn wrapper on 32 bit machine but when i tried on a 64 bit machine (with 64 bit jre) i get the following error:

java.lang.UnsatisfiedLinkError: JStarBurn.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

Is there a JStarBurn.dll compiled for 64 bit machines?

I'm also a little bit confused about what should I include for star burn when i distribute the application. If I understand correctly I need to include the following files:

JStarBurn.jar
JStarBurn.dll
StarBurn.dll
WnASPI32.dll

My problem is that there are a bounch of StarBurn.dll's included in the distribution:
Rocket Division Software\StarBurn SDK V12 'Trident II'\Bin\Core\StarBurn Core\libcmt\Release\i386\StarBurn.dll
Rocket Division Software\StarBurn SDK V12 'Trident II'\Bin\Core\StarBurn Core\libcmt\Release\amd64\StarBurn.dll
Rocket Division Software\StarBurn SDK V12 'Trident II'\Bin\Core\StarBurn Core\msvcrt\Release\i386\StarBurn.dll
etc..
Which version should i include? Do i need to include different dll's for different processors (amd, intel).

Regards,
Czibula Istvan

Hello,

1)
link was removed

This link to updated StarBurn SDK binaries, x64 version for JStarBurn.dll included.
Please update your JStarBurn.jar, JStarBurn.dll, StarBurn.dll by files from this archive.

2)
For distribution your application must be included with JStarBurn.jar, JStarBurn.dll, StarBurn.dll and with WnASPI32.dll if you use ASPI scsi transport. In JStarBurn by default using SPTI scsi transport and WnASPI32.dll is not needed.

3)For JStarBurn wrapper you can use next core dlls:
-StarBurn Core\libcmt\Release\i386\StarBurn.dll - for x86 platform
-StarBurn Core\libcmt\Release\amd64\StarBurn.dll - for x64 platform
And you don't need to include different dll's for different processors (amd, intel).

Regards,

Trubetskoy Andrew
StarBurn Software

Hi,
10x for the update. It is working now even on 64 bit machines with 64 bit jre.

Whit the new version i have the following issue:
I use: JStarBurnBurnerGrabber.scanDevices() method to obtain the available recording devices. When i create a new JStarBurnBurnerGrabber i use the returned DeviceInfo.getDeviceName(). It's working fine but i can not figure out what is the associated drive letter for a writer. I need the drive letter because after i write a CD/DVD i want to access some files from it.
In the previous version JStarBurnBurnerGrabber.scanDevices() returned the drive letter in the DeviceInfo object. The device name contained the associated window drive letter (like f:).
In the current version the device name is something like : "cdrom0".

Is there a way to obtain the drive letter for a given recording device?

Czibula Istvan

We can add such method for getting drive letter.
How fast you need this feature?

10x for the quick reply.
I need this functionality in the current milestone. So i need it as soon as possible.

Regards,
Czibula Istvan

Here link to the build with added method getDeviceLeter() for class DeviceInfo.

link was removed

P.S.
Necessarily update all binaries from current archive (including StarBurn.dll).

Hi,
10x for the drive letter update, it's working fine.

I have another issue.
I'm writing to DVD aprox. 4500 files. The directory structure and file names on the DVD need to be different from what i have on the HDD.
I use JStarBurnBurnerGrabber.addFile(java.lang.String parentPath, java.lang.String filePath, java.lang.String fileNewName) for adding files to the DVD and JStarBurnBurnerGrabber.burnFileTree() for burning the DVD. The DVD is burned fine, but i have some performance issue.
Adding the 4500 files takes aprox. 146 seconds. (about the same if i use JStarBurnBurnerGrabber.addFile(java.lang.String parentPath, java.lang.String filePath)
If i use JStarBurnBurnerGrabber.addFile(java.lang.String filePath) the same operation takes 12 seconds. I really want to use the 3 parameter version, because i need to reorganize files on the DVD, but the performance difference seems to big. I do not see any major reason for this performance difference between the 2 operations.
If i have a really big number of files to add, the burnFileTree() method take less than the addFile part.
Is there some options to speed up this? The recorded performance is normal for this kind of operation? I suspect that the 3 parameter version of the addFile, does not scale well for large number of files.


Regards,
Istvan

Major reason is b/c we do or do not handle collisions inside the code.

Before the first invoke of the addFile I do:

JStarBurnBurnerGrabber.CollisionDetectionDisabled(true);

I think that in this scenario the addFile method should not have any processing related to the collisions.

Hello,

Please try performance with our new ISO engine.
Look sample BurnISOTree.java in java engine update which you last received.