Forum Replies Created

Page 123 of 428
  • Agree with Scott that the “creative editorial” had to do with pace and rhythm as well as selection of the boy’s performance (facial) to create the emotional storyline of the piece. But, as you can see from the AdWeek credits, this was like a mini-VFX type feature, so most likely lots of roundtrip with different phases of VFX, such as where the penguin was going to be in each of the shots during that creative editorial. It may have even started off as a moving rectangle that gets animated, etc. All of these objects need to be managed and accounted for during “creative” editorial. Even a film like Gravity that ended up having 156 edits. But that does not include the editing and timing of all the layers and events that led up to the shots that resulted in 156 edits. Each production works with the talent and tools that best serve their needs, and again it shows that there is not one tool that does it all.

  • Michael Phillips

    November 26, 2014 at 2:11 am in reply to: 768X1024 sequence

    I would do it in After Effects if you have that available.

    Michael

  • Michael Phillips

    November 26, 2014 at 1:43 am in reply to: 768X1024 sequence

    Do you need to recompose the shot, or just take it as it is and have the monitor display as portrait?

    That aspect ratio is basically a flipped 4:3 monitor (3:4). So is there a crop involved as well as scaling down?

    Michael

  • Hmmmmm…. I can’t recall what that version had for track dependent waveforms. It is 13 years old now!

    Michael

  • The original Avid 10 was released in 2001 for Apple OS 9 and Win NT and 2000. Is that really the version you are using?

    Or is 10.5 the OS X version you are running? If so, then it is MC v3’ish and later.

    Michael

  • What version are you running> In the last 2-3 major version you have a per track waveform setting in the timeline next to the A1, A2, etc.

  • Michael Phillips

    November 25, 2014 at 10:18 pm in reply to: Getting Drives ready for logging?

    Productions will usually have a set organization that is used, but can vary from production to production,

    You have a pretty good start – usually starts with a ShootDate. I also like to add a basic time range as most if not all footage is now TOD. So for today I may have it as:

    112514_1230-1600

    Telling my it was shot November 24th, 2014 between hours of 12:30PM and 4:00PM. Doesn’t need to be seconds and frame accurate – just a basic range. It usually helps in the gathering of a director or producer asking about a shot that was captured “Tuesday afternoon…”

    Inside that, you may have multiple camera that are labelled as A,B, or perhaps by model if using different cameras. Then in there you would have each of the cards as they are coming off the camera. These can be Card_1, Card_2 and even here you might consider a time range such as Card_1_1445-1510. In this folder is an exact “clone/copy of the card preserving its structure so that AMA is happy with the essence and the metadata when linking.

    Again, find one that works for you, but one you start a project the most important thing is to be consistent in naming and structure/folder level organization.

    Michael

  • Michael Phillips

    November 25, 2014 at 6:44 pm in reply to: Speech to text

    SoundBite, like PhrseFind does not require a transcript to be done. You may be confusing that with ScriptSync. SounBite and PhraseFind eliminate the need for transcripts as it can do ad-hoc searching for words and phrases directly on the media itself. In many cases, it can save the cost of doing a transcript in the first place.

    Adobe’s Speech to text did add a feature that “helped” it by providing it is script to start with, but then again, that sort of defeated the whole purpose of a speech to text engine in the first place.

    Michael

  • Just some historical context on SmartTool… When it was first released, you could not turn the functionally off altogether and it took several point releases to get it to the state it exists now. Before those issues were addressed, you have to remember that navigation was anywhere in the timeline – muscle memory sets in. With SmartTool in its first few releases, one had to remember to only navigate via timecode strips out outside tracks. For existing users, that was a lot of muscle memory to undo.If they did not pay attention, something was potentially changing in the timeline.

    It was brought up several times before beta even released that SmartTool should be an option that is defaulted on, but the user could turn off completely. This way the more progressive user base would have it available from the get-go and long time users can introduce it when they needed or wanted to. This would have eliminated the first impression syndrome that existed with the first (bad) first release and point releases that still linger today.

    I will also say that this user base is not so much resistant to change if done well. But it has to be better and not done for the sake of change. There were a lot of “new” things in v6 that were done for the sake of change, but did not add functionality and in some cases made it worse for many users.

    My two cents.

    Michael

  • Michael Phillips

    November 21, 2014 at 3:08 pm in reply to: 8K at 60p, and the future of post?

    It’s a response to different market needs. Japan has been big on their 8K efforts and of course need tools to get them there in post. Whether everyone needs it? Up to the individual, but the side-effect of 8K performance at 60p is that it should do 4K and 2K at 23.976, 24, 25, and 29.97 very well. 🙂

    Michael

Page 123 of 428

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy