script2disc can run into problems if unconventional naming practices are employed. Potential problems include:
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.
/cd/GREEN/stuff.rtf
in your script, and the file is actually on HD:Assets:Green:
, you would need to alias /cd/GREEN/
to 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.
/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"./cd/GREEN/
" to "/h0/GREEN/
", and not "/h0/GREEN
". Or, in the case of Macs, "HD:Assets:Green:
", and not "HD:Assets:Green
".
Case-sensitive aliases...
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.