Matt Campbell
Forum Replies Created
-
Unfortunately it wasn’t up to me or I’d already be on a MAC Pro. They built 2 Hacks for the price of 1 tower, to try and save money. These were built back before I started, so I was dealt these cards. I’d rather spend the $ upfront, then spend the time later fixing problems. Other than whats in the system profiler (below), I have no idea what specs are used.
Although I do know the GFX card is: AMD Radeon HD 6870
Which says isn’t supported by Premiere, but read others have used it and had no problems. Maybe this is it. But would think not, because I used PProCS6 to just cut about 6 videos. Import 7D footage, edit, export to ProRes, all with no issues. Only when I Quit.
OSX 10.7.5 with a 3.39 Ghz Intel Core i7 on a built up Hackintosh
16 GB of RAM with OSX on SSD, (2) internal HDDs RAID’d 1 for project files and External RAID 5 for all project assets (media, GFX, stills, etc.) -
uhhhh, what? Have no idea what that is or how to do it. Believe me, this isn’t the first time something hasn’t agreed with this Hackintosh crap.
OSX 10.7.5 with a 3.39 Ghz Intel Core i7 on a built up Hackintosh
16 GB of RAM with OSX on SSD, (2) internal HDDs RAID’d 1 for project files and External RAID 5 for all project assets (media, GFX, stills, etc.) -
Thanks. I’ll try the permissions. I’ve had nothing but issues with the Hackintosh. But unfortunately its not my call. I’m trying to get a new tower! Fingers crossed.
OSX 10.7.5 with a 3.39 Ghz Intel Core i7 on a built up Hackintosh
16 GB of RAM with OSX on SSD, (2) internal HDDs RAID’d 1 for project files and External RAID 5 for all project assets (media, GFX, stills, etc.) -
Yup. 16-bit Float. I’ve just started using MOTN 5, which I love. MOTN 5 though doesn’t let me render to Animation codec, so I’ve had to use ProRes 4×4, which is fine, or an Image Sequence. Yes to QT 7, which I always use. Hate QT X.
I’ll run some tests and see. I’ve always left to Auto as well, but was just never sure.
OSX 10.7.5 with a 3.39 Ghz Intel Core i7 on a built up Hackintosh
16 GB of RAM with OSX on SSD, (2) internal HDDs RAID’d 1 for project files and External RAID 5 for all project assets (media, GFX, stills, etc.) -
Thanks Tim. But those were my old specs. I’m currently running:
OSX 10.7.5 with a 3.39 Ghz Intel Core i7 on a built up Hackintosh
16 GB of RAM with OSX on SSD, (2) internal HDDs RAID’d 1 for project files and External RAID 5 for all project assets (media, GFX, stills, etc.)Thanks for your comments. With my small interview type projects that are quick, I plan to go native throughout and export my archival master to ProRes.
For more critical work, I’ll build in load time to jobs and compare native to my tried and true FCP method of transcode up front. ProRes has been flawless for me and other than that increased file sizes, its great.
Looking forward to putting PPro through the ringer. So far so good and glad I went this route vs. AVID. Which is great too, don’t get me wrong, but for the speedy workflow and simplistic resemblance to FCP, I’ll take Premiere.
OS 10.7.5, Hackintosh 1x 3.66 ghz 8-core intel xenon, 16 gb ram
-
Understood. But watched a video on PPro from Jason Levine @ Adobe and he says that Premiere auto upscales all footage to a 444 color space. So if 420 h.264 files come in to PPro, you edit native and export to ProRes 422 you should be fine. Any color correction or grading done in PPro is up scaled to 444. So even thought its only as good as camera format 420, you’ll have more head room on edit, grading and final output with 422 or 444.
And thanks everyone. I guess I’ll just run some live tests with various projects. I plan edit native dslr for an upcoming interview but with the next project being a larger one, I think I’ll try the tried and true FCP method on going ProRes all the way through. Thx again all.
OS 10.6.7, Mac Pro 2 x 3 ghz quad-core intel xenon, 4 gb ram and AJA IoHD
-
Good tip. Jason, I’ve actually used and quite like the round trip function. Being able to have a .motn doc in your timeline is a huge time saver from having to render, import and edit into FCP timeline. Now, I would always do that once I get approval, but for offline type GFX and edit, works great. However, I do agree about crashes. As projects grow, the more unstable they become. At least with MOTN 3, Loved 4 but think I’ll try 5. Again, 50 bills, you can’t beat it.
Mark, love the MBS episodes. Huge reason why I use and love MOTN. You make it easy to understand.
OS 10.6.7, Mac Pro 2 x 3 ghz quad-core intel xenon, 4 gb ram and AJA IoHD
-
Dave and Michael, I’ve double checked my footage and Michael you are correct. Video is 23.976 and audio is 48 khz, not 44.1. My external audio is also 48 kHz, but 24-bit, where as the transcoded footage is 48khz 16-bit. Does the bit depth affect sync? It shouldn’t right? Screen shots of Item Properties below.
Video has 2 mono channels each. A-cam & B-cam. External audio has 4 mono channels. Lav 1&3 Boom 2&4.
Images attached.
Audio:
Video:
OS 10.6.7, Mac Pro 2 x 3 ghz quad-core intel xenon, 4 gb ram and AJA IoHD
-
Kirk, do you have your the Virtual GFX card enabled (not sure if that model MBP has this or not)? If so, disable it. I had a similar issue with my 2010 17″ MBP and disabling that virtual (or 2nd) GFX card solved my issue.
I realize this is an old post, but ya never know.
OS 10.6.7, Mac Pro 2 x 3 ghz quad-core intel xenon, 4 gb ram and AJA IoHD
-
Hey Dave, I don’t think so. I know dslr shoots 44.1 audio but with the canon plugin for FCP, it converts to ProRes and 48khz. The external audio is 48 as well. I’ll take a deeper look tmrw when in office as I’m not 100% on audio from the PR files. But again, syncs manually in timeline no problem, which is all from same In-Points that I used for multiclip, which is off.
I’ll do a test tmrw with one clip and use Streamclip to convert to PR and 48, which I don’t like to do cause it strips metadata, but will see if it works. Or even Compressor.
OS 10.6.7, Mac Pro 2 x 3 ghz quad-core intel xenon, 4 gb ram and AJA IoHD
