-
All replies
-
Helpful answers
-
Jul 17, 2012 8:33 AM in response to Douglas Parker1by jack_1611,No you are not the only one. I have the same problem. I can import everything from the camera - even RAW/jpeg pairs. However, after importing videos (1080p @24 fps in HQ), the video starts to play, freezes (black frame) but the playing indicator continues to move. I exported the movie file to the desktop and received file error. The exported movie file did not have the original metadata, and even lost the filename. Weird. The exported file would play with QT. Also to note, the file exported was not the same size as the original file. I am glad I tested this before taking real video with this new camera.
-
Jul 17, 2012 10:14 AM in response to Douglas Parker1by SierraDragon,What OS, Aperture version, Mac, RAM, HDD/SSD and how full, specific workflow, referenced or managed original, etc?
-Allen
-
-
Jul 17, 2012 12:24 PM in response to SierraDragonby jack_1611,OS - Lion 10.7.4
RAM 4GB
HDD 500 GB 7200 RPM 16MB cache (WD Scorpio Black) 1/3 full
Referenced files (orig on usb also Scorpio Black)
I've been using Aperture since 2.x days on this MB (duo core 2.1GHz) and does not have issues with my two Canon PNS cameras 1080p 30fps videos.
-
Jul 17, 2012 12:25 PM in response to SierraDragonby jack_1611,My orginal file size was 152MB, the Aperture exported file was 144MB - with no meta.
-
Jul 18, 2012 9:41 AM in response to jack_1611by SierraDragon,150 MB is a fairly large file size. My expectation is that you have inadequate RAM in that old relatively weak box. I suggest evaluating whether or not you have adequate RAM:
Look at the Page Outs number under System Memory on the Activity Monitor app before starting a typical Aperture work session and write the number down. Recheck the Page Outs count after working and wirite the number down again. if the page outs change (manual calculation of ending page outs number minus starting page outs number) is not zero your workflow is RAM-starved. Ignore the pie charts and other info in Activity Monitor.
If your test showed that page outs increased during operation you can
• add RAM (I recommend all Ap users shoot for minimum 8 GB RAM)
• and/or simply try to run Aperture by itself
• Restart before Aperture work sessions to clear possible memory leaks
• and/or switch from 64-bit operation to 32-bit operation (which will make some additional RAM space available). See Switching Kernels:
http://support.apple.com/kb/HT3773?viewlocale=en_US&locale=en_US
All that said, I have a spare 2.33 GHz C2D MBP that does "work" for Aperture under its max of 3 GB RAM. However it is slow and I doubt if it would properly digest a 150 MB file. Also I run 10.6.8 on that box. 10.7.4 is more RAM-demanding so personally I do not recommend 10.7 or above on Macs that old.
My 2011 MBP has 8 GB RAM and rocks under 10.7.4. However I do get page outs when I run an Aperture-Photoshop workflow, so I will be upgrading to 12 GB RAM soon.
HTH
-Allen
-
Jul 18, 2012 2:08 PM in response to SierraDragonby jack_1611,Allen,
YES, it works following your recommendation of rebooting! My videos taken with D800 look/sound well. Thus far zero Page Outs. My Page Out count was 1.06 GB. I haven't rebooted my MB in 2-3 months... huh.
I still cannot export the movie file created by the D800. I can with any 1080P movie files created by other HD PNS cameras.
This is a different more meaningful error when I try exporting a D800 video:
The movie file in Aperture:
exported file info below. This does play with QT. This shows a larger file, while other times, the exported file can be smaller. Weird.
Unfortunately, I am maxed out on RAM. Wish I had known about 10.7.x being more RAM hungrier than 10.6.x. Would have not upgraded. I suppose I can't go back? My Aperture also updated and has "modified" the dB so I couldn't go back on Ap either... I guess more the reasons to go with a new MBP. Thank you for your help.


