avid technology, inc. setup of standalone (peer to peer...

Avid Technology, Inc. Setup of Standalone (Peer to Peer) Transfer Manager April 5, 2005

Broadcast Support 1

Objective: This document discusses the concept of Standalone or (Peer to Peer) Transfer Manager Configuration. Primary Reason: This allows individual editing clients to exchange media with other editing client without the use of a separate server with Transfer Manager software installed. I. Standalone or Peer to Peer Transfer Manager Configuration......................................................................... 2

A. Each editing client requires the following software to be installed. ........................................................... 2 B. Configuring the Standalone TM Client Configuration. .............................................................................. 2

II. Setting Up Standalone Transfer Manager for Windows XP (ncworkgroup1)................................................ 2 A. If the other workgroup is not a Windows XP machine, use the configuration steps for Windows 2000 and the configuration parameters below. ............................................................................................................ 2 B. Identify the PC Name.................................................................................................................................. 2 C. Configure the TM Client............................................................................................................................. 4 D. Now configure the Standalone Transfer Manager Server........................................................................... 6 E. Start the TM Server software.................................................................................................................... 10 F. Start the editing client. .............................................................................................................................. 10 G. Windows XP Standalone Transfer Manager Log File.............................................................................. 10

III. Setting Up Standalone TM for a Windows 2000 Machine (ncworkgroup2)............................................ 14 A. If the other workgroup is not a Windows 2000 machine, use the configuration steps for Windows XP and the configuration parameters below. .......................................................................................................... 14 B. Identify the PC Name................................................................................................................................ 14 C. Configure the TM Client........................................................................................................................... 15 D. Configuring the Standalone TM Server Configuration. ........................................................................... 18 E. Starting Standalone TM. ........................................................................................................................... 22 F. Start the editing client. .............................................................................................................................. 22 G. Windows 2000 Standalone Transfer Manager log file ............................................................................. 22

IV. Changing Transfer Manager Options so users cannot type in the Transfer Manager Server window when the TMServer prompt is not displayed.................................................................................................................. 26 V. Standalone TM Troubleshooting. ................................................................................................................. 28

A. When transferring media........................................................................................................................... 28 B. Important Notes: ....................................................................................................................................... 28 C. Make sure the IP addresses are correct in the hosts files or the DNS server. ........................................... 28 D. When transferring from one NC to another. The clip and sequence information will go into the active bin on the NC sent to. ....................................................................................................................................... 28


Broadcast Support 2

I. Standalone or Peer to Peer Transfer Manager Configuration A. Each editing client requires the following software to be installed.

1. Transfer Manager Server. 2. Transfer Manager Client. 3. NewsCutter Adrenaline FX, XP or NewsCutter Meridien FX

B. Configuring the Standalone TM Client Configuration. 1. Each editing client is going to be considered a workgroup, not to be confused with a Microsoft Windows workgroup. 2. The client workgroup configurations are configured within the editing client application itself. In this example we are using NewsCutter for our editing client.

II. Setting Up Standalone Transfer Manager for Windows XP (ncworkgroup1). A. If the other workgroup is not a Windows XP machine, use the configuration steps for Windows 2000 and the configuration parameters below. B. Identify the PC Name.

1. Right click on the "My Computer" icon and select "Properties" from the list box.


Broadcast Support 3

2. The "System Properties" window is displayed.


Broadcast Support 4

3. Select the "Computer Name" tab.

4. The computer name to use is "BCSADRENALINEFX". 5. Select "Cancel".

C. Configure the TM Client. 1. Open the NC Software. 2. Select the "Project-->Settings-->Transfer" setting. If there are multiple "Transfer" settings, select the one with the check box on the left hand side.


Broadcast Support 5

3. The "Transfer Settings - Current" window is displayed. 4. Select "Accept After Timeout..."

5. Select the "TMClient.ini" tab. 6. The "Transfer Settings - Current" window is displayed.


Broadcast Support 6

7. Select "Edit". 8. The "Edit My Workgroup" window is displayed.

9. Type in the PC Name as the Server, "BCSADRENALINEFX" and the Avid workgroup name assigned to this PC, "ncworkgroup1". The Avid Workgroup is not the same as the windows workgroup. 10. Select "OK" in the "Edit My Workgroup" window. 11. Select "OK" in the "Transfer Settings - Current" window.

D. Now configure the Standalone Transfer Manager Server. 1. From the "Windows Task Bar" 2. Select "Start-->Programs-->Avid-->TransferManager Server Configuration"


Broadcast Support 7


Broadcast Support 8

3. In the Standalone Settings.

a) Check "Accept incoming transfer after timeout" b) Select the "Browse" button under "Directory for incoming"

