Skip to main content

[BD-J-DEV] GRIN Mosaics / Staggered Preloading

3 replies [Last post]
Anonymous

Bill,

We currently have a show split out into several different groups of
segments. In order to minimize memory usage and load times, graphics
preloading isn't done for the entire show at once, but is instead
done for various groups of segments at logical places, for instance
where there's a change in PlayLists.

My reading of the docs for the mosaic builder indicates that the
entire show will be parsed to create one mosaic image.

Does this imply that the entire image will be loaded into player
memory immediately, obviating our staggered preloading configuration
in the show file? Or will the mosaic builder recognize which graphics
are preloaded separately and create multiple mosaics?

Cheers,
Joe

---------------------------------------------------------------------
To unsubscribe, e-mail: bd-j-dev-unsubscribe@hdcookbook.dev.java.net
For additional commands, e-mail: bd-j-dev-help@hdcookbook.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Bill Foote

Joe Rice wrote:
> Bill,
>
> We currently have a show split out into several different groups of
> segments. In order to minimize memory usage and load times, graphics
> preloading isn't done for the entire show at once, but is instead done
> for various groups of segments at logical places, for instance where
> there's a change in PlayLists.
>
> My reading of the docs for the mosaic builder indicates that the entire
> show will be parsed to create one mosaic image.
>
> Does this imply that the entire image will be loaded into player memory
> immediately, obviating our staggered preloading configuration in the
> show file? Or will the mosaic builder recognize which graphics are
> preloaded separately and create multiple mosaics?

It won't figure it out automatically - that is something I'm
thinking about for the future. But, for now you can do
it manually. It's called "mosaic_hint", which is a structure
in the show file that says "please group these images together in
the same mosaic."

I do this in the book menu xlet - the spinning yinyang image is
grouped in one mosaic, so I can show the "Loading" image more
quickly. It looks like this:

mosaic_hint loading 600 600 {
Graphics/Menu/Load_0000.png
Graphics/Menu/Load_0001.png
Graphics/Menu/Load_0002.png
Graphics/Menu/Load_0003.png
Graphics/Menu/Load_0004.png
Graphics/Menu/Load_0005.png
Graphics/Menu/Load_0006.png
Graphics/Menu/Load_0007.png
Graphics/Menu/Load_0008.png
Graphics/Menu/Load_0009.png
Graphics/Menu/Load_0010.png
Graphics/Menu/Load_0011.png
Graphics/Menu/Load_0012.png
Graphics/Menu/Load_0013.png
Graphics/Menu/Load_0014.png
Graphics/Menu/Load_0015.png
} ;

Cheers,

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: bd-j-dev-unsubscribe@hdcookbook.dev.java.net
For additional commands, e-mail: bd-j-dev-help@hdcookbook.dev.java.net

Joe Rice

Bill -

When hinting is done in this way, will only the mosaic(s) necessary
for any given segment be loaded at the time the segment is activated?

I just hinted a show which has three distinct feature groups used for
preloading. The files for each are in separate mosaics. Reviewing
player logs, it looks like all of the mosaics might be read in when
the show is initialized rather than when a segment which sets up or
activates the associated preload feature is activated.

Cheers,
Joe

On Jul 24, 2007, at 10:47 AM, Bill Foote wrote:

