Version 3.3.0 ReadMeresources.avid.com/SupportFiles/attach/Broadcast/ReadMe...Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes on

��iNEWS® Newsroom Computer System Version 3.3.0 ReadMe

Date Revised Changes Made

30 November 2010 Added information related to v3.3.0 release

23 November 2010 Added information related to v3.2.2 release

14 October 2010 Added information related to v3.2.1 release

24 May 2010 Initial version (based off of v3.1.1 doc.)

Important Information Avid recommends that you thoroughly read all of the information in this ReadMe file before installing or using any new software release.

Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport) for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published.

This document describes compatibility issues with previous releases, hardware and software requirements, software installation instructions, and summary information on system and memory requirements, when applicable. This document also lists any hardware and/or software limitations.

Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes on important features and changes have been brought forward from previous ReadMe documents. Notes that are less important were not brought forward, and users should reference older iNEWS ReadMe files for additional change information not contained in this ReadMe.

http://www.avid.com/onlinesupport�

Version 3.3.0 ReadMe

2

Contents Important Information ............................................................................................................................................ 1

Compatibility Notes and Issues ................................................................................................................................. 5

Community Feature ............................................................................................................................................... 5

iNEWS Client ........................................................................................................................................................ 5

iNEWS Server ....................................................................................................................................................... 5

Command .............................................................................................................................................................. 5

ControlAir .............................................................................................................................................................. 5

MOS Gateway ....................................................................................................................................................... 5

Console Multiplexer .............................................................................................................................................. 6

Data Receiver ........................................................................................................................................................ 6

Fast Text Search .................................................................................................................................................... 6

Instinct ................................................................................................................................................................... 6

NewsCutter ............................................................................................................................................................ 6

Teleprompter ......................................................................................................................................................... 6

Changes between 3.2.2 and 3.3.0 .............................................................................................................................. 6

Installation ............................................................................................................................................................. 6

User Interface ........................................................................................................................................................ 6

Monitor Server ....................................................................................................................................................... 7

Server ..................................................................................................................................................................... 7

NSML .................................................................................................................................................................... 7

URLs and Web Services API ................................................................................................................................ 7


Active X ................................................................................................................................................................. 8

SYSTEM.MAP ...................................................................................................................................................... 8

User Interface ........................................................................................................................................................ 8


Searching ............................................................................................................................................................... 8

User Interface ........................................................................................................................................................ 8

Calendar Issues ...................................................................................................................................................... 9

Miscellaneous ........................................................................................................................................................ 9


Hyperlinks ............................................................................................................................................................. 9

Macros ................................................................................................................................................................... 9

User Interface ........................................................................................................................................................ 9



3

ActiveX Plugins ..................................................................................................................................................... 9

dbrestore and Restoring Stories ........................................................................................................................... 10

Message Server .................................................................................................................................................... 10

Changes between 3.0.x and 3.1.0 ............................................................................................................................ 10

User Interface ...................................................................................................................................................... 10

Playout ................................................................................................................................................................. 10

Searching and FTS ............................................................................................................................................... 11

Stories .................................................................................................................................................................. 12

NewsCutter Integration ........................................................................................................................................ 12

Unicode ................................................................................................................................................................ 12

Changes between 3.0.0 and 3.0.1 ............................................................................................................................ 12

Client ................................................................................................................................................................... 12

Server ................................................................................................................................................................... 12

Monitor Server ..................................................................................................................................................... 12

User Interface ...................................................................................................................................................... 13

Indexing & Searching .......................................................................................................................................... 13

Macros ................................................................................................................................................................. 13

Changes between 2.x and 3.0.0 ............................................................................................................................... 13

Messaging ............................................................................................................................................................ 13

Monitor Server ..................................................................................................................................................... 13

User Interface ...................................................................................................................................................... 13

iNEWS Server ..................................................................................................................................................... 14

FTS Multiple Indexes .......................................................................................................................................... 14

Site files ............................................................................................................................................................... 15

New Features ........................................................................................................................................................... 15

For iNEWS v3.3.0 ............................................................................................................................................... 15

Desktop Icon .................................................................................................................................................... 15

Projects and Facets .......................................................................................................................................... 15

Search Queues ................................................................................................................................................. 16

Queue Templates ............................................................................................................................................. 16

For iNEWS v3.1.0 ............................................................................................................................................... 16

Script Templates .............................................................................................................................................. 16

NewsCutter media ............................................................................................................................................... 17

For iNEWS v3.0.0 ............................................................................................................................................... 17

Hyperlinks ....................................................................................................................................................... 17

Story links ........................................................................................................................................................ 17

Comboboxes .................................................................................................................................................... 17


4

Check boxes ..................................................................................................................................................... 18

Duration ........................................................................................................................................................... 18

Calendar ........................................................................................................................................................... 18

Field write groups ............................................................................................................................................ 18

Editorial groups ............................................................................................................................................... 18

Colors .............................................................................................................................................................. 18

Lists ................................................................................................................................................................. 19

Play Interplay Low-res Streams ....................................................................................................................... 19

Installation Notes and Issues ................................................................................................................................... 20

iNEWS Installer ................................................................................................................................................... 20

FTS v3.1.x ........................................................................................................................................................... 20

New End User License Agreement ...................................................................................................................... 20

Upgrading iNEWS Server Software from Previous Versions ............................................................................. 20

Upgrading iNEWS Client Software from Previous Versions .............................................................................. 21

Upgrading iNEWS v2.8 Client Software to Future Versions .............................................................................. 21

Upgrading iNEWS Server from Previous Versions ............................................................................................. 21

Qualified Asian Languages and IMEs ..................................................................................................................... 21

Korean ................................................................................................................................................................. 21

Chinese Simplified .............................................................................................................................................. 21

Chinese Traditional .............................................................................................................................................. 22

Japanese ............................................................................................................................................................... 22

Vietnamese .......................................................................................................................................................... 22

Microsoft Windows Critical Updates ...................................................................................................................... 22

Known Issues and Limitations ................................................................................................................................. 23

iNEWS Web Services API .................................................................................................................................. 23

Multiple Monitors ................................................................................................................................................ 23

