Decklink issue with Aperture

Over on the Aperture forum, there's a recent post from a Final Cut user who had to disable Decklink to get Aperture to run.
I don't have a Decklink system to confirm or deny.
bogiesan

David
are you using Aperture, and what do you use it for, is it video related or just for still photography?
I wondered about trying it, but as Iv Photoshop CS, I felt it would just be another app to learn. I use Photoshop for all the usual still and graphics imorts to FCP
Gary

Similar Messages

Full screen mode - Issue with Aperture freezing

Hi I have an issue with Aperture 3 freezing if I send an image to a plug-in or external editor while in full screen dual display mode. I have to exit full screen mode first and then send to photoshop/external plugin.
It is not a huge deal and a simple workaround but if I forget to do it Aperture will freeze and I will have to force quit the application.
Any thoughts or suggestions welcome.
Thanks!

Just send a comment to Apple via "Aperture→Provide Aperture Feedback".
IME, both full-screen mode and dual-display mode have some rough edges. (I don't expect any improvements until OS 10.7, which is widely reported to include a full re-design of full-screen mode.)

Is anyone else having issues with Aperture 3 since downloading Lion?

Hi All,
Is anyone else having issues with Aperture 3 after downloading the Lion update? Aperture 3 is running so ssssslllloooowwww !!! I am a sports photographer who needs this to run the way it used to with Snow Leopard. Any suggestions?????
Thanks,
George

It was one of the many issues I had when I was running Lion. I watched the beach balls and the very, very slow rendering of image edits and restored back to my SL clone immediately. It was looking like Aperture 2 and my sanity just couldn't take that again.
I have to assume that Apple must have tested Lion with Aperture 3, but you wouldn't know it from how it behaved on my system.

Printing issues with Aperture 3 - color management

I just made three prints of the same images, two with Aperture 3 that turned out very dark and off color, almost as it they were printed without color management or double profiles. I then printed the third by exporting the image to CS4 and printing with the same settings (rendering intend, printer settings and custom printer profile) and that print looks fine. Has anyone else run into similar problems with A#? I did not have this issue with Aperture 2.
Thanks,
Message was edited by: pcalvin

I print on an Epson 2880 with Lyson inks and custom profiles. In Aperture 2 it worked perfectly, with exactly the same settings as for printing Photoshop - using the laboratory prescribed settings:perceptual and no black point compensation in Photoshop, and Adobe RGB Gamma 2.2 in the Print settings.
Using the same profile and settings with Aperture 3, the colours are way, way off - exactly as described.
I then tried with Aperture 3 turning off the Adobe RGB setting, so there was no colour space adjustment in the Print setting. This gave a slightly better result, but rather dead and slightly blue.
I ran some tests with the GretagMacbeth colour chart used in preparing the profiles, which confirmed the above but also shows a lack of sharpness when printing from Aperture 3, and a blue border on three sides of the image - even though the border was set to 0.00. I have checked the printer head adjustments and run the test chart through Photoshop again to verify these are Aperture 3 artefacts.
Unless this is resolved, it renders Aperture completely useless! (I have tried reinstalling printer drivers, to no effect).

Screen/Display Issues with Aperture 3.6 & iPhoto 9.6 on Yosemite

When I open Aperture or iPhoto, my screen goes all wonky. I have an early 2011 MacBook Pro with 8 GB Ram with the Intel HD Graphics 3000 512 MB. What is it doing this? How can I fix it?

Hello there, tehat17.
The following Knowledge Base article offers up some great recommendations for troubleshooting issues with the display on your MacBook Pro:
Apple computers: Troubleshooting issues with video on internal or external displays
Start with these:
Reset the system
You can reset the Mac's parameter RAM and SMC.
Reset the resolution
Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
Start up in Safe Mode.
From the Apple () menu, choose System Preferences.
Choose Displays from the View menu to open the preferences pane.
Select any resolution and refresh rate that your display supports.
Restart your computer.
If you tried all of these steps for your display and the video issues persist, contact Apple technical supportor take your Apple computer to the nearest Apple Store or Apple Authorized Service Provider (AASP) for diagnosis. If you plan to visit an Apple Retail Store, make a reservation at the Genius Bar using http://www.apple.com/retail/geniusbar/ (available in some countries only).
Note: Diagnostic fees may apply for issues not covered under warranty or the AppleCare Protection Plan (APP).
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Mac Book Pro DVI and Display LED 27" + Atlona DP400 - Issue with Aperture

Hello,
I bought the new LED 27" and connect it through the Atlona DP400 to my "old" Macbook Pro with a DVI port.
Works well except with Aperture.
I can launch the application, navigate though the project and the pictures, but when I want to work on a picture, the mac is blocked and the only way to exit this situation is a hard reboot.
Does anyone had the same issue ? and found some solution ?
Thanks

Interesting. I usually expect newer OS versions to cause issues with older boxes rather than to solve them.
Glad it worked out for you.
-Allen

Issue with Aperture full screen mode on HD 5870

I have a very strange problem with Aperture, which may be linked to the HD 5870 and it's probably faulty drivers and would be very grateful if somebody with the same hardware could try this out if he/she can replicate this behavior:
I have a brand new 6-core with the 5870 optional card using a dual display setup (ACD 23" and NEC PA241W).
Whenever I enter full screen mode and activate the brushes, the image on the full screen monitor is reduced in size to about 70% of the full screen resolution. This also gets triggered, when I use the HUD display ("H" key) and lock the floating window on the browser display.
It's a bit hard to describe, but anybody with the same or similar setup, please try this:
- enter full screen mode in Aperture by hitting "F"
- press "H" and lock the window using the small slider in the upper right corner
- activate any of the quick brushes, like dodge or burn
Is your image, which is displayed full screen on the main monitor, getting smaller in size or is it starting to flicker a bit, getting darker? If yes, we have a universal bug here.
I could narrow the problem down in a sense, that it does not matter if either screen is hooked up using the DVI or the Mini-Display-Port. It also happens when I switch the main screen over to the other, so it's (fortunately) not a problem of my new NEC display, the ACD shows the same behavior.
My best guess right now is some kind of bug in Aperture combined with a faulty driver of the HD 5870.
Any help here is greatly appreciated.

People have said that Aperture library benefits from, and should not be, on the boot drive, and placing on SSD or alternate drive, maybe RAID 0 in some cases.
64-bit kernel mode helps overcome some of the limitations and obstacles when working with large data sets, which is why I always kept data off the system and placed on RAID 0 which does improve system responsiveness.
If you have already done that and taken steps to optimize your storage layout hard to imagine it is a graphic driver.
And I would limit removing caches to just Aperture's own, though can't hurt to clean out the system's, that is something that SuperDuper will do if you use it, as it doesn't copy those and just skips caches and temp files best rebuilt (but does not touch user caches).
And a touch of Disk Warrior just for good preventative maintenance measure of course.

Having issues with Aperture while editing...Black Screen!

I'm having problems when editing with Aperture...For example:
-Picture goes black after applying an edit, then continues on to all other pictures untill I reboot Aperture
-Exposure goes out of whack after applying an edit
-Skin smoothing strocks are shown after being applied
These are just a few. They do not happen the entire time I am editing, but about 30 minutes in everytime i get on Aperture something goes wrong and i have to reboot. It becoming incedibly frustrating especially when i have delines to meet with clients.
I love using Aperture, but i can't afford for this to continue happeneing. I may have to consider using a different editing system if this problem contiues.
Please help!

I have 5 plug-ins that I never use...I need to delete them, but don't know how.
At least check, if the plug-ins need updating - look at the manufacturer's website, if they are compatible with Aperture 3.5 and Mavericks. (see: Aperture 3.4 and later: Some third-party plug-ins are no longer compatible)
To uninstall plug-ins open the folders
~/Library/Application Support/Aperture/Plug-Ins/
(that is the user library in the Library folder in your Home folder)
and
/Library/Application Support/Aperture/Plug-Ins/
(that is the in the Library folderat the top level of your MacintoshHD)
Quit Aperture. Remove any "Edit" or "Export" plug-in, that you do no longer need.
Your User Library may still be hidden. Open it from your "Home" folder:
Select the "Home" folder icon in the Finder's sidebar and press the key combination ⌘J to open the view options. Enable "Show Library Folder".
Then open the Home folder and open the Library folder inside and navigate to ~/Library/Application Support/Aperture/Plug-Ins/.
For the second location, the system library on your hard drive, simply open the "Library" folder after clicking and opening the HD icon.
After removing the plug-ins restart the system. Test, if removing the plug-ins will mitigate the problem.
If not, check, if the problem occurs for all your Aperture libraries. Create a new Test library and check, if the problem depends on the library.

Yet another export issue with Aperture 3

Judging by a search of topics, there seem to be a myriad of problems associated with getting files out of Aperture, some of which represent occult setting issues, others which seem to be actual bugs. I've run into an issue which seems to defy categorization, and I'm not sure if it's me doing something wrong, or if it is actually yet another bug with this software. I've been an Aperture user since 1.0 and I have to say the current version I'm running (3.4.3) is by far the worst yet. Anyway, enough whining. Here are the issues:
I'm running Aperture on a 6 core Mac Pro with Lion 10.7.5. There are two thing happening.
1. Exporting JPEGs is INCREDIBLY slow - perhaps as long as 4 or 5 minutes for a 3MB file.
2. This is the one driving me batty right now. Tried exporting a batch of images as JPEGs at the 50% original size setting. The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2. They are 80-100MB in size. When I export the images to a file on my Desktop, it consistently exports 6- 10 KB thumbnails. I've checked and rechecked my export settings and can find nothing amiss there. Has anyone else had a similar experience? Could the view I'm working in have anything to do with this? I work 95% of the time in split view.
Thanks,
Russ

I agree that there re a lot of posts about exporting, but a very large number of them refer to the same thing, and it's not a bug, but rather a misunderstanding.
For instance:
Tried exporting a batch of images as JPEGs at the 50% original size setting.
Okay.
The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2
Not relevant.
They are 80-100MB in size.
Not relevant either.
Why?
Because size refers to the dimensions of the image. So a 1,000 x 1,000 pixel image exported at 50% will turn out as 500 x 500 pixels.
Were you expecting a jpeg between 40 and 50 MB? That's Jpeg quality or the amount of compression applied to the image. And as you're compressing a lossless format (tiff) to a lossy one, and one with an aggressive compression algorithm, he resulting Jpeg, even at high quality, will be much, much smaller, more likely in the 6 - 8 MB range.
That's the nature - and indeed the point - of Jpegs.
So, if you're getting 6 - 10 kb images, you're exporting at a very low Jepg Quality.
This may also explain why it's taking so long to export. Getting rid on 99.99% of the data and compressing into 10kb is always going to take time.

Issues with Aperture 3.3.1 and LX-5 raw files

Having used my Lumix LX-5 raw files successfully with previous versions of Aperture, after loading some into V3.3.1 this morning, the initial preveiws were fine, and then I watched everyone change from a normal well exposed image to vertially all black with a very dark green colour cast!
No amount of adjustment via the inspector tools wil fix them.
Anyone got any suggestions or solutions?
Thanks

Two things to try:
Force the generation of new previews by holding down the option key while selecting "Update Preview"
If this only happened after you upgraded to 10.7.4 and worked well before, then register your camera with the lauch services database - see this post by Alan Roseman:This solved my questionRe: Aperture 3 preview of raw file greenish, but read the follow up posts (the lsregister command) as well, on how it is supposed to work and how to correct the typos.
Added: if that does not help, try to remove the raw presets from ~/Library/Application Support/Aperture/RawDecodePresets.plist
Regards
Léonie

Stability and Performance Issue With Aperture 3

I'm running Aperture 3.0.3 on my iMac. This is a switch from Adobe products and I'm having a ton of stability and performance problems.
Environment:
* My library is about 32,000 images, about 1/3 of which are 21 megapixel, the remainder are 10 megapixels or smaller.
* I have no smart albums.
* All images are referenced and live on an external FW800-connected RAID5 array. The library lives on my internal drive.
* I have an Apple Cinema display connected through the mini-DVI port.
Here's what's happening. Initially, Aperture starts up fine and things are peachy. After a few adjustments -- particularly cloning or patching, rendering becomes slow. It becomes slow as in a minute or more. On a 21 megapixel file, this is an incredible productivity killer. Here is what I've tried to make Aperture go faster (not all at the same time):
- Log in holding the shift key to make sure nothing but core system stuff is running
- Rebuild Aperture library
- Defragment internal hard disk using iDefrag
- Export a subset of images to a separate library and work on them there
None of these has had the desired effect. Worse, if I switch to full-screen mode, the whole interface becomes balky and can become unresponsive to the point where the only way out is to cold reboot the computer. Cmd+TAB doesn't even work.
I can't imagine this is an experience shared by many users of the screaming would be deafening. Lightroom and Photoshop are insanely fast by comparison so it can be done -- and on this computer.
What are the best practices for speeding up Aperture?
Thanks,
Steve
Message was edited by: films-so-last-year

Have you tried the Bergsma BAsh?
Many of us who have upgraded our library's over time have cleaned out caches using a technique discovered by Matthew Bergsma . It cleans out some obsolete files that significantly slow aperture 3 down.
Here's what you should do:
Quit aperture
Navigate to your aperture library.
Ctrl click library and select show package contents
Open the thumbnails folder and drag contents to trash.
Then delete the entire contents of the following cache folders:
Hard Drive/Library/Caches
Hard Drive/System/Library/Caches
Hard Drive/Users/Your username/Library/Caches
You may also like to delete the preferences file but that's up to you.
~/Preferences/Library/com.apple.aperture.plist
Open Aperture:
Rebuild Thumbnails click library - photos
Then select one photo and apple(command) A to select all.
Then go to the photo menu and choose generate thumbnails.
It'll take a while to go through them all but once it's all done Aperture 3 should zip along
You can read Matthew's original post:
here http://discussions.apple.com/thread.jspa?threadID=2359859&start=0&tstart=0
Hope this is of help!
M.

Too late to start up with Aperture?

I'm aware of both Aperture and iPhoto being trashed by Apple in the near future. I have been using iPhoto on my MacBook Pro since it was introduced and usually do some additional editing as required using Adobe Photoshop Elements. But now I'm starting to shoot in RAW, and iPhoto won't even take RAW files into it's library without converting them to Jpegs. I think the best bet for me would be to upgrade to Aerture but I also know it's no longer going to be supported. In fact, I've read that Apple is no longer interested in the entire advanced enthusiast and pro photography spaces. Thoughts and advice for me? I have been spoiled by the wonderful Apple apps that work so nicely. By the way, I haven't upgraded to Yosemite, nor do I intend to. I think in my case it will take me in the wrong direction.

Reasons for migrating to Aperture of course depend upon your intended use. As pointed out here, development for Aperture has ceased. Apple has decided to migrate to another application, using cloud based back end for image storage. There has been more than one or two posts of disappointment on this course of action. In the end it's Apples decision however right or wrong the users believe that decision to be. Your best bet is to look at the features, determine if those are of use to you, scan the threads here for comments, then determine if the cost is worth it.
As opined Aperture probably has about a year of life left. After that you may be able to use it so long as you do not upgrade your operating system. But make no mistake - there will not be an Aperture 4.x. Nor, in my opinion will there be any significant (or heroic) efforts to fix what are now significant issues with Aperture.
The trade off, in my opinion is not worth it. Especially when you can get Lightroom now for a modest price. That is if you don't mind paying a monthly usage fee and really don't need facial recognition. The former being the pricing plan Adobe is moving to and the latter being completely absent from Lightroom. I don't know of any other viable professional package on the market right now. On the upside, Adobe products do support IPTC extended metadata which Apple never adopted. Understandable, it was an Adobe push - but the data stored is pretty nice. Mostly dealing with model and release information (and others, read the IPTC specs if you are interested) - if you deal with that kind of thing.
As for my experiences - Aperture use to be an incredible product. Especially with the introduction of Facial Recognition - which is now horribly broke. Here are some of my experiences.
FACES:
- Aperture now scans my entire photo library for new faces in every image every time the application fires up. This isn't a problem if you have a few hundred images. Once you start hitting about ten thousand (10,000) it becomes a nuisance. It takes about 45 seconds. Multiply that time out based on your library size.
- Aperture now rescans every identified face for a match, every time you identify a new face. Ok, I get this process. You have marked this guy as John Smith, now we are going to look for possible matches for John Smith. The only problem is that it appears to being in every face which it cannot justify as someone else.
- Aperture often double tags a face. To explain this you have to understand what the software is (probably) doing and how it records facial locations. First it applies some order of facial recognition. It looks for things which appear to be faces. Eyes, nose, mouth. It then draws a box around that area. You have the option to select that boxed area and in the upper left hand corner click on the "x" to close the box. Except when two boxes are exactly on top of each other. It's maddening. You cannot get rid of either box. Nor, can you identify the name of the person in both iterations of the box. If you understand all the places where you can name people (every software package has multiple places to do the same task) then you can select one of the boxes and tell Aperture that this area "is not a face". But since you are now telling the AI that the information contained within the defined area is not a face (when in fact it is) you are setting yourself up for a real HAL9000 moment. And if you don't get that reference, you are simply confusing the system. Especially when you leave box 2 in place and give that person a name. So is it a face or isn't it? Aperture appears to be using both decisions (is and isn't a face) in future iterations of facial identification (finding faces in an image) and facial recognition (is this face Johnny Smith or Jane Smith).
PLACES:
- A number of folks have reported problems with the geolocation of images. With the upgrade to the latest OS I have also begun to experience this problem. Images which I shot in my home studio were correctly mapped within a few feet of my home. With Aperture 3.6 many of them are not even on the same block. I actually have photographs which were previously (properly) mapped in central Maryland, that with the 3.6 upgrade are now tagged in the middle of the Pacific Ocean. Yes you can manually move them to their correct location - but again, thats great with a few hundred images. Thousands becomes a real nightmare.
This same geomapping problem has reared its head in faces as well with some users reporting the placement of the facial identification box in the wrong location on the image. Far be it from me to disparage software developers but it's almost as if the crew forgot that the image coordinates (whether for dropping a box on a photo or a pin on a map) start at 0,0 being the upper left corner of the display. /snark
STORAGE:
- A couple "upgrades" back Aperture migrated a reasonable and easily understandable storage methodology in which photos were filed (on your hard disk) in a directory architecture based on the date/time of image. So, if something horrible happened a savvy user could open the Aperture package, navigate through the directory and recover lost or damaged data. Not anymore. I defy anyone to explain the system now. It appears to have something to do with the ingest date, solar or lunar cycle and a hashed algorithm of some programmers mothers birthdate which is then translated into an XML filename. All that to say - good luck finding your photo IF you need to AND you are storing images internal to the Aperture database. But lets get serious about filing images under a directory system based on import date/time. This is great - if you import your photos on the date of the shoot. But, if you go on a two week trip of Europe and ingest all your photos the day you get home, well that's not too bad. A year later when you have to recover all your photos from a significant system failure and end up ingesting 10,000 photos on 15 May 2014 that is another story entirely. Now, good luck finding your photos on the hard disk (if you need to that is).
SECURITY:
- Apple applied the "sandbox" theory to image security. Basically in a nutshell all your photos are locked from editing by only approved applications. So don't even think you are going to download some awesome script to do some wonderful task and have it work. Sorry. It took me months of phone calls with apple support before one of those on the line even thought to walk me through my editing process and determined the script/app I was using was not apple approved and this was causing my problem. I get it, new risks in computer data and all. But there comes a point when you have taken security so far as to lock the user out of the loop.
CRASHES:
- We all have them, and they all happen at the worst possible moments. In the past 2 days I have been working in Aperture with my data and experience Aperture crashes about every 45 minutes or so. Yes, I have repaired my permissions, yes I have repaired the database and Yes I have rebuilt the database. It just appears to be another nuisance of Aperture that wasn't there a couple years ago. I have even gone so far as to completely uninstall Aperture, reload it from scratch and re-ingest all my images (that is how I discovered the whole ingest date/time versus shoot date/time storage della described above). My entire library now (in the Aperture Package) falls under a single year (2014) when previously it was spread across 40 years (from the 70's to current date). Yes, I have images from the 70's in aperture. I scanned a lot of film over the years. Regardless, I could never track down exactly why the crashes were happening. Some feedback from Apple would be nice - I have after all must have sent them a few hundred crash reports by now. My RAM is good (yup, I have tested it), drive space is fine and I have plenty of it so ..... Im left scratching my head.
Aside from all of that - I loved Aperture, while it lasted. I will be saddened by it's loss and to date I haven't heard anything yet which gives me hope about Photos. As someone who is occasionally paid, and who occasionally pays to shoot (read into that what you will) I refuse to store my image library on anyone else cloud. I have my own storage architecture which has worked fine for me. I haven't lost an image now in the many many years I have been using it. If you shoot a lot I recommend you look into Drobo. I was an early adopter and have never looked back. I have two 16TB units on my desk - one for live data, one for TimeMachine.
Cloud storage is simply too risky.
1. You are reliant on too many factors which are (a) out of your control and (b) are run by people who really don't care about your data or your business. Not to mention the constant finger pointing. If a switch goes out somewhere in Nebraska I hope you had a local copy of your data because now you can't work. But then again, that defeats the whole purpose of cloud storage doesn't it? How many Apple users signed up and put up web pages in what is now the cloud? You remember those days? You data is your data and will always be there? Until we change our ToS and now longer support personal websites.
2. Pricing. Seriously look at the pricing. The cloud tops out at 1TB for $20/month. Not bad. What do I do with the other 15TB of data I have? Oh, and after 3 months I could have purchased a Western Digital portable USB 1TB. If Moore was right (and so far he has been pretty close) that 1TB next year will only cost me $30 at the local Best Buy. If you can find it. You know 6TB drives come out this fall? Only a couple hundred dollars each. About 1 years payments on the cloud. Now I realize I might get slammed there - not everyone has $60 extra dollars for a portable 1TB drive. But I am assuming you do since you are tinkling about spending $70 for an app which is only viable for another year.
3. Cloud storage really? I don't know about you but the last time I ran an all day shoot I used up about 128GB of card space which took me a couple hours of transfer time (card to local disk). Now, how long would it take me to run that up to the cloud before I can use it. And that was on an older camera which was half the megapixels of what I am shooting now. So, 1/4 of my storage maximum being transferred up to the cloud after only one shoot. Awesome. Ill get a coffee, take a road trip, and in a couple days my images will be ready for first draft editing. Meanwhile my client will be ..... strumming his fingers? Don't worry though sir - a couple more days and your proofs will be available online. For everyone with any mad skillz to hack into. The only secure computer is one not online.
So, there are the down sides from my perspective. Yup, it's one sided. If you want to know the good stuff (and there is a lot of good stuff) just read the sales brochures. It's fine product - so long as you understand the limitations. And overall I am happy with it. And I will, again, be saddened when it leaves the market.
Aperture's days are numbered. I am past denial and isolation. I guess this places me in the anger stage. There is no use in bargaining. It is Apples decision and they have made it. Depression is next. I doubt I will make it to acceptance - unless there are some significant changes to Photos and I don't see that in the works. Apple appears to be dropping their professional line of products and pushing to the general market.

