Content overview
StreamingMedia Export (common)

• No dynamic on the slides
• Browser support
• Internet Explorer: Error message about unsafe ActiveX controls
• "Click" sound during paging in the Internet Explorer
• Copying a locally created document onto a server
• Replay: local or via server
• Integration into CLIX
• Codecs for conversion
• Codecs for replay
• Quality and resolution of the slides
• Screengrabbing clips and accompanying video
• Document can not be replayed via server
• Audio/video can not be replayed
• Problems with the HTTPS protocol
• Progress bar not always correct
• The conversion of a document takes very long
• StreamingMedia documents under UNIX/Linux
• StreamingMedia documents under MacOS
• Umlauts and/or special characters displayed wrongly if replayed over web server (Apache)
• Not supported characters or No ASCII characters resp. in path/filenames
• Error message: "Unable to find an API adapter"

RealMedia-Export

• Supported RealPlayer versions
• Bandwidth settings of the RealPlayer
• Bandwidth lower than expected
• RealPlayer notifies "Connecting...", but no replay possible from HTTP server
• Error message about full data medium

Windows Media-Export

• Supported Windows Media Player versions
• Error message in Netscape, Mozilla und Firefox - no replay possible
• Error message "Windows Media Player cannot find the file. ..." and Windows Media Player 11
• ActiveX plugins in Firefox, Mozilla and Netscape
• Black video window, even if sound can be heard
• Black video window while scrolling
• Part of a screengrabbing clip is a still image

Flash-Export

• Blocked ActiveX Controls in Internet Explorer
• Problems during replay with Flash Player 10
• No video visible if Real Player 11 is installed
• Supported audio bitrates
• Unsynchronized playback of audio, slides and graphical annotations

SCORM Support

• Which SCORM data is submitted to a LMS?
• Which SCORM data is visible in CLIX?
• Which SCORM variables are visible in CLIX?
• Used SCORM 1.3 variables

Publisher - CD Publisher

• Unerased files in the CD export
• Presentation problems with tables in HTML pages

Miscellaneous

• Error message "Could not find main class. Program will exit!

Question:

Why does it happen that during replay the StreamingMedia document remains static and shows neither slide changes nor any other dynamic? Audio and video data are replayed by an embedded Player in the RealMedia resp. Windows Media format. For this purpose, the appropriate PlugIn has to be installed in the browser.Player PlugIns have interfaces for communication with the player. This is necessary for the dynamic (slide changes, annotations, etc.) on the slides. Some browsers don't support these PlugIn interfaces (there are problems with e.g. Opera). Thus it can happen that the replay of audio and video via PlugIn works fine, but the LECTURNITY StreamingMedia document remains static without any dynamic.

Solution:

Check the installed PlugIns of your browser (e.g. type "about:plugins" in Netscape, Mozilla and Firefox) and re-install them, if they are missing.

If you have installed a new browser or an update for a browser, you have to (re-) install the RealPlayer / Windows Media Player resp. their PlugIns afterwards and you maybe have to restart your computer! This is especially true if you have installed new versions of Netscape (7.x) or Mozilla/Firefox.
Otherwise the document can remain static during replay though the PlugIns seem to be installed correctly.

Question:

Which browsers are supported by LECTURNITY StreamingMedia documents?

Solution:
Until LECTURNITY version 1.6.0.p1 the Internet Explorer and Netscape 4.x are supported.
Since LECTURNITY version 1.6.0.p2 more browser types are supported. LECTURNITY RealMedia documents can now be replayed with Netscape 6.x/7.x, Mozilla 1.x and Firefox 1.0 and higher. LECTURNITY Windows Media documents can be replayed with Netscape 7.1 and higher, Mozilla 1.4 and higher (with ActiveX PlugIn) and Firefox 1.0 and higher (with ActiveX PlugIn). (See also the PDF document Browser support in StreamingMedia documents, 4 pages, 112 KB, PDF format.)
Flash documents, which can be created since LECTURNITY version 1.7.0, can be replayed with any browser, which supports the Flash PlugIn (version 5 or higher).
Since LECTURNITY version 1.6.1.p1 Netscape 4.x is not supported any more.

Question:

During opening a LECTURNITY Streaming document in the Internet Explorer an error message appears, that an ActiveX control is unsafe and cannot be executed. Maybe a second error message about missing plugins appears and the document can not be replayed. What has to be done here?

Solution:

In the Internet Explorer plugins for RealPlayer, Windows Media Player, etc. are embedded as ActiveX controls. For the replay of LECTURNITY streaming documents the execution of ActiveX controls must be enabled in the security settings.

Check the security settings of the Internet Explorer as follows:

