Andy Patterson
Forum Replies Created
-
[Brian Seegmiller] “I don’t understand, the video you posted in this forum was posted May 28th 2017 not 2016. It may have been created back in 2016, but you posted it just yesterday”
I am referring to the Premiere Pro bug video that Robin posted. That one is old.
-
I would be ticked of if someone applied these cheesy effects to any of the Motley Cure, Metalica or Iron Maiden videos I grew up watching. I say tell the story don’t bore me with cheesy effects. The cheesy effects ruined the cinematography in my opinion.
I think the video below is an example of a good music video. Having said that who wants to go for a ride : )
https://www.youtube.com/watch?v=mQ_k_VG6Syc
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.
-
[Robin S. Kurz] “Never mind that that was A SIERRA BUG (or quite possibly even one of the usual shoddy drivers for BMD hardware) not an FCP one.”
Either way it does not look good for Apple. Keep in mind Adobe has to write code for Mac and PC. FCPX is only available on the Mac OS. There should be less risks of bugs for FCPX than Premiere Pro but you forgot about that part of the equation didn’t you? Having said that this is not a thread about bugs in Premiere Pro or FCPX. If you want to start a thread about bugs in the NLEs feel free to do so. This thread is about Premiere Pro having inferior titling system according to you and many others. Could you please comment on that instead of changing the subject?
-
[Brian Seegmiller] “This funny. Showing the problems with FCP X a few versions back. Kind of irrelevant at this point.”
It is not as funny as your comment considering the FCPX video was posted on Oct 16, 2016. The FCPX video is actually newer than the Premiere Pro video but you missed that part didn’t you? As stated in the FCPX video simply changing the color of a title caused FCPX to crash. I would be ticked off if Premiere Pro crashed like that. Having said that this thread should not be about bugs in FCPX or Premiere Pro. The obvious topic of the thread is does Photoshop have an old and outdated titling system from the 1990s? If not how could anyone claim Premiere Pro does?
[Brian Seegmiller] “Dying to see the demo.”
If you want to start a new discussion about bugs in Premiere Pro you can but this thread was started in part because you were dying to see the demo. I couldn’t live with my self if you died. Simply posting “thanks for taking the time to make the demo” might be a nice gesture don’t ya think?
-
[Oliver Peters] “[andy patterson] “Could OS X have more problems than the Windows computers? Premiere Pro was rock solid when it only supported CUDA. Could Open CL be a problem?”
If you have certain Nvidia cards in your Mac, you still have CUDA support.”
I know. I am asking if it happens only with Open CL or does it do it with both?
[Oliver Peters] “[andy patterson] “Premiere Pro has always had the titling tools of Photoshop.”
Hmm… It’s my understand that prior to this newest update, the titling in Premiere was based on a third party plug-in adopted by Adobe some years earlier.”
The titling system of Premiere Pro works the same as Photoshop. You have all the same drawing tools and options. I am only saying the tools are the same. The code is probably different.
-
[Robin S. Kurz] “Yeah, so? One single keystroke.
Helps to actually know the app.”
I know FCPX can show waveforms but you are probably not going to easily see 26 tracks with wave forms that well on a 15″ laptop. That is probably what the original comment by Neil was referring to. See my point?
-
[Robin S. Kurz] “Okay, now that you’ve stated that over and over and over and over again ????… do tell: who? When? Where? Because it apparently had to have been a BUNCH of “all the people” here, since why else would you post this otherwise unrelated clip in this particular forum?”
https://forums.creativecow.net/thread/335/94929
Perhaps you should read the comments in the link above. There have been many times people have said negative things about Premiere Pro’s titling system while glorify FCPX. I am not going to waste my time going through comments form 2 and 3 months ago but here are some recent quotes for you.
[Scott Witthaus] “”Doesn’t FCPX need a new titling tool much more than Premiere Pro?”
No, or not as nearly as bad as Premiere needed it. That title tool was stuck in the 1990’s. In my opinion only, of course.”
[Robin S. Kurz] “[Scott Witthaus] “In my opinion only, of course.”
Not only yours, believe me.”
[Doug Metz] “I am *dying* to see an example from you using PP CS 4.
No, not literally dying. Let’s say ‘eager’.
Doug Metz”
[Brian Seegmiller] “Dying to see the demo.”
For the record the titles in my video were done with Premiere Pro 1.0 not Premiere Pro CS4. Having said that I believe you have your quotes.
[Robin S. Kurz] “And, I dunno… maybe someone got the notion from you?”
I did not say the titling tool was bad in my video. I made a video that showed a bug in Premiere Pro. I find it interesting that after watching my video you cannot just simply say “I guess Premiere Pro does have a decent titling system”. Instead you have to show a video of a bug in Premiere Pro. As stated in the video in CPU mode everything works OK. It did not crash the machine unlike the bug in FCPX video below but you won’t ever bad mouth FCPX. You shake your pom poms for FCPX when ever possible and bad mouth Premiere Pro when ever possible. Everyone on these forums knows it and it can get annoying. I bad mouth Adobe as much as Apple and everyone knows that as well. Having said that if you cannot create stylish titles using Premiere Pro, Premiere Pro would not be the problem.
https://www.youtube.com/watch?v=AhASx3odv4k
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 think it’s important to note that AE doesn’t use the GPU much at all, especially for rendering. Premiere does, but as an option (4 on a Mac). Not all GPU results are the same. For example, with RED raw files, there are visible differences between a software render/debayer and one using the RED Rocket card, which is a purpose-driven GPU. Not better or worse, just not the same.”
Could OS X have more problems than the Windows computers? Premiere Pro was rock solid when it only supported CUDA. Could Open CL be a problem?
[Oliver Peters] “SpeedGrade guts ended up in Premiere and now type from Photoshop and audio elements from Audition.”
Premiere Pro has always had the titling tools of Photoshop. The essential graphics panel left a lot of them out. I was told Adobe is aware of this and will add more features over time. I hope so.
-
[Robin S. Kurz] “[Jeremy Garchow] “I hope you don’t use it as an example of the full (or empty) capabilities of FCPX.”
Unfortunately for you, my predictions came true. Oh well. Better luck next time. ????”
You could have responded by saying “thanks for posting Andy”.
Having said that you must have watched a different video because everyone else had a totally different opinion about it including Jeremy himself. My video was not a FCPX VS Premiere Pro video. I posted it to show that Premiere Pro’s titling system can do some cool things. That was the only purpose of the video. After watching the video do you still think the titling system of Premiere Pro is horrible and needed a revamp? Do you think Photoshop has horrible titling capabilities? Having said that if you cannot create complex titles and simple motion graphics using Premiere Pro it is not the fault of Premiere Pro. That is what I wanted to demonstrate in the video. Did I not do that?
-
[Jeremy Garchow] “I didn’t see the part where Premiere could make a 3D hexagon and have the text reflected in the hexagon.”
I never stated Premiere Pro could make a 3-D hexagon (polyhedron). I had wanted to see what FCPX could do a with a polyhedron. I could make a flat 2-D hexagon in Premiere Pro like you did but I was more concerned with the interaction of surfaces and other elements in the scene than the actual shape. Premiere Pro is not going to make true 3-D glass nor did I say it could so I didn’t bother.
[Jeremy Garchow] “Also, FCPX is track matte capable, you can also draw masks and shapes to use for compositing. I don’t think it’s a great tool for this, but it is possible. You can get gradient fills, you can have “transparent fills”, you can have a “hollow” 3D object within FCPX.”
I never stated you could not do that in FCPX. My video was in response to all the people claiming Premiere Pro has a horrible and outdated titling system. Now everyone knows that is not true. Had people known Premiere Pro has the same titling system as Photoshop I would not have made my video. That was the purpose of making the video. Not to show what FCPX is capable of. I also wanted to pose the question if canned effects are the best option. Keep in mind a FCPX user posted the video in the Cow about the guy who used the canned effects plugins. I thought it was worth showing because for me masks and mattes are more useful than rotating titles in 3-D but everyone will have different needs.
[Jeremy Garchow] “What I don’t like about Pr’s titling isn’t about 3D vs 2D or even overall capability, it’s about usability in the pop up window without canvas control, and the sheer amount of files it generates in the project that have to be managed”
It works OK for me but things can always be better.
[Jeremy Garchow] ” I think this may have changed in the latest version of Pr, but I haven’t installed since the new media cache clearing function was deleting media as well as the cache. I’ll have to revisit after I gain the confidence to install the latest version and patches.”
I finally downloaded it. It kind of sucks as of now because you don’t have all the options of the old titling tool. People have stated Adobe knows it and things will get better over time. I hope so.
[Jeremy Garchow] “Again, thanks for the effort. It’s nice to be able to talk and react to concrete examples instead of hypotheticals.”
Thanks for the kind words and thanks again for letting me use your video.