David Johnson
Forum Replies Created
-
[Yup, you’ll probably get a few comments.]
That’s fine…from the many hours I’ve spent on this and other forums (including Apple’s), It’s very clear to me that I’m not the only one experiencing problems with FCP that are beyond the norm with NLEs.
The only peripherals, so to speak, are the AJA I/O and X-Serve RAID, which are both connected and fucntioning properly. -
No prob…I very much appreciate you trying to help. Based on this and other experiences in a relatively short time period, it seems to me that FCP is just very buggy software of the “pro-sumer” type. That’s what we get for trying to save a buck on unproven tools, rather than going with tried and true “pro” gear such as Avid or the like. I mean no offense to the dedicated FCP users who will likely respond to that comment with rage, but I can only base my opinion on my experiences and am simply not the type to hold my words for fear of offending.
-
I’m in a corporate media department and we have a very good Mac Tech who has done those things and many others to ensure the G5 itself stays in stellar condition, but his expertise tapers off when it comes to specific production software like FCP. Even so, he is very good at checking software-specific documentation, etc. to make sure he doesn’t do anything that’ll effect the software and i’m always right there with him as he works on our Macs (we have about a dozen, although only one FCP).
-
[https://www.kenstone.net]
Been there, done that the first time this happened…that time, after several days of restarting, trashing prefs, etc., it eventually opened, but it’s now obvious the problem wasn’t really resolved…FCP apparently just felt like working again for a while. Doubt it’s a corrupt project problem since it happened both when trying to open FCP fresh to start a new project and when trying to open various existing projects that worked fine before all the way through mastering. -
I stand corrected. Sorry about the misinfo Brian…I should’ve been sure before advising someone else…guess I just never had a need to scrub audio in AE.
-
As Del suggested, first make sure you have enough memory avaialble to PS, but also keep in mind PS is a resource intensive program and can bog down if you have too many other apps open or too many background processes running…that varies depending on your system specs (CPU, RAM, etc.). The same can happen if you’re working with unusually large files and/or unusually high resolution, but again depends on system specs.
-
There are several plugins that can generate fireworks, but I’ve found that compositing real fireworks stock footage gives a much more realistic look…and is certainly faster/easier. I think I got mine from ArtBeats, but a quick Google search will yield some options if my memory is incorrect.
-
If plugins are within your budget Aurora Sky available from Digital Element and Digital Anarchy, as well as The Foundry’s Sky plugin (part of Tinderbox 1) both make very nice clouds.
-
AE isn’t an NLE so it doesn’t “scrub” audio, but you can press the period key on the number pad to preview audio only or, to preview audio during RAM preveiws, make sure Audio is checked in the dropdown menu Composition>Preview>Audio., or serach AE’s Help for “preview audio”.
-
Don’t know about the SHFT+0 method, but the asterisk (* aka multiply) key on the number pad will set layer markers, but only if a layer is selected in the timeline.