• Open in the menu "Tools" the dialog "Internet Options...".
• Choose the tab "Security".
• Choose the zone "Internet" and press the button "Custom Level...".
• In the new dialog "Security Settings" choose the entry "ActiveX controls and plugins".
• The sub entries "Run ActiveX controls and plugins" and "Script ActiveX controls marked safe for scripting" must be activated.
• Do the same for the "Local Intranet" zone.
• If your system is Windows XP with Service Pack 2, then check also the following security settings:
  
  • In the dialog "Internet Options" choose the tab "Advanced".
  • Search for the enty "Security".
  • The sub entry "Allow active content to run in files on My Computer" must be activated, maybe also the entry "Allow active content from CDs to run on My Computer".

Question:

Why is always a "click" sound audible during paging in the Internet Explorer? Can this "click" sound be suppressed?

Solution:

This "click" sound only appears in the Internet Explorer, in other browser no sound is audible during paging. This sound is a MS Windows default setting of the Windows Explorer and Internet Explorer resp.
To change or suppress this sound one has to open the Windows Control Panel. Open the Folder "Sounds and Audio Devices". The tab "Sounds" shows a list of sound effects associated with several actions (identifiable with the speaker icon). The "click" sound ("start.wav") is associated to the action "Start Navigation" in the section "Windows Explorer". This is the default setting. If changed to "(None)" no "click" sound is audible from now on.

Changes done in the Windows Control Panel affect the whole Windows System.

Question:

How can I copy a locally created RealMedia resp. Windows Media document onto an HTTP or streaming server afterwards?

To do so, a little "manual work" is necessary:

• First step: Change into the directory which contains the locally created RealMedia resp. Windows Media document.
• Second step: You have to change the URL (Unified Resource Locator) in at least one file. 
• The next step depends on the used server(s). On the respective server, you naturally have to have access to and write authority on the released directories.
  
  • Copy of the document onto an HTTP server: Copy all files including subdirectories into the data directory on the HTTP server.
  • Copy of the document onto a Real and an HTTP server: Copy the file(s) with the suffix ".rm" and the file with the suffix ".smi" (if it exists) into the "Content" directory on the Real server.
    Copy the remaining files including subdirectories into the data directory on the HTTP server.
  • Copy of the document onto a Windows Media and an HTTP server:
    Copy the file(s) with the suffix ".wm" into the "ASFRoot" directory on the Windows Media server. Copy the remaining files including subdirectories into the data directory on the HTTP server.

If you do not dispose of a server at the time of conversion or if you just want to avoid the manual post-editing in step two (see above), then you may proceed as follows:

• In the LECTURNITY Publisher, in the target selection dialog, choose HTTP and/or streaming server.
• In the next dialog you can determine a local directory instead of a server directory.
• In the dialog window for the URL the correct address must be entered in any case.
• After the conversion the document can be copied on the respective server(s) as described above.

Question:

What is the difference between local replay and the replay via a server?

Solution:

During the conversion, the video and audio data are written into a RealMedia resp. Windows Media file (.rm resp. .wm). The decisive difference lies in the way of how these files are called from the document. This works by naming a URL (Unified Resource Locator) which differs according to its target in the Publisher. Possible targets are: local, HTTP, Real resp. Windows Media server. If the target has to be changed, the URL can be adapted to the respective conditions.
For the change of URLs a tool named "LocationUpdate" can be used to adapt the document for the replay via a server.
This tool can be downloaded as an executable program (.exe).

RealMedia:

• Audio/video file: suffix ".rm" (e.g. My_Presentation.rm).
• Local replay: The URL might look as follows:
  My_Presentation.rm
• Replay via HTTP server: The URL might look as follows:
  MyHTTPServer.com
  MyDemoDirectory/My_Presentation.rm
  (Here, the HTTP protocol is used. The transport of the audio/video data is similar to a progressive download, i. e. the data are not really streamed.)
• Replay via Real server: The URL might look as follows:
  rtsp://MyRealServer.com:554/
  MyDemoDirectory/My_Presentation.rm
  (Here, the RTSP protocol is used with which the audio/video data are streamed. The specification ":554" is necessary and refers to the Port which is used for streaming.)

Windows Media:

• Audio/video file: suffix ".wm" (e.g. My_Presentation.wm).
• Local replay: The URL might look as follows:
  My_Presentation.wm
• Replay via HTTP server: The URL might look as follows:
  MyHTTPServer.com
  MyDemoDirectory/My_Presentation.wm
  (Here, the HTTP protocol is used. The transport of the audio/video data is similar to a progressive download, i. e. the data are not really streamed.)
• Replay via Windows Media server: The URL might look as follows:
  mms://MyWindowsMediaServer.com/
  MyDemoDirectory/My_Presentation.wm
  (Here, the MMS protocol is used with which the audio/video data are streamed. The specification of a Port is not necessary.)

Avoid whitespaces, umlauts and special characters in the names for documents and directories.

Question:

How can a converted document be integrated into CLIX®?

Solution:

Here, two cases have to be differentiated:

• HTTP-Server:
  
  • Upload of documents as ZIP-Upload via CLIX
  • No streaming in its actual sense, but a download

