Jump to content

Robert Bailey

  • Content Count

  • Joined

  • Last visited

Everything posted by Robert Bailey

  1. Irritating indeed, by all means keep the one that failed to remind you. But the others haven't failed they just haven't been checked. By the way, in a post about QC a while ago you suggested a Fuji X camera. Whilst I didn't buy it to keep Alamy happy I did get an X100 (first model, no suffix) and am very impressed. Even jpegs strait out of the camera are good.
  2. I appreciate the I can leave them but they are irritating me. I would like to delete them.
  3. I have just had one fail out of 39. They are all taken using the same lens which has had failures before. I don't want them hanging around but cant find a way to delete them. How do I delete them. Thanks
  4. There is a PDF which has full instructions on the discoverability issue. It explains it all. The above quote in bold blue is taken from it. http://www.alamy.com/myupload/help/AIM-InstructionManual.pdf#page=16
  5. For the benefit of all those who have given advice I am uploading another batch. Let's see how we get on this time
  6. Thank you to the original poster for this information. I have downloaded and installed to both PC and Mac. I'd be interested to know if anyone has had QC problems after using any of the Nik Collection.
  7. Hi I'd like to restart this one. Suppose I have a property release but the owner of the property doesn't want the number shown. I'd have no problem in removing the number but would it casue any problems with Alamy. Robert
  8. Hi All Just for the record I thought I would let you know that all of my second batch of pictures failed QC also for soft or lacking definition (same as last time). I followed most of the relavent advice given here and spent one hell of a long time on it. The bottom line for me is that it isn't worth the time spent on fideling around to get a few pictures on here. I enjoy my photography and I enjoy making pictures that others like, I think I'll leave it at that. Thanks again for all your help. Robert
  9. You didn't put me off David, I was just having a bit of fun. I did have a look at some scans of slides I took with my Pentax MX a few years ago and the quality is truly awful. So maybe this digital stuff isnt that bad ;-) Indeed since reading this thread and the help that has been offered I have been very selective about the RAW files used and done a minimum of processing and the results, at least to me, are a great improvement. Thanks again. Robert
  10. Thank you David, that is a very comprehensive reply. I've taken what you say on board, and it makes sense. But if this "simple" digital photography gets any more complicated I think I may go back to my Pentax M kit and scan the films :-) I use Flickr to choose the shots, that's all. Regards and thanks. Robert
  11. Thank you Michael, your help has been encouraging, supportive and constructive, it's appreciated. I'll take it from here and perhaps post to a new thread when I have moved it on. Thanks again. Robert
  12. I have now exported this file to JPG at level 12. The file size is now 15Mb https://app.box.com/s/sw8atercf1g5cm1spwiiv5aegrz74o49 Robert
  13. As you have only tweaked the CA, have you uploaded these as an example of how you are saving them (as per your chat with Mark/spacecade re size? Are these as you would upload? Without going too much further my first observation on download is how small the JPG is (3.3mb). That is way too small for an image which is over 5000 on it's longest. I opened your TIFF in PS and saved as a Level 12 JPG. That gave me a 9mb JPG. I then did the same with the TIFF but at Level 10 JPG. That gave me a 3.5mb JPG. That 6mb difference is missing pixels which is all image detail! I only tweaked the CA but after posting I noted that Aperture had added some sharpening. I have uploaded these with as little manipulation as possible to estabish a baseline with regard to getting my pictures through QA. They failed at my first attempt due to SaLD. I found the following on an Apple Aperture forum with regard to Alamy and used that: Create a new export preset JPEG - image quality 10 or 11 Color space Adobe RGB (1998) Size fit within pixels 5200 300 DPI you will get uncompressed size about 51MB, but JPEG's will be 3-20MB size as they are compressed I noted the small file size and tried both 10 and 11; the difference was 0.3Mb When I next have the Mac running I will try 12. Robert
  14. As promised here is a revised JPEG and an 8 bit TIFF for comparison. The only thing I did was tweak the colour aberation. Robert JPEG: https://app.box.com/s/cdihw1nmv4tkqtz5owcnbcgbj9jots42 TIFF: https://app.box.com/s/q114myezwg6d1juy73smjvdsc0vizopc
  15. Thank you Brian, the idea of using the Canon software is a good one that I hadn't though of. However I am not too keen on Adobe products so I will continue with Aperture for a while as it's bought and paid for. I have looked at Capture One Pro which could be a possibility in the future. Robert
  16. Perhaps I should have another go and ask here before sending to Alamy as I want to avoid another failure. That's a great idea! Then that I will do!
  17. The thumbnail should be clickable and link to my Photobucket page. You should be able to get the full size file from there. Let me know if it doesn't work! The options button doesn't include download. Thanks Mark. Try this: https://www.dropbox.com/s/w9szdica47zbtqs/IMG_1092%20Edited.jpg?dl=0 Wow! That's a totally different picture. Thank you! Seems I need to get to grips with Aperture and if that fails look at something else. Robert
  18. Hi Mark Yes they are RAW+JPG from the same exposure. But my Alamy submission as a JPG did not come from the RAW file it came from the JPG produced by the camera. I'll clarify. The picture was shot RAW+JPG with the camera set to highest quality for the JPG. The RAW was filed and took no further part in the process. The JPG (produced by the camera) was loaded into Aperture and tweaked (including, I agree, the awful colour change). It was then "Exported" to JPG from Aperture with the default setting and sent to Alamy. Thanks to all for helping me out. Perhaps I should have another go and ask here before sending to Alamy as I want to avoid another failure. Regards Robert
  19. Thanks for your feedback. Just to clarify the JPG is not from a processed RAW, it's the JPG that came off the camera and then processed (minimally) in Aperture. As I said in an earlier post, that was a mistake. From days gone by I seem to remember that Alamay wanted files with minimum processing including cropping and NO sharpening, that is why this particular picture isn't cropped. Has that changed? Regards Robert
  20. Michael That is a very kind offer, thank you. I would appreciate it. By all means post it here. Thanks Robert
  21. Hi Everyone ...and thanks for your time. I have put my Alamy submission and the coresponding RAW file on Box. JPG: https://app.box.com/s/qhczutfmxrc5jsniwpwvmk11ln2pa1ik RAW: https://app.box.com/s/im3m9ht09cj9x4rbgrjocx9mhyjqus5n Regards and Thanks Robert PS The shot is of the Chichester (West Sussex, UK) Guildhall taken from the old city wall with the Cathedral spire in the background. It was taken a couple of weeks ago.
  22. Thank you Marianne My intended process was to review the pictures on Flickr Magic View and then find my choice as RAW files from my local drives, but in the excitement of the moment it just didn't happen. I ended up using the JPG's and remember thinking "humm, perhaps that was not the best thing to do". But by then it was too late. I suspect that not using RAW and accepting Apertures defaults may be the cause of my probem. These issues are in my control and could be rectified easliy. If however feedback suggested the problem is with my camera or lens then, well, goodbye Alamy! My post and request was about asking anyone who had better knowledge what the most likely step in my process would have caused the problem. Thanks again for all feedback and I will post one of the pictures soon. Regards Robert
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.