Macros and Keystrokes........................................................................................................................................ 23

Technical Support Information ................................................................................................................................ 24

Accessing Online Support ................................................................................................................................... 24


5

Compatibility Notes and Issues This section contains compatibility information related to the iNEWS 3.3.0 release.

Community Feature iNEWS 3.3 Server can be in a Community with iNEWS 2.8 and later, and iNEWS 2.8 (and later) Workstations can connect to an iNEWS 3.3 Server directly or via Community; however, iNEWS 3.3 Workstations cannot connect to 2.8 through iNEWS 3.2 (or earlier) Servers directly or via Community.

The following Community connections are supported:

• iNEWS 3.3 Workstation to iNEWS 3.3.0 Server directly and to an iNEWS 3.3.0 Server through Community.

• iNEWS 2.8 Workstation to iNEWS 2.8 Server directly, and then to iNEWS 3.0 (or later) Server through Community.

• iNEWS 2.8 Workstation to iNEWS 3.x Server directly, and then to iNEWS 2.8 Server through Community.

• iNEWS 3.2 (or earlier) Workstation to iNEWS 3.2 Server directly, and then to iNEWS 3.0 (or later) Server through Community.

The iNEWS 2.8 client software does not support the new features in iNEWS 3.x: combo boxes, check boxes, story links, URL links, calendar fields, duration fields.

Clients prior to iNEWS 3.3 do not support the new features in iNEWS 3.3: projects, facets, search queues, and queue templates.

iNEWS Client The iNEWS client software is qualified and supported for use on Windows 7 (32-bit), Windows Vista, Windows 2000 Professional (SP4), Windows 2000 Server (SP4), Windows XP Professional (SP2 or SP3) and Windows Server 2003 (SP1). This version of iNEWS is not officially supported for use on any other Windows operating system.

The iNEWS 3.3 client software cannot connect to servers earlier than iNEWS 3.3.0.

iNEWS Server The iNEWS Server is qualified and supported for use on 32-bit Red Hat Enterprise Linux 5.x.

The iNEWS Server is qualified with VMWare Server v2.0 and later for Windows operating systems and is supported to run in a VMWare image. It must have networking set to BRIDGED to allow a unique IP address.

Command The iNEWS Server is qualified and supported for use with Command 1.0.1 or later.

ControlAir The iNEWS system is qualified and supported for use with ControlAir 1.6 or later. However, for the loading of single playlists with between 500 to 1000 stories, ControlAir v1.7.4.4 or later is required.

MOS Gateway The iNEWS system is qualified and supported for use with MOS Gateway 3.0.2 or later.


6

Console Multiplexer The iNEWS Server requires version 2.0 of the console multiplexer (MUX) software, which is on the iNEWS installation CD. The console multiplexer cannot currently display Unicode characters. A terminal emulator that supports Unicode characters can be used if Unicode support is required.

Data Receiver The iNEWS system is qualified and supported for use with Data Receiver 1.8 or later. iNEWS 3.0 Server saves data as well-formed XML. Data Receiver SFCs must be updated to deliver well-formed XML. Also, field tags have changed from <f id=TYPE></f> to <string id=”TYPE”></string>.

Fast Text Search The iNEWS system is qualified and supported for use with Fast Text Search 3.1.0 and later. A full re-index is required with an upgrade to iNEWS 3.0. See below for FTS changes.

Instinct The iNEWS system is qualified and supported for use with Avid Instinct 1.1 and 1.6 or later. After the iNEWS client software is installed on an Instinct computer, manual registration of the Instinct installation’s COM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\Avid iNEWS Instinct\iNewsCOMU.dll”.

NewsCutter The iNEWS system is qualified and supported for use with NewsCutter NRCS Tool 6.1.5 or later. After the iNEWS client software is installed on a NewsCutter, manual registration of the NewsCutter installation’s COM control should be performed: Start > Run > regsvr32 “C:\Program Files\Avid\Avid NewsCutter\iNewsCOMU.dll”. If both NewsCutter and Instinct are on the machine, the Instinct COM control should be the one you register.

Teleprompter The iNEWS system supports the following teleprompter software: WinPlus BDL Unicode version 6.8.7.3 and WinCue version 1.30 (build 674 or higher).

Changes between 3.2.2 and 3.3.0

Installation • In previous versions of iNEWS, the server installer allowed installation on 64-bit operating systems. This is

fixed. The iNEWS installer no longer allows installation on 64-bit operating systems.

• When installing iNEWS 3.3.0 Server, installers must run 'dbgen p' to initialize projects

• When installing iNEWS 3.3.0 Server, installers must run 'dbgen m' to initialize the mailbox, which allows project-related notifications.

User Interface • In previous versions of iNEWS 3, production cue text would not be displayed if cursor focus moved from

the production cue directly to a non-iNEWS application. This is fixed. Production cue text continues to display regardless of cursor focus.

• In previous versions of iNEWS, button and keyboard macros that move from the Queue panel to the story body and up to the story form could insert unwanted characters into the first field in the form. This is fixed.


7

• In previous versions of iNEWS, editing of text pasted into the Queue panel was not allowed if the user had double-clicked or used F2 to enter input mode before pasting. This is fixed. Double-clicking followed by pasting will allow further editing of the pasted text.

• In previous versions of iNEWS 3, the Directory panel flickered or flashed as focus moved. The issue existed in all operating systems, but was most apparent in Windows 7. This is fixed.

• In previous versions of iNEWS, moving focus among search results, a mail workspace, and a directory workspace could result in an 'object not managed' error. This is fixed.

Monitor Server • In previous versions of iNEWS, monitor could exit if Command disconnected immediately after initial

connection. This is fixed. monitor now recognizes that Command is unavailable, and will go to error.

• In previous versions of iNEWS, monitor could exit with some item-channel changes in MOS-enabled rundowns. This is fixed.

Server • In previous versions of iNEWS 3, dblines reported script and margin errors every time it was run. This

resulted in large diagnostic output that was difficult to parse. These messages have been removed.

• In previous versions of iNEWS, running the 'remove' console command against a non-empty queue would result in that queue being purge locked. This is fixed.