• Streaming-Server:
  
  • Distribution of files on CLIX and the streaming server:
    
    • the streaming files are placed on a streaming server
    • the remaining files as ZIP-upload via CLIX
  • True streaming

Hint:

In order to upload a LECTURNITY document into CLIX, an easy way is to use the SCORM feature of LECTURNITY. Such a ZIP file may then be uploaded into CLIX as a SCORM-WBT very easily.

Question:

Why are extra codecs necessary for the conversion of a RealMedia resp. Windows Media document in individual cases?

Solution:
This can happen if recording and conversion are not executed on the same computer. For the conversion of a document into a streaming format the codecs used for the recording of the video resp. audio have to be available on the used system.

Question:

Why are extra codecs necessary for the replay of a RealMedia resp. WindowsMedia document in individual cases?

Solution:

For the replay of a RealMedia resp. Windows Media document normally no extra codecs are necessary since the embedded Player already contains the required codecs for the RealMedia- resp. Windows Media format. If RealMedia resp. Windows Media documents which are created for a specific player version (e.g. Real 8 or Windows Media 7), are replayed on a system with a player of a lower version (e.g. Real 6 or Windows Media 6.4), then the missing codecs are downloaded via Internet, if necessary.  

The Windows Media player 6.4 can not replay videos with Windows media Codec 9!

Question:

How can I improve the resolution and the quality of the pages representation?

Solution:

Pages are represented by pictures in the browser (exception: Flash export). The higher the resolution the better is the quality of the pages. One constraint, however, is the maximum size of the browser window in which the pages are displayed. It also depends on the screen resolution of the used system. If the page picture does not match the browser windows it is cut off if necessary. The selection of the page resolution should depend on the used screen resolution. The default selection for the page resolution is based on the widely-used screen resolution of 1024×768 pixels.

In the LECTURNITY Publisher, the page resolution can be changed as follows: in the dialog window "Bandwidth and Quality" (RealMedia) resp. "Settings" (Windows Media) go to more setting options by clicking on the button "Advanced...". In the dialog "Pages" change the settings for the slide resolution (s. fig. 1). 

Figure 1: Dialog "Pages" to set the page resolution

Question:

How are Screengrabbing clips displayed and how do I change the resolution of Screengrabbing clips resp. of an accompanying video?

Solution:
If a document contains Screengrabbing clips they can be displayed in two ways after the streaming export: in the video area or on top of the slides - independent of the existence of an accompanying video.
In the LECTURNITY Publisher, the display mode and the resolution are set as follows: In the dialog window "Bandwidth and Quality" (RealMedia) resp. "Settings" (Windows Media) go to more setting options by clicking on the button "Advanced...". In the dialog "Video and Clips" change the settings for the the display mode and the resolution (s. fig. 2 - 5).

The two display modes for clips are:

• Clips on top of the pages: (default setting)
  
  Figure 2: Dialog "Video and Clips", Selection "Clips on top of the slides" for a document without accompanying video
  
  
  Figure 3: Dialog "Video and Clips", "Clips separated from video" selected for a document with accompanying video
  
  When converting into a streaming format this way, the Screengrabbing clips and, if existing, an accompanying video are turned into a streaming format independent of each other and are displayed separately: the video clip is displayed in the video area left of the slides while the clips are displayed on top of the slides. The resolution of the clips is adapted to the selected maximum resolution by zooming down, if necessary. By using this method, large-sized clips are less critical in relation to the used bandwidth compared to the option "Clips in video area". This is based on the fact that for the conversion resp. replay of the clips a video codec can be used which is optimized for Screengrabbing. In the case of Windows Media this codec needs much less bandwidth than a video codec.
  
  
• Clips in video area:
  
  Figure 4: Dialog "Video and Clips", Selection "Clips in video area" for a document without accompanying video
  
  
  Figure 5: Dialog "Video and Clips", "Clips separated from video" not selected for a document with accompanying video
  
  When converting into a streaming format this way, the Screengrabbing clips (and, if existing, an accompanying video) are turned into one single video with a fixed resolution. The standard target resolution for this video is set to 320×240 pixels. This video is displayed in the video area left from the slides.
  The target resolution can be changed in the dialog "Video and Clips". The resolution of the single clips will then be adapted to the target resolution by zooming down.
  The maximum clip resolution is calculated by the resolution of the single clips so that every clip can be replayed in its original resolution.
  The target resolution should not exceed 640×480 pixels since in this case the conversion will not be executed correctly, respectively the Player cannot replay the video correctly. The result is a black video window during replay. Reason: the used video codec is optimized for video records and not for Screengrabbing. The required bandwidth for the replay is too high. This affects RealMedia and Windows Media. For documents with large-screen clips it is better to use the method "Clips on top of the slides" for conversion.

Read the section Audio/video can not be replayed about this problem.

Question:

The player embedded in my document can not be started and/or leads to an error message if started. Why does the replay not work?
There can be different reasons for this problem.

Case 1:

