-
Background processes are an impediment to starting the edit
-
[Jeremy Garchow] ” During editing, I’ll beachball 3-4 times a day, and this started with 10.3.4. 10.3.3 and 10.3.2 were much better. I agree something is wrong and not quite sure it’s hardware related. This happens on all the machines we have.”
I’m curious about that, as it’s not an experience I’m seeing on our machines with either FCPX or Premiere Pro. My projects are also pretty large and from a variety of sources.
The only big difference in what you’ve described, is that I transcode the oddball formats first. This would be most mp4 files from DJI, GoPro, A7s, 5D, etc. I’ll typically transcode these to ProRes or ProResLT. We don’t get that much RED material either, so I’ll transcode those, too. My rule-of-thumb is that if it’s kind of a broadcast camera, I’ll stay native. Otherwise, transcode.
My native files tend to be Alexa and/or Canon C-series clips. Right now we are also cutting inherited content with a lot of Sony F-series camera material (various models) and that’s native, too. We do beachball from time to time, but across 7 machines, I would say the average is less than once a day on one of the machines.
Hardware mix includes iMacs, Mac Pro towers, one 2013 Mac Pro, plus 256TB QNAP NAS.
– Oliver
Oliver Peters – oliverpeters.com
-
[Oliver Peters] “Yet this problem doesn’t appear to exist with the *ancient* Media Composer. Why?”
No clue.
But some folk watching early “electric ignition” cars probably railed against those too – opining that their hand crank model T’s never failed to start due to a dead battery.
Point is that over time, smart changes in approach aren’t ALWAYS without bumps.
Simpler, seemingly foolproof and effective processes always have there adherents.
Magnifying glass and dry leaves, wooden match, or butane lighter tech. They all start fires.
Pick what you prefer – and have fun burning things up.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Jeremy Garchow] “So we can agree that there’s issues beyond being “traditional editors” even though we use FCPX daily?”
I’ve never ONCE said that X has “no issues” for any user of any class anywhere.
All I’ve tried to do is meet negative comments with what I see as “balancing” ones.
Key concept – balancing.
To me, that means a 100% negative post ABOUT X, whether that one post is factual or imaginary – it should be met with one that’s 100% positive for balance.
Read both – then the reader gets to make up their own mind.
Have some of mine been totally positive? Sure.
Want me to recall posts that were totally negative about X?
(I bet I could go 50 to 1 in the first years of X and still probably 3 to 1 in my “across the web) reading about X today. )If I can get the overall “things written about FCP X” to just be closer to neutral, overall, I’ll be happy.
People are smart enough to choose for themselves. So long as both sides get aired in a balanced fashion.
It would actually be nice to be able to bitch about the things in X that I think could be improved.
But I’m not holding my breath. Cuz the scale is still not even close to equal, IMO. And adding my water to a still running hose of negatives, only works after the results of the negative flood is quelled and things have dried back to a neutral state.
And overall, we’re not even close to that yet, IMO.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Tom Sefton] “I have quite literally zero interest in debating Mac vs PC with you Andy.”
Who said anything about debating Mac VS PC? I am just curious to why you are having so many problems with Premiere Pro on the PC side. Aren’t you curious as to why your PC is bogging down when editing large JPEG files? If it were happening with FCPX I am sure you would want to find a way to correct the problem. Having said that I have posted two videos below. There were several hundred JPEG files in each project even though I did not use that many images for the final output. Are you saying your computers could not edit the videos bellow? If your system cannot then there is something wrong with your system because mine can. I have never had a problem editing JPEG images with Premiere Pro. Even when using CS 4.0 I could edit large JPEG files.
-
[Oliver Peters] “Setting the import to ignore silent tracks doesn’t seem to help much.”
Why would it?
In digital cloning, the most efficient process will always be bit for bit copy of the original digital file without any change.
Asking the software to “un-mux audio, separate two out of four or six audio samples, then digitize ONLY the rest” would probably be massively more processing work than simply the “see a bit – clone a bit” thing it does now.
In X, once that signal is parsed by the database, it’s trivial to go in and just tell it to disable “all but tracks one and two.”
It’s just a metadata adjustment that you can batch apply to 1000 clips in two seconds.
Much smarter the way they do it, IMO.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Bill Davis] “In digital cloning, the most efficient process will always be bit for bit copy of the original digital file without any change.”
What cloning? No media is being copied.
[Bill Davis] “Asking the software to “un-mux audio, separate two out of four or six audio samples, then digitize ONLY the rest” would probably be massively more processing work than simply the “see a bit – clone a bit” thing it does now. “
So what you are acknowledging is that this setting in the import window is essentially useless, since all of the tracks – silent or not – still have to be analyzed.
– Oliver
Oliver Peters – oliverpeters.com
-
[Bill Davis] “But some folk watching early “electric ignition” cars probably railed against those too – opining that their hand crank model T’s never failed to start due to a dead battery.”
Really? You can’t do better than the “Luddite argument”? ☺
– Oliver
Oliver Peters – oliverpeters.com
-
[Bill Davis] “Key concept – balancing.
To me, that means a 100% negative post ABOUT X, whether that one post is factual or imaginary – it should be met with one that’s 100% positive for balance.
Read both – then the reader gets to make up their own mind.”
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Oliver Peters] “I’m curious about that, as it’s not an experience I’m seeing on our machines with either FCPX or Premiere Pro.”
It’s all some sort of waveform or video out based or both. Closing the inspector helps (a waveform source), closing the browser helps, minimizing the chiclet size helps, turning off video out helps, same old tricks, but still doesn’t account for why and when.
-
[Jeremy Garchow] “but still doesn’t account for why and when.”
Sounds like some sort of RAM leak or something. Does it vary with model of Mac – for example, Mac Pro versus iMac?
– Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up