c) Select "OMFI MediaFiles" in the "C" directory. d) Select "OK" e) In the upper left hand corner, "No-login workspace for incoming transfers:" f) Type "OMFI Media Files".

4. In the lower left hand corner, the "System Settings" section. a) Check "Enable auto-cleanup for transfer queues". b) Check "Standard logging on"


Broadcast Support 9

5. Workgroups, in the top middle section. a) Check "Workgroup transfers enabled" b) Check "Incoming workgroup transfers enabled. c) Change "Max. simultaneous workgroup" to 2. d) Browse "Directory for temporary composition files": Select "C:\temp". Make sure this directory exists in the windows folder.

e) Select "OK" f) Check the "Delete temporary composition files after transfer" option. g) Add the remote workgroup. This is the info from the other standalone TM we have already configured. h) Select "Add" next to "Workgroup names:".

i) Enter the workgroup from the other machine as "ncworkgroup2" and the Server name as "bcncfx".


Broadcast Support 10

j) Select "OK".

6. On the right hand side in the middle, select "Total Transfers (All Types)" a) "Max. simultaneous transfers" to 2.

7. Select "Save"

8. Select "OK". E. Start the TM Server software.

a) From the "Windows Task Bar" b) Select "Start-->Programs-->Avid-->TransferManager Server" c) A "DOS" window with text is displayed. Do not close this window. This needs to be open in order for the transfer manager server to run.

F. Start the editing client. a) The Transfer Manager Server window will display the following. b) The most important part is to make sure the "Hold for Permissions" value is "TRUE". c) This "Hold for Permissions" value is displayed two times, the first time it is "disabled and the second time is "TRUE".

G. Windows XP Standalone Transfer Manager Log File

---------------------------------------------------------------------------------------------------------------------------------------------------------------- 03/11/2005 15:03:04 ------------------------------ 03/11/2005 15:03:04 Starting Transfer Manager Server 03/11/2005 15:03:04 CompanyName: Avid Technology, Inc. 03/11/2005 15:03:04 ProductName: Avid Transfer Manager 03/11/2005 15:03:04 ProductVersion: 2.7.2 03/11/2005 15:03:04 TransferManager::TransferManager: logging level = 3 03/11/2005 15:03:04 APIMessageInterface::APIMessageInterface Starting listener - com.avid.xmgr 03/11/2005 15:03:04 TransferManager::GetInitializationData: WorkGroups: HostName = [0] ncworkgroup2 bcncfx 03/11/2005 15:03:04 TransferManager::GetInitializationData: Primary directory =C:\OMFI MediaFiles 03/11/2005 15:03:04 TransferManager::GetInitializationData: comp directory = c:\temp 03/11/2005 15:03:04 TransferManager::TransferManager: No Unity drives found, scanning local media drives.



03/11/2005 15:03:04 TransferManager::TransferManager: Scan local media drives. 03/11/2005 15:03:04 --- C:\OMFI MediaFiles 03/11/2005 15:03:04 TransferManager::StartPMRManager: CacheReset = True 03/11/2005 15:03:04 TransferManager::StartPMRManager: UpdateCache = True 03/11/2005 15:03:04 TransferController::TransferController Entered. 03/11/2005 15:03:04 TransferController::TransferController Started TransferControllerQueue for Workgroup. 03/11/2005 15:03:05 TransferController::StartupMCT Entered. 03/11/2005 15:03:05 TransferController::StartupMCT This Hostname is BCSADRENALINEFX. 03/11/2005 15:03:05 TransferController::StartupMCT AM::Controller::Create 03/11/2005 15:03:05 TransferController::StartupMCT Creating AM::NetParams npMCT 03/11/2005 15:03:05 TransferController::StartupMCT Creating AM::Plugins gPlugins 03/11/2005 15:03:05 TransferController::StartupMCT Starting MCTListener. 03/11/2005 15:03:05 TransferController::StartupMCT Leaving 03/11/2005 15:03:05 *** \\\Transfer Manager\OMFI MediaFiles\TM_BCSADRENALINEFX -- contains 0 file(s) 03/11/2005 15:03:05 TransferController::TransferController Leaving. 03/11/2005 15:03:05 TransferController::Run Entered, starting main thread loop. 03/11/2005 15:03:05 TransferManager::DumpTMConfigurationParms 03/11/2005 15:03:05 --- Playback transfers: disabled 03/11/2005 15:03:05 --- Ingest transfers: disabled 03/11/2005 15:03:05 --- Workgroup transfers: enabled 03/11/2005 15:03:05 --- Incoming Workgroup transfers: enabled 03/11/2005 15:03:05 --- MaxPBXfers: 0 03/11/2005 15:03:05 --- MaxIGXfers: 0 03/11/2005 15:03:05 --- MaxIncomingWGXfers: 4 03/11/2005 15:03:05 --- MaxOutgoingWGXfers: 1 03/11/2005 15:03:05 --- ConnectionManager: disabled 03/11/2005 15:03:05 --- AssetManager: disabled 03/11/2005 15:03:05 --- MaxCMConnections: 2 03/11/2005 15:03:05 --- Hostname: BCSADRENALINEFX 03/11/2005 15:03:05 --- AMHostname: 03/11/2005 15:03:05 --- SStreams: 2 03/11/2005 15:03:05 --- HoldForPermission: disabled 03/11/2005 15:03:05 --- IncomingRequestTimeout: 0 03/11/2005 15:03:05 --- AcceptOnTimeout: TRUE 03/11/2005 15:03:05 --- Rundown: disabled 03/11/2005 15:03:05 --- NewsroomServerHostname: 03/11/2005 15:03:05 --- PlaylistScheduleFilename: 03/11/2005 15:03:05 --- AutoCleanup: enabled 03/11/2005 15:03:05 --- AutoCleanupAge: 360 minutes. 03/11/2005 15:03:05 --- AutoCleanupInterval: 12 minutes. 03/11/2005 15:03:05 --- Default Unity Volume: 03/11/2005 15:03:05 --- Default Workspace: Transfer Manager 03/11/2005 15:03:05 --- Default Catalog: Transfer Manager 03/11/2005 15:03:05 --- Primary Directory: C:\OMFI MediaFiles 03/11/2005 15:03:05 --- Composition Directory: 03/11/2005 15:03:05 --- Metadata Directory: c:\temp 03/11/2005 15:03:05 --- MediaFormat: OMF 03/11/2005 15:03:05 --- Max DET Push Transfers: 0 03/11/2005 15:03:05 --- Max DET Pull Transfers: 0 03/11/2005 15:03:05 --- Max DET Remove Transfers: 0 03/11/2005 15:03:05 --- Max DET Iterate Transfers: 0 03/11/2005 15:03:05 --- OMM version: 2 03/11/2005 15:03:05 --- Delete temp comp files: enabled 03/11/2005 15:03:05 --- Network timeout(millisec): -1 03/11/2005 15:03:05 --- Debug trace: disabled 03/11/2005 15:03:05 --- DET Config Directory: C:\Program Files\Avid\TransferManager Server\DET