During the replay of a Windows Media document via HTTP server and/or Windows Media Server the embedded Player breaks up immediately after a short activity. Similar things happen during the replay of a RealMedia document via HTTP server and/or RealServer. The embedded RealPlayer breaks up with the following (or similar) error message:

• "A general error occured."
• "Requested file not found."

Figure 6: Error message during replay of a locally created RealMedia document via internet

Here, one tried to make a presentation accessible via the Internet by copying a locally created Real document on an HTTP server. In the error message this is visible in the wrong path specification for the RealMedia file ("file://..."). The embedded player cannot find the RealMedia file on the server because it looks for it on the computer of the user.

A specification like "http://Demo1.rm" shows that no URL has been set at all, because there is no specification of the web address of the server.
This can also be the error cause of a Windows Media document. 

Solution:

For the replay via an HTTP- or Real server the URL has to be referenced for the RealMedia file with an absolute path definition. For corrections afterwards one can use the tool "LocationUpdate".

Case 2:
In a Windows Media document loaded from a HTTP server and/or Windows Media Server the embedded Player can not be started because the navigation elements are inactive. During the replay of a RealMedia document via HTTP server and/or RealServer the embedded RealPlayer breaks up with the following (or similar) error message:

• "A general error occured."
• "Requested file not found."

Figure 7: Error message during replay of a RealMedia document via HTTPS protocol

The documents are transmitted through a secure connection via HTTPS protocol. The embedded RealPlayer does not support the HTTPS protocol. Only version 7 and higher of the Windows Media Player supports the HTTPS protocol.

Solution:
For this read the section "Problems with the HTTPS protocol".

Case 3:

The replay of a RealMedia document works fine in the local intranet. Why does an error message appear during the replay via internet?
Reason: The data copied onto the RealServer have the wrong group rights. This can happen in particular if the RealServer is installed on a Linux or UNIX system.

Solution:

Check the group rights for the data on the RealServer and change them if necessary. Every group should have at least reading rights on the files.

Question:
Which problems can occur using secure connections with the HTTPS protocol?

• RealMedia:
  The embedded RealPlayer does not support the HTTPS protocol as mentioned in the RealForum from RealNetworks.
• Windows Media:
  As mentioned in the Microsoft Knowledge Base version 7 and higher of the Windows Media Player supports the HTTPS protocol. Until version 8 of the Windows Media Player the PlugIn of version 6.4 of the Windows Media Player is used in web sites, which does not support the HTTPS protocol. Only since Windows Media Player 9 the corresponding new PlugIn is used in web sites, which supports the HTTPS protocol. Windows Media documents created with LECTURNITY can be reviewed via HTTPS if the Windows Media Player 9 is installed, otherwise unfortunately not.

During the conversion of a document into the RealMedia or Windows Media format, the progress display for the audio and/or video is updated regularly. It might happen that the progress bar is not set at 100% after the conversion has finished with the message "Conversion successfully finished".

This has no effect and the conversion has been executed correctly.

Records which contain video and/or Screengrabbing clips require a long conversion time.

Please note: the more bandwidths you select, the longer the conversion takes! This does not only affect RealMedia but also Windows Media.

Example: If your presentation contains a video, then on an 800 MHz system the conversion may take as long as the presentation recording took, if you use the default settings for the bandwidth. 

Question:

Can StreamingMedia documents be replayed under UNUX/Linux? 

Solution:

RealMedia documents can be replayed under UNIX/Linux with a Netscape/Mozilla Browser and a respective RealPlayer PlugIn.
Windows Media documents can currently not be replayed under UNIX/Linux.

• Document type

• Web-Browser

• RealPlayer-PlugIn

*) Exception: Netscape 4.x with older LECTURNITY documents until version 1.6.1

Web browser

The Browser used must be able to communicate with the RealPlayer PlugIn via interfaces (for this see also "No dynamic on the slides"). In uur cognition this works with Netscape version 7.1 and higher and with Mozilla reap. Firefox version 1.0 and higher.
For this, according to a statement from Mozilla (see "Mozilla Plugin Support on Linux (x86)" for more details), the RealPlayer 10 must be installed and then the PlugIn files must be copied by hand into the respective browser directories (nphelix.so into the "plugins" directory, nphelix.xpt into the "components" direcory).

http://www.mozilla.org/

http://plugindoc.mozdev.org/en-AU/linux.html#RealPlayer

RealPlayer PlugIn

• Recommended version:
  The RealPlayer 10 should be installed with the respective PlugIns..
• Installation of a new RealPlayer version:
  Download the current version of the RealPlayers for UNIX resp. Linux at RealNetworks. 
• BHow to provide the PlugIns (see "Mozilla Plugin Support on Linux (x86)"):
  Copy the file nphelix.so into the "plugins" directory.
  Copy the file nphelix.xpt into the "components" directory.

Linux is not officially supported by LECTURNITY.

Question:
Can StreamingMedia documents be replayed under MacOS?

