Version 4.0.1 ReadMe - resources.avid.com

Version 4.0.1 ReadMe

1

��iNEWS® Newsroom Computer System Version 4.0.1 ReadMe

Date Revised Changes Made

23 October 2012 Added information for v4.0.1

11 September 2012 Initial v4.0 version (based on v3.5.3 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�


2

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

Fast Text Search .................................................................................................................................................... 5

Workstation/Server Compatibility Chart ............................................................................................................... 5

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

iNEWS Client ........................................................................................................................................................ 6

iNEWS Server ....................................................................................................................................................... 6 Command .............................................................................................................................................................. 6

MOS Gateway ....................................................................................................................................................... 6

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

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

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

NewsCutter ............................................................................................................................................................ 6 Teleprompter ......................................................................................................................................................... 6

Installation Notes and Issues ..................................................................................................................................... 7

iNEWS v4.0 ........................................................................................................................................................... 7

FTS v4.0 .............................................................................................................................................................. 11

FTS Installation and Configuration Procedure ................................................................................................ 11 Upgrade Notes and Issues ........................................................................................................................................ 17

iNEWS v4.0 ......................................................................................................................................................... 17

iNEWS v3.5.0 and FTS v4.0 ............................................................................................................................... 17

Changes between 4.0 and 4.0.1 ............................................................................................................................... 17

Changes between 3.5.3 and 4.0 ............................................................................................................................... 18

Server ................................................................................................................................................................... 18 Searching ............................................................................................................................................................. 18

Workstation ......................................................................................................................................................... 20

Spell-checker ....................................................................................................................................................... 20

MOS Integration .................................................................................................................................................. 20

New Features ........................................................................................................................................................... 21

For iNEWS v4.0 .................................................................................................................................................. 21 Users ................................................................................................................................................................ 21

Searching ......................................................................................................................................................... 21

BUCKET Queues ............................................................................................................................................ 21

MOS Integration .............................................................................................................................................. 22

For iNEWS v3.5 .................................................................................................................................................. 24

FTS .................................................................................................................................................................. 24


3

Blockmode Command ..................................................................................................................................... 24

For iNEWS v3.4.5 ............................................................................................................................................... 24

Community ...................................................................................................................................................... 24 SYSTEM.MAP Syntax .................................................................................................................................... 25

For iNEWS v3.4.0 ............................................................................................................................................... 26

Mapcheck Utility ............................................................................................................................................. 26

SYSTEM.MAP Queue .................................................................................................................................... 26

For iNEWS v3.3.0 ............................................................................................................................................... 26

Desktop Icon .................................................................................................................................................... 26 Projects and Facets .......................................................................................................................................... 26

Search Queues ................................................................................................................................................. 27

Queue Templates ............................................................................................................................................. 27

For iNEWS v3.1.0 ............................................................................................................................................... 27

Script Templates .............................................................................................................................................. 27

NewsCutter media ............................................................................................................................................... 28 For iNEWS v3.0.0 ............................................................................................................................................... 28

Hyperlinks ....................................................................................................................................................... 28

Story links ........................................................................................................................................................ 28

Comboboxes .................................................................................................................................................... 28

Check boxes ..................................................................................................................................................... 29

Duration ........................................................................................................................................................... 29 Calendar ........................................................................................................................................................... 29

Field write groups ............................................................................................................................................ 29

Editorial groups ............................................................................................................................................... 29

Colors .............................................................................................................................................................. 29

Lists ................................................................................................................................................................. 30 Play Interplay Low-res Streams ....................................................................................................................... 30

Qualified Asian Languages and IMEs ..................................................................................................................... 31

Korean ................................................................................................................................................................. 31

Chinese Simplified .............................................................................................................................................. 31

Chinese Traditional .............................................................................................................................................. 31

Japanese ............................................................................................................................................................... 31 Vietnamese .......................................................................................................................................................... 32

Microsoft Windows Critical Updates ...................................................................................................................... 32

Known Issues and Limitations ................................................................................................................................. 33

Plug-ins ................................................................................................................................................................ 33

UNC Paths ........................................................................................................................................................... 33


4

Keyboards ............................................................................................................................................................ 34

iNEWS Web Services API .................................................................................................................................. 34

Multiple Monitors ................................................................................................................................................ 34 Macros and Keystrokes........................................................................................................................................ 34

Technical Support Information ................................................................................................................................ 35

Accessing Online Support ................................................................................................................................... 35


5

Compatibility Notes and Issues This section contains compatibility information related to the iNEWS 4.0 release or earlier. Specific versions are mentioned when pertinent.

Fast Text Search Fast Text Search (FTS) version 4 is required for iNEWS Server version 3.5 and later. FTS 4 is not supported on any iNEWS Server versions lower than 3.5. FTS 4 is supported on Windows Server 2008 R2, Windows XP SP3 (32-bit), and Windows Server 2003 SP2 (32-bit). The recommended operating system is Windows Server 2008 R2. A full re-index is required with an upgrade to FTS 4.

Workstation/Server Compatibility Chart

2.8 Server 3.0/1/2 Server 3.3. Server 3.4/5 Server 4.0

2.8 Client Allowed Allowed Allowed Allowed Allowed

3.0/1/2 Client Not allowed Allowed Allowed Allowed Allowed

3.3 Client Not allowed Not allowed Allowed Allowed Allowed

3.4/5 Client Not allowed Not allowed Not allowed Allowed Allowed

4.0 Client Not allowed Not allowed Not allowed Not allowed Allowed

Community Feature

The 4.0 client can only connect to 4.0 and later servers, whether through community or direct connection.

If a 4.0 server is present in a community, all other servers in the community must be version 3.4.5 or later.

During transition periods, clients should not be upgraded to 4.0 until all servers that client connects to—directly or through community—are upgrade to 4.0 or later. In this situation, the latest 3.5.x client should be used until the full community is upgraded.

For iNEWS 3.4.5 to connect via community to iNEWS 3.4.5 or earlier servers, the 3.4.5 servers need to have a file named /site/env/gnews. The following string must be placed in that file: GCOMMUNITYSMALLDATABASE=1. See the New Features section of this document for additional information.

iNEWS Clients cannot be used in a community where any server in their path is of a lower version than the client.

• 3.4 clients can connect to 3.4 servers, which can connect through community to 3.4 servers.

• 3.4 clients cannot connect to pre-3.4 servers directly or through community.

• 3.3 clients can connect to 3.3 and higher servers, which can then connect through community to 3.3 and higher servers.

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

• 2.8 clients can connect to 2.8 and higher servers, which can then connect through community to 2.8 and higher server.

• 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.


6

iNEWS Client The iNEWS client software is qualified and supported for use on Windows 7 (32-bit), Windows 7 64-bit Service Pack 1, Windows Server 2008 R2, and Windows XP Professional (SP2 or SP3). This version of iNEWS is not officially supported for use on any other Windows operating system, including the pre-SP1 release of Windows 7 64-bit

• The iNEWS 4.0 client software cannot connect to servers earlier than iNEWS 4.0.

• The iNEWS 3.5.0 client software cannot connect to servers earlier than iNEWS 3.5.0.

iNEWS Server The iNEWS Server is qualified and supported for use on Red Hat Enterprise Linux 6.x 64 bit.

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.

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

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>.

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).


