Already have an account?
Go to to login

To learn more, contact our sales team

Keep the Content in Context While Working Remotely

October 3rd, 2010 by Mark Lasser

The perfect production tools to keep you involved when you are not at the production office

I’m standing in a very long security line at Denver International Airport.  During 2009, I hardly traveled at all so now I’m a no-status frequent flier.  I used to be George Clooney from Up in the Air but now I’m sandwiched between a family on their way to Disney and a pair of grandparents who have packed every prohibited item on them short of guns and bombs.  My boarding pass says seating area 20.  And now the economy is picking up so I’m traveling almost every week. In the middle of all this, I’m trying to get work done.

We all know that the days of immobility are gone.  Despite great innovations in telecommunications, our production needs still put us on the road frequently. Whether we travel by planes, trains, or Segways, it’s always a challenge to stay involved in our projects which are progressing while we lose time standing in line at security and crammed in wifi deprived metal tubes at 35,000 feet. (By the way, if you are trying to work while in your automobile, please wait until you’re not the driver!)

I love smart phones and some days even my BlackBerry, but being involved in a video project by merely exchanging emails and spreadsheets from the airport is so 2008.  Sure, there are a few collaborative project management tools on the market, but I always feel these have been designed more for construction projects and software development than for video.  Where’s the player? Where’s the scripting tool?

Whether you’re creating narrative content or internal communications, you need tools that keep remote participants in the loop and collaborating in seamless and easy interactions and these tools need to be built with video in mind.  At Market7 we know this from experience.  We’ve tried producing video projects with participants on the road and based in various physical locations.  When we develop features for Market7 we’re always thinking about better ways for remote collaboration.

For example, we know it’s crazy not to be able to paste images into a script.  If you want to illustrate a point or to show the director location and wardrobe options, why use email and risk miscommunication?  This is easy in Market7.  Just upload an image to the scene and other collaborators can see it.  Don’t like an edit but you know your company has stock footage that’s better?  Why send a long email or worse, a DVD? Instead, upload the alternative footage into a comment made in our dynamic media player in the exact spot you think the footage would work. Now the content is in context. The wardrobe alternative pairs to the scene.  The stock footage plugs in to the shot in the player and everyone understands what is being suggested as an alternative edit. We know this is a better way of doing things.  To learn more or to schedule a demonstration contact us at

, , , , , , , , , , , ,


video.Market7 release from Feb 9 ‘10

February 10th, 2010 by Seth Kenvin

Security’s getting tighter in here

Below this paragraph you’re looking at a significant advance in our securing content and information about production that’s run discreetly through video.Market7. The first modules in the application to feature access controls were collaborative script and resource management — in both of these people can be explicitly invited or excluded from access based on permission levels granted either to them personally & directly, or more indirectly through association of privilege with their roles. Roles in this context sort of act like tags. Thing is that until recently roles could be openly changed by anyone. So, if I’m locked out of a script I want to see, but I suspect the “crew” role (or of course some other one) does have access, then I can just expand my roles to include “crew”, and I’m in. We’re about to expand content security considerations to other parts of our service, so it’s become time to close the roles loophole, now done.

The above image is a project-owner’s perspective. This is the only person in a project who may determine which people in a project may assign roles. The red padlock towards upper-right indicates that some users are restricted from role assignment, and that button is only visible to the project owner who may press it to modify. When there are no restrictions set for any team member on role-setting, which is the default condition when a new project starts, the button is green instead of red, and reveals an open padlock. Then there’s the nearby floating rectangle containing text — it’s our new (& more on-screen persistent during mouse-over) style of text/information-revealing (aka tooltip). Looks nice, right? This message tells the project-owner about their being allowed to modify roles themselves, also indicated by the little, green, open padlock above the Team module’s Roles column, right by the pointer. When someone who’s denied role modification privileges by the project-owner looks at the Team module, the lock over that column is red and closed, the person can not add or modify (but CAN see) roles, and the tooltip includes identification & contact information for project-owner along with advice to contact that person for modification request.

, , , , , , , , , , , , , ,