> Joe Rice wrote:
>> Bill,
>> We currently have a show split out into several different groups
>> of segments. In order to minimize memory usage and load times,
>> graphics preloading isn't done for the entire show at once, but is
>> instead done for various groups of segments at logical places, for
>> instance where there's a change in PlayLists.
>> My reading of the docs for the mosaic builder indicates that the
>> entire show will be parsed to create one mosaic image.
>> Does this imply that the entire image will be loaded into player
>> memory immediately, obviating our staggered preloading
>> configuration in the show file? Or will the mosaic builder
>> recognize which graphics are preloaded separately and create
>> multiple mosaics?
>
>
> It won't figure it out automatically - that is something I'm
> thinking about for the future. But, for now you can do
> it manually. It's called "mosaic_hint", which is a structure
> in the show file that says "please group these images together in
> the same mosaic."
>
> I do this in the book menu xlet - the spinning yinyang image is
> grouped in one mosaic, so I can show the "Loading" image more
> quickly. It looks like this:
>
> mosaic_hint loading 600 600 {
> Graphics/Menu/Load_0000.png
> Graphics/Menu/Load_0001.png
> Graphics/Menu/Load_0002.png
> Graphics/Menu/Load_0003.png
> Graphics/Menu/Load_0004.png
> Graphics/Menu/Load_0005.png
> Graphics/Menu/Load_0006.png
> Graphics/Menu/Load_0007.png
> Graphics/Menu/Load_0008.png
> Graphics/Menu/Load_0009.png
> Graphics/Menu/Load_0010.png
> Graphics/Menu/Load_0011.png
> Graphics/Menu/Load_0012.png
> Graphics/Menu/Load_0013.png
> Graphics/Menu/Load_0014.png
> Graphics/Menu/Load_0015.png
> } ;
>
> Cheers,
>
> Bill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bd-j-dev-unsubscribe@hdcookbook.dev.java.net
> For additional commands, e-mail: bd-j-dev-help@hdcookbook.dev.java.net
>

[att1.html]

Bill Foote

Joe Rice wrote:
> Bill -
>
> When hinting is done in this way, will only the mosaic(s) necessary for
> any given segment be loaded at the time the segment is activated?
>
> I just hinted a show which has three distinct feature groups used for
> preloading. The files for each are in separate mosaics. Reviewing player
> logs, it looks like all of the mosaics might be read in when the show is
> initialized rather than when a segment which sets up or activates the
> associated preload feature is activated.

It shouldn't, but the key is to get the setup clause
right. Loading gets triggered when a feature containing
an image is included in a setup clause of the active segment.
Of course, if any part of a matrix is needed, the whole matrix
gets loaded.

Bill

>
> Cheers,
> Joe
>
>
> On Jul 24, 2007, at 10:47 AM, Bill Foote wrote:
>
>> Joe Rice wrote:
>>> Bill,
>>> We currently have a show split out into several different groups of
>>> segments. In order to minimize memory usage and load times, graphics
>>> preloading isn't done for the entire show at once, but is instead
>>> done for various groups of segments at logical places, for instance
>>> where there's a change in PlayLists.
>>> My reading of the docs for the mosaic builder indicates that the
>>> entire show will be parsed to create one mosaic image.
>>> Does this imply that the entire image will be loaded into player
>>> memory immediately, obviating our staggered preloading configuration
>>> in the show file? Or will the mosaic builder recognize which graphics
>>> are preloaded separately and create multiple mosaics?
>>
>>
>> It won't figure it out automatically - that is something I'm
>> thinking about for the future. But, for now you can do
>> it manually. It's called "mosaic_hint", which is a structure
>> in the show file that says "please group these images together in
>> the same mosaic."
>>
>> I do this in the book menu xlet - the spinning yinyang image is
>> grouped in one mosaic, so I can show the "Loading" image more
>> quickly. It looks like this:
>>
>> mosaic_hint loading 600 600 {
>> Graphics/Menu/Load_0000.png
>> Graphics/Menu/Load_0001.png
>> Graphics/Menu/Load_0002.png
>> Graphics/Menu/Load_0003.png
>> Graphics/Menu/Load_0004.png
>> Graphics/Menu/Load_0005.png
>> Graphics/Menu/Load_0006.png
>> Graphics/Menu/Load_0007.png
>> Graphics/Menu/Load_0008.png
>> Graphics/Menu/Load_0009.png
>> Graphics/Menu/Load_0010.png
>> Graphics/Menu/Load_0011.png
>> Graphics/Menu/Load_0012.png
>> Graphics/Menu/Load_0013.png
>> Graphics/Menu/Load_0014.png
>> Graphics/Menu/Load_0015.png
>> } ;
>>
>> Cheers,
>>
>> Bill
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: bd-j-dev-unsubscribe@hdcookbook.dev.java.net
>>
>> For additional commands, e-mail: bd-j-dev-help@hdcookbook.dev.java.net
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: bd-j-dev-unsubscribe@hdcookbook.dev.java.net
For additional commands, e-mail: bd-j-dev-help@hdcookbook.dev.java.net