7

Installation Notes and Issues

iNEWS v4.0 • Changes to the iNEWS Server installation include the addition of domain information to /etc/krb5.conf.

This is necessary for sites that require User ID validation through an LDAP server for an External User account.

An iNEWS user account can be set as an External User when added to the database via a setting in the Add New User dialog box.

The purpose of the External User account is for the User ID credentials to be validated on an LDAP server instead of the iNEWS Server. For this external validation to work, customer domain information must be entered in the /etc/krb5.conf file during the iNEWS Server installation.

Below is a sample of the updated iNEWS v4.0 server installation procedure:

1. Set up user authentication. Initializing Kervberos configuration… The default realm is ‘EXAMPLE.COM’. Do you wish to change it? [y/n] y Enter the default realm: global.wavd.com Do you wish to set the default realm to “<domain of LDAP server>”? [y/n] y Creating certificate…

• With iNEWS v4.0, you can import users from LDAP servers. There are many ways of acquiring a list of LDAP users, various applications that can export LDAP information in LDIF and/or CSV formats; the following procedure is one option. To import users from an LDAP server: 1. Find domain and currently logged in LDAP server.


8

a. In a Windows MSDOS prompt from local computer, run the command: echo %UserDnsDomain% Example output: GLOBAL.WAVD.COM

