[directmusic] Re: Intro and Containers
- From: "Scott Morgan" <scott@xxxxxxxxxxxxxxxxx>
- To: <directmusic@xxxxxxxxxxxxx>
- Date: Fri, 8 Nov 2002 05:24:06 -0600
If its a streaming wave there is still a certain amount of memory reservered
for the streaming buffer (I think almost 1MB?). So actually its not
exempted, but it doens't load the entire wave either.
-Scott Morgan
http://Morganstudios.com
----- Original Message -----
From: "Ciaran Walsh" <ciaran@xxxxxxxxxxxxxx>
To: <directmusic@xxxxxxxxxxxxx>
Sent: Friday, November 08, 2002 7:19 AM
Subject: [directmusic] Re: Intro and Containers
>
> This is a bit too techy for me. There is a "Download all content" checkbox
> in the script properties which allows you to either load everything or to
> let your script control the loading. I get the impression from other
peoples
> posts on here that there may be problems with that, but I'm sure one of
the
> MS people can fill you in.
>
> I have a related question actually - if I'm using streaming WAVs triggered
> from segments, presumably these are exempted from the "Download all
content"
> setting? It would seem obvious that anything that's streamed shouldn't be
> loaded but I thought I better check...
>
> -----Original Message-----
> From: directmusic-bounce@xxxxxxxxxxxxx
> [mailto:directmusic-bounce@xxxxxxxxxxxxx]On Behalf Of Paul Stroud
> Sent: 08 November 2002 12:43
> To: directmusic@xxxxxxxxxxxxx
> Subject: [directmusic] Re: Intro and Containers
>
>
>
> Cheers Ciaran,
>
> So an application has to physically load a script file (into memory)
before
> it can call upon any of the script's routines? And anything that is
> embedded within the script file is loaded as and when the script file is?
>
> Are the referenced files automatically buffered? Or do I need to Load them
> using a command in the script?
>
> This is all a bit like cars for me; I know the principals of how it works
> and I know how to work it, but I really do not have a clue about what goes
> on under the bonnet/hood.
>
> Paul
>
>
>
> > -----Original Message-----
> > From: directmusic-bounce@xxxxxxxxxxxxx
> > [mailto:directmusic-bounce@xxxxxxxxxxxxx]On Behalf Of Ciaran Walsh
> > Sent: 08 November 2002 12:05
> > To: directmusic@xxxxxxxxxxxxx
> > Subject: [directmusic] Re: Intro and Containers
> >
> >
> >
> > Hey Paul,
> >
> > wilkommen, bienvenue ;)
> >
> > First of all, reference / embed runtime (this applies to scripts
> > too, which
> > are a kind of container in a way and my answers are referring to
> > scripts. I
> > believe that the same rules apply to containers in general though):
> >
> > It's more or less as it sounds - reference runtime points to a separate
> > runtime file, so you need to include that file along with your
> > script file.
> > embed runtime will, erm, embed the file in the runtime version of
> > the script
> > (or container) file. Try embedding a DLS collection, exporting the
runtime
> > and look at the file size - you'll see it's appropriately bigger.
> >
> > Embedding is useful if you have a single script file, and you want to
> > deliver all your content as a single runtime file. It just makes
> > everything
> > a bit more tidy.
> >
> > Referencing is useful if you want to share content between
> > different script
> > files (for different levels for example), or in my experience if you are
> > delivering changes incrementally over a remote network and you
> > don't want to
> > be checking in unnecessary extra stuff each time.
> >
> > I have also run into problems where I have a project that uses multiple
> > cross-referenced scripts. I tried various ways of embedding everything
but
> > couldn't figure out a way to do it without doubling up on shared
content,
> > and suffered from loads of bugs.
> >
> > The other situation where you don't want to embed would be if you
> > are using
> > streaming. Someone please correct me if I'm wrong but as I understand
it,
> > embedded files will always be loaded straight away - they are part of
the
> > same file after all...
> >
> > As to how non-script containers should best be used, I'm sure someone
else
> > can fill you in. I've never used them myself, but as far as I know the
> > reference / embed stuff works the same.
> >
> > Cheers,
> > Ciaran
> >
> >
> > -----Original Message-----
> > From: directmusic-bounce@xxxxxxxxxxxxx
> > [mailto:directmusic-bounce@xxxxxxxxxxxxx]On Behalf Of Paul Stroud
> > Sent: 08 November 2002 10:13
> > To: directmusic@xxxxxxxxxxxxx
> > Subject: [directmusic] Intro and Containers
> >
> >
> >
> > Hi All,
> >
> > Newbie to the list and also a little wet behind the ears when it comes
to
> > DMP. I will therefore be asking a mixture of stupid questions
> > and hopefully
> > not so stupid questions.
> >
> > So here comes the first stupid Q - Containers? What are they good for?
> >
> > It seems like they're a good way to organize your components, but what
are
> > the consequences?
> >
> > What are the correct ways to use containers? You see I don't know how
an
> > application uses the DM API, how it loads, streams or what ever.
> >
> > Advantages/Disadvantages of Embedding/Referencing?
> >
> > Cheers or Thanks (as this is an international forum)
> >
> > Paul
> >
> >
> >
> >
>
>
Other related posts:
