Jeff Kirkland
Forum Replies Created
-
I’m glad someone members all the math 🙂
As to the black bars, I’ll just add that, like the original poster, I’ve never had PAL DV import without the black bars at the sides – at least not for the past few years.
It started happening in Premiere around CS3 (I think) and has always been the case in FCPX. There are probably still some horrendously long explanations for it lurking in older Premiere Pro forums. Mostly pointing fingers at the BBC and compliance with their broadcast standards from memory.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
It’s caused by exactly the same issue though, whether you’re dealing with 4:3 or anamorphic 16:9.
I can remember this causing much debate when the black bars first started appearing in NLEs. The BBC used to have a page explaining the whys and wherefore a but its long since been taken down.
In the browser, hange the spatial conform of those clips to fill rather than fit and all should be well.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
you can’t remove the channel but you can switch it off in the info panel so it doesn’t show when you expand the audio components, etc.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Oliver, the problem with the photo processing analogy is that there is a lot more work involved in say, an AE motion graphics piece, than there is typically is in processing a photo. And, while there are any number of applications that do what photoshop does, and even support photoshop files, there’s no other program that cam load an AE project.
Usne any of Adobes video applications and you’re locked in to paying the subscription for the life of the project and beyond.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Try creating a new library and copying the project into it. With any luck the audio issue will be left behind.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Good to hear 🙂
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
That’s the point. There are no settings, and FCPX doesn’t get that kind of thing wrong. If there’s an issue its with the files you’re importing or with your particular installation of FCPX.
Anyway, I’ve made some suggestions that could help diagnose your issue, and the old saying about leading horses to water comes to mind, so I’ll leave it In your capable hands.
Hopefully you’ll find an answer.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
There’s no guide for importing audio because it just works. There’s nothing special to do. It’s 100% rock solid. Well, maybe 99.99% because you are having issues – but your issue is an issue and not the normal way FCPX works.
Have you tried a known good audio file from somewhere else – which is to say a WAV file not created by you on your computer? maybe download something and import that. Or maybe get someone else to import a sample of your audio into FCPX and see what happens there.
The thing to do is try and isolate whether the issue is with the files, the Operating system (QuickTime/AV foundation) or with FCPX.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
As others have said, it’s not the tools – it’s how you use them.
Word processors are available to everyone, and pretty much everyone knows how to use one, but not everyone can write. And, as mentioned above, not everyone wants to write.
The same will be (or actually has been for a long time) true of video. I sell my creativity, my experience, and my ability to deliver what you want on time and on budget. For most of my clients, what equipment or software I use to get there is completely irrelevant.
I personally find having clients with some production knowledge a good thing. It lets me communicate and collaborate with them on a higher level, and I find they have a better idea and acceptance of why I’m quoting a particular dollar value for a project.
The real change is that it will be (is) no longer considered a job for the ‘cool kids’ – It’ll just be an everyday thing like gardening and house-keeping.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
I’ve never had a problem with a WAV, and even though it’s rare I’d use an M4a or MP3 I don’t recall ever having any issues – FCPX sees them as audio files and just plays ’em back as expected.
I have no idea what makes an mp4m so can’t comment on that.
The OP mentioned that they’re showing up in the browser as movie rather than audio files so I’d suspect there’s something wrong the files themselves that’s causing FCPX to misinterpret them.
My suggestion would be to run them through an audio editor and spit them out as 48khz WAV files first. Hopefully that would clean up any source file weirdness.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland