[quote="Mike Cumbo"]John, what about the possibility of someone sending you a file and you checking it and then create a link. The file in question is a PDF, have the virus creators found a way to corrupt them yet? I can see issues with Word or Excel files since they can have macros and the macros can be made to do evil things.[/quote] I think the virus creators can find ways to corrupt most anything, but you're right, the Word macros and .exe's are the major culprits. The thing is we have tried to make Editsuite.com a self-sustaining venture. If it's just one file now and then, no worries. But if it escalates to much more, then I'm afraid I wouldn't have the time to keep it up. It probably wouldn't be a bid deal, so I should just quit whining and offer to host the file. :-) Ok, so send me the file and I'll put a link to it in this thread. And I'll try to look for an add-on to allow people to upload and link files in this forum s/w. -JH

John, what about the possibility of someone sending you a file and you checking it and then create a link. The file in question is a PDF, have the virus creators found a way to corrupt them yet? I can see issues with Word or Excel files since they can have macros and the macros can be made to do evil things.

[quote="Rick Edwards"]Editsuite.com doesn't seem to support attaching a file so I'll just have to cut and paste here.[/quote] Hi Rick, Yeah, we decided that we didn't want to get into storing files on our web servers and have the possibility of viruses being passed around via our site. I know it'd be nice to have sometimes, though. Thanks for your continued support of Editsuite.com! -John

Just a note, on the old version of the board someone posted a URL to the PDF that Rick mentions above, when I checked EVS's site now the file doesn't seem to be there anymore. I wish I had remembered this file last year when I worked on HD-6. Eric, or others, if you want the PDF just click the "e-mail" link near my name. It's a 650k file, 6 pages.

[quote="EricG"]It wasn't P-Bus, it was direct machine control. P-Bus I can handle - I've used it before with a Sony. I did eventually get the thing to work, but it was with a crazy workaround. Once I got clips to be called up when I called the effect up (and I don't know how I did it, that's the worst part - I toyed with it and hit buttons for probably a half hour to get to that point), I then ran into a different problem. I could cue the clip, and I could play it by firing the Test Trigger, but running the timeline, the clips wouldn't play. So I rigged it by putting a pause keyframe in between the first "cueing" keyframe" and the third keyframe, or my "start" keyframe. Then I made the shotbox Autorun so that I wouldn't have to hit run twice. That seemed to work - only problem was, effects aren't really loopable that way because of the extra pause. So, a really dirty way to do it, and I didn't like doing it that way, but it got the show done. Any thoughts on why I couldn't get the timelines to work when I built them the normal, "Grass Valley" way? Obviously I was missing something. I just don't know what.[/quote] Eric, Editsuite.com doesn't seem to support attaching a file so I'll just have to cut and paste here. EVS Systems has a very good PDF document describing exactly how to connect and use their spotboxes with a Sony MVS under Sony's machine control. Below is the text. In a nutshell, you need to make aure the EVS is running in the correct VDCP mode otherwise it will act strange. When you go to make your device effect..... recall an empty device register, the load the clip manaully then cue it and press START TC on the trackball module (make sure you are in DEV mode on the trackball). If all is set well, then you should be fine. If you want to set ANOTHER clip on a subsequent keyframe, YOU MUST ALWAYS MANAULLY LOAD THE FILE AGAIN whether you're on the same clip or not. Hope the stuff below helps although it's kind of hard to read without the pretty pictures, TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 1 of 6 How to interface a MVS-8000 Switcher with a EVS Spotbox-XT / Spotbox-XT[2] system using VDCP Protocol. This will utilize the Louth VDCP Protocol on the devices to communicate and allow the switcher to load, store, and recall clips from the switcher?s timeline. Physical Connection from the Switcher to the Spotbox-XT For each channel under control, the user must run a RS422 cable from the Switcher?s DCU to the server. On the Spotbox-XT Setup parameters for VDCP Slave mode?. With the desired number of recorders and players assigned under VDCP control. VDCP 0REC 4PLAY EVS Americas Version 1.00.00 Created 30/06/05 TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 2 of 6 Compatibility Note: The Sony Switcher, as of version 4 software uses a VDCP spec that requires the usage of the Louth 1998 specifications. By default the EVS-XT servers default to Louth 2000 specifications. To make operations easier, the Spotbox-XT should be changed to operate in the 1998 mode. Proceed to the DOS Prompt by pressing ALT+Q from the EVS Menu At the C:> prompt, type cd multicam followed by [enter] We want to edit the exec.bat file to add a command line switch for the Louth 98 mode? At the c:multicam> prompt, type q exec.bat The following will appear in the Q Edit program: @ECHO OFF del bootwins.log bootwins /q if errorlevel 10 goto error if errorlevel 0 goto exec goto end :exec multicam.exe if errorlevel 100 goto end goto dump :error echo ERROR while booting pause goto end :dump echo An error forced the multicam to close. Note all 0x... codes and send them to EVS echo You need to do a full hardware reboot before restarting the application. pause :end Move the cursor to the exec area and add a command to the following line: :exec multicam.exe /Louth98 /Louth_IDLSM if errorlevel 100 goto end goto dump When done, press [ALT]+[X] to save and exit the editor Then press [CTRL]+[ALT]+[DEL] to reboot the system. Note: These commands only apply to the Louth VDCP commands when used. These do not affect any other aspect of the Multicam application. /Louth98 will utilize the 1998 mode for position requests, allowing the Sony switcher to receive the TC of the clip?s position. Otherwise, it would receive the current position relative to the start of the clip, in a clip counter. /Louth_IDLSM will allow the user to see and use the LSM-ID formatting for the list of clips and OSD Displays instead of the autogenerated UmID. EVS Americas Version 1.00.00 Created 30/06/05 TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 3 of 6 On the MVS-8000/9000 switcher Goto the Page 7355 to configure the DCU Locate the correct DCU Number and Port that you have connected to. Change the device type to DDR VDCP Press [Device Type Set] Define a PORT SETTING for each device defined to VDCP Critical to set the PORT SETTING for each channel to a relevant video PGM Outputnumber Important: To correctly recall the video to the Spotbox-XT PGM Outputs? you MUST define a valid PORT SETTING. This allows the MVS-8000 to indicate which video output the clip recall should be routed to. In Port Settings, the user changes from 0 to a number that matches the PGM output of the Spotbox-XT. Example: PGM1 = 1, PGM2 = 2? etc. The user could be connected to Spotbox-XT RS422 port 4, but in the video port, manage PGM 1 for example. EVS Americas Version 1.00.00 Created 30/06/05 TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 4 of 6 Goto the Page 7325.4 to configure the PANEL DEVICES These are the buttons where the Spotbox-XT will appear for operations If desirable, the system can utilize the same FILE LIST for all channels, to reduce the need to refresh all channels individually. Assigns the physical DCU port to a virtual DEVICE assignment on the switcher?s userinterface. This allows the user to tell the switcher that different devices are managing the same file listfromoneSpotbox-XT Using the sidecar?s control panel, select the Device Menu, which is also 5321. Goto the Device menu to begin management of the Spotbox-XT by way of VDCP EVS Americas Version 1.00.00 Created 30/06/05 TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 5 of 6 On the Device menu?the user can see the 3 subpages for Device Management ? CUEUP & Play ? allows the user to see the current status of the devices, and know if a clip is loaded ad cued. Note: If the Spotbox-XT is using Louth2000 settings, the MVS-8000 will receive clip counter values when setting TC points, which will NOT allow the user to cue correctly to the TC of the clip. The user should change the Spotbox-XT to Louth98 at the commend prompt. ? FILELIST ? allows the user to UPDATE the File List, and LOAD a clip onto each device. FILE LIST UPDATE will refresh the LIST. NOTE: If the Spotbox-XT is set as a MASTER for the SDTI Networking, the user may receive a list of all clips on the XNet! EVS Americas Version 1.00.00 Created 30/06/05 TECH NOTE ? VDCP with MVS-8000 C:Documents and SettingsjstDesktopMVS- 8000_TECHNOTE_JST.doc Page 6 of 6 ? TIMELINE ? allows the user to place the clip CUEUP, START, STOP actions into timeline keyframes. Note: a CUEUP action should be placed in the REWIND ACTION for the timeline. The REWIND ACTION fires each time a keyframe is recalled. Having a CUEUP Timecode is optional, if not used, the clip will load to the Short IN. REWIND ACTION is the event that happens when the effect is recalled. Tis is normally where the user should place the Clip for cueup In the REWIND ACTION Menu, the user uses the FILE SET to define the clip that is loaded as the FILE that will be loaded in the REWIND ACTION. This is a useful feature when use user has a generic timeline and wants to load a new clip, and save the timeline ? Normally most users will define a CUEUP for the rewind action, and no START TC value. If the user is using 1 long clip? the user would need to add a Start TC for the clip to cue correctly inside the long clip. FILE SET will add the current clip on the channel to be added as the clip for the REWIND ACTION set. The Clip ID will appear in File Name