Solution:
RealMedia documents can be replayed under MacOS with Firefox resp. Mozilla version 1.0 and higher and the RealPlayer 10 with the respective PlugIn. Replay is not possible with the MacOS default web browser Safari.
Currentlly we have no information about the replay of Windows Media documents under MacOS.

(This was tested with the actual MacOS X version 10.3.7.)
 
MacOS is not officially supported by LECTURNITY.

From version 1.7.0.p3 and upwards, LECTURNITY uses UTF-8 as character encoding instead of the previously used ISO-8859-1. If special characters and/or umlauts are displayed incorrectly (e.g. "Ãœ" instead of "Ü", "ß" instead of "ß") if a document is replayed from a web server, but looks correct if replayed locally, please check the settings of your web server.

It is important that the web server does not supply a predefined character encoding in the page header in order to force the web browser to detect the correct encoding. In LECTURNITY documents, the encoding is specified in the web page. Though if the web server specifies an encoding for the page, e.g. Firefox assumes that the web server is correct and ignores the information in the page itself. This problem may specifically occur on Apache 1.3 installations, but also with Apache 2 installations which were migrated from Apache 1.3. Please check your httpd.conf for the occurrence of the directive AddDefaultCharset. This settings has to be set to off. In Apache 1.3, the default is on (which makes the web server tell the browser that all pages are ISO-8859-1-encoded). In Apache 2, the default is off (which is correct).

Not ASCII characters in the path or filename of a Web Document can cause problems, which make it impossible to replay the Document. This affects the HTML files and also the media files (*.rm, *.wm, *.swf).
During the creation of a Document it is not known in which environment (browser, server, etc.) it is used later on. So it is not predictible if the use of Not ASCII characters in this environment is possible or not (see tables). For this reason always a warning message appears in the Publisher (since 2.0.p3) during the creation if Not ASCII characters are used. If this warning is ignored then it can not be excluded that the replay of the Document is not possible. For the same reason a warning message appears after loading the Document into a web browser. The usage of Not ASCII characters is not forbidden in the Publisher because there can exist some environments in which such characters can be used and the replay is therefore possible.

The following tables show different combinations of browser, target selections and not supported characters in path or filename.

Supported characters:

• ASCII: A-Z, a-z, 0-9, -, ., _, ~, !, @, $, &, +, ,, ;, =, (, ) and blanks.

Not supported characters:

• IN_CP: All other characters inside the current codepage (e.g. ä, ö, ü, ß in the codepage 1252).
• EX_CP: All other characters outside the current codepage (e.g. Σ, š, ض, ᇩ in the codepage 1252).

Used plug-ins:

• RealMedia: Version 10.5
• Windows Media: Version 11
• Flash: Version 9

Used browser:

• Internet Explorer 6 und 7
• Firefox 2.0.0.x

Annotations to the tables:

• (1): HTML page loaded, but the plug-in does not react.
• (2): HTML page loaded, but the plug-in throws a "File not found" error message.
• (3): HTML page loaded, but the Flash plug-in shows only a blank white page.
• (4): No codepage foreign characters possible on a UNIX/Linux file system.
  
  

A. Filename contains not supported characters

• A.1 Browser: Internet Explorer

• A.2 Browser: Firefox

• B.1 Browser: Internet Explorer

• B.2 Browser: Firefox

Question:

After opening a Streaming document the following error messages appear: "Unable to find an API adapter" and "Unable to locate the LMS's API implementation. LMSInitialize was not successful." What is the cause for these messages?
These messages appear when the item "SCORM support" is selected in the settings of the LECTURNITY Publisher. In this case the document is packed into a ZIP package which can be embedded into a Learning Management System (LMS). If no LMS is used but the ZIP file is unpacked and loaded into a browser, then the error messages mentioned above appear because the document tries to contact a non-existing LMS without success.
If documents have to be used without a LMS then no "SCORM support" should be selected in the settings of the Publisher.

Solution:

If you want to turn off the "SCORM support" of an already created document, you can do it with a little hand work using a simple text editor:

• Open the file "<Targetname>.html" or "__main.html" (depending on the used design template) with a text editor ("<Targetname>" is the target output name selected in the Publisher).

• In the upper part of thet file search for the following lines:
       <script type="text/javascript">
         <!-- var g_scormEnabled = true; // -->
       </script>

• Deactivate the SCORM support by changing one line as described below:
       <script type="text/javascript">
         <!-- var g_scormEnabled = false; // -->
       </script>

Save and close the file.
If you load the document into your browser then no error message should appear again.

Question:
Which RealPlayer versions are supported?

Solution:

The RealMedia export with the RealPlayer Basic was tested successfully for the versions 6, 7, 8, RealOne, 10 and 11. Documents created by the LECTURNITY Publisher can not be replayed by older versions of the RealPlayer.
For RealPlayer 11 it has to be noted that in the settings the option "Download & Recording" has to be deactivated. Otherwise no replay of RealMedia documents is possible.
You can find out the version number of your RealPlayer by selecting the entry "Help", "About RealPlayer" in the menu line. You get the version number of the RealPlayer PlugIn embedded into the HTML page by clicking on the Player with the right mouse key. Now select the entry "About RealPlayer" in the context menu.
The following versions of the RealPlayer were tested on the replayability of the converted documents:

• RealPlayer Basic 11 (version 6.0.14.x and higher): works without problems if the oprion "Download & Recording" is deactivated
• RealPlayer Basic 10 (version 6.0.12.x and higher): works without problems.
• RealOne Player (version 6.0.10.x and higher): works without problems.
• RealPlayer Basic 8 (version 6.0.9.584 and higher): works without problems.
• RealPlayer Basic 7 (version 6.0.7.x): works without problems.
• RealPlayer Basic 6 resp. G2 (versions 6.0.3.x to 6.0.6.x): works without problems.
• Older versions of the RealPlayer do not work!

Question:

How do the settings for the bandwidth affect the replay quality in the RealPlayer?

Solution:
In the RealPlayer the settings for the normal and the maximum bandwidth can bechanged and adapted to the given environment. This is recommended, because the default values rarely correspond to the real conditions.
Example: You have a DSL connection. Too high values in the settings (e.g. T1/LAN) have no negative bearings to the replay quality. But too low values (e.g. modem) can lead to poor quality. For this read the section "Lower quality than expected". This affects also documents which are replayed locally on the own system.

Question:

How can it happen that during the replay of a RealMedia document the used bandwidth is notably lower than expected?
During the local replay of a RealMedia document or a fast Internet connection provided, a high bandwidth can be expected. However, in case the actual bandwidth displayed by the player is notably lower than expected, then this might be due to the settings of your RealPlayer.

Solution:

Check the settings of the RealPlayer as follows:

• RealPlayer 8: Click with the right mouse key into the embedded RealPlayer window. In the appearing context menu, select the entry "Preferences...". In the next dialog, under "Connection", you can change the settings for the bandwidth. The default setting for the "Normal bandwidth" is "56 Kbit/s-Modem". Adapt the setting to the bandwidth of your internet connection.
• RealOne Player/RealPlayer 10: Open the RealPlayer. Choose "Tools" in the menu bar and select "Preferences". Choose "Connections" in the settings dialog. Under the item "Bandwidth" one can change the settings for normal and maximum bandwidth. Using the button "Test Connection" one can test the actually available bandwidth and can update the settings automatically. Indeed, this test gives no information if a RealServer can stream audio/video data and which bandwidth is actually used.

Question:

Trying to replay a RealMedia document from a HTTP server, the RealPlayer notifies "Connecting..." but nothing happens or an error message "The RealMedia Plugin could not find the file referred to" appears. Why is the replay not possible?
In this case it is probable that one produced a local RealMedia document and put it on a HTTP server later on without adapting the relating URLs.

Solution:

For this please read the section Copying a locally created document onto a server.

Question:

The conversion disrupts with the error message "Encoding of the data stream failed!". As a possible reason it is stated that the data medium is full. Why does this error message appear, even if enough disk space is left on the target drive?
Possible reason: During the conversion into the RealMedia format the video/audio data are not written correctly into the target directory, but into the temporary directory first. After that the data are transferred into the target directory. This temporary directory is usually located on your system partition. The system partition contains your "Windows" directory and is normally labelled with the drive letter "C".
If system drive and target drive are not identical, then the conversion process disrupts when not enough disk space is left on the system partition.

Solution:

Check where this temporary directory is located. Either arrange for free disk space on this partition or place the environment variable for the temporary directory (%TEMP%) on a different partition with enough disk space.

You can find information on environment variables and temporary directory in the Windows Help (via "Start", "Help").

Question:

Which versions of the Windows Media Player Versionen are supported?

Solution:

The Windows Media export was tested successfully for the Windows Media Player versions 6.4, 7.0, 7.1, 9, 10 and 11. Documents created by the LECTURNITY Publisher can not be replayed by older versions of the Windows Media Player.
You can find out the version number of your Windows Media Player PlugIn by selecting the entry "?", "Info" in the menu line. You get the version number of the WindowsMedia Player embedded into the HTML page by clicking on the Player with the right mouse key. Select the entry "Info" in the appearing menu.

Question:

Which causes lead to the following error messages, especially in browsers like Netscape, Mozilla or Firefox ("Gecko" browser)?

Solution:

Figure 8: Error message about a not detected PlugIn

The player control elements are disabled and no reply is possible.One possible cause can be that your browser has no Windows Media PlugIn installed or that this PlugIn does not work correctly after a browser update.Please reinstall the Windows Media Player. It is recommended to use Windows Media 9 or higher. Your browser will be detected during the installation process and the appropriate PlugIn will be installed automaticly. This reinstallation of the Windows Media Player is necessary especially for the Netscape, Mozilla or Firefox browser ("Gecko" browser). Please note also the theme No dynamic on the slides associated with browser PlugIns.