• Beginning with this version of iNEWS, dbvisit and dblines now display a diagnostic for every REFRESH, UPDATE, or SORTED queue that contains more than 1000 stories.

• In previous versions of iNEWS, 'finit -' would fail if the database partition was larger than 17GB. This is fixed. 'finit -' now initializes the database to the maximum size allowed by the server or the partition. If the partition is larger than the the maximum database size, finit will initialize up to the maximum allowed size. Space remaining on the partition will not be used.

NSML • iNEWS now uses NSML 3.1. This version of NSML adds the projects section and the body-level <sb/> tag

that will be used by future journalist editor applications. <sb/>, when encountered by the iNEWS client, will display a "Segment Break" that looks like the current "Page Break" line.

• In previous versions of iNEWS 3, file links in the story body were formatted improperly, leading to NSML read errors with some external applications. This is fixed.

URLs and Web Services API • In previous versions of iNEWS 3.0, using keystrokes to launch URLs had inconsistent behavior. This is

fixed. The keystroke now launches the link on which the cursor resides.

• In previous versions of iNEWS 3.0, using the mouse to highlight a URL could result in the URL launching. This is fixed.

• Double-clicking a production cue that has an attachment now launches the embedded URL, if found, when an ActiveX plug-in is not available. A context option is also available - "Launch Link to Machine Control."

• In previous versions of iNEWS, empty formatting tags submitted by the iNEWS Web Services API would be translated incorrectly, causing the text that followed to be formatted improperly. This is fixed. Empty formatting tags are now maintained with no impact on trailing text.


8


Active X • In previous versions of iNEWS 3, ActiveX plug-ins were skinned by the iNEWS skinning engine, causing

refresh issues and possible client crashes. This is fixed. Third-party plug-ins are no longer skinned by iNEWS.

SYSTEM.MAP • In iNEWS Server v2.6.5 through v3.2.1, form-level MOS items and form-level video items could not be

sent to playout from the same rundown if mossvr was primary in SYSTEM.MAP. This is fixed. Also added is the event-status of both item types in the same rundown, regardless of which appears first in SYSTEM.MAP.

User Interface • In previous versions of iNEWS, entering hundreds of lines of text into a production cue could result in a

"No error occurred" error message and an unusable story body. This is fixed.

• In previous versions of iNEWS, some dialogs (delete confirmation, copy/move to) when dismissed would cause the OS desktop and icons to refresh. This is fixed.


Searching • In previous versions of iNEWS, changing the form in the Search Results required logging out and logging

back in. This is fixed. The Use Form selection now switches the form immediately.

• In previous versions of iNEWS 3, manually sorting search results by date did not work correctly. This is fixed. Manual sorts in search results now behave as expected.

• In previous versions of iNEWS 3, seek searches of queues that had modify-date in the form would report modify-date as 1969. This is fixed.

• In previous versions of iNEWS 3, operators in seek/non-indexed searches were not formatted properly, causing "invalid keyword expression" errors. This is fixed. The operators are now submitted properly, and the searches succeed.

User Interface • In previous versions of iNEWS, copying a story from a queue with hidden parents and pasting into a

different queue would cause the client to terminate. This is fixed. This situation occurred when a user had access to a queue but not to the parent folder—the PEOPLE folder, for example.

• In previous versions of iNEWS 3, form updates to a story would cause that story's body to scroll to the start of the story. This is fixed.

• In previous versions of iNEWS 3, typing in an editable combobox in the queue view followed by clicking in the form area of that story would cause the typed value to be lost. This is fixed. The user no longer has to tab out of the queue cell for the value to register.

• In previous versions of iNEWS 3, selecting exactly half of the stories in a queue and moving those stories would result in all stories in the queue being moved. This is fixed. Only the selected stories are moved.

• In previous versions of iNEWS 3, only the first machine control entry in a single production cue was recognized. This is fixed. All machine control entries in all production cues are now recognized and acted on by the monitor server.


9

Calendar Issues • In previous versions of iNEWS 3, duration and calendar values in the queue view could not be cleared with

the spacebar. This is fixed.

• In previous versions of iNEWS 3, entering calendar field values in the story form and not including time or not leaving the field before saving would result in the entered value not being saved. This is fixed. Empty time is saved as 00:00:00, and the user does not have to leave the field for the value to save.

Miscellaneous • In previous versions of iNEWS, the client would terminate when closing the Sony NewsBase Filing

Control ActiveX. This is fixed.

• In previous versions of iNEWS, txnet/rxnet connections between servers could reconnect with improper information, causing orphaned connections. This issue is fixed.

• In previous version of iNEWS 3, the roChannel MOS Gateway workflow did not function properly. This is fixed.


Hyperlinks • Previously, in iNEWS 3.0 and higher, non-hyperlink strings that contained slashes were not saved when

pasted into the client. This is fixed. All text pasted into the client is now saved correctly.

• Previously, in iNEWS 3.0 and higher, lines beginning with the at symbol (@) were treated as hyperlinks. This is fixed.

Macros In previous versions of iNEWS, [<dialog name>] was used in macros to define a dialog wait. This syntax interfered with other macros already using the square brackets. A new token, K_WINDOW has been created in /site/dict/keymacros to replace that syntax. The default value for the K_WINDOW token is: window.

Usage example: If a macro should wait for the Local Printing dialog box before continuing, the syntax is: {window Local Printing}. The text following the word window must match exactly the title of the dialog box. If the text does not match, the user must press the Escape key to exit the macro.

User Interface • In previous versions of iNEWS, duplicate CG addresses could be assigned mistakenly. The duplicate

assignment was related to the order in which CG events for different devices were inserted into stories. This is fixed.

• In a previous version of iNEWS, multi-word Find searches (Ctrl+F) did not work correctly. This is fixed.


ActiveX Plugins In previous versions of iNEWS, ActiveX plugins would not repaint correctly at times, causing blank plugin workspaces. This is fixed.


10

dbrestore and Restoring Stories Previously, in iNEWS 3.0 and higher, restoring stories with Hebrew form information could result in dbrestore terminating. This is fixed.

Message Server In previous versions of iNEWS, message server could terminate at times of high monitor message traffic, resulting in system slowness. This is fixed.

