BD-J into Scenarist

[srfscenar]

Hi!
One question for the gurus!

Lets say that a Java programmer will provide you with all the necessary jar files to import in Scenarist.
If I know correct (never actually done it) all the authoring is made by the Java developer and is implemented in the jar files?
Is that correct?

And when you import the jar files in Scenarist, import all the AV assets and subtitles, what is the next step? Is there any kind of programming into Scenarist?

Can someone please tell me what is the workflow after inserting the jar files in Scenarist?

Thanks!

[Hase99]

When the JAR- and BDJO-Stuff is ready for the project, you have to drag your jar-File into the Data tree, then include BDJO-File.
The connections of JAR-Files and videostuff, ... is ready then.

Is the security BDJ-stuff completed too?
You have to place the security file “app.discroot.crt".

The mux it.

[srfscenar]

When the JAR- and BDJO-Stuff is ready for the project, you have to drag your jar-File into the Data tree, then include BDJO-File.
The connections of JAR-Files and videostuff, ... is ready then.

Is the security BDJ-stuff completed too?
You have to place the security file “app.discroot.crt".

The mux it.

Thanks Hase99!
FYI, I only need this info just to know and not for actual use. Yet.
So, Import all the AV and Subs assets, import jar and BDJO files and thats it? Sounds so simple...
The developer i guess makes the security, right?

[srfscenar]

and one more thing,
The BD-J application (eclipse) is the software the developer uses to create the jar & bdjo files, right?

[Hase99]

Yes, using Scenarist BDJ is the answer.

Some developer who take the Scenarist BDJ Converter by using Flash.
70 % of the work is done in Flash & with the BDJ Converter, then you still need Java knowledge to complete the code...

[rik1138]

and one more thing,
The BD-J application (eclipse) is the software the developer uses to create the jar & bdjo files, right?

That's the Scenarist version of it, but any blu-ray Java environment can be used with Scenarist. There's one called Kaleidoscope, another called Do-Studio (which can make the entire disc actually, but I'm pretty sure you can use it's Java side in conjunction with Scenarist if you want to), as well as just hand-coding the Java yourself if you are so inclined... :cool:

If you have a BDJO to import, you are probably set (but you do have to know exactly how the Java was programmed with regards to what PlayLists it accesses, etc. If your Java code is trying to play PlayList 200, there better be a PlayList 200 on the disc...)

If a BDJO isn't provided, you can create it in Scenarist. It's not too hard, but if there's the slightest mistake it can prevent the JAR from being launched properly.

This is all assuming a 3rd-party making the JAR for you. If you are doing everything yourself (Java code and the whole authoring setup), then you will have all the information you need.

[srfscenar]

Thank you guys!

So, if I got it correctly there is the java developer who
can use the Scenarist BDJ utility or the Kaleidoscope or BDStudio or even write everything in script to create the BDJO and the JAR files and then there is the Scenarist author who takes all these and the actual AV and subtitle assets and just makes the links to the playlists accordingly.
Correct?
May I also ask what is exactly the BDJO and JAR files and what are the differences between them?

Thanks.

[Hase99]

I think, the links to the Playlists are done in the previous work by the Java developer.

For example, a button action of the Java menu should play the main video, then it has to refer (?) to a special playlist created in Scenarist BD.
Java producer and the Scenarist author have to communicate and have a lot of information exchange.
(I know... my English sucks...)

[rik1138]

Thank you guys!

So, if I got it correctly there is the java developer who
can use the Scenarist BDJ utility or the Kaleidoscope or BDStudio or even write everything in script to create the BDJO and the JAR files and then there is the Scenarist author who takes all these and the actual AV and subtitle assets and just makes the links to the playlists accordingly.
Correct?
May I also ask what is exactly the BDJO and JAR files and what are the differences between them?

Thanks.

Like Hase99 said, the _links_ to the PlayLists are in the Java code, the Scenarist author just needs to make sure the PlayLists exist. Like, if the 'Play Movie' button in the Java jumps to PlayList 100, the author better put the movie in PlayList 100... :cool:

The JAR file(s) is basically just a Zip file that contains all the actual Java code, xlets, classes, etc... All the programming basically. Usually graphics are stored outside this file in a separate folder as well.

The BDJO is like a permissions file. It states what PlayLists the Java code is allowed to access, languages codes for the JAR files, organization ID for the disc, application binding (which I believe can be used to leave the menus active when the disc is removed) and various other properties... In Scenarist, in the Data tree, create a new 'virtual asset'. BDJO is one of the options. Create one, click on it, and look at the properties window, you will see all the setting there. There's a Sonic Knowledge Base article that explains how to make them. Basically the BDJO tells the player exactly what to expect in the JAR folder and how it's allowed to access the disc.

Hopefully though, whoever is doing your Java programming will just supply the BDJO file. It's usually generated by the programming environment.

[srfscenar]

Thank you both for all the details!