Another possible reason can be that a "Gecko" browser like Netscape, Mozialla or Firefox can not communicate with the Windows Media Player via PlugIn interfaces. The communication can then be established via an "ActiveX Control". For this an ActiveX PlugIn has to be installed into the browser, if necessary.

If on tries to start the replay of a LECTURNITY Windows Media Document which audio and video content is streamed from a Windows Media Server then an error message "Windows Media Player cannot find the file. ..." appears. The replay of the document is not possible.

Cause: 

For the streaming of audio and video data the MMS protocol is used. On the client side does the Windows Media Player 11 (opposite to the older versions) not support the MMS protocol and tries to use an alternative protocol via "protocol rollover". If on server side with the Windows Media Server the settings do not support or allow "protocol rollover" then streaming is not possible.

For further information you can read this entry in the Windows Media Services FAQ.

www.microsoft.com/windows/windowsmedia/forpros/server/faq.aspx

Firefox:

For the replay of Windows Media Documents created with LECTURNITY version 3.0.p1 or higher the installation of an ActiveX plugin in Firefox is not necessary. Instead the "Windows Media Player Firefox Plugin" must be installed.
Windows Media Documents created with LECTURNITY version 3.0 or older can not be replayed with the "Windows Media Player Firefox Plugin".

port25.technet.com/archive/2007/03/29/windows-media-player-firefox-plugin-download.aspx

Question:

How do I install ActiveX plugins in Firefox, Mozilla and Netscape for the replay of Windows Media documents? Which ActiveX plugins are suitable for which browser?

Disambiguation: What is ActiveX?

"ActiveX is a technology for the execution of program code established by Microsoft which claims to be an alternative or competition to Java. ActiveX is an umbrella term for different software components. All these components base on the so called Component Object Model (COM). ActiveX is not an internet standard in general, but the attempt to use specific properties of the MS Windows operating system in web pages. For example, with the help of ActiveX Controls it is possible to read entries of HTML forms directly into an Excel sheet or an Access database with OLE interfaces (or vice versa). Microsoft tries to find solutions which can be adapted to Macintosh and Unix systems. But finally ActiveX is optimized for MS Windows ..." (Translated from the German source: de.selfhtml.org/intro/technologien/activex.htm)

The replay of Windows Media documents in a browser via an embedded player is at last optimized for the Internet Explorer. It can not be taken for granted that the replay works with other browsers, especially the "Gecko" browser Firefox, Mozilla and Netscape. The "Mozilla ActiveX Project" (see below) tries to embed Windows Media as ActiveX plugins. But you have to be warned that the use of these ActiveX plugins has to be done at your own risk.