Changes between 3.0.x and 3.1.0

User Interface • In previous versions of iNEWS, assigning a color to a combobox value required leaving the row and

returning. This is fixed. Colors can now be assigned immediately after typing or selecting the entry value.

• In a previous version of iNEWS, comboboxes in the Story Form panel did not resize with font size changes. This is fixed.

• In iNEWS v3.0.0, custom toolbar buttons could reset to an incorrect size when toolbars were moved. This is fixed. Custom toolbar buttons now retain their size.

• In iNEWS v3.0.0, disconnected local databases did not show the system colors of the most recent server. This is fixed. The system colors used by a disconnected local database match the system colors assigned in the most recent server connection.

• In a previous version of iNEWS, right-clicking on a URL would not allow opening the URL into the iNEWS Web browser workspace if the user’s preferences were set to launch hyperlinks externally. This is fixed.

• In a previous version of iNEWS, moving from a story row with a background color to a row with a different background color could result in the field background of duration and calendar controls in the Story Form panel being the incorrect color. This is fixed.

• In iNEWS v3.0.0, font sizes greater than 18 did not appear correctly in comboboxes displayed in the Queue panel. This is fixed.

Playout • In previous versions of iNEWS, moving monitored production cues within a story could result in the items

being out of order on the playout device. This is fixed. The order on the playout device will always reflect the order in the iNEWS story.


11

Searching and FTS • Find All Advanced searching has been changed so that it is now aware of custom check box and calendar

fields. In the Find All dialog box, on the Advanced tab, when a user chooses to search a custom check box field (such as v-check in the sample graphic below), the user can then select Is or Is Not Checked.

When a customized calendar field (such as v-cal) is selected, the new DT button activates as shown in the following sample graphic:

The search parameters allow the user to specify the standard date search criteria: Equal To, Not Equal To, Less Than, Greater Than, Less Than Or Equal To, and Greater Than Or Equal To. The DT button launches the Select Date dialog box, shown below:

• In FTS v3.0.0, placing the index bases and the FTS installation on separate drives could result in ftssch.exe crashes. This is fixed.

• In previous versions of iNEWS, using the Find All button on the Find toolbar (the button shown far right in below graphic of toolbar) caused the default Find dialog selection to be “First # paragraphs”.

This is fixed. Using the Find toolbar no longer impacts the default selection of the Find dialog box.


12

• In previous versions of iNEWS, the Stop button would not appear in the Search Results window. This is fixed.

Stories • Starting with v3.1.0 of iNEWS, story links and file paths can now be added to stories via drag and drop.

To add a story link to another story:

1. Select the story that will be linked.

2. Drag it into the body of the story that will hold the link.

To add a link to an external file:

Drag the file into the story body.

Note: Windows Vista and Windows 7 User Account Control (UAC) will prevent dragging items from external areas into iNEWS. UAC can be disabled if this feature is needed. Avid engineers are currently working with Microsoft on other solutions to the UAC issue.

NewsCutter Integration • In iNEWS v3.0.0, story changes made via NewsCutter’s NRCS Tool were rejected if the NRCS Tool used

FTP-only communication. This is fixed. The iNEWS Server now supports both FTP-only and COM+FTP NRCS Tool communications.

Unicode • In a previous version of iNEWS, some Unicode characters were converted to question marks at save. This

is fixed.


Client • In iNEWS 3.0.0, initial start time of the client software after double-clicking the shortcut was slow. This is

fixed. The start is now faster.

Server • The trademark and copyright information has been updated in the latest version of software, which can be

viewed at the console by typing what appears in bold: NRCS-A# version

• In previous versions of iNEWS, the dbdump command would skip the contents of all subdirectories and queues if a parent directory had the skip trait enabled, even when the children did not have the skip trait. This is changed. Queue contents will only be skipped by dbdump if the queue has the skip flag.

• In previous versions of iNEWS, top-level directories and queues could be created with "[" as the first character, resulting in a corrupt directory or queue. This is fixed. "[" is no longer allowed as the first character in a top-level node.

Monitor Server • In previous versions of iNEWS, an empty entry in SYSTEM.MAP was the only way to declare 'no end

time' for a monitor. This is fixed. The value now allows empty and "-" (hyphen) to declare 'no end time.'


13

User Interface • In iNEWS 3.0.0, ALT keystroke combinations used to trigger menu options did not work when the layout

was set to auto-arrange off with workspaces maximized. This is fixed.

• In iNEWS 3.0.0, form field labels placed Left, Bottom, and Right would realign to Top after saving. This is fixed.

• In iNEWS 3.0.0, form area checkboxes did not show as checked when users first navigated to the story. This is fixed.

Indexing & Searching • In iNEWS 3.0.0, date and duration field types were not indexed correctly. This is fixed. If an indexed queue

contains date or duration fields, it must be re-indexed after upgrading to 3.0.1 server and 3.0.1 FTS.

• In iNEWS 3.0.0, newly indexed items were only searchable after a period of time up to an hour. Now, indexed items are searchable immediately after indexing.

• In iNEWS 3.0.0 and FTS 3.0.0, restarting the FTS server or processes required a restart of the ftsindex and ftsseek devices on the iNEWS server. This is fixed.

Macros • In previous versions of iNEWS, some macros would send keystrokes to dialogs before the dialogs were

available. There is now a way to prevent that behavior. In the button or keyboard macro definition, place the name of the dialog in square brackets immediately following the keystroke that launches the dialog. This entry will cause the macro to pause until the named dialog is available. For example, if {ctrl p} is used to launch Local Printing, {ctrl p}[Local Printing] will cause the macro to pause until the dialog is available. The text in brackets must match the dialog title exactly. If the text does not match, the macro will pause indefinitely or until a user presses the escape key. This enhancement will resolve some instances of macros not working as designed. This enhancement will not necessarily resolve all macro timing issues introduced by the upgrade to Internet Explorer 7 or 8.

Changes between 2.x and 3.0.0

Messaging • In previous versions of iNEWS, a message sent across a community would generate an extra message to a

blank username. This message buildup eventually caused slowness when receiving messages. This is fixed.

