Forum Replies Created

Page 32 of 54
  • Mark Smith

    November 21, 2016 at 4:57 pm in reply to: Changing the ‘focus’ of tools on timeline

    The cmd up and down arrow is a 10.3 addition and great for keyboard navigation. Mac break studio has a segment about just this feature.

  • Mark Smith

    November 14, 2016 at 9:56 pm in reply to: What do you think of this future?

    Years ago I worked on a show that involved The Red Hot Chili Peppers. We interviewed the band one at a time and they were all very cooperative. One band member was barely articulate at the time, he said words but not sentences as we know them. The director and editor spent 3 weeks putting together about half a dozen complete sentences for his part of the show from various fragments of his interview. With Voco this would be an afternoon’s work, perhaps. Voco still remains a convenient but dangerous tool for many of the reasons cited in this thread.

  • Mark Smith

    November 12, 2016 at 1:05 pm in reply to: Importing Canon XF with FCP-X 10.3

    I work with C300 Mk2 footage all the time and don’t have any of the problems reported. My Plug in is up to date , I don’t see duplicates on import. If I select all the clips in a card and import I will get a message saying some files were not imported and these files are the xml, & .cif files that are a part of the XAVC file structure but do not affect the video portion of the clip. I would like to see FCPX import the xml file- I think in general we might be missing some benefits in editorial from not having the XML file come in with the clip.

  • Mark Smith

    November 12, 2016 at 2:19 am in reply to: What do you think of this future?

    This Blazing Saddles scene without the sfx is like watch the DVD version of Y Tu Mama Tambien which had none of the sex scenes of the theatrical release. Neither made any sense at all.

  • Mark Smith

    November 10, 2016 at 12:22 am in reply to: What do you think of this future?

    Just stop a moment and think about the Veritas project and people like James O’Keefe who are deft at editing and taking the words of people out of context to create an agenda driven false impression of what was actually said by a given person. Ok , so unleash Voco on the world of editorial, and then what might be possible? Thanks Adobe, please burn your source code and sprinkle the ashes over the US west of the Mississippi.

  • Mark Smith

    November 8, 2016 at 3:33 pm in reply to: Compression codec for archival documentary

    Storage:

    In general everything that is on tape is now digitized on drives. I have the original tapes and machines to play back all formats, though some stuff from the late 80’s is now on shaky ground playback wise. Any way its all digitized and stored on some large format 3.5″ drives. EVERYTHING on drives is backed up to LTO 5 tape at this point as drives can and will fail over time. By everything I mean all tape based media and file based media post 2005.
    The X Library itself is currently on a 4 drive raid 5 thunderbolt drive that is 3 TB. The project will likely be done in chunks, so once one chunk is done, I’ll out put pro res and archive the library to LTO tape, wipe the drive and move on.

    That’s the big picture. I do take a lot of comfort in the fact that I have LTO back ups of all files. I’ve been burned by drives a few times.

  • Mark Smith

    November 8, 2016 at 2:50 pm in reply to: Compression codec for archival documentary

    I’m involved in a long term doc project which has archives on tape going back almost 30 years. I used pro res lt and pro res 422 when digitizing tape material. Some tape is VHS, 8mm, hi-8 and digital 8 and anything more than pro res lt seemed a total waste of storage space. Pro res 422 was used for digitizing Betacam and some DV tapes. After about 2005 everything is file based, so no problem with that stuff as it all works in X just fine.

    I captured tape to digits using a Black Magic ultra studio box which did a fine job of converting analog tape to pro res files.

  • I think the big picture view is that 15 years ago, Apple’s toe hold or life line was in the heart of the creative biz, video editing, photo editing, layout, printing etc. So Apple had created a niche in the creative world which was essential to their survival. THen there was the iPod, iPad, iPhone, and apple became a large consumer company based on those devices and their ecosystems of hardware and software. MacPros and other more niche things like video editing, photo editing that call for machines with lots of connectivity options and computing power are but a rounding error in Apple’s bottom line these days.
    For those of us that spend our days working these niche realms whether or not Apple releases a new and more powerful cpu means a lot as HD 1080 becomes the new ‘DV’ and 4K and higher resolutions become more common in our work. For Apple, a new Mac Pro is just a rounding error in terms of revenue. They could probably find an equivalent amount of money by pulling out some couch cushions and looking in some crevices.
    For those of us laboring in these niches, the feeling is one of insecurity, because some of the tools we like and use could dry up at some random moment.

  • Mark Smith

    November 7, 2016 at 3:18 pm in reply to: FCPX 10.3 Bugs

    Just finishing up on a project and had to change fonts on some lower thirds. I selected all the lower third titles and rolled through the list of fonts selected the new one and applied it. Then going thru the lower thirds I found that the first one in the list worked fine and the subsequent titles jittered on play back. I solved the problem by going to each title, selecting a random font from the list and then switching back to the desired font . All titles were fine after that.
    Its a minor bug but seemingly a bug nonetheless.

  • Mark Smith

    November 3, 2016 at 10:41 am in reply to: FCPX 10.3 Bugs

    I had a random occurrence that happened when zooming in to the time line . When using either the zoom or CML + to zoom into the time line, the focus would shift to an area near the beginning of the time line and not the area that I wanted to magnify. Zooming out would bring the area of interest back into focus, but of course in a non magnified view. I haven’t been able to recreate this situation which happened twice . A restart solved the problem and I haven’t had this bug pop up since.

Page 32 of 54

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