From the CONTROL ROOM @onairgfx - Tumblr Blog

Importing into WSI

TVM_Import

1) Save the files you want as .png files cropped to just the size they need to be.

2) Place them on the desktop of the MAX computer.

3) Shut down the Max software the importer won't run if max is running.

4) On the desktop, you will see an Icon called Import Media.

5) In the import software, the first thing it will ask is what type of media you wish to import. Make an appropriate selection.

6) It will ask you where from your computer you want to import from.

7) Move all the content you wish to import into the column on the right using the Add button.

8) On the next screen, it will ask you where in the MAX system you want the content to go.

9) Click Import and let it process.

#weather #WSI #Graphics #forcast #TVM #MAX

Clearing the Cache on Vertigo

You Should clear the cache on the Xplay > XG > XMS.

Please note that the Services need to be Stopped prior clearing the cache on each machine.

The location of the Cache folder is the following for all units:

XMS = C:\Documents and Settings\All Users\Application Data\VertigoXmedia\XMSCACHE XG-E= C:\Documents and Settings\All Users\Application Data\VertigoXmedia\XMSCACHE Xplay=C:\ProgramData\VertigoXmedia\XMSCACHE

To quickly access the folder use the following:

%vxm% and hit enter

On the XMS it should be the XG IP address. On the XGE is should be the localhost folder. On the Xplay machine it should be the XG IP address

#Vertigo #XMS #XG #Cache #Xplay

Error messages with multiple news pop-up windows.

In ENPS, under MOS Configuration in System Maintenance I finally learned from my own people that in the ENPS config for the Xnews plugin, these are the entries for the following settings: Use Detached – unchecked Detached ActiveX – blank Modal UI Default Settings – blank Modal UI ActiveX – blank

Doing all of this prevents a second instance of Xnews opening, and when editing an existing Vertigo page, that page will always open in the plugin in an embedded window instead of in a floating window.

onairgfx

onairgfx:

This has been much improved in V4.9 Quicktime animations have been working much better sense the upgrade

The original problem was with clips stuttering or skipping on playback. I’ve spent a great deal of time with Miranda support working on getting clips to play cleanly in vertigo and also loop.

If you are seeing clips skip or jump the first thing to check is a setting in the dashboard of the actual...

Below are the details on how Axis Ingest was set up and how it operates.

1) Create a folder on the D drive of FlipVanWinkle (WFA-XDNEWSFLIP 10.XXX.XXX.XXX) and name it OUT.

Create a folder on the D drive of FlipVanWinkle (WFA-XDNEWSFLIP 10.XXX.XXX.XXX) and name it IN.

Create a folder in the OUT folder and name it AXIS_TO_VERTIGO.

Create a folder in the IN folder and name it AXIS_TO_VERTIGO.

Create a folder in the IN folder and name it G3_RX.

2) On the backup Vertigo XMS server (WFAA-VERT-XMS4) Map “I:” drive to \\10.XXX.XXX.XXX\k\OUT.

3) Start the File Ingest Server on the backup Vertigo XMS server by clicking Start, All Programs, Vertigo, File Ingest Server.

4) Configure the File Ingest Server on the backup Vertigo XMS server by clicking Start, All Programs, Vertigo, Control Panels, File Ingest Server Control Panel.

5) In the File Ingest Server Control Panel click Instance1, then click the Edit button.

6) Make the following entries to the General tab.

7) Make the following entries in the XMS tab. Click Save when finished.

8) On the FlipVanWinkle computer, navigate to the D:\OUT\AXIS_TO_VERTIGO folder. You will see 4 new folders that were just created by the Vertigo File Ingest Server. Create the following directory tree inside the Images folder “Belo\Library\Replace”.

9) Create a factory on FlipVanWinkle that monitors the local folder location D:\IN\AXIS_TO_VERTIGO and does a Duplicate Copy to the above “OUT\AXIS_TO_VERTIGO\Images\Belo\Library\Replace” folder.