TIFF export date issue with 40D images

Hi.
I have a strange issue with Aperture 1.5.6, Leopard 10.5 and Canon 40D RAW images.
The problem is this:
1) Import a 40D RAW image in aperture.
2) The exif image date is 13.11.07 20:21:10.
3) Then edit the image in Adobe Photoshop CS3 (TIFF).
4) Now we have two version of the image: the original RAW file and a TIFF file.
5) Export the two images with aperture to JPEG files.
Now the exif date/time of the image exported (RAW) is 13.11.07 20:21:10 and that's correct.
The problem is that the time of the second image (TIFF) has exactly two more hour ( 13.11.07 22:21:10 ).
In aperture the date/time is correct for both the images.
Someone can please try to replicate this issue?

Thanks for your reply.
1. I select the photos from iPhoto - varied between 5 and 20 (ran different test)
2. Click on FILE
3. Select EXPORT
4. Under the FILE EXPORT tab I have tried all the various options with no success
5. KIND - I make sure they are JPEG files - I have tried the Original also which is actually JPEG files
6. JPEG QUALITY - I have tried all 4 options from LOW to MAX
7. SIZE - I tried all 4 size options from SMALL to FULL
8. FILE NAME - I use filename
9. Select EXPORT tab
10. I export to the thumbdrive and I chcek and they are on the thumbdrive
11. I also tried to EXPORT to the desktop and copy them to the thumbdrive
I click on the photos on the exported images I placed on the thumb drive and they come up fine on PREVIEW on my MAC. No prroblem with the images until I try to use them on the plasma. I go back and use images from iPhoto 06 that I did not call up with the "08" program and they work fine.
Hope that explains what I do. Thanks again

