Home Page · Up 1 Level · Site Map · Send Us Mail
script2disc naming conflicts
script2disc can run into problems if unconventional naming practices are employed. Potential problems include:
- Naming files/folders the same as OS9 device drivers
Do not name a folder/directory "h1", for instance, whether on OS9, Sun, Mac, or PC platforms. Names like these confuse
script2disc and will often cause fatal errors.
- Using the same name for different scripts/menus/assets
Every file should have its own unique name, or bad things will happen. So, even though 2 files are in different directories, do not name them the same since script2disc will ignore your hard drive directory structure when it assembles the disc image.
- Improper aliasing
Other errors can result from not properly aliasing hard drives, particularly in respect to digital video.
DV file aliasing in Script2disc
- In order to play digital video insimulation in Scriptwriter, you must green your mpeg file(s) and build it into a disc image. Burning a disc from that image is optional.
- In the
cdi_dvpl call in your script, you must call the file off the cd (or disc image) if you want to play dv in simulation. This means the path to the rtf file will be something like:
/cd/GREEN/stuff.rtf. If you are bypassing simulation (not recommended), this restriction does not apply.
- In order to build the title with script2disc, the rtf (or mmd,mpg) file must be on the hard drive. If you only have the rtf file in a green directory on a cd, you will need to use coprtf to copy it to a hard drive. Non-greened files (mmd,mpg) can be copied from cd to hard drive in the normal manner.
- If you are using an rtf file in your title build, the script calling it must reference it off the cd in your script. Script2disc assumes that anytime cdi_dvpl calls a file off of the cd, it is a greened file. Remember, though, that although the script calls the file off the cd, it actually must be on the hard drive. The aliasing syntax (Sun, OS9 platforms) or Find/Replace option(Mac,PC) in script2disc takes care of resolving this. For example, if cdi_dvpl calls
/cd/GREEN/stuff.rtf in your script, and the file is actually on
HD:Assets:Green:, you would need to alias
HD:Assets:Green:. If you try to do a build with an rtf file, and your script's cdi_dvpl calls it off the hard drive, you will get an error like "Not a valid ISO stream". This is because it has already been greened, and script2disc is expecting an ungreened file.
- If you are using an mmd or mpg (i.e. not greened) file in your title build, you cannot reference it off the cd in your script. If cdi_dvpl calls a file from anything other than the cd, it assumes the file is not greened. Therefore, the cdi_dvpl should call your file off the hard drive, e.g.
/h0/GREEN/stuff.mmd. Trying to build a title with an ungreened file referenced to the cd will give you an error like "Not a realtime file".
Other aliasing considerations:
The trailing slash ....
Be sure to include the trailing "/" (or ":" on a Mac, or "\" on a PC) for both sides of the aliasing equivalence. For example, you should alias "
/cd/GREEN/" to "
/h0/GREEN/", and not "
/h0/GREEN". Or, in the case of Macs, "
HD:Assets:Green:", and not "
Unlike MediaMogul, the path in a script2disc alias is case sensitive. This is most important when it comes to /h0 itself, but also applies to aliases made of other directories. The default alias in script2disc is /h0 to the MediaMogul directory. To use the default aliasing scheme, do not use
/H0 instead of
/h0 in any menu or script. Or, if you do, you'll need to alias
/H0 to the same MediaMogul directory as
/h0 in script2disc. script2disc will not include in a disc image all scripts, menus, or assets unless it can resolve aliases properly.
Don't alias the root...
Although script2disc should not have a problem with this, CDi Playback does not like to alias an entire drive, but rather a folder/directory on the drive. Thus simulation would not work.
·Up 1 Level
· Send Us Mail · ICDIA Main