Monitor Server • In previous versions of iNEWS, monitor server would hang if it encountered duplicate qrstamps in a

rundown. This duplicate will only occur with database corruption. The hang has been fixed. If the monitor server encounters a duplicate qrstamp, it will print a diagnostic and exit.

User Interface • The User Properties dialog no longer contains the Broadcast Control option; it is no longer utilized.

• In previous versions of iNEWS, changing the formatting of a block of text that included multiple text types – presenter instructions, normal text, and closed captioning – would only save the change to the first text type. This is fixed.


14

iNEWS Server • The output header for the list u command has changed. The T representing the technical direct (td)

option is no longer used. The old output header appeared like this: user rr kb su m | SOEKCVTH sc destination The new output header appears like this: user rr kb su m | SOEKCVH sc destination

• In previous versions of iNEWS, the list c console command displayed invalid characters in the Computer column. This is fixed.

• The verbose list command (list s-v) has been enhanced to display the command used to invoke the displayed session. The expanded information includes values such as the monitored rundown and the program. The expanded information is only available on the server running the program.

• The s <slow> option has been removed from diskcopy.

• The list d command now has an ‘i’ option. ‘list d-i <directory>’ displays the FTS index base and Interplay server used by the directory.

• The dbtraits command has two new options: ftsindex and interplay.

• The doc utility now includes the verbose (v) flag for its put command. When a parsing error occurs on a put, the administrator can run the put again with the verbose option enabled. When verbose is active, each tag is output as it is parsed. This allows easier detection of the source of the parsing error. The doc utility has changed to default to NSML entry instead of simple text entry. 'doc -p' accepts NSML, while 'doc -pt' accepts text. A '2' has also been added to allow inputting of NSML 2 data. The new doc syntax is outlined below:

To get text from database:

Use: doc -gt[u] <queue> [slug...] or: doc -gts[u] <queue> <story id>

To get NSML from database:

Use: doc -g[2] <queue> [slug...] or: doc -gs[2] <queue> <story id>

If no slugs are given entire queue is done.

To put text into the database:

Use: doc -pt[u] <queue> [file...]

To put NSML into the database:

Use: doc -p[2] <queue> [file...]

If no files are given standard input is read.

FTS Multiple Indexes • iNEWS now supports up to 50 separate index bases. This separation allows indexing of more documents

while avoiding the index base file size limit of 2GB. The index base is assigned using the dbtraits command. All directories default to index 0. For example, the following commands will separate index bases: dbtraits wires ftsindex 1 dbtraits archive.2007 ftsindex 2 dbtraits archive.2008 ftsindex 3


15

• ‘list d-i’ displays the index base used by a directory. When the index base is changed, the directory is automatically removed from its current base and added to the new one.

• FTS handles the separation of the bases. There is still only one ftsindex device on the iNEWS server, and there is still only one ftsidx.exe process on the FTS server.

• An ftsindex attribute was added to iNEWS that supports any value from 0 to 49. The ftsindex attribute is independent of the INDEXED attribute and determines which FTS index base is used for the data in the queue with that ftsindex value. Also, the word definition W_INDEXBASE must now contain a path to a directory and not the full pathname for the index files. For example, the following old definition should be changed to the new definition: (old) W_INDEXBASE /C:/FTS/FTSINDEX (new) W_INDEXBASE /C:/FTS That directory will contain a subdirectory for each index. These subdirectories will have 3 digit names with leading zeros. So, index base 0 is in the directory C:\FTS\000, and index base 32 is in C:\FTS\032.

The index base files are always named “ftsindex”, with the distinction coming in the tag. For instance, four files would be: ftsindex.in1, ftsindex.in2, ftsindex.in3, and ftsindex.in4.

W_AGEWEIGHT, W_HITSWEIGHT, and W_LOCWEIGHT are removed from /site/dict/words. FTS search results will always be returned in descending date order.

Site files • The iNEWS Server software upgrade from pre-Unicode versions now substitutes /&#164 for /164 when

that character appears in /site/dict/words: W_CUE_REF.

• Both scriptrhmax and scriptlhmax have been removed from /site/system and the connect parameters. These parameters are no longer used.

• In this version of iNEWS, the device limit in /site/config is increased from 4096 to 5000. Device count by type (inws, aiws, etc.) must still comply with licensing, but the total device count allowed is now 5000, which means that valid device number assignments are 1 through 5000.

• There is a new resource type in /site/config: api. This type handles connections from the iNEWS Web Services API. It is a licensed resource.

New Features This section contains a listing of new features.

For iNEWS v3.3.0 This section contains a listing of new features implemented in this version of iNEWS.

Desktop Icon The iNEWS v3.3 client software has a new desktop icon on the workstation. The new icon is shown at left.

Projects and Facets

• The iNEWS system now supports projects and facets. Projects are a way of categorizing stories by topic so that news teams working on a particular topic can find everything related to it in a single place, without


16

moving or copying original source information within the database. Facets are sub-topics of projects that provide additional granularity. For more information about projects and facets, see the iNEWS Projects chapter in the Avid iNEWS v3.3 Setup and Configuration Guide.

Search Queues

• The iNEWS system now supports search queues. A search queue is a special queue that stores a pre-defined query of indexed queues, along with its own queue form and read group. When users with proper read access open a search queue, a fast text search (FTS) is activated, and the results are delivered to the workspace in the Queue panel instead of the Search Results pane. For more information about search queues, see the section called “Search Queues” in the Database: Directories, Queues, and Stories chapter of the Avid iNEWS v3.3 Setup and Configuration Guide.

Queue Templates

• The iNEWS system now provides a Copy From Template button in the Directory/Queue Properties dialog box. Templates are created as queues in SYSTEM.PROPERTIES, and once created, they can be used to help speed up the process of configuring directories or queues in the iNEWS database. For more information about copying queue templates, see the section called “Database Traits Summary” in the Database: Directories, Queues, and Stories chapter of the Avid iNEWS v3.3 Setup and Configuration Guide.

For iNEWS v3.1.0 This section contains a listing of new features implemented in iNEWS v3.1.0.

Script Templates