03/11/2005 15:03:05 --- XML Cookie Directory: c:\temp\XMLCookies 03/11/2005 15:03:05 --- UNC file names: enabled 03/11/2005 15:03:05 --- ChunkSize (frames/ingest): 5400 03/11/2005 15:03:05 --- IngestQLimit (frames): 100 03/11/2005 15:03:05 --- PMRScan: enabled 03/11/2005 15:03:05 --- PMRScanIntervalShallow: 15 minutes. 03/11/2005 15:03:05 --- PMRScanIntervalDeep: 0 minutes. 03/11/2005 15:03:05 --- File Balancing: enabled 03/11/2005 15:03:05 --- Max files: 10000 files 03/11/2005 15:03:05 --- File Count Threshold (%): 95 03/11/2005 15:03:05 --- Logging level: 1 03/11/2005 15:03:05 PMR Media Folders -- primary media folders 03/11/2005 15:03:05 PMR Media Folders -- secondary media folders 03/11/2005 15:03:05 --- C:\OMFI MediaFiles TMServer> 03/11/2005 15:03:41 APIMessageHandler::ProcessVersion: version: 0.8 03/11/2005 15:03:41 APIMessageHandler::ProcessVersion: releaseVersion: 2.0 03/11/2005 15:03:41 APIMessageHandler::ProcessVersion: Champlain or higher 03/11/2005 15:03:41 TransferController::SetStandaloneMode true 03/11/2005 15:03:41 In APIMessageHandler::ProcessSetIncomingResponse called: Hold For Permission value is TRUE 03/11/2005 15:03:41 In APIMessageHandler::ProcessGetDeviceList called: List Type is: WorkGroup TMServer> ----------------------------------------------------------------------------------------------------------------------------------------------------------------



C:\WINDOWS\TMServer.ini

C:\Program Files\Avid\NewsCutter Adrenaline FX\TMClient.ini

[Asset Manager] enabled=0 [Connection Manager] enabled=0 NumConnections=2 [Playback Transfers] enabled=0 [Ingest Transfers] enabled=0 [Workgroup Transfers] Incoming Enabled=1 Enabled=1 MaxTransfers=1 [Incoming Transfers] accept=1 Timeout=0 DeleteTempCompFiles=1 AcceptUnauthIncoming=1 DefaultWorkSpace=OMFI MediaFiles [Directories] Composition=c:\temp Primary=C:\OMFI MediaFiles [DET] XMLCookieDirectory=c:\temp\XMLCookies MaxPushTransfers=0 MaxPullTransfers=0 [System Stuff] AutocleanupEnabled=1 LoggingLevel=1 AutocleanupAge=360 AutocleanupInterval=12 [Workgroups] num=1 wgname_1=ncworkgroup2 servername_1=bcncfx [Playlist] use=0

[MyServer,MyWorkgroup] MyServer = BCSADRENALINEFX, ncworkgroup1



III. Setting Up Standalone TM for a Windows 2000 Machine (ncworkgroup2) A. If the other workgroup is not a Windows 2000 machine, use the configuration steps for Windows XP and the configuration parameters below. B. Identify the PC Name.

1. Right click on the "My Computer" icon and select "Properties" from the list box.

2. The "System Properties" window is displayed.



3. Change to the "Network Identification" tab.

4. Use the "Full computer name" value, in this example "bcncfx" for the "Server Name" in the "Edit My Workgroup" window. The "Edit My Workgroup" window will be discussed further below.

C. Configure the TM Client. 1. The Avid workgroup name is assigned by the user; in this example we are going to use "ncworkgroup2". 2. Select "NewsCutter-->Project Window-->Settings Tab-->Transfer" and if there are more than one "Transfer Setting" displayed, select the one with a check mark on the left hand side.



3. The "Transfer Settings - Current" window is displayed. 4. Select "Accept After Timeout..."

5. Change to the "TMClient.ini" tab.



6. Select "Edit". The "Edit My Workgroup" window is displayed.

7. Type in the name of the PC you are on as outlined from right clicking on "My Computer" and selecting "Properties" from the list box. 8. In the "Edit My Workgroup" window, select "OK". 9. In the "Transfer Settings" window, select "OK".