Playback Issues with multiple framerates and Blackmagic Decklink 4K Extreme

I recently swapped by AJA Kona Card for a Blackmagic Decklink 4K Extreme in order to get external monitoring in DaVinci Resolve.
I'm working in a 1080p 23.976 project that includes some 29.97 SD and HD footage. When loading this 29.97fps footage into my source footage, I periodically encounter frozen playback (The play triangle in my toolbar becomes a square symbol and remains that way). From there I am unable to playback any footage in any timeline, and requires a full system shutdown to return to normal! The problem is seemingly intermitent, with successful playback happening sometimes.
The 29.97 footage was DVCPRO, I attempted to transcode to Prores to troubleshoot. No dice. I believe it to be an issue related to the Decklink's inability to handle multiple framerates on-the-fly but wanted to submit here, too. I've also experienced intermittent sync delays on my broadcast monitor.
Decklink Driver 10.0
Premiere CC 7.2.1
Mac OSX 10.9.2 (same problem pre-mavericks)

Hi Andy,
You should not have any issues with Blackmagic handling multiple formats on the fly. However, I believe the frozen playback issues your describing is related to the Desktop Video 10 driver. I suggest rolling back to 9.3.3 for the time being. Blackmagic is looking into this issue now.
Best,
Peter Garaway
Adobe
Premiere Pro