• iNEWS now supports a new feature called Script Templates. Script templates are templates created by an administrator for users to quickly insert predefined text into stories. The database structure for script templates is the same as the structure used for forms and lists:

SYSTEM.SCRIPT-TEMPLATES.<first letter>.<name>

For example, if a standard weather story has a set of production cues and presenter text that are always the same, you can create a story in SYSTEM.SCRIPT-TEMPLATES.W.WEATHER. In this story, place the standard text, presenter text, and production cues found in the weather story. After the template story is saved, the template is available to users via the Story menu or through an option in the Story Text sub-panel’s context menu.

To use a script template:

1. Right-click in the Story Text sub-panel.

2. Select Insert Script Template. A Templates dialog box will appear with a list of all available templates.


17

3. Enter the name or select the template from the list.

4. Click OK.

Once the template is chosen, the template is inserted in the story’s body at the cursor position.

Note: This new feature can replace the use of complex macros currently used to insert template material.

NewsCutter media • iNEWS can now stream material created using the NewsCutter NRCS Tool 8.0.5 feature that inserts a

production cue into the story when a user creates a new sequence from a story. If the production cue is not created when the sequence is created, iNEWS will not be able to stream the mixdown. Depending on the NewsCutter version used to create the production cue, the cue displayed in the iNEWS client will either be a full MOB ID or simply a read-only {N}.

For iNEWS v3.0.0 This section contains a listing of new features implemented in iNEWS v3.0.0.

Hyperlinks

• iNEWS now supports the addition of hyperlinks in the story body. Links can be in the form of http:// or www. E-mail addresses are also recognized. A user preference is available defining whether clicked links will launch into an Internet Explorer workspace within the iNEWS application, or into the user’s default browser outside of the iNEWS application.

Story links

• iNEWS now supports creating story links. When focus is on a story, the context menu and the story menu have available the “Copy story link to clipboard” option. When this option is selected, it creates a story link on the user’s clipboard. This link can be pasted into another story and will appear as: inews://<server>/<path>/<story>. Clicking the link will create a new workspace displaying the linked story.

Comboboxes

• Form fields can now be assigned predefined values. When these fields are used in a form, the user is presented with a drop-down list instead of a text field. These fields are called comboboxes.

To create a combobox:

1. Edit a field property or insert a new field.

You will notice a new section named Type on the right side of the Form Properties dialog box.

2. Select the Combobox radio button.

• Include Blank Row means there will be a blank row provided before the list entries.

• Editable means a user can type their own value into the combobox in addition to selecting a pre-existing value

• The New button allows the administrator to create ad-hoc values that will appear in the combobox, instead of using a system list or group

• The Delete button removes an existing entry.

• The Up/Down buttons are used to reorder the values in the combobox.


18

• The Add List/Group button presents a dialog to the user in which they can select system lists and groups to be added to the combobox. <G> will appear in front of a group name, and <L> will appear in front of a list name.

• The color boxes show the current system colors. Colors can be assigned to individual entries or to entire groups and lists. To add a color, select the entry row and then select the desired color. A ",<#>" will appear after the entry, indicating which color index is assigned to the entry.

Check boxes

• A new field type, check box, is now available in forms. Any user-created field type can be assigned as a check box. The values saved are "1" for checked and blank for unchecked, allowing use with raw queries and affects-ready. Check boxes can be selected with the mouse or with the spacebar. Check boxes will always have the "Text alignment" attribute set to "Center."

Duration

• A new field type, duration, is now available in forms. Any user-created field type can be assigned as a duration field. Duration fields use spinners to display duration in the form, HH:MM:SS.

Calendar

• A new field type, calendar, is now available in forms. Any user-created field type can be assigned as a calendar field. Calendar fields use spinners to set and store dates. The dates default to a time of 00:00:00, but times can be added if more specificity is needed.

Field write groups

• Individual fields can now be assigned write groups. Only group members and superusers are permitted to edit those fields. The write group is assigned in Form Properties.

Editorial groups

• Another group type, editorial group, has been added to iNEWS. Members of the editorial group can delete, move, float, and break stories. If no editorial group is assigned, the relevant permissions apply to the write group to stay consistent with previous functionality.

Colors

• There is now a queue that holds system colors. By default, the colors reside in the queue SYSTEM.COLORS (/site/dict/queues:Q_COLORS sytem.colors). The first story in SYSTEM.COLORS defines the system's colors.

The syntax is a four-column list. The first column is the index of the color, from 1 to 10. The second column is the RGB red value. The third column is the RGB green value. The fourth column is the RGB blue value. The color values are numerical, from 000 to 255.

Example:

1 255 000 000 ; red

2 000 255 000 ; green


19

3 255 255 000 ; yellow

Only indexes 1 to 10 are accepted. Syntax errors in SYSTEM.COLORS will cause no colors to be displayed.

Community: When in a community, the colors displayed for a client will be the colors of the local server, regardless of the location of the queue they are currently viewing.

Lists

• The ability to create system lists has been added. By default, the lists reside in the directory SYSTEM.LISTS (/site/dict/queues:Q_LISTS /system.lists). The structure of the SYSTEM.LISTS directory is the same as the SYSTEM.FORMS structure, where the first character in the list's name defines which sub-folder holds the list. For example, a list called "format" is the first story in the queue SYSTEM.LISTS.F.FORMAT.

The lists are used for combobox form fields.

The syntax of a list is a two-column story. The first column holds the text value. Double-quotes should be used if special characters or spaces are used in the text value. The second column holds the background color index value. The second column is optional, and no color is used if the column is blank.

Example, using the colors defined above: SYSTEM.LISTS.S.STOPLIGHT

Stop 1

Go 2

"Slow Down" 3

"No Light"

; the value "Stop" has a red background color

; the value "Go" has a green background color

; the value "Slow Down" has a yellow background color

; the value "No Light" has no background color

Play Interplay Low-res Streams

• Low-res streams created by Interplay 2.0.1 and later can now be played through the iNEWS client. Several Interplay components are required for this workflow: iNEWS Instinct, Interplay Transcode, Interplay Stream Publish, Interplay Media Services, and Interplay Stream Server. QuickTime 7.5 must also be installed on the iNEWS client machine.

