Andrew Kimery
Forum Replies Created
-
[Hajer Ibrahim] “Am I doing something wrong or does premiere have a hard problem managing merged clips?”
PPro has a problem with merged clips. Never used them myself because they sound like a PITA. I just use the multicam feature to sync what I have (even if it’s only 1 camera plus second system sound) and cut like that. Works like a charm.
-
[Gary Huff] “Poor analogy because restaurants provide “convenience”,”
So does pretty much every job/profession though. If the directors, producers, etc., I work with had the time, inclination and/or desire to edit their own projects they most certainly could, the tools are pretty cheap these days, but they don’t so they hire editors. If I had the time, inclination, and/or desire to do my own taxes I would but I don’t so I pay a pro to do them for me.
The Chicken Little Work Theory of Doomâ„¢ seems to be that once both the basic skills and the basic tools to do a job become ‘common’ then the opportunities to get paid to do that kind of work just go *poof* overnight but that’s just not the case. Change will happen and disruption will happen but that’s just the nature of the beast. Some revenue avenues will dry up, others will still exist but maybe not in the same way and new ones will spring up places they didn’t used to be.
Maybe I sound unsympathetic to the impending apocalypse but working in LA is a non-stop grind so the constant hustle and fear that I’ll never work again isn’t part of a possible, dystopian future, it’s my daily existence. 😉 Even staff jobs only provide a false sense of security because you never know when your entire department is going to get laid off (like, say, the week before Christmas without any warning whatsoever).
With regards to talented young people… I’m not really worried about them for a few reasons. First, it’s motivation to not get complacent. Second, if a 20yr old can one up me for a gig then I’m in the working the wrong gigs and/or I’ve become complacent. Third, talent, at least in my neck of the woods, only gets you so far. Tons of talented people flock to LA or NY to vie for a tiny number of gigs. Tiny number of jobs. In my experience the people that ‘make it’ are the most determined, not the most talented. 5-10yrs struggling in LA seems to be the breaking for a lot of people. They’ll either find a cushy 9-5 job, leave industry or leave LA. Every one that does that is one less competitor I have to worry about.
[Bob Zelin] “But unlike all the PROFESSIONAL editors on this forum (including Bill Davis)- it is my personal opinion that Apple’s ONLY goal is to make editing a common place task”
Won’t get any disagreement from me. Hopefully I don’t incur anyone’s wrath, but I think it was pretty obviously that Apple’s primary target out of the gate with X was the ‘fat middle’ where you have people that don’t necessarily edit all day, everyday but they still edit frequently. There are a lot more of those types of people than full time editors.
[Bob Zelin] “The commodity of the video business is approaching – no different than it happened to the print business, and music business, and word processing business. This will apply to all video applications, including streaming (you are a streaming professional ? My son has his own YouTube channel, and he has 200,000 subscribers and he is 12 years old). That’s the future. And I blame Bill Davis for all of this !!!!!!”
I personally like the “adapt or die!” Bob Zelin more than the “we’re all gonna die!” Bob Zelin. 😉
-
I’m still waiting for the restaurant industry to cease to exist since individuals have been cooking for the past few million years…
-
[Joe Marler] ” Those would not be reliable for a camera but it shows in principle how straightforward the concept is.”
I think this the gist of the whole thing. Conceptually it’s straightforward but in practice the time needs of our smart phones, computers, etc., aren’t the same as our time needs for our video cameras and audio recording devices so since the needs are different the solutions will be different as well.
One of the biggest differences between the GPS idea and how sync is current done is that with the current implementation of sync we have a single box (wired or wireless) that all the other devices slave to (either through a constant connection or just periodically in the case of a jam sync). With the GPS idea we remove that that single box concept and it’s up to each device to create their own GPS connection, maintain/refresh their own GPS connection and convert that independently collected GPS clock data into HH:MM:SS:FF (all in sync and with accuracy of at least 1/60 of a second).
That seems like a lot of variables in play, especially if there are no standards across the board, and even something as minor as Brand X rounding up nanoseconds vs Brand Y truncating nanoseconds would result in different HH:MM:SS:FF results and thus drift. Again, maybe fine for another way to jam sync, because jam syncing is already a compromised approach, but it would depend of course on how quickly the devices drifted of sync. Not to mention this ‘always on’ connection would probably put a load on the battery.
An obvious fix to this is to still use the single box method but now the single box can use GPS, wifi, and/or cellular as a clock source (which might be cheaper than a high quality quartz crystal clock source), do the conversion to HH:MM:SS:FF, and then push that signal out to the devices. The general pros/cons of this method would presumably be similar to already existing wireless sync options which may or may not make this GPS route a superior solution compared to ones that already exist.
And this doesn’t even get into the TC needs of post but I figure we’ll talk about one element at a time. 😉
-
[Bill Davis] “You presumably carry a device in your pocket called a cel phone. It keeps perfect time. It does that by internal time chips that might drift fractionally, but the central system resets them as needed. So they are always scrupulously accurate – providing they are anyplace on the planet that gets a carrier signal. So the ENTIRE developed world is good to go. They also largely have attendant tech like Bluetooth and nearfield – that makes it trivial to TALKbto other devices. “
But that’s not the case Bill. Go back and read my other posts (and the other pages I linked to). iPhones and iPads, for example, have very poor internal clocks (relatively speaking) and rely heavily on GPS, cell towers and/or WiFi connections to correct the their drift multiple times a day. A time piece jumping forward/back a fraction of a second at different points during the day isn’t a big deal because no one is going to notice that their watch jumped back 1/15th of a second between 12:01:01 and 12:01:02 or that it jumped forward 1/45th of a second between 11:30:59 and 11:31:00. Devices trying to stay in sync while writing continuous metadata every 1/60th of a second (or higher) don’t have the same amount of wiggle room. Just as an example of the level of accuracy needed, Tim Cook has said the Apple Watch is accurate down to 50ms yet if you are shooting at 60p you need constant accuracy of at least 16.666666666666667 milliseconds (1/60th of a second).
Like I’ve said over and over again throughout this thread, for jam syncing using a GPS clock signal could be another option to coexist with what’s already out there, but given the current state of tech I don’t see GPS as viable replacement for the functional equivalent of a single box sending out constant sync (wired or wirelessly) to multiple recording devices.
[Bill Davis] “Nobody is trying to take away your precious 1950s flashing numbers dude.”
Wow. Epic response, Bill. You either haven’t read (or are just ignoring) the questions other people are asking and/or points they are raising so it’s pretty preposterous for you to cop an attitude in lieu of having an actual conversation.
-
[Bill Davis] “A person who enjoys discussing Expressionism does not necessarily want to burn all the works of the Old Masters.
As usual, some just wanted to push back – which is fine. Others were more interested in looking at what it might mean to push forward.
“I think people are just trying to figure out what exactly you are talking about because other than SMPTE TC is old, GPS is new and we can do better than using something that’s old, you haven’t added much depth to the discussion other people are trying to have with you about a topic that you brought up.
[Bill Davis] “If that’s where I’ve got to work, there is nothing wrong with realizing that it would be swell if there was a higher level time signal available that made them ALL easy to deal with without the modern version of blacking and pre-striping tapes as I wasted hours doing in the 80s.”
Okay, so how do you envision this higher level time signal working out? Do the devices have internal clocks capable of generating SMTPE TC and GPS can be used an alternative way to jam sync them? Do the devices have *no* internal clocks and are solely reliant on GPS to give them a clock signal which is then converted, by the device, into SMPTE TC? Is SMTPE metadata no longer part of the picture at all and some other form of metadata is created to take its place?
-
[Jeremy Garchow] “I am looking to remove Pr form this workflow, but I haven’t found the best way so far.”
Yeah, it kinda sounds like you are being forced to use a sledge hammer to swat a fly because you don’t have any other options.
-
Have you tried opening up the XML in a new, Temp PPro project, closing that project, opening up your PPro Project and using the Media Browser to import what you need from the Temp project. I think that should do fix the duplicate media issue.
It’s a kludgy workaround but it might be less annoying then having duplicate media in your project.
-
[Charlie Austin] “Yeah, rereading his quote I think he was referring to FxPlug vs Panels,”
Ah, thanks for the clarification.
-
[Jeremy Garchow] “Rarely, do I need to share edits between multiple Pr users, at least in my case. It’s usually going to/from some other application like FCPX/Baselight/Ae/Compositing via some form of interchange.
“Ah, I see. I think PPro relies a lot on XMP metadata and other metadata that the Media Browser reads on import to keep things straight so if you use an XML or the normal Import command it is more likely to not recognize that the right media already exists in the project.