Andy Patterson
Forum Replies Created
-
Andy Patterson
March 8, 2017 at 1:12 am in reply to: FCPX performance – codecs and external IO hardware[Oliver Peters] “I think a lot more is being done internally by FCPX when presenting a signal to the device than other apps do. That’s likely part of the issue here. For example, I have 4K video in a 4K timeline, but the UltraStudio is a 1080 HD device. FCPX takes care of the scaling to send a full frame image out to my 1080 monitors. The same situation using Premiere Pro results in a black screen. In Resolve I have to set the output of the timeline to 1080 in order to see full screen video. Otherwise I see a 1080 window of the 4K image.”
You should not get a black screen because Premiere Pro does the exact same thing with 4K timelines to a 1080P monitor using the Intensity Shuttle. There is no real-time performance loss when using Premiere Pro on a PC. You have to go into the settings to scale down. Watch my video link below at 5:30. Premiere Pro can out put 4K timelines to IEEE DV converter as well. Let me know if it works for your Mac after watching the video.
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.
-
Andy Patterson
March 7, 2017 at 9:03 pm in reply to: FCPX performance – codecs and external IO hardware[Helge Tjelta] “The point is, not all codecs support segmentation or multi-core use. And some programs utilise this very much, hence FCPX is so insane efficient with ProRes.”
But FCPX shouldn’t take a performance hit when using 3rd party I/O gear. Something is wrong with FCPX’s real-time playback engine.
-
Andy Patterson
March 7, 2017 at 9:00 pm in reply to: FCPX performance – codecs and external IO hardware[Dave Jenkins] “I have the same problem. I dumped the BMD products because of this. AJA T-TAP is a little better but I often get freezes on my I/O monitor and the FCPx viewer keeps playing using JKL.”
It seems like you would want to contact BMD and Apple both to correct the problem.
-
Andy Patterson
March 7, 2017 at 8:59 pm in reply to: FCPX performance – codecs and external IO hardwareI don’t doubt FCPX does handle Pro Res better than Premiere Pro. It is interesting that when using 3rd party I/O gear FCPX chokes up on your systems. My PC takes not performance hit when using the Blackmagic Design Intensity Shuttle USB 3.0 version?
-
Andy Patterson
February 28, 2017 at 4:56 am in reply to: Premiere Pro 2017.0.1 Laggy “Play” playback – GTX 1080, SSD Raid, Xeon E5-2630 2.20 GHz (2 processors)Did it used to work and now it does not? Could it be the Nvidia display card drivers?
-
Andy Patterson
February 26, 2017 at 7:45 pm in reply to: MacBook Pros “underpowered?” Not for FCP X editors. Not AT ALL.[Robin S. Kurz] “Obviously exchanging FCP 7 with PPRo would yield the exact same result. Check the time and do the math… there are a plethora of other examples.”
The original post was about FCPX and Intel’s Quick Sync. Who stated Premiere Pro CC is better than FCPX as of now? Can you show how FCPX can allow for speeding up collaborations like Adobe Anywhere? Why not demonstrate FCPX’s alternative to Adobe’s Anywhere? I don’t doubt the Apple alternative is much better but I would like to see a demonstration first.
-
[Brian Seegmiller] “I have a second monitor. How do I get the video I am hoover scrubbing to go to the second monitor?”
Simply go to the “edit tab” on the menu bar. Then select “preferences”. Use the jump list menu and navigate to playback. There you will find your second monitor and any 3rd party hardware. Mercury Transmit must be enabled.
-
[Brian Seegmiller] “for me it is not just the UI that I like in FCP X, It is the way FCP X functions. For example, In pp you can hoover scrub a thumb nail but to be acurate in order to set in and out points you have to open it up in the viewer. Then all yopu have is just a frame of the video that you see at any given time. You have to scrub the whole clip to find that one shot you want and you don’t see the audio waveforms to boot unless you click the button to see it. In FCP X you have a film strip view in the browser either in list view or thumbnail view. While you scrub you have the progam window show your video automaticaly. No need to double click to open it in the viewer. Plus with the filmstrip view you can find that one shot faster by going directly to it. Plus you can choose to see the waveforms. Even if the UI in FCP X maybe lacking for some, I can get my work done faster because it is simple and not cluttered. IMHO.”
I can use the tilde key function in Premiere Pro and save several different layouts. Having said that you don’t have to open a clip up in the viewer (source monitor) to add in and out points. You can use JKL and shift key in hover scrub to get the exact frame where you want to set the in and out. If you have a second computer monitor or 3rd party hardware the video clip that you hover scrub over will out put to the external monitor. No need to double click to see it on the external monitor. I image FCPX will do the same.
-
Andy Patterson
February 26, 2017 at 5:10 am in reply to: MacBook Pros “underpowered?” Not for FCP X editors. Not AT ALL.[Bill Davis] “So a year later Premiere had a skimmer-like capability in what I presume was the rough equivelent of the X Event Browser?
I don’t remember seeing it IN THE TIMELINE (where the editor presumably does the vast majority of their actual editing in a traditional NLE.)
I know Premiere Pro has feature parity via “hover scrub” in the actual Timeline now. Right?
Did that also appear in 2012 and I just missed it?”
Bill you do realize Premiere Pro had GPU acceleration, 64 bit and good metadata capabilities prior to the release of FCPX don’t you?
Keep in mind upon release FCPX had no broadcast monitor support, no native Red One R3D support, no multi-cam editor and a bunch of other features were missing form FCPX when it was first released. Having said that FCPX has gotten better. I know you claim you started using FCPX from day one. Keep in mind some people could not. Not because the the GUI of FCPX was different but because it couldn’t support their work flow. Why make such a big deal out of the hover scrub? Also stating FCPX was a total rewrite of the program does not cut the mustard. Premiere Pro 1.0 was a total rewrite of the code form Premiere 6.5 but it did not lack any features in fact it had more. The bottom line is FCPX was released premature because Apple did not have another 14 months to wait to include all the features that most NLE already had. Apple had to release it as is because Premiere was starting to get recognized once Premiere Pro went 64 bit with GPU acceleration.
I guess it is cool you had hover scrub but you didn’t have multi-cam, broadcast monitor support or support for R3D files when FCPX was first released. Which feature listed above is the most important? I think that would depend on who is using it wouldn’t you agree?
I think FCPX is a good program but the level of cheer leading amazes me at times. FCPX, Avid, Premiere, Sony Veagas etc all have incorporated features form other companies. I don’t necessarily consider it copying or stealing. I consider it all part of software evolution.
-
[Scott Witthaus] “[andy patterson] “Don’t back out on me, dude.”
ooooohhhhh”
Don’t you want to see this awesome GUI that makes Premiere Pro’s GUI look lousy? If I stated FCPX has crappy metadata capabilities compared to Premiere Pro wouldn’t you want proof? I’m sure you would leave a comment of some kind if I made that statement. You don’t see Avid users or Premiere Pro users bad mouthing FCPX the same way FCPX users bad mouth Premiere Pro and Avid. I think most people who use FCPX and Premiere Pro would say Premiere has a better GUI than FCPX but they don’t say FCPX has a lousy GUI. See my point?