If other types of ingest are needed for Audio, Animations or Clips, a category naming standard in XMS will have to be decided on and created. Then destination folders to match those categories can be created in FlipVanWinkle, then the factories can be created for those destinations. Then create instances to monitor those locations in File Ingest Server.

The workflow for Axis is as follows.

A. Users Log in to Axis and create their graphics (JPG, BMP, or TGA) and either download or save them to the “IN\AXIS_TO_VERTIGO”. There should already be a mapped k(\\10.XXX.XXX.XXX) drive on their workstations. It is there where they will find the “IN\AXIS_TO_VERTIGO” folder.

B. FlipVanWinkle will monitor the “IN\AXIS_TO_VERTIGO” folder and copy the files to the “OUT\AXIS_TO_VERTIGO\Images\Belo\Library\Replace” folder.

C. File Ingest Server monitors that folder “OUT\AXIS_TO_VERTIGO” and each of the subfolders in it (Clips, Images, Audio, CelAnimations). When a file is detected, it ingests the file and stores it in the XMS server in a category matching the folder that the file was found in. For example, if found in Images\Belo\Library\Replace folder then it is stored in XMS\Images\Belo\Library\Replace. If a matching category does not exist, the ingest will fail.

In this case, if a file is found in the OUT\AXIS_TO_VERTIGO\Images\Belo\Library\Replace folder, File Ingest will place the converted file in the XMS\Images\Belo\Library\Replace category.

Thanks to Darrell Hargrove for putting this together.

Axis Training

2 hours until todays #ChupacabraSighting Join me for the training session this afternoon to learn more.

#www.axiswg.com

Axis to vertigo ingest solution

From Jeff at WZZM

He's come up with script that watches a folder, it looks at specific file types, and moves them into the appropriate folder in the File ingest server folder structure.

This solves two major issues.

1. Unknown file types failing the ingest server and causing problems with the XMS services.

2. Makes it easier for producers as they now have one folder to dump everything into. They no longer need to navigate a deep folder structure.

Code available upon request.

#FileIngestServer #Miranda #Vertigo

X-Play preview output

It looks like our little project of using a scan converter on the X-Play to give us a preview output is a success. Attached is a picture of the end result. We purchased an Ensemble BEM-4, cut-out the section of our X-Play preview/program window and fed it into a second monitor. Our directors only need to see XG1 and XG2 so that is all we use but you can define the window based on what you wish to see.

Thanks Ron

#Xplay #Miranda #preview #CG

The following website has a list of the possible characters that may cause issues within Xplay. http://www.cplusplus.com/reference/cstdio/printf/

#xplay Miranda

ENPS Configuring the Globe Rover

Configuring the Globe Rover

Wanted to go cover some settings for Deko and Miranda in ENPS:

1. Rover Menu Item. This applies to both Deko and Miranda ActiveX Plugins.

a. In order for a group to be able to see Deko or Miranda as a selectable choice in the bottom right a ENPS Supervisor must configure this for you.

b. Here is a screen shot of this:

Note: The plugin software must be installed on system to be able to see the Deko/Miranda option.

c. To have this configured for your site, email the GTV-ENPS-SUPERVISORS group to take care of this for you.

2. This is for Deko sites. Blocking MOS ID’s in your NOM MOS window. This is for sites that do not want to see other sites mos objects in your NOM after a mos object is redirected.

Here is a screen grab of the MOS window inside WTSP’s NOM:

b. If any of your users drag and drop a mos obkect from another site’s rundown(s) your MOS window will then start displaying that site’s MOS Device.

To prevent this, all the stations that are using Deko (not yet on Miranda) should go into each of their rundown templates (the Parent Instance) -> Go into the Rundown Properties -> Find the MOS Block property and select all the Miranda MOS IDs.

3. This is for Miranda sites only. This to enable site specific graphics for mos object redirection.

a. Applying this setting will automate backgrounds, graphics, etc. that are specific to your site in a redirected mos object.