D. Configuring the Standalone TM Server Configuration. 1. Start the "TransferManager Server Configuration".



2. In the "Standalone Setting". 3. Check "Accept incoming transfer after timeout" 4. Below "Directory for incoming transfers:" window, select "Browse".

5. Choose the "OMFI MediaFiles" and select "OK". 6. In the "System Settings" section. 7. Check "Enable auto-cleanup of transfer queues". 8. In the "Workgroup Settings", configure the "no-login workspace for incoming transfers:" to a valid directory on the NC PC 9. we are using "OMFI Media Files" 10. In the top middle of the "Transfer Manager Server Configuration" window is "Workgroups". 11. Check "Workgroup transfers enabled" 12. Check "Incoming workgroup transfers enabled" 13. On the right hand side in the middle, change "Total Transfers (all types)" 14. "Max. simultaneous workgroup transfers:" to 2. 15. Browse the "Directory for temporary composition files:" and choose "c:\temp". Make sure this folder exists in windows. 16. Check "Delete temporary composition files after transfer". 17. Add a remote workgroup. This could be another standalone TM or a full Unity workgroup. In this example it is another standalone TM. 18. Select "Add".



19. Type the remote NC PC Workgroup Name and Server Name. The "Server Name" is the name of the PC. Use the method similar to finding the name of this PC to find the name of the remote PC.

20. Select "OK". 21. Select "Save" on the lower right hand corner of the window. The following window is displayed.

22. Select "OK". 23. Right Click on the TM Server Shortcut.



E. Starting Standalone TM. 1. Start the TM Server first.

F. Start the editing client. 1. The TM screen will appear as follows, the important part is the "Hold for Permissions" value is "TRUE". 2. This is typically occurs two times on the screen.

a) The first time it is "Disabled" b) The second time it is "TRUE".

G. Windows 2000 Standalone Transfer Manager log file ----------------------------------------------------------------------------------------------------------------------------------- 03/11/2005 13:46:43 ------------------------------ 03/11/2005 13:46:43 Starting Transfer Manager Server 03/11/2005 13:46:43 CompanyName: Avid Technology, Inc. 03/11/2005 13:46:43 ProductName: Avid Transfer Manager 03/11/2005 13:46:43 ProductVersion: 2.7.3 03/11/2005 13:46:43 TransferManager::TransferManager: logging level = 3 03/11/2005 13:46:43 APIMessageInterface::APIMessageInterface Starting listener - com.avid.xmgr 03/11/2005 13:46:43 TransferManager::GetInitializationData: WorkGroups: HostName = [0] ncworkgroup1 BCADRENALINEFX 03/11/2005 13:46:43 TransferManager::GetInitializationData: Primary directory =C:\OMFI MediaFiles 03/11/2005 13:46:43 TransferManager::GetInitializationData: comp directory = c:\temp 03/11/2005 13:46:43 TransferManager::TransferManager: No Unity drives found, scanning local media drives. 03/11/2005 13:46:43 TransferManager::TransferManager: Scan local media drives. 03/11/2005 13:46:43 --- C:\OMFI MediaFiles



