Andy Patterson
Forum Replies Created
-
I am really not that impressed myself. Having said that I fear that there will be even more bugs and that really bugs me : (
-
[Scott Witthaus] “A new title tool. Finally.”
Doesn’t FCPX need a new titling tool much more than Premiere Pro?
-
I am not a fan of Mitch Ryder but I think this totally rocks! I am not sure if Prince liked it or not.
https://www.youtube.com/watch?v=w1NLrpNhfRc
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.
-
[Noah Kadner] “Probably more because all of those long-GOP formats lose major quality when re-encoded. I don’t follow how that’s Apple’s fault. If every camera recorded to ProRes instead of H.264 we’d be all set.”
H.264 uses much less hard disk space and requires much less sustained data transfer speeds than Pro Res. A lot of SD cards will not sustain writing speeds to record Pro Res at 4k. H.264 gives a good clean image without need for a lot of storage space or super fast storage type media.
-
[Morten Ranmar] ”
– A completely rewritten text tool that lets you edit directly on the canvas like in Photoshop.”
The old titling tool worked great and had a lot of cool options. I am not saying this new method is no good. I am saying the old titling tool already worked great.
-
[Jeremy Garchow] “Pr crashes on a SAN, Pr crashes on local storage, on both laptop and desktop in multiple locations. While storage is easy to suspect, it doesn’t seem to be the common culprit as the storage changes, and the software I’m using remains constant.”
Are you on Mac or PC? If you are on a Mac is Premiere the only thing running? People have reported Premiere on it’s own works fine but once Safari and other programs are open Premiere gets glitchy. Is that OS X’s fault or Premiere’s fault? Could it be a combination of both? If you are on Windows I would wonder if it is MS’s fault or Premiere’s fault. Keep in mind no OS is perfect and no software program is perfect.
-
Perhaps someone there will have a 4G phone with unlimited data that you can tether to a laptop. I have unlimited data with my 4G phone (no dropping to 2 G after 20GB). I can use the Blackmagic Design Intensity Shuttle along with a DSLR camera to stream over Google Hangouts. I have been told the Intensity Shuttle works with most online streaming software but there are cheaper USB devices that would work as well. There is also free and inexpensive software that will let you use almost any DSLR cameras as a live webcam without the need for any extra USB devices. Most streaming software will see it as a webcam. The software worked with my DSLR cameras. It would probably be best to use 1280 X 720. The 4G might take a hit at NAB.
-
[Robin S. Kurz] “[Scott Witthaus] “From version 10.0.6?”
I know, right? ????????”
That is not the only bug in the history of FCPX. You make bug issues with Premiere Pro (that affect a few people) seem like the end of the world but if FCPX has a bug issue like Oliver pointed out it is BMD who is at fualt. Interesting if someone has issues with Premiere Pro you would never stop to think it could be OS X. Why is that?
Keep in mind I am on a Windows PC so in regards to the bug you made a big deal out of right back at ya ????????
Emojis can be fun ????
-
[Scott Witthaus] “[andy patterson] “From what I can tell Premiere Pro did not actually crash like FCPX did in my video link.”
From version 10.0.6?”
Do you seriously think that is the only bug FCPX has ever had?
The difference between Premiere Pro users and many FCPX users is the fact that Premiere Pro users do not constantly bad mouth FCPX in order to make Premiere Pro look good. I think some people are in these forums to give honest criticism and feedback. I think others are here only to shake their pom poms for Apple. What good does that do other than become annoying? Having said that constantly bad mouthing Adobe or Premiere Pro is not going to make FCPX any better so why do it? Does it make some of you FCPX user happy when a video editor is having problems with Premiere Pro? I can find YouTube videos of bug issues with FCPX. I can also find discussion forums where people have bug issues with FCPX. Why would I want to post about the bug issues with FCPX when I use Premiere Pro? If I start bad mouthing FCPX is not going to make Premiere Pro any better. I myself hope things get fixed with Oliver’s problems when he uses FCPX with third party hardware because I like using 3rd party hardware myself. It may be a bug that is part Apple’s fault and partly a BMD driver issue. Who knows for sure but I hope things get resolved soon.
-
https://forums.adobe.com/thread/1663472
You found some people who had a problem. There may have been a total of 100 people who had this problem.
Here is what you should have read.
“I was able to do some testing on a new edit (about 30-40 clips) and it got to a point where the thumbnails were refreshing constantly. I then closed all open apps (iTunes, Safari, IM) and the refresh issue went completely away. I opened the apps back up and the refresh issue instantly came back. I repeated this several times and ran a screen cap: Dropbox – apps-issue.mov
“I isolated the problem to Safari. I tried Chrome (normally not open) and it did refresh once or twice, but not nearly as much as Safari.”
That is a Mac OS X issue.
Safari is what caused the issues for some. Perhaps Adobe should drop Premiere Pro from the Mac platform. Having said that you like to find videos and forum threads where a few people are having problems with Premiere Pro. Why didn’t you post videos of FCPX users having problems?
https://www.youtube.com/watch?v=VPo9ac7U3Nw
[Robin S. Kurz] “I did. Only none of what you wrote, aside from maybe the waveform thing, had anything to do with general use i.e. performance that could be relevant to ALL users of either app. As I said, “niggles and bugs” or rather specific use cases that may apply to you, but say nothing about the performance for any and everyone overall, which is what I was looking for. Unless of course you’re saying “FOR ME”, in which case, that’s fine. Just not what I took it to mean or meant myself.”
The supposed timeline thumbnail bug that you mad a big deal out of probably effected less than 100 people. In fact I will ask the obvious question. Has anyone in these forums experienced the timeline thumbnail bug that supposedly brought Premiere Pro to it’s knees? From what I can tell Premiere Pro did not actually crash like FCPX did in my video link.