• When Instinct associates a sequence with an iNEWS story, the iNEWS client will display a context option called “Play Low-res Video.” When this option is selected, iNEWS will contact the Interplay server to retrieve the streaming URL. If the sequence has been mixed down and published to a streaming server, iNEWS will then disconnect from the server and open a QuickTime window inside the iNEWS client. The QuickTime application will automatically play the available stream.

• The queue SYSTEM.INTERPLAY (/site/dict/queues: Q_INTERPLAY) must exist for this workflow to be supported. The first story in SYSTEM.INTERPLAY is a four-column story. The first column is the index of the Interplay server, starting with 0. The second column is the hostname of the Interplay server. This name must be resolvable by the iNEWS Workstation. The third column is an optional column holding the username to be used when connecting to Interplay. The fourth column is an optional column holding the


20

password to be used when connecting to Interplay. If the third and fourth columns are blank, the iNEWS username and password will be used to connect to Interplay.

o 0 interplay1

o 1 interplay2 streamuser streampass

• Interplay servers can be assigned to individual directories using the dbtraits command or the Directory/Queue Properties dialog. All directories default to Interplay 0.

o dbtraits show.sports interplay 1

o dbtraits show.weather interplay 2

• ‘list d-i <directory>’ displays the Interplay server associated with the directory.

Installation Notes and Issues

iNEWS Installer • The iNEWS installer no longer allows installation on 64-bit operating systems.

FTS v3.1.x • FTS no longer includes an uninstall option. When removing FTS, delete the installation folder. When

installing multiple FTS instances on the same computer, ensure the installation folders differ.

• Beginning in FTS 3.1, "ftsdebug index statistics" reports index base file size as well as truncated file size. The truncated size is a measurement of the "in use" size of the files. When stories or queues are removed from an index base, the file size does not decrease, but the truncated size does decrease. The truncated size can be used to more accurately determine the free space in the index base. A truncated size of 0 (zero) indicates that the file cannot be truncated. Queues should be moved to different index bases if the truncated size of any file in the index base approaches two gigabytes

New End User License Agreement • Beginning with version 3.0, the iNEWS Server now displays an End User License Agreement (EULA) on

the master at the first configure/startup after an installation or upgrade. The EULA is in English and formatted at 80 columns for the iNEWS Console Multiplexor. Non-English EULAs are available on the release DVD.

• Beginning with version 2.8, an End User License Agreement is part of the iNEWS client software installation. This EULA must be accepted for installation to proceed. Administrators should generate a new silent install script before rolling out the client.

Upgrading iNEWS Server Software from Previous Versions • When upgrading iNEWS to 3.3.0 from any version, both dbgen p and dbgen m are required.

The dbgen p command initializes projects, and the dbgen m command initializes mailboxes for project-related notifications.

• When upgrading iNEWS from a version prior to 3.0, a dbrestore is required.

The dbrestore command converts the database to the NSML 3.0 specification. This conversion formats existing stories into well-formed XML documents. Stories containing invalid data will not be restored, and will display StoryCreate errors during the dbrestore process. Errors include 'Anchor missing element,' 'AE missing attachment,' and 'Finish aelist bad M.' These errors should be rare, and the NSML2 version of the story are accessible by the 'remnant ID' reported to the console.


21

Upgrading iNEWS Client Software from Previous Versions • Client upgrades have changed in version 3.0 to allow smoother minor and major upgrades in future. All

iNEWS 2.6+ language installations are seen as the same product, so a major upgrade from 2.6+ to 3.0 will uninstall all 2.6+ languages that are installed. Beginning in version 3.0, different language installations will be considered different products of the same family, allowing upgrades to version 3.x of specific languages without uninstalling all other 3.0 languages.

During transition periods, both 2.6+ and 3.0 clients may need to be on the same machine. The 3.0 installation uninstalls 2.6+, so if both are needed, simply re-install 2.x into a different directory after 3.0 has been installed.

• When installing or upgrading iNEWS, you must have adequate user rights to install the client software.

Note: During the install procedure, iNEWS client software version 3.0 will not provide an option to upgrade from any previous iNEWS version. iNEWS 2.6 and higher will automatically be uninstalled by the iNEWS 3.0 installation. iNEWS 2.1 and lower should be uninstalled manually before the iNEWS 3.0 installation.

Upgrading iNEWS v2.8 Client Software to Future Versions Due to changes made for Windows Vista, upgrades on Windows XP, Windows Server 2003, and Windows Vista require escalation to administrator privileges. When iNEWS administrators have set their system to roll out upgrades, Windows Limited and Power users will receive the iNEWS auto-upgrade dialog when logging in to a server. Once the user accepts the option to download the new installer they will receive a Run As dialog box in which an administrator's name and password must be entered to complete download and installation. If the Current user in the Run As dialog box is an administrator, it is necessary to deselect the check box called: Protect my computer and data from unauthorized program activity for the upgrade to succeed. This is a Windows security restriction outside of iNEWS client control.

Using the v2.8 download.exe program to download and upgrade to a new client version still requires a manual Run As… administrator. Limited users running download.exe without running the program as an administrator will not be able to complete installation.

Upgrading iNEWS Server from Previous Versions • When moving to the Red Hat Enterprise Linux 5.0 version from Red Hat 3.0, a full OS and iNEWS install

must be completed. There is no upgrade path from Red Hat 3.0 to Red Hat 5.0.

Qualified Asian Languages and IMEs

Korean The following Korean IME (standard Windows IME) is tested and qualified:

• Korean Input System (IME 2002)

Known Issue – While the Korean-text queue navigation works correctly, the Go To > Destination menu option does not allow direct navigation to folders with Korean-text names.

Chinese Simplified The following Chinese Simplified (PRC) IME (standard Windows IMEs) is tested and qualified:

• Microsoft Pinyin IME 3.0

• WangMa Wubi 86

• WangMa Wubi 98


22

Chinese Traditional The following Chinese Traditional IMEs (standard Windows IMEs) are tested and qualified:

• New ChangJie

• New Phonetic

• ChangJie