03/11/2005 13:46:43 TransferManager::StartPMRManager: CacheReset = True 03/11/2005 13:46:43 TransferManager::StartPMRManager: UpdateCache = True 03/11/2005 13:46:43 TransferController::TransferController Entered. 03/11/2005 13:46:43 TransferController::TransferController Started TransferControllerQueue for Workgroup. 03/11/2005 13:46:43 TransferController::StartupMCT Entered. 03/11/2005 13:46:43 TransferController::StartupMCT This Hostname is bcncfx. 03/11/2005 13:46:43 TransferController::StartupMCT AM::Controller::Create 03/11/2005 13:46:43 TransferController::StartupMCT Creating AM::NetParams npMCT 03/11/2005 13:46:43 TransferController::StartupMCT Creating AM::Plugins gPlugins 03/11/2005 13:46:43 TransferController::StartupMCT Starting MCTListener. 03/11/2005 13:46:43 TransferController::StartupMCT Leaving 03/11/2005 13:46:46 *** \\\Transfer Manager\OMFI MediaFiles\TM_bcncfx -- contains 0 file(s) 03/11/2005 13:46:46 TransferController::TransferController Leaving. 03/11/2005 13:46:46 TransferController::Run Entered, starting main thread loop. 03/11/2005 13:46:46 TransferManager::DumpTMConfigurationParms 03/11/2005 13:46:46 --- Playback transfers: disabled 03/11/2005 13:46:46 --- Ingest transfers: disabled 03/11/2005 13:46:46 --- Workgroup transfers: enabled 03/11/2005 13:46:46 --- Incoming Workgroup transfers: enabled 03/11/2005 13:46:46 --- MaxPBXfers: 0 03/11/2005 13:46:46 --- MaxIGXfers: 0 03/11/2005 13:46:46 --- MaxIncomingWGXfers: 4 03/11/2005 13:46:46 --- MaxOutgoingWGXfers: 1 03/11/2005 13:46:46 --- ConnectionManager: disabled 03/11/2005 13:46:46 --- AssetManager: disabled 03/11/2005 13:46:46 --- MaxCMConnections: 0 03/11/2005 13:46:46 --- Hostname: bcncfx 03/11/2005 13:46:46 --- AMHostname: 03/11/2005 13:46:46 --- SStreams: 0 03/11/2005 13:46:46 --- HoldForPermission: disabled 03/11/2005 13:46:46 --- IncomingRequestTimeout: 0 03/11/2005 13:46:46 --- AcceptOnTimeout: TRUE 03/11/2005 13:46:46 --- Rundown: disabled 03/11/2005 13:46:46 --- NewsroomServerHostname: 03/11/2005 13:46:46 --- PlaylistScheduleFilename: 03/11/2005 13:46:46 --- AutoCleanup: enabled 03/11/2005 13:46:46 --- AutoCleanupAge: 360 minutes. 03/11/2005 13:46:46 --- AutoCleanupInterval: 12 minutes. 03/11/2005 13:46:46 --- Default Unity Volume: 03/11/2005 13:46:46 --- Default Workspace: Transfer Manager 03/11/2005 13:46:46 --- Default Catalog: Transfer Manager 03/11/2005 13:46:46 --- Primary Directory: C:\OMFI MediaFiles 03/11/2005 13:46:46 --- Composition Directory: 03/11/2005 13:46:46 --- Metadata Directory: c:\temp 03/11/2005 13:46:46 --- MediaFormat: OMF 03/11/2005 13:46:46 --- Max DET Push Transfers: 0 03/11/2005 13:46:46 --- Max DET Pull Transfers: 0 03/11/2005 13:46:46 --- Max DET Remove Transfers: 0 03/11/2005 13:46:46 --- Max DET Iterate Transfers: 0 03/11/2005 13:46:46 --- OMM version: 2 03/11/2005 13:46:46 --- Delete temp comp files: enabled 03/11/2005 13:46:46 --- Network timeout(millisec): -1 03/11/2005 13:46:46 --- Debug trace: disabled 03/11/2005 13:46:46 --- DET Config Directory: C:\Program Files\Avid\TransferManager Server\DET 03/11/2005 13:46:46 --- XML Cookie Directory: c:\temp\XMLCookies 03/11/2005 13:46:46 --- UNC file names: enabled 03/11/2005 13:46:46 --- ChunkSize (frames/ingest): 5400 03/11/2005 13:46:46 --- IngestQLimit (frames): 100