Photo file issues with iWeb and Aperture....also too much duplicating!!

A little background, before I get into my iWeb issue.....
Years ago I tried iPhoto, but I didn't like how it duplicated all my photo files and I wasn't very fond of the file structure it created. Years later (last month) I got Aperture. Aperture (still has a long way to go) also duplicates all your files and places them in their own file structure. If I can get along with Aperture (and if it will get along with my other programs), I won't mind putting all my files into the file structure it creates. But for now, I still have my original files in the original file structure I have had for many years as a back up.
On to my issue with iWeb and Aperture....
To add photos to iWeb, you can either go into the iWeb media center or you can drag and drop photos from other locations.
1st: iWeb media center
To get my photos into the media center, I would have to load them into iPhoto (iP 6 does allow you to keep your original file structure, but it still creates .jpg files, which fills up your hard-drive. More duplicates I don't need or want). So that is out for me. iP6 will let you view and use your Raw files.
Another way is to drag and drop your file structure directly into the media center window. I don't think this duplicates any files (at least I haven't been able to find any), but it takes an awfully long time to thumbnail all your photos (several hours and still waiting for 22K + files). Also, it won't show any Raw files. Again, out for me.
Aperture won't let you drag and drop its library into the media center at all. So if I was to move all my files into the Aperture Library, I wouldn't be able to access them for iWeb at all.....Out for me.
2nd: Drag and Drop
I was able to drag and drop Raw files directly into iWeb from C1 Pro, Adobe Bridge and Adobe Lightroom.
As I said before, I am trying to move over to Aperture. However, Aperture won't let me drag and drop photos. What is the deal here??? These are both Apple programs and they won't play nice with each other. Very annoying.
Anyway, I put a link below to my iWeb test webpage I made. All the photos were Raw files that I did a drag and drop from C1 Pro, Adobe Bridge and Lightroom. There were no problems with the publishing.
http://web.mac.com/phil_navarro/iWeb/Site%202/Drag%20and%20Drop%20test.html
So, does anyone know if they can get photos from Aperture to work?? Thanks for any responses.
Phil
G5 Desktop Mac OS X (10.4.4)

