Andy Patterson
Forum Replies Created
-
[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.
-
[Tom Sefton] “Yes”
There reason why I ask can be seen in the video below. Having said that my system does not get bogged down with JPEG files. What size are your JPEG files? My mediocre PC can edit several hundred 18 & 16 megabyte JPEG files without fail. Even CS 4 could do it. Perhaps Xeon CPUs are not the best option. The Quadro graphics cards have been proven to be inferior to the GeForce graphics cards when using Premiere Pro. For MAYA and 3D Studio MAX things might be different.
https://www.youtube.com/watch?v=NDmOHU6lmRw
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.
-
[Tom Sefton] “We edit on nearly all programs – avid, premiere, fcpx and resolve – whichever is the best tool for the job and more often than not with an honest evaluation we are using fcpx and resolve more often.”
Have you tried a mediocre PC with 4.0 GHZ i7 Skylake, a GTX 1070 and 32 GB of RAM? Obviously a 500 SSD for the OS would be wise and 6 3 TB HD in a RAID array would be nice.
-
Keep in mind if you are editing h.264/AVCHD/MPEG4 Intel’s Quick Sync will help for rendering and playback. An iMac with a Kaby Lake CPU would probably handle playback of 4K AVCHD better than an octo core Xeon. People will probably get different results depending on the computer system and video codecs being used
-
[Bill Davis] “You can start to move your edit forward via all the many database preparation tools X pioneered that do not need ANYTHING to be prepped to function.”
Not this again : )
[Bill Davis] “Every traditional editor I’ve ever walked through X has this same bias. They don’t think their edit has commenced until they have clips on a timeline. It’s maddening since I’ve been talking about this for six years now.”
Why not give us a demo of how proficient FCPX really is as opposed to just talking about it?
[Bill Davis] “Removing ALL the crap from your view via Reject saves sometimes whole days later on. It clarifies editorial thinking EXACTLY like a string out – except it’s 100 times more flexible.”
As I stated why not do a demo for us?
[Bill Davis] “After Hide REJECT – the shape of your raw materials starts to emerge – telling you precisely where you have options and where you might have content holes.”
Once again a demo would be nice.
[Bill Davis] “After six years on X, I’ve truly come to see Tagging AS editing. It’s a “first cut” in everything but name. Those not comfortable with X thinking just miss this because it happens away from the “timeline” but it’s as palpable to me as using a motor to fix an AC rather than starting with magnets and wire and assembling the motor from scratch. Precision range keywording creates useful custom “parts” I can use to build more efficiently with later.”
I have FCPX and I can create keyword with ranges but I should also add other NLE can create custom built parts of their own.
[Bill Davis] “The point is that there is lots and lots of effective edit prep that can take place during the first few days of a typical X pre-edit period that lets me move my edit very much forward – they just don’t take place on my timeline.”
You can prep stuff in other NLE as well.
[Bill Davis] “Once again, if you try to drive X using non-magnetic prep thinking and expectations (the “the edit happens only on a timeline) approach) X will probably slow down to about the efficiency of any other NLE.”
Why not do a demo and see if someone else has a better technique? You always say you want to learn. Perhaps you use a grappling style when a striking technique might prove to be just as efficient.
[Bill Davis] “It’s only when you embrace its complete gestalt – that things start to really fly.”
There is also many obstacles with FCPX as well.
-
This looks interesting. My other post had the wrong link.
https://www.youtube.com/watch?v=-eSFcIJk8Lc
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.
-
[Tom Sefton] “However, once the files are imported into fcpx (sometimes an overnighter) it has been waaaaay faster and snappier than premiere for us – mostly due to the issues that premiere has when working on projects with large libraries of r3d and high resolution material. Importing one jpeg was bringing premiere to a halt – tech support just advised to make the project smaller or cut it into chunks…not very Pro.”
I do not have that problem with Premiere on the PC side. Having said that why are you even using Premiere if it so awful? The first time I tried FCPX on my Mac Mini it constantly locked up the system. I did not bring that many files or images into FCPX. I think it was just a fluke because as of now FCPX works OK. It is obviously not as quick and peppy as Premiere Pro running on my PC. Having said that FCPX does OK with h.264 at 1902 X 1080. That is al I plan on editing with it.
-
[Peter Gruden] “But I’m not sure if complex programs like FCPX or Premiere Pro would benefit from a dedicated controller, except for basic transport and editing.”
Premiere Pro can make use of control surfaces for color grading and audio. Someone stated that FCPX will not work with Mackie and I imagine other audio based control surfaces like the Korg nanaKontrol 2 because it does not have audio tracks. I think you can get a 3rd party app to make the audio control surfaces work with 15% functionality. To me it is not worth doing. As far as FCPX making use of color correction control surfaces it might be able to.
-
I remember when I did my BMD Intensity Shuttle VS the Canopus ADVC 110 using Premiere Pro and Edius I don’t remember Edius having to conform audio. Edius can playback h.264/AVCHD files as good as Premiere Pro because it makes use of Intel’s Quick Sync but Pro Res and Red One R3D files it will struggle with. There will always be pros and cons to all editing systems but perhaps at NAB 2018 Adobe will have a much better Premiere Pro to demo.
-
[Steve Connor] “Still better than waiting for PPro do do it’s thing though, which seems to take just as long!”
How is it better if they take the same amount of time? Does FCPX make coffee for you while you wait?