b. Run the command: echo %LogonServer% Example output: \\MSN-DC01

c. From the output given, combine the results to make up the name of the logged in LDAP server on the domain. For example, using the previous sample output: msn-dc01.global.wavd.com

2. Find LDAP server on the domain to get the port number.

In a console session on the iNEWS Server, run the command in the following format: dig +short-t srv_ldap._tcp.<User DNS Domain> The User DNS Domain is the output obtain in the previous step of this procedure. For instance, type: dig +short-t srv_ldap._tcp.global.wavd.com Example output: 0 100 389 kai-dc01.global.wavd.com

0 100 389 ldn-dc01.global.wavd.com

0 100 389 msn-dc01.global.wavd.com

These sample results show all LDAP servers on the domain. The third set of numbers in the results is the port number; in this case, it is 389.

3. Search LDAP server from the iNEWS Server and create output file of users. a. Obtain Kerberos ticket-granting ticket by running the command:

kinit <windows user account name> b. When prompted, provide the Windows domain password. This will result with the account

being cached on the iNEWS Server so the credentials can be used by the ldapsearch function. c. Create a script file to search an LDAP server by starting a document on the local workstation

in Notepad. For example: ldapsearch\ -H ldap://msn-dc01.global.wavd.com:389 \ -b DC=global,DC=wavd,Dc=com \ “(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType

=80 5306368))” sAMAccountName cn sn mail objectclass \ kdestroy In the example, ldapsearch\ is the ldap command. The -H line is a URL for the AD server. The port number (389) shown in the example is the same sample port used in previous steps of this procedure. The -b line is the searchbase. It is possible that DC=global is not needed. The last line of the search is the query followed by the attributes that you want to see. You only need samaccountname and cn. The example is a set of three matching criteria that are joined together via the Boolean ampersand (&). The syntax is to enclose each term in parentheses and to prefix a set with the Boolean operator. So you see the ampersand (&) before the 3 criteria and the set is enclosed in parentheses. This example search limits the user account names, “sAMAccountName”, to those starting with “bri”. The “sAMAccountType” value is a Windows defined value for a user account. It might not be needed in the script you create, but note that the last term appears as if it has a carriage return. It does not have a carriage return before =80—it only appears that way because of margin settings for this document. Make sure the script that you create does not have carriage returns either.


9

d. Name the .txt file what you want, minus the tag (.txt). Copy script file from Windows

workstation to /tmp/ directory on the iNEWS Server, using the WinSCP ftp utility. e. Convert the script file to linux via a PUTTY session to the iNEWS Server. Go to the /tmp/

directory by typing cd /tmp/, and then run Dos2Unix by typing: dos2unix <name of script file>

f. Run the script file to see it return results by typing: sh-x /tmp/<name of script file> Example results:

+ ldapsearch ldap://msn-dc01.global.wavd.com:389 -b DC=global,DC=wavd,DC=com '(&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=805306368))' sAMAccountName cn sn mail objectclass