• Phonetic

• DaYi

The following Chinese Traditional IMEs (3rd party IMEs) have had minimal testing done and are not yet qualified or supported:

• Boshamy (WuXiaMi)

• Natural Input

Japanese The following Japanese IME (standard Windows IME) was tested and qualified:

• Microsoft Standard IME 2002 version 8.1

Vietnamese The following Vietnamese IMEs were tested and qualified:

• UniKeyNT 3.6

o Input Methods: Telex and VNI

o Character Set: Unicode

• Vietkey 2000 Build 10727

o Input Method: Telex

o Character Set: Unicode Pre-Compound

Known Issue with both Vietnamese IMEs - Certain Vietnamese characters do not get inserted correctly via keyboard macro when the IME is set to Vietnamese input. The workaround for this issue is to set the IME to English input before starting the macro.

Microsoft Windows Critical Updates Avid recognizes that it is very important to be able to deploy Microsoft security patches to our Windows-based products as quickly as possible. We recommend that systems be kept up to date in order to maintain the highest level of security and encourage you to install all critical operating system updates provided by Microsoft.

In the unlikely event that one of these updates causes an issue, it is recommended that you uninstall the update and contact Avid customer support as soon as possible. Avid will investigate the incompatibility and if necessary, will provide a software update or work around to allow our products to properly function with the Microsoft update in question.


23

Known Issues and Limitations

iNEWS Web Services API • The iNEWS Web Service API cannot be undeployed via the Tomcat management interface when Tomcat is

running on a Windows host.

To undeploy in Windows:

1. Stop the Tomcat service

2. Delete the inewswebservice file and folder from the Tomcat webapps directory.

3. Place the new .war file into the webapps directory.

4. Start the Tomcat service.

Note:Undeployment through the management interface works correctly if the Tomcat service is running on a Linux host.

Multiple Monitors • If running the iNEWS client software on a dual monitor workstation, there are some key issues you could

encounter:

• If the application is maximized at close, it will be maximized on the primary monitor when it is reopened, regardless of which monitor it was on when closed.

• Moving a user from a dual monitor machine to a single monitor machine, such as an undocked laptop, could result in the application opening to a screen that no longer exists. Workaround: Right click on iNEWS in the Windows taskbar and select Move. Then press one of the arrow keys on the keyboard; this will lock the application’s window to the mouse. You can then move the mouse pointer onto the screen and the iNEWS main window will move with it.

Macros and Keystrokes • Some PCs, when upgraded from Internet Explorer 6 to Internet Explorer 7 or 8, will experience issues with

macros that perform several functions in rapid succession; the macros might not complete all assigned activity in iNEWS. Avid is working with Microsoft on this issue. This issue is most apparent with macros that trigger the Local Print dialog box or the User Preferences dialog box.

Workaround: Place the name of the dialog box in square brackets immediately following the keystroke that opens the dialog box. For instance, instead of just {ctrl p} to open the Local Print dialog, the macro should be: {ctrl p}[Local Printing]. The text in the square brackets must match exactly the name of the dialog box as it appears in the title bar.

Another available workaround is to add {pause <#>} statements of one or two seconds to problem macros at the point in the macro where activity ceases. In the example of the Local Printing macros, the pauses are likely needed when typing a name of a printer or changing a print style.


24

Technical Support Information Most products feature a number of coverage options. Avid Assurance service offerings are designed to facilitate your use of Avid solutions. Service options include extended telephone coverage, automatic software maintenance, extended hardware warranty, and preferred pricing on replacement parts. Offerings and options may vary by product and are not available for all products.

For more information regarding Avid’s service offerings, visit www.avid.com/support or call Avid Sales at 800-949-AVID (800-949-2843).

Program availability and details might vary depending on geographic location and are subject to change without notice. Contact your local Avid office or your local Avid Reseller for complete program information and pricing. However, if you need help locating an Avid office or Avid Reseller near you, please visit www.avid.com or call in North America 800-949-AVID (800-949-2843). International users call 978-275-2480.

Accessing Online Support Avid Online Support is available 24 hours per day, 7 days per week. Search the Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read/join online message-board discussions.

To access Avid Online Support:

Go to www.support.avid.com .

Note: Supplemental documentation for this release, if available, is provided on the Knowledge Base. For the latest up-to-date information, browse the Knowledge Base at Avid Online Support.

http://www.avid.com/support�

http://www.avid.com/�

http://www.support.avid.com/�


25

Copyright and Disclaimer

Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at

www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse

assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any

medium except as specifically allowed in the license agreement.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and

recording, for any purpose without the express written permission of Avid Technology, Inc.

Copyright © 2010 Avid Technology, Inc. and its licensors. All rights reserved.

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer

software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all

rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS

§227.7202-1(a), as applicable.

Trademarks

Adrenaline, AirSpeed, ALEX, Alienbrain, Archive, Archive II, Assistant Avid, Avid Unity, Avid Unity ISIS, Avid VideoRAID, CaptureManager,

CountDown, Deko, DekoCast, FastBreak, Flexevent, FXDeko, iNEWS, iNEWS Assign, iNEWS ControlAir, Instinct, IntelliRender, Intelli-Sat, Intelli-sat

Broadcasting Recording Manager, Interplay, ISIS, IsoSync, LaunchPad, LeaderPlus, ListSync, MachineControl, make manage move | media, Media

Composer, NewsCutter, NewsView, OMF, OMF Interchange, Open Media Framework, Open Media Management, SIDON, SimulPlay, SimulRecord,

SPACE, SPACEShift, Sundance Digital, Sundance, Symphony, Thunder, Titansync, Titan, UnityRAID, Video the Web Way, VideoRAID, VideoSPACE,

VideoSpin, and Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

All other trademarks contained herein are the property of their respective owners.

Avid iNEWS v3.3.0 ReadMe • 0130-30596-01 Rev. A • 30 November 2010

This document is distributed by Avid in online (electronic) form only, and is not available in printed form.

Documents

Version 3.3.0 ReadMeresources.avid.com/SupportFiles/attach/Broadcast/ReadMe...Note: Since this release of iNEWS will be more widely distributed than previous versions, some notes on