mggm59

<p>Thanks, Dusseldorf is also closer to me, might even drive it there and see what they tell me (if they take this kind of jobs on the spot). I am thinking of opening it anyway, to see what happens, maybe there is some mechanical hitch I can solve</p>

<p>Lite update: tesi morning it scared two slides after restarting and then just stopped, after a few tens of seconds the scanner "quit" trying to scan (there was a sort of click) and the SW continued to try a bit and then saved the partial scan. I tried again and it stopped at the same point. this point is more or less at the same position where the stripes started in the scan above. </p>

<p>Thanks to all,<br> the problem appears after about 10-15 slides with the automatic feeder. It goes away after a rest (unpowered) of 10-15 minutes at least.<br> I am located in Europe, and Mr Ketzner recently had a big problem, he told me he'll not be around until mid September.<br> I have a USB scanner, not a FW, on a mac Pro.<br> Here is a bigger image.</p><div></div>

My scanner, after processing many tens of thousands of slides, produces from time to time partially scanned pictures where a part (smaller or larger at each time) where it just seems to repeat the last read row of pixels, thus producing a striped image. When the scan stops to be regular, the noise changes. <br />After some time I can restart and it works again. <a href="http://www.pentaxforums.com/forums/attachments/107-film-processing-scanning-darkroom/321973d1471505524-strange-coolscan-5000-behavior-image002.jpg">321973d1471505524-strange-coolscan-5000-behavior-image002.jpg</a> If I continue scanning, the scan is black on a side and part of the slide is regularly scanned, only shorter (but the slide is completely inserted) or has the same striped appearance. <a href="http://www.pentaxforums.com/forums/attachments/107-film-processing-scanning-darkroom/321974d1471505524-strange-coolscan-5000-behavior-image004.jpg">321974d1471505524-strange-coolscan-5000-behavior-image004.jpg</a> I must point out that the problem initially presented itself at longer time intervals, and it is becoming more and more frequent (I suspect this has something to do with heating of some component). <br /><br />Is this an HW problem? Anybody had it and can tell me what the problem was? How costly was the repair? Can it be done by a reasonably able DIYer?<br /><br />Thanks in advance<br />Maurizio

<p>Adobe is bringing everything to the cloud, they mentioned keeping Lightroom available as a package "for the foreseeable future" which for corporations is rarely longer than a development cycle or two. I hope to live and take pictures for longer than that.</p> <p>I don't trust Adobe anymore, the same way I don't Microsoft and am starting not to trust Apple, at least on pro SW (ask video professionals about Final Cut).</p> <p>If Adobe stops supporting the package at some point I would be in the same situation as today with Aperture, only having spent some more money on a dead end, not to mention the effort to learn it and move 136 687 pictures with their organization (not sure how the export tools will work, but I don't trust them either, migrations are a pain in the neck more often than not).<br> <br />Should I decide to start paying for CC and then I wish to stop, I have the images in my HD, true, but lose a lot of effort to archive them and the non-destructive edits, not to mention the hassle of exporting a few tens of thousands pics in TIFF (thus freezing all changes, so for instance if I want to apply some mods to another picture I have to do it all over again instead of just "lifting and stamping" them) and keeping these huge files along with the originals. Convenient, right? Call it drama, if you wish, or is there anything wrong in the above (I just tried the trial of Lightroom for a few weeks, so it might be)?</p> <p>Today the minimum for CC is 146€ per year (i.e. paying more than a copy of Lightroom package every single year), tomorrow? I know I am a cheapskate, but I am no longer making money on photography and I am used to buy my stuff and own it for many years. At my age I'm not going to change that, at least until there is the possibility to do it and I can avoid being shafted by the likes of Adobe.<br /><br />I'll keep Aperture (and the MacPro it's on) and wait for Photos for the time being. Or for a cheaper CS offer (something like half today's rates might convince me). </p>

<p>The problem with lightroom and the whole CS is the lifetime commitment to pay or lose access to your stuff. I just don't like this system. I like to own my stuff and do whatever I want with it. What if Adobe decides to raise the prices, and you're stuck with an investment of hundreds of thousands of hours of work? I am staying with aperture (which i pad 300€ and not 60 as it costs now) and see what Phots does. Hopefully someone else will come with some other solution, or I'll keep this Mac just for this version of Aperture.</p>

<p>I might have found the reason for these problems, at least on a Mac.<br> The bin file which is included in the zip file has the same name as other upgrades, so if you have one of more of these previous versions in your download destination, when the bin is extracted it gets a number attached to the end in order not to destroy the previous file, and therefore is no longer recognized by the camera.<br> That's why saving directly in the camera solves the issue, but it is enough to delete the added number and it works also when downloading to the computer</p>

Seem to remember it was the first Pentax Dslr to have it, only it could memorize only a few lenses

<p>Thanks to all<br> yes, I was doing this for have higher precision in focus confirmation and this worked on all previous models I owned (K10, K20, K5). The difference is that there you set a manual lens as a common value applying to all, except if it knew the lens, in which case it applied a specific value you defined for that lens.<br> Here it seems it does not have the possibility to store a value for manual lenses at all. Of course, if with previous cameras you put a correction for a lens and then used another, it might lead to gross errors, but having to set it every time is even more tedious, at least in the past you could note a value for each lens and dial it in when you changed lens, and then the value was applied to all shoots with that lens.<br> I am not that interested in using manuals, I am gradually selling them, but the 50 f1.4 is still the best lens in terms of resolution I own, and sometimes it comes in handy. Provided it is in focus, that is...</p> <p> </p>

<p>Yesterday I put myself to work on the tedious but fundamental job of searching the best focus point for all my lenses on the K3 and I found some surprises.<br> First, the Sima 10-20mm wanted quite different corrections at the two ends, i.e. +3 at 10mm et -10 at 20 (and possibly it needed more)<br> Second, the camera refuses to store the -8 value for the manual focus 50mm f1.4 A and goes back to 0 every time (but the correction seems to be there at least just after I set it, the differences in focus point are sensible). <br> Did anybody find similar issues? Any way around the problem for the MF lenses (I'll try with the 20mm f4 M as soon as I have time to see if the issue is common to all MF or just the 50.)</p>

<p>Good news on the subject.<br> Even though it is not mentioned in the list of new cameras whose support is added with the latest update (and I had fused Apple for this), I had the surprise to see that I could reprocess the K3 DNG files that were' previously recognized. I did not test the PEF files since I had none (I'll try when I have time).</p>