03/11/2005 13:46:46 --- PMRScan: enabled 03/11/2005 13:46:46 --- PMRScanIntervalShallow: 15 minutes. 03/11/2005 13:46:46 --- PMRScanIntervalDeep: 0 minutes. 03/11/2005 13:46:46 --- File Balancing: enabled 03/11/2005 13:46:46 --- Max files: 10000 files 03/11/2005 13:46:46 --- File Count Threshold (%): 95 03/11/2005 13:46:46 --- Logging level: 1 03/11/2005 13:46:46 PMR Media Folders -- primary media folders 03/11/2005 13:46:46 PMR Media Folders -- secondary media folders 03/11/2005 13:46:46 --- C:\OMFI MediaFiles TMServer> 03/11/2005 13:47:21 APIMessageHandler::ProcessVersion: version: 0.8 03/11/2005 13:47:21 APIMessageHandler::ProcessVersion: releaseVersion: 2.0 03/11/2005 13:47:21 APIMessageHandler::ProcessVersion: Champlain or higher 03/11/2005 13:47:21 TransferController::SetStandaloneMode true 03/11/2005 13:47:21 In APIMessageHandler::ProcessSetIncomingResponse called: Hold For Permission value is TRUE 03/11/2005 13:47:22 In APIMessageHandler::ProcessGetDeviceList called: List Type is: WorkGroup TMServer> -----------------------------------------------------------------------------------------------------------------------------------



C:\WINNT\TMserver.ini

C:\Program Files\Avid\NewsCutter\TMClient.ini

[Asset Manager] enabled=0 [Connection Manager] enabled=0 NumConnections=2 [Playback Transfers] enabled=0 [Ingest Transfers] enabled=0 [Workgroup Transfers] Incoming Enabled=1 Enabled=1 MaxTransfers=1 [Incoming Transfers] accept=1 Timeout=0 DeleteTempCompFiles=1 AcceptUnauthIncoming=0 DefaultWorkSpace=OMFI MediaFiles [Directories] Composition=c:\temp Primary=C:\OMFI MediaFiles [DET] XMLCookieDirectory=c:\temp\XMLCookies MaxPushTransfers=0 MaxPullTransfers=0 [System Stuff] AutocleanupEnabled=1 AutocleanupAge=360 AutocleanupInterval=12 LoggingLevel=1 [Workgroups] num=1 wgname_1=ncworkgroup1 servername_1=BCSADRENALINEFX [Playlist] use=0

[MyServer,MyWorkgroup] MyServer = bcncfx, ncworkgroup2



IV. Changing Transfer Manager Options so users cannot type in the Transfer Manager Server window when the TMServer prompt is not displayed.

1. The example below is for Windows 2000. Make sure this is done on all PC's running the Transfer Manager Server software. 2. Select "Start-->Programs-->Avid-->TransferManager Server" and Right Click, a listbox is displayed, select "Properties".

3. Select "Properties".



4. The "TransferManager Server Properties" window is displayed.

5. NOTE: Anytime a shortcut to start Transfer Manager exists verify the following. a) Change to the "Options" tab. b) Verify the "Edit Options" are as follows. c) Unchecked "QuickEdit Mode" d) Unchecked "Insert Mode"

e) Select "OK" f) If the editing client is open, close the editing client.



V. Standalone TM Troubleshooting. A. When transferring media

1. Media must be selected when transferring to the other workstation or workgroup 2. Then "Transfer" can be selected from the NC menu bar and the workgroup can be selected.

B. Important Notes: 1. Your own workgroup name should NOT be listed in the TM Server window. Only the other workgroups you are communicating with. 2. Your own workgroup and PC name should be listed in the TMClient.ini window only, not the names of any of the other workgroups.

C. Make sure the IP addresses are correct in the hosts files or the DNS server.

1. If the either machine is in the host file, verify it is the correct IP address and name on both sides. 2. Remember windows gets the ip address and name info from the hosts file before the DNS server, if DNS is correct and the host file is wrong, this could be a problem. 3. Windows 2000 - C:\WINNT\system32\drivers\etc\hosts

4. Windows XP - C:\WINDOWS\system32\drivers\etc\hosts D. When transferring from one NC to another. The clip and sequence information will go into the active bin on the NC sent to.

avid technology, inc. setup of standalone (peer to peer...

Documents