b. go into each of their rundown templates (the Parent Instance) -> Go into the Rundown Properties -> Find the MOS Redirection property and change the entry to your specific MIRANDA device.

c. All sites configured with Miranda have a dedicated mos device named MIRANDA.VERTIGO1.XXXX.GANNETT.MOS. The XXXX in the naming convention is your stations call letters. Example: MIRANDA.VERTIGO1.KUSA.GANNETT.MOS (this is KUSA’s Miranda device)

#ENPS #Globe Rover #Active X

Render setting from Edius for use in Vertigo

Here are some screen shots showing render settings from edius for clips going into vertigo. This is for clips with no alpha channel

Here are the Edius settings I used:

You do get the following error message on Ingest from Miranda, but it plays:

#vertigo #Miranda #clips #Edius #grass valley

clips that pause

I've been asked a number of times how to get clips in Miranda Vertigo to pause or hold at the start of playback. Despite the lack of documentation on this process it's actually really easy.

In Miranda these type of templates are referred to as multi-take templates.

For this example lets say we want to pause the clip on frame 10 of the animation.

Assuming that you wish to play your clip sometime after it has been paused (when the director takes it on the switcher) you will need more that one take.

1) in the Control:Model (The template on the template side) in the properties set your available takes to 2.

2) On the scene side add your clip

3) On the template side in the "On Cue" insert a clip command and set it to Cue Clip. Add your clip on the scene as the target.

4) On the template side in on Take add a clip command and set it to play clip. Add your clip on the scene as the target.

5) On the scene side open your animation timeline and go to frame 10. Right click and select send call-back from the contextual menu. Name your call back "pause"

6) On the template side add a user defined event and name it pause. add a clip command and set it to pause clip. Add your clip on the scene as the target.

7) In Take(2) add a clip command and set it to play clip. Add your clip on the scene as the target.

On playback the template should go through Cue, when taking it on air the clip will play for ten frames and pause. It will wait there for the director to hit take again.

#Miranda #Vertigo #pause at start #Multitake #Clip

Getting the most from your clips

The original problem was with clips stuttering or skipping on playback. I've spent a great deal of time with Miranda support working on getting clips to play cleanly in vertigo and also loop.

If you are seeing clips skip or jump the first thing to check is a setting in the dashboard of the actual XG titled "Hardware Acceleration.

Miranda has a very limited set of video formats you can import into the system. One "allowed" format is Quicktim animation. There was no alpha on this clip so the file ingest server wanted to make it an MFX upon doing so the clip would stumble or jitter on playback. According to support the bit rate of my quicktime animation was too high.

the max bit rate the FIS can handle is 20 MBS

Problem is in after effects there is no way to adjust the bit rate.

The work around is to render a quick time animation from After effects.

(Note Miranda doesn't recognize straight unmated alphas)

Then use adobe media encoder to convert your clip to an MXF

Under format Use MXF OP1a. Under Preset I chose NTSC 50 30P to insure a non interlaced format.

When ingesting this into the vertigo system it produced a clip that played cleanly with no jerking or stuttering.

In the vertigo world an MXF and a VAF have a different set of available options for looping. Though the options are identical in the properties window of X-studio an MXF file can not do a 3 point loop. Only a vaf has this option. As my clip had no alpha I needed a work around to be able to get this into vertigo as a VAF. So what I did was render out my clip as a targa sequence. Upon importing it into the system the FIS gives you the option to convert it to a VAF and set the looping functions. Setting up your looping upon import of the clip seems to be more important than setting it up in the scene. The start loop and end loop fields are asking for frame numbers.

#Vertigo #looping #3PointLoop #Miranda

test

How to use the clip editor in avid deko, specifically as it relates to the G3P0 L3 clips

#avid #deko #clips #settings #import #looping #unshaped

Phoenix fire coverage comparison.

Trending Blogs

Recently Viewed Blogs

From the CONTROL ROOM