It wasn't P-Bus, it was direct machine control. P-Bus I can handle - I've used it before with a Sony. I did eventually get the thing to work, but it was with a crazy workaround. Once I got clips to be called up when I called the effect up (and I don't know how I did it, that's the worst part - I toyed with it and hit buttons for probably a half hour to get to that point), I then ran into a different problem. I could cue the clip, and I could play it by firing the Test Trigger, but running the timeline, the clips wouldn't play. So I rigged it by putting a pause keyframe in between the first "cueing" keyframe" and the third keyframe, or my "start" keyframe. Then I made the shotbox Autorun so that I wouldn't have to hit run twice. That seemed to work - only problem was, effects aren't really loopable that way because of the extra pause. So, a really dirty way to do it, and I didn't like doing it that way, but it got the show done. Any thoughts on why I couldn't get the timelines to work when I built them the normal, "Grass Valley" way? Obviously I was missing something. I just don't know what.

Eric, Assuming you're using a controller connected to the switcher P-bus.... go to the devices menu and select P-bus/timeline. On your controller recall the reg # you want to recall. In the P-bus menu, at the bottom there is a direct store button. Push it and enter the number that corresponds to the reg # on the controller. While still here, call up each reg #, one at a time on the controller and do a direct store in the switcher for each reg # you'll need. Now when building your effect, call up the effect # in the switcher, enabling P-Bus and whatever else you'll need. In the Device menu, P-bus/Timeline, push rewind action. Set the rewind action for the controller device ID to "Recall X" (X being the controller Reg # you want to recall). Then push previous to get out of the rewind action sub-menu. Attach any triggers you need to keyframes here in the main p-bus/timeline menu. Good luck. --Mike