Jedi,
Perhaps you are right.
I am not a web developer and I will never be. I don't feel like spending countless hours learning how to use Dreamweaver or some other Pro web app. iWeb looked like a way to start making websites of my photos for my friends and family (much easier and better than Home Page on .Mac). All I was asking was for a way to drag and drop my photos (especially Raw files) with Aperture. Which I can do with Lightroom, Adobe Bridge and C1 Pro, and without using iPhoto.
I am not a Pro photographer either, but I purchased Aperture based on what was advertised on the Apple website. From that ad, Aperture fit my photo needs almost to a tee. I am looking to adjust Raw files, Crop, Archive and keep my use of Hard Disk space down to a minimum. I can use Photoshop for the other 5% of things I do. However, Aperture has some issues (if you own it, then you already know. If you don't, you can read the Aperture Forum) This is one of the reasons I never went to iPhoto for archiving. I didn't like the way it duplicated all my files, taking up more disk space and its file structure. So even though Aperture won't play nice with other programs, I was surprised that it wouldn't play nice with any Apple programs.
After reading your post and based on what you are saying, everyone either needs to have/learn/use Pro apps only or have/learn/use iApps only. Don't Cross the Streams!!
I guess that means Apple will need to fix DVD Studio Pro. It uses photos that are in your iPhoto library and music from iTunes (iApps in a Pro app??....for shame...."it was never intended"). Also, DVD SP won't read the Aperture library. Does that mean there are 3 platforms? Pro, iApp and Mediocre??
Now I have 2 questions:
1. Can someone please tell me which apps are Pro and iApp, or if there is Mediocre? I don't want to mix them up and "Cross the Streams".
2. Again....is there anyway to use Aperture with iWeb?
TIA,
Narvon

Decklink issue with Aperture

Similar Messages

Maybe you are looking for