Download of the ActiveX plugins from the "Mozilla ActiveX Project" (http://www.iol.ie/~locka/mozilla/plugin.htm#download). 

Hint:

After Download of the appropriate file with the extension ".xpi" an ActiveX plugin can be installed by opening it in the appropriate browser. After installation the browser has to be closed and reopened.
If the ActiveX plugin does not work properly, you should continue as follows:

• Type "about:plugins" into the adress bar. You will get a list of the installed plugins. During this step the new installed ActiveX plugin will be detected normally. Then reopen your Windows Media document.
• If the previous step does not proved successful please reinstall the Windows Media Player. It is recommended to install Windows Media player 9 or higher. Firefox can't replay Windows Media documents (even if the correct ActiveX plugin is installed), if the Windows Media Player 8 or an older version is installed (see also forums.mozillazine.org/viewtopic.php for more details).

If no ActiveX plugin or a not properly working ActiveX plugin is intalled in a "Gecko" browser, an "Error message in Netscape, Mozilla und Firefox - no replay possible" appears.

The following "Gecko" browser are tested with ActiveX plugins:

Question:

Why can it happen during replay that the video windows remains black, even if sound can be heard?

Maybe a Windows Media Codec 8 has been used during the creation of this document. And this codec is not installed on the computer replaying this document. Normally the Windows Media Player should recognize this ask automatically, if the required codec should be downloaded and installed (if an internet connection exists). In some cases this codec request does not appear, especially in older versions (e.g. 6.4) of the Windows Media Player.

In a Windows Media file, Audio and video stream are coded with different codecs. Normally a codec compatible to Windows Media 6 is used for the audio stream. Therefore the Windows Media Player can replay the audio stream, even if the codec for the video is not installed. As a result the audio stream can be heard, but the video windows remains black.

Maybe only the effect "Black video window while scrolling" appears.

Solution:

Download a Codec Installation Package from Microsoft or install the Windows Media Player 9 or higher.

www.microsoft.com/windows/windowsmedia/format/codecdownload.aspx

Question:

Why does the video window remain black for a short period of time while scrolling in a Windows Media document?

Solution:
If there is a lot of scrolling action in a Windows Media document with various video clips, then the video window remains black for a short period of time although the sound can be heard. Short video clips might not even be displayed at all. During "normal" replay (without scrolling), this problem does not occur.

This is a trait of the Windows Media Player itself. After a scrolling action the player needs some preload time during replay in which the video window remains black.

Question:

Why is a certain part of my screengrabbing clip not shown?

Solution:
f you have a screengrabbing clip in your document that contains very different contents, it may happen that during replay certain parts of your clip are not shown on the web page. The repaly seems to have halted as the replay window shows a still image.

Documents like these you can get for example by joining two very different documents with the Editor. This problem however only occurs when using the option "Windows Media Player 6.4 and higher" during the publishing.

Question:

How can I turn off the security warning about blocked ActiveX Controls when I load a Flash document into the internet Explorer?

Solution:
Open in the menu "Tools" the entry "Internet Settings" and check the option "Allow active content to run in files on My Computer" in the "Advanced" tab.

If a LECTURNITY generated Flash document is replayed with the Flash Player 10 (exactly version 10.0.12.36 of the Flash Player) it can happen that the replay is permanently bucking and the audio is not understandable.
Flash documents generated with a newer version of LECTURNITY (e.g. 2.0 or 3.0) do not show this behaviour.

Solution:

The problem does not occur any more with the version 10.0.22.87 of the Flash Player, which was published after version 10.0.12.36.
Please update your Flash Player.

Question:

ow can it happen that the replay of a Flash document with video is not possible because the video is not displayed? Additionally the RealPlayer 11 is installed.
There is an option "Download & Recording" in the settings of the RealPlayer 11. If this option is activated then the video stream is not displayed but downloaded into the local RealPlayer library directly.

Solution:

Deactivate the option "Download & Recording" in the settings of the RealPlayer 11.

Question:

Which bitrates for audio are supported for the Flash export? 

Solution:

When creating a Flash document with the LECTURNITY Publisher the audio stream will be converted. For this conversion you can choose a quality level (bitrate). Depending on the sample rate of the original audio stream you have differing choices:

• Audio with up to 22 kHz: 8 - 64 kbit/s
• Audio with more than 22 kHz: 32 - 64 kbit/s

Question:

In long Flash documents, unsynchronized playback between audio and slides and/or graphical annotations may occur in the sense that the audio sequences belonging to the slides and/or annotations is played back with a time delay.

Solution:
This can generally only be recognized in documents over 30 minutes long. The synchronization problems increase relative to the current playback point, and are most noticeable at the end of the document.

For this you can read the section Used SCORM 1.3 variables. There is a table which lists all SCORM variables which are used for the exchange between LECTURNITY Document and LMS.

If a LECTURNITY Document created with SCORM support is uploaded into CLIX and opened then in the background a permanent data exchange occurs between the LECTURNITY Document and CLIX. In the browser window the most important data like availability, learning success, total time and testing results are displayed.

• After clicking on a LECTURNITY WBT a new browser windows is opened which displays a list of all SCOs according to the WBT. Because a LECTURNITY Document contains only one SCO only one entry is displayed:
  
  
  Figure 9: Browser window with the most important SCORM data of a LECTURNITY Document
  
  
• A click on the "?" symbol of the "Status" colums opens a new browser window with a legend:
  
  
  Figure 10: Legend of the symbols in the "Status" column
  
  
• A click on the "clocks" symbol in the "Accesses" column opens a new browser window containing a list with the accesses to the LECTURNITY Document:
  
  
  Figure 11: Legend of the symbols in the "Status" column

The "SCORM data which is visible in CLIX" have the corresponding SCORM 1.3 variables:

• cmi.entry
• cmi.location
• cmi.score.raw
• cmi.session_time
• cmi.success_status
• cmi.completion_status

The meaning of the variables is explained in the section "Used SCORM 1.3 variables".

Question:

One or more presentations are removed from a CD project of which a CD image has already been created. A new CD image is created. How come that in the directories of the CD image some files of the already removed presentations still exist?

Solution:
This happens because the directory of the CD image is not deleted before a new creation. If you want to make sure that you receive a "clean" CD image, delete the content of the target directory manually (for example with the Windows Explorer) before creating the final CD image.

Question:

Why do in HTML pages created by the CD-Publisher sometimes problems arise in the context of presentations of HTML tables if I use my own created HTML templates?

In some cases, errors appear when the HTML pages contain tabulator symbols (ASCII value 9).

Solution:

Only use blanks, avoid tabulators in the HTML templates.

 
Figure 12: Error message: "Could not find main class. Program will exit!"

The error message "Java Virtual Machine Launcher: Could not find main class. Program will exit!" appears upon the start of the Player or Publisher if there is any of the following three characters in the path to these programs: % ! #

This may be the case if you

• either have LECTURNITY installed in a directory with such a name or
• have put a cd image in a directory with such a name.

Solution:

You can deinstall LECTURNITY and install it in another directory or simple rename the respective directory in the cd image case.