ldap_initialize( ldap://msn-dc01.global.wavd.com:389/??base )

Note: The utraits user input will only inport the cn and sAMAccountName attributes (shown as bold italics below).

# extended LDIF

#

# LDAPv3

# base <DC=global,DC=avidww,DC=com> with scope subtree

# filter: (&(objectClass=person)(sAMAccountName=bri*)(sAMAccountType=805306368))

# requesting: sAMAccountName cn sn mail objectclass

#

# John Doe, Users, Engineering, AVID Technology Inc, global.wavd.com

dn: CN=John Doe,OU=Users,OU=Engineering,OU=AVID Technology Inc,DC=global,DC=wavd,DC=com

objectClass: top

objectClass: person

objectClass: organizationalPerson

objectClass: user

cn: John Doe

sn: Doe

sAMAccountName: jdoe

mail: [email protected]

# Jane Smith, Users, North America, AVID Technology Inc, global.wavd.com


10

dn: CN=Jane Smith,OU=Users,OU=North America,OU=

AVID Technology Inc,DC=global,DC=wavd,DC=com

objectClass: top

objectClass: person

objectClass: organizationalPerson

objectClass: user

cn: Jane Smith

sn: Smith

sAMAccountName: jsmith

mail: [email protected]

# search reference

ref: ldap://DomainDnsZones.global.avidww.com/DC=DomainDnsZones,DC=global,DC=wavd,DC=com

# search result

search: 2

result: 0 Success

# numResponses: 4

# numEntries: 2

# numReferences: 1

4. After the output is verified as good, dump exported users to file by typing: sh –x /tmp/<script file> > /tmp/<output file>

Note: It will appear as if the command is halted. Technically, it is halted. What you don’t see is the “Enter LDAP Password:” prompt for the password used in the –D parameter of the script file. So after you enter the command, when it halts, enter the password. In a few moments, the linux prompt will be back, and the file will be placed in /tmp/ directory.

This file is then used to import new users into iNEWS.

5. Import

a. Users from output file.

Users in output file are imported into iNEWS using the utraits command. There are two file types that can be imported, csv and ldif. Common output of active directory query will be ldif. Sometimes customers might export their users to csv file eliminating the work above. You can also use the ‘list’ option in utraits to create a comma separated output from ldif output, or just use ‘list’ to verify the data to be imported into iNEWS. In each scenario a template user that already exists in the iNEWS system is used as the clone user. Every user in the output file will be imported using the template user’s settings and password. If you choose to give these imported users a different startup password than


11

what is used by the template user, you will need to include the ‘password’ option of utraits as well. Otherwise imported users will first login using the password of the template user, then be forced to create their own unique password. Import users into iNEWS from output file, using the standard ldif format.

Type: utraits ldif:<output file> clone <template user> password extern-user +eu

Import users into iNEWS from .csv file. Type: utraits csv:<output file> clone <template user> password extern-user +eu Example output for either import method: User jdoe added User jsmith added 2 user records added Running a list u j* command or logging in as the users will verify that the users are now imported into the system.

Note: To create a .csv file from an ldif output file, run the utraits command in the following format: utraits ldif:<ldif output file> list > <new csv file>.

b. Group names from output file

• Run the query script without the OU values • Note the OU values from the query results as these will tell you the group names • Modify –b value to include OU group data • Save script and rerun

You now have a query that will segregate based on groups

6. Use the kdestroy command to delete the Kerberos ticket-granting ticket.

FTS v4.0 • An FTS server installation supports up to 50 iNEWS systems.

FTS Installation and Configuration Procedure The new installation and configuration procedure for FTS server version 4 is provided here. To install and configure FTS:

1. Navigate to the FTS folder on the iNEWS installation DVD and click Setup.exe.


12

The InstallShield Wizard starts and displays a Welcome dialog box.

2. Click Next.

The License Agreement dialog box appears.

3. Read the Avid Software License Agreement, accept the terms, and click Next.


13

The Destination Folder dialog box appears.

4. (Optional) Click Change if you want to alter the default installation location. Otherwise, you can

accept the default and click Next.

5. Click Install when you are ready to begin the installation.

When the InstallShield Wizard completes the installation successfully, the following dialog box


14

appears.

6. Select the Launch Avid FTS Configuration check box and click Finish.

You are now ready to configure the system. The Fast Text Search configuration window appears. By default, no services are active.

7. Click Configure to configure the FTS_1 services.


15

The default configuration values will appear, as shown in the following illustration.

8. Set the Active field to ACTIVE. 9. Set the System Name to the name of the iNEWS system to be associated with this service. 10. (Optional) Modify the ports and index path. 11. Click Save.

A warning might appear to indicate if the Index Path Folder, indicated in the Index Path field, does not exist.

12. Click Yes to create the folder at the configured path. The firewall exceptions, service configurations, and index path are created at this time.

13. Click Back to return to the main configuration window and start the services. The configuration

window will now display the active services with the configured system name. 14. Configure additional systems by selecting unused FTS_# entries from the list.


16

Stopping and starting services should be performed from the Fast Text Search configuration window, using the Pause and Play buttons next to the relevant system name. Even though the services will appear in the Windows Services list, all stopping and starting should be performed from the FTS management UI.

15. By default, logs and index bases are stored in C:\ProgramData\Avid\FTS in Windows Server 2008 R2 and in C:\Documents and Settings\All Users\Avid\FTS in Windows XP and 2003. If FTS needs to be uninstalled, all FTS entries should be set to “DISABLED” prior to the uninstall. Below is sample output from ftsdebug…

NRCS-A$ ftsdebug index statistics Service name: ftsindex1

Version: 4.0.0.33

Process id: 2364

Started: 12/20/11 07:30:47

Debug value: 0

Tuning: on

Index Base: C:\ProgramData\Avid\FTS\NRCS

iNEWS System: nrcs

Port: 6100

Current Index: 000

Total Documents: 39736

Requests Serviced: 95081

000 File sizes (KB): 25702/25660 16376/1 15823 1

Documents: 34076 Added: 39724 Removed: 5651 Replaced: 3 Purged: 0


17

001 File sizes (KB): 592/543 572/1 1215 1


003 File sizes (KB): 2540/2528 2547/1 1086 1


010 File sizes (KB): 4/0 4/1 3 1


An index rebuild is required when upgrading to FTS 4.

To build the iNEWS index:

Perform the following commands: ftsdebug index statistics — This confirms communication with the FTS Index

service. ftsdebug search statistics — This confirms communication with the FTS Search

service. list c fts — This displays the ftsseek and ftsindex device numbers (ftsseek# and

ftsindex#). stop <ftsindex#> <ftsseek#> — This stops the FTS devices. dbpurge system.index 0 — This clears any unhandled index requests. dbpurge system.fts 0 — This clears any unhandled search requests. dbtraits . reindex > /dev/null & — This creates an index request for each

indexed queue. The output is sent to /dev/null because of output volume.

Note: Alternatively, more important wires and recent archives can be added to the index before adding the full database during the reindexing.

start <ftsindex#> <ftsseek#> — This restarts the FTS devices.

Upgrade Notes and Issues This section contains information related to upgrading from previous versions of iNEWS.

iNEWS v4.0 • When a client database is upgraded to v4.0, current projects will get the new BUCKET queue; however,

this queue is not yet indexed, which is required for all stories associated with projects and/or facets. After the dbrestore, the administrator must run dblines c: to index the new BUCKET queues. After that an iNEWS user will be able to go to the BUCKET queues and select their preferred index base.

iNEWS v3.5.0 and FTS v4.0 • An upgrade to iNEWS 3.5 and FTS 4 requires a full rebuild of each index.

Changes between 4.0 and 4.0.1 • In previous releases, dragging and dropping text between production queues could crash the iNEWS client

under Windows XP. This has been fixed. • In previous versions of iNEWS, diskcopy performance was slow at high copy levels and over-taxing at low

copy levels. This has been fixed.


18

• In previous versions of iNEWS, if you added "DEKOMOS DEKOMOS" as an mos-map entry, DEKOMOS items could not be loaded. They produced an "invalid MOS item" error at the client and a " mosId[dekomos] does not map to device[DEKOMOS]" error at the server. This has been fixed.

• In previous versions of iNEWS, there were client Import/Export dialog display issues with top left and right areas of the navigation bar. This has been fixed.

Changes between 3.5.3 and 4.0

Server • In previous version of iNEWS 3, iNEWS worked on 32-bit operating systems with 1k blocks. Beginning

with iNEWS v4.0, this has changed. The iNEWS newsroom computer system version 4.0 runs on RHEL 6 64-bit with 4k blocks.

• User credentials are now passed to server using encryption. This functionality happens on the backend and is invisible to iNEWS users, so there is no change to the user interface.

• In previous versions of iNEWS 3, forced logouts from the server would lose the user's last known location and instead default to Project tree view the next time they logged into iNEWS. This is fixed.

• In previous versions of iNEWS 3, UTF16 code was being replaced with the wrong surrogate code. This is fixed.

Searching • Beginning with iNEWS v4.0, date variables have been added as options in the Search Queue and Find All

dialog boxes.


19

The options are documented in more detail in the following table:

Option Description

Today Range = 00:00:00 through 23:59:59 of present day

Tomorrow Range = 00:00:00 through 23:59:59 of tomorrow

Yesterday Range = 00:00:00 through 23:59:59 of yesterday

Next Week Range = 00:00:00 of next Sunday through 23:59:59 of next Saturday

This Week Range = 00:00:00 of this Sunday through 23:59:59 of this Saturday

Last Week Range = 00:00:00 of prior Sunday through 23:59:59 of prior Saturday

Next Month Range = 00:00:00 of the first day of next month through 23:59:59 of the last day of next month

This Month Range = 00:00:00 of the first day of this month through 23:59:59 of the last day of this month

Last Month Range = 00:00:00 of the first day of prior month through 23:59:59 of the last day of prior month

Next Quarter Range = 00:00:00 of the first day of first month of next quarter through 23:59:59 of the last day of last month of next quarter

This Quarter Range = 00:00:00 of the first day of first month of this quarter through 23:59:59 of the last day of last month of this quarter

Last Quarter Range = 00:00:00 of the first day of first month of prior quarter through 23:59:59 of the last day of last month of prior quarter


20

Option Description

Note: Quarters are defined as:

1st quarter = January 1st through March 31st

2nd quarter = April 1st through June 30th

3rd quarter = July 1st through September 30th

4th quarter = October 1st through December 31st

Next Year Range = 00:00:00 January 1st through 23:59:59 December 31st of next year

This Year Range = 00:00:00 January 1st through 23:59:59 December 31st of this year

Last Year Range = 00:00:00 January 1st through 23:59:59 December 31st of prior year

Workstation • In previous versions of iNEWS, when a new user account was created without MAIL and NOTES queues,

messages would appear informing you that those queues could not be found. Beginning with iNEWS v4.0, MAIL and NOTES queues are automatically created when new user accounts are made; therefore, pop-up warnings about queues not being found no longer appear.

• In previous versions of iNEWS 3, stories that contained invalid encoded characters would fail to ingest properly. This is fixed.

• In previous versions of iNEWS 3, {Alt} combination keystrokes would insert bad characters after using the SGT application. This is fixed.

• In previous versions of iNEWS 3, queue's named with special characters, and queues inside folders named with special characters could not be searched against because the special character corrupted the search string. This is fixed.

• In previous versions of iNEWS 3, some characters were not copy and pasted from iNEWS story body to other 3rd party products such as Microsft Word. This is fixed.

• In previous versions of iNEWS, duplicate WIRES.DISTRIBUTION lines would cause wires to terminate the news program. This is now fixed.

• In previous versions of iNEWS 3, story links inside script templates were not active without user intervention to add a space or carriage return to the end of the story link instead of being active immediately upon import. This is fixed.

Spell-checker • In previous versions of iNEWS 3, certain lines of text would cause iNEWS to hang when spell check was

run. This is fixed. • In previous version of iNEWS 3, when cursor was placed inside of a word, spell check would find a

spelling error for the last part of that word. This is fixed.

MOS Integration • In previous versions of iNEWS 3, spaces could be entered into the item-channel field that would be sent to

the MOS device, which would result in the wrong channel assignment. This is fixed. • In previous versions of iNEWS 3, editing stories with MOS cues in the Web client would add a space

between the AMCPID and template ID, which could cause problems with some customer automation. This is fixed.

• In previous versions of iNEWS 3, MOS time updates were not updating their times in the iNEWS story. This is now supported.


21

New Features This section contains a listing of new features.

For iNEWS v4.0

Users

• This version of iNEWS provides the optional ability to import users. For more information, see “Installation Notes and Issues” on page 7.

• This version of iNEWS provides the ability to set a user account as an External User. For more information, see “Installation Notes and Issues” on page 7.

Searching

• In this version of iNEWS, the searching and Find-All features were enhanced to include user-definable date variables. For more information, see “Searching” on page 18.

BUCKET Queues

• The iNEWS newsroom computer system now offers BUCKET queues as part of its existing Projects feature. Also, iNEWS lets users create new stories inside of Projects in either the ALL or FACET queues, as well as in the new BUCKET queue added to all projects. The procedures for doing so are as follows: To create new story inside of a project: 1. On the Project tab, navigate to the project’s queue in which you want to add the story, such as:

BUCKET, ALL, or FACET. 2. Create the new story.

• New stories created in either the BUCKET or ALL queues are automatically associated to the project and cannot be de-associated from it, although they can be associated to any other project or facet as well. The following illustration shows a newly created story in the ALL queue, associated to the Education project.

The following illustration shows a newly created story in the BUCKET queue, associated to the


22

Education project.

• New stories created in the FACET queue are associated to the FACET by default and displayed

inside of it. De-association of a story created in the FACET queue does not delete the story from the project’s bucket.

MOS Integration

• iNEWS v4.0 now lets users insert MOS object placeholders within iNEWS stories in either the story form or as a story’s production cue. The procedures for doing so are as follows: To insert a MOS object placeholder: 1. Right-click while mouse pointer is either in the Story Form panel or in the Story Text panel. 2. Select Insert Placeholder. 3. Select the MOS device.


23

4. Enter a new slug or use the default.

5. (Optional) Enter a description. 6. Click OK.

If you right-clicked in the Story Form panel, the new MOS object placeholder appears in the story form.

If you right-clicked in the Story Text panel, the new MOS object placeholder appears as a production cue in the Instruction panel.


24

The MOS device user can update the placeholder with a real ID and object by turning on or loading the monitor server. MOS Gateway will then return data back to iNEWS where the placeholder is located in either the story form (below at left) or production cue (below at right).

For iNEWS v3.5

FTS

• The iNEWS Server now logs a diagnostic when any queue is added or removed from indexing. This feature allows tracking index rebuild progress without scheduling ftsdebug index statistics commands. The first diagnostic reports the start of indexing, and the second diagnostic reports total number of documents indexed.

Dec 22 10:20:03 NRCS-B S120: Queue WIRES.ALL::add:0:-1:-1:0

Dec 22 10:23:24 NRCS-B S120: Queue WIRES.ALL 11226 adds

Blockmode Command

• Some customers send many changing stories via FTP to third party FTP servers. This can consume many TCP port numbers and with a large TIME_WAIT setting prevents the reuse of those port numbers. This can lead to “port exhaustion,” that is, no ports available for further transfers. When using Stream Transfer Mode, the end-of-file is denoted by the closing of the data connection, hence the need for a new connection for every transfer. Block Transfer Mode includes end-of-file information in the data so the data connection can be kept open for successive data transfers. This can be used when the iNEWS proprietary FAST mode cannot be used. The syntax is: blockmode [no|yes] If Yes or No is not declared, blockmode all by itself assumes a value of Yes.

Note: To function correctly, the blockmode command must be placed after the scan/bscan/poll/bpoll command and before the open command. The blockmode command will take precedence over the fast command default.

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

Community Because of upcoming expansion to allow databases larger than 16GB, the iNEWS Community communication protocol was modified. This modification breaks compatibility with iNEWS Server version 3.4.4 and earlier. iNEWS 3.4.5 still supports Community communication with either iNEWS 3.4.5 or earlier for systems with a small database, but for those with large databases, Community communication is


25

supported only with iNEWS 3.4.5 and later. Both simultaneously are not supported. All 2.x and 3.x servers should be upgraded to at least 3.4.5 when a large database server is added to the community.

By default, iNEWS 3.4.5 is configured to support Community communication with large databases. Even though it is still a 16GB database, a 3.4.5 default configuration is considered a large database in regard to iNEWS Community.

To configure iNEWS 3.4.5 as a small database:

Create the file /site/env/gnews. In this file, place the following line: GCOMMUNITYSMALLDATABASE=1.

For example:

NRCS-A$ cat /site/env/gnews GCOMMUNITYSMALLDATABASE=1

Rules:

• A single community cannot have both small and large databases.

• iNEWS 3.4.4 and earlier cannot be in a community with large database servers.

• Large database servers cannot be in a community with small database servers.

• iNEWS 3.4.5 can be in a community with iNEWS 3.4.5 if both systems have the same GCOMMUNITYSMALLDATABASE setting, large or small.

Troubleshooting:

Below are the error messages and the cases in which they will appear:

Case Error Message

3.4.5 Large connecting to 3.4.4 or earlier

local: G###: Error (1) during SETCOMMUNITY to <REMOTE>

remote: C###: Cannot service request: eB

3.4.4 or earlier connecting to 3.4.5 Large

local: G###: Unable to set community server number with <REMOTE> (9)

remote: C###: Cannot participate in small database community

3.4.5 Large connecting to 3.4.5 Small


remote: C###: Cannot participate in large database community

3.4.5 Small connecting to 3.4.5 Large


remote: C###: Cannot participate in small database community

SYSTEM.MAP Syntax The SYSTEM.MAP syntax has changed slightly. For iNEWS Command (wnasvr) CGs, there is now an optional sixth column. When blank, the value defaults to YES. When this column is set to "NO," iNEWS monitor will not validate style names before sending CGs to Command. This change allows the loading of CG items to the Command playlist before they exist in Command’s inventory.

<rundown> <EL directory> <composite> <group> <timeout>


26

wnasvr <primary> <backup> <form>

cg <AMCP ID> <alias> <default channel> <style> <validate style YES/NO>


Mapcheck Utility The mapcheck utility validates all stories in a designated queue. Errors are produced for any syntax violations, missing queues (rundown, composite, or event), and trait omissions.

For example, typing mapcheck -f system.map at the console will make the system analyze all stories in SYSTEM.MAP. It sets the monitored trait for any listed rundowns that do not have the trait set, and it reports any syntax errors in SYSTEM.MAP. Mapcheck should be run after an upgrade to 3.4 and as part of error investigation.

NRCS-A$ mapcheck

usage: mapcheck [-v] [-f] <queue name>

Flags

f - Fix monitored trait

v - Verbose

vv - Very verbose

vvv - Very very verbose

SYSTEM.MAP Queue The entire SYSTEM.MAP queue is now used to define rundowns. The behavior is similar to the SYSTEM.RESOURCE queue, where separate stories can be used to segregate rundown definitions into categories, such as ”morning”, “afternoon”, and “evening”. Multiple small stories are easier to manage and maintain than the one large story used previously.

Restrictions:

• A single rundown’s definition cannot span stories.

• The same rundown cannot appear in separate stories; only the first instance will be consulted.


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 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.


27

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 example, a queue named SYSTEM.PROPERTIES.RUNDOWN can be created and assigned all standard rundown traits: Inverted, Refresh, Monitored, Save All, etc. When a user selects the Copy From Template button, they will see "RUNDOWN" as an option. Selecting that option will apply the traits from SYSTEM.PROPERTIES.RUNDOWN to the queue they are currently editing. 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.


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.


28

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

4. Click OK.

After 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}.


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.


29

• 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


30

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


31

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.

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

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


32

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.


33

Known Issues and Limitations

Plug-ins • Some plug-ins, such as AMG Journalist, will not paint correctly in iNEWS.

Workaround:

To resolve the painting problem issue, use the following procedure.

Note: AMG Journalist is used in the procedure as a plug-in example.

1. In the iNEWS executable directory, create a new text file named ActiveXRedraw.txt. • For 64 bit workstations, the directory is located at: C:\Program Files (x86)\Avid\iNEWS\ • For 32 bit workstations, the directory is located at: C:\Program Files\Avid\iNEWS\

2. Open the registry editor, using regedit in the Run dialog box. 3. Select Edit > Find > AMG Journalist and locate the CLSID for the plug-in.

• For 64 bit workstations, the CLSID is located at: Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\

• For 32 bit workstations, the CLSID is located at: Computer\HKEY_CLASSES_ROOT\CLSID\

4. Take the CLSID, which is the folder name, and put it into the ActiveXRedraw.txt file.

5. Save the file. 6. Reload iNEWS. The painting problem for plug-ins like AMG Journalist will be resolved.

UNC Paths • As a result of the server-side URL changes in iNEWS 3.4.2, UNC paths with spaces no longer work

correctly in the iNEWS client software. In a future version of the iNEWS client software, these links will be client-only, allowing a user to launch them from the iNEWS Workstation without saving them as URLs on the iNEWS Server.


34

• Third-Party IntegrationiNEWS integration with Intelliscribe printing should be configured at 300 DPI with "Enhanced Features" disabled. Setting a higher DPI or enabling enhanced features can cause long delays in printing.

• There are screen painting issues when the Vertigo Xmedia plug-in and the Aurora Assignment List plug-in (version 7 or later) are both installed on the same client. The Xmedia splash screen can cause the Xmedia tree to be inaccessible. Workaround: When this issue occurs, the workaround is to rename or remove skinCrafter3_vs2008.dll from the Assignment List installation directory.

Keyboards • Some early versions of iNEWS 3 created NSML links in SYSTEM.KEYBOARDS. When the dblines

command fixes those links, they become invalid keyboards. To repair the keyboards, remove the excess whitespace at the beginning and the middle of the keystroke line.

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 after the K_WINDOW token value 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}{window Local Printing}. The text following ‘window’ must match exactly the name of the dialog box as it appears in the title bar. The ‘K_WINDOW /window’ token can be changed in /site/dict/keymacros.


35

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.

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 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/�


36

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 © 2012 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 v4.0.1 ReadMe • 9390-65146-00_A • 23 October 2012

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