| Known Issues in IC3 | |
|
| English | 日本語 (Japanese) |
For up-to-date information on known issues, consult the Scala FAQ web site and the Scala Technical Support web site.
Here are some specific issues:
Release 7.4 introduces the Scala System Optimizer, which adjust various Windows system settings on a Player system for optimal behavior. Many of the settings it modifies are in the Windows registry.
Some of those settings are stored per user, so the Optimizer dutifully modifies those for each user account (as well as for the template that is used when creating new users). However, the tool can only modify "local machine" accounts, plus the currently logged-in user. The settings for any other "domain accounts" cannot be modified by this tool, and are therefore not touched.
Starting with Release 7 Scala scripts can be saved in the Unicode UTF-8 encoding, or in the old ANSI form. Scala scripts that text from different "code pages", or that use Asian text such as Japanese, must be saved in UTF-8. Scala scripts that use a single Western code page can still be saved in the old ANSI form that is by and large compatible with older versions of IC3 (provided that other new features are not used).
Designer's Text Encoding for New Scripts setting lets you select the text encoding that should be used, and you can override the default in the Advanced... settings under Save as.... The choices are:
Note that UTF-8 ScalaScripts always have a byte-order mark (BOM).
ANSI scripts from older versions of Scala generally will work fine in Release 7 and higher. Certain rare combinations of advanced scripting techniques, that combine text variables with and text elements that use fonts from other than the default font theme, become fundamentally ambiguous under Unicode and will need to be updated.
Scala configuration files are always saved in ANSI format unless they contain values that can only be represented in Unicode. In that case, Unicode UTF-8 is used.
An InfoChannel network uses FTP paths that are based on things like player names, media file names, and so on. Starting with Release 7, these items can contain Japanese or other Unicode characters. Therefore, in a Japanese network the FTP paths will typically contain Japanese characters. For proper operation, Scala requires one of the following:
Additionally, FTP user accounts must be ASCII. Japanese account names are not part of the FTP specification and are not universally supported.
If a subscript is called from both the main script and another subscript, IC3 will not publish the script correctly. (Release 7.1 fixes the related bug of a subscript being called from multiple other subscripts.)
If a proxy server has been selected in the LAN Settings of Microsoft's Internet Options, IC3 will fall back to the Wininet FTP client, which was always used in Release 6 and earlier. To force use of the Release 7 (and up) built-in FTP client, add this to your MMOS.INI:
Microsoft's DirectX 9.0b update caused several TV Tuner capture card/driver combinations using video formats other than NTSC (NTSC-J, PAL, SECAM) to no longer initialize correctly on Windows 2000, Windows XP, and Windows Server 2003. Symptoms include loss of capture functionality and potential inability to set/retain device capture settings.
To correct this problem, obtain a hotfix from Microsoft.
WinDVD 5 can crash with the back-to-back movie playback optimizations introduced in Release 7.1. As a workaround, those optimizations can be disabled by adding this to your MMOS.INI:
(WinDVD 3 and WinDVD 4 do not have this problem. It is possible that some revision of WinDVD 5 may address the problem as well.)
Various versions of WinDVD including 3, 4, and 5 have issues with their AC-3 audio support when multiple movies are playing in parallel. Release 7.1 adds back-to-back movie playback optimizations that apply to non-overlay Movie backgrounds. These optimizations cause the second movie to pre-start before the first one is completed, and thus can trigger this problem if the movies use AC-3 audio. As a workaround, either use videos with a different audio encoding, or disable the back-to-back optimizations by adding this to your MMOS.INI:
On certain Pentium 4-based systems (technically those with a "C1" stepping, which corresponds to most Pentium 4s at 2.4 GHz or higher, but also some in the 1.3-2.4 GHz range), the WinDVD 3 component used for playing MPEG-2 files or generating thumbnails from MPEG-2 files can crash.
A patch to resolve this problem may be found on the Scala Support CD, or it can be obtained through Scala Technical Support.
When uploading large files to certain versions of Microsoft's IIS 5 FTP server, IIS appears to incorrectly retain a lock on the file for a time after the upload should be complete. This can interfere with file uploads and cause an Access Denied error (with Wininet error code 12002) to be reported. Examples of file uploads that might be affected include:
This problem appears to be corrected if IIS is updated with Microsoft's October 30, 2002 Cumulative Patch for Internet Information Service (Q327696).
Various versions of the drivers for the Netstream 2000 family set erroneous "merit" values on their DirectShow components. This can prevent advanced video playback applications such as Scala from displaying video correctly. A typical error might be:
Script "myscript.sca" played incorrectly. Script "myscript.sca", Page "<untitled>": Analyzing video format of "C:\mymovie.mpg". DirectShow Error (80040217) No combination of intermediate filters could be found to make the connection.
The Scala Support CD includes a tool called NS2KMeritFix that corrects for this. Whenever you install or update your Netstream drivers, you will need to run NS2KMeritFix afterwards.
Scala uses double- or triple-buffering to achieve smooth graphical effects. (This means the program is drawing into a different copy of screen memory than what's displayed, and then flips the new one into view in place of the old one.) On certain ATI Radeon-based systems with recent drivers, on various SiS chipsets, and on the VIA "Nehemiah" chipset, the act of waiting to flip buffers consumes a lot of CPU. This can result in sub-ideal performance, and becomes more acute with the changes in Release 6. To work around this, you can force single-buffering by adding this to your MMOS.INI:
Starting with Release 7.4, a different workaround is available for the ATI and VIA cases. This preserves the benefits of double- and triple-buffering. To enable the workaround, add the following to your MMOS.INI file:
Note:: If you have previously set XDRAW_AlwaysSingleBuffer=1 (the previous workaround), remove that before trying this new option.
This problem affects some systems where IC3 Release 4 or earlier has ever been installed. (Many systems appear not to be affected.)
When the Scala installer (Release 4 and earlier) installed the key driver, an additional driver component was selected that should not have been. On some systems, this additional component can cause 16-bit executables to fail to run. Since 16-bit executables are quite rare these days, the problem can remain unnoticed for some time. However, the Scala setup executables are 16-bit executables, and on such systems they will no longer run. The setup.exe found on our product CDs will do absolutely nothing, and any self-extracting executables such as software updates will unpack, and then do nothing.
To correct this problem, you need to uninstall then correctly
reinstall the key driver. The key driver installation program is
called HInstall.exe and can be found in the folder where
your Scala product was installed, which is often something like:
C:\Program Files\Scala\<Product>C: is the drive the product was installed to, and
<Product> is one of ICDesigner3,
ICDesigner, ICPlayer,
NetManager, NetManagerEnterprise, or
ICBroadcastServer.
Proceed as follows:
"C:\Program Files\Scala\<Product>\HInstall" /r /kp /alldrv "C:\Program Files\Scala\<Product>\HInstall" /i /kpAnother approach is described in the Microsoft Knowledge Base article Q254914.
Using the standard Windows interfaces, there is a limit of 256 characters for the path to any file. For example, files in
C:\Documents and Settings\All Users\Application DataIf you need longer limits, you will need to instruct Scala to use different folder locations, for which you can use folders having relatively short paths:
WIN32_RootDataFolder to a folder having a
relatively short path.
Caution: when setting
WIN32_RootDataFolder or any other path, you need to
ensure that the correct accounts have suitable read/write privileges
in those locations. Under Windows 2000, not all users have write
permissions to all locations. Be sure you test under the actual
accounts your system will be logged in under (e.g. the player
account) — if you only test under Administrator you may
not notice a problem because Administrator may have greater
privileges.
The IC3 Network Manager Enterprise Edition and the IC3 Broadcast Server can send email programmatically to an address you configure. Prior to Release 7, this was done using the Microsoft MAPI interface, which meant that the mail server settings were set in the email client program (e.g. Outlook) that was the MAPI mail-handler.
Since the MAPI solution had various problems, IC3 starting with Release 7 sends mail directly via SMTP. Therefore you must now configure various mail server settings in the options/settings for these products:
Scala's IC3 products must be installed from an account with Administrator privileges. Although we try to check for this and display an informative dialog if the account is not an Administrator, on certain systems the following obscure message appears before we get the chance:
Setup has detected that uninstallShield is in use. Please close uninstallShield and restart Setup. Error 432.
The correct interpretation of this message is that the account does not have the required privileges. Log in under a different account and try again.
