I am not impressed... so far...
Greetings!
I installed P1 C1 4 on both my desktop (Micron with XP Pro SP2) and laptop (Toshiba with XP Pro SP2).
1) My major problem is that C1 4 causes a memory access violation (crash) every time I attempt to process a DNG image. It appears that it doesn't matter whether I actually make any alterations or what output format I use (I tried both TIFF and JPEG). Every time I hit process, the progress bar gets to 100% and then I get a message box telling me that ImageCoreProcess.exe has crashed due to invalid memory read access. This appears to be 100% reproducible on both my laptop and desktop. This is pretty BAD as far as QC is concerned. Has anyone else experienced this issue?
2) Two other things that I find extremely annoying (these have already been mentioned in earlier posts) are:
a) inability to access the curve control when I am running at my preferred resolution -- this is a huge usability issue as far as I am concerned, and
b) the fact that C1 creates cache folders in every single folder I happen to have RAW files -- another terrible usability issue.
PhaseOne, how about addressing these issues?
-Gene
I installed P1 C1 4 on both my desktop (Micron with XP Pro SP2) and laptop (Toshiba with XP Pro SP2).
1) My major problem is that C1 4 causes a memory access violation (crash) every time I attempt to process a DNG image. It appears that it doesn't matter whether I actually make any alterations or what output format I use (I tried both TIFF and JPEG). Every time I hit process, the progress bar gets to 100% and then I get a message box telling me that ImageCoreProcess.exe has crashed due to invalid memory read access. This appears to be 100% reproducible on both my laptop and desktop. This is pretty BAD as far as QC is concerned. Has anyone else experienced this issue?
2) Two other things that I find extremely annoying (these have already been mentioned in earlier posts) are:
a) inability to access the curve control when I am running at my preferred resolution -- this is a huge usability issue as far as I am concerned, and
b) the fact that C1 creates cache folders in every single folder I happen to have RAW files -- another terrible usability issue.
PhaseOne, how about addressing these issues?
-Gene
0
-
[quote="berg" wrote:
Greetings!
I installed P1 C1 4 on both my desktop (Micron with XP Pro SP2) and laptop (Toshiba with XP Pro SP2).
1) My major problem is that C1 4 causes a memory access violation (crash) every time I attempt to process a DNG image. It appears that it doesn't matter whether I actually make any alterations or what output format I use (I tried both TIFF and JPEG). Every time I hit process, the progress bar gets to 100% and then I get a message box telling me that ImageCoreProcess.exe has crashed due to invalid memory read access. This appears to be 100% reproducible on both my laptop and desktop. This is pretty BAD as far as QC is concerned. Has anyone else experienced this issue?
2) Two other things that I find extremely annoying (these have already been mentioned in earlier posts) are:
a) inability to access the curve control when I am running at my preferred resolution -- this is a huge usability issue as far as I am concerned, and
b) the fact that C1 creates cache folders in every single folder I happen to have RAW files -- another terrible usability issue.
PhaseOne, how about addressing these issues?
-Gene
We've been talking about these things for months and PO hasn't done
anything. If they didn't make any improvements within two betas and
the final release, what makes you think the next update will be any
better?
Rob0 -
[quote="Robert Hoffman" wrote:
We've been talking about these things for months and PO hasn't done
anything. If they didn't make any improvements within two betas and
the final release, what makes you think the next update will be any
better?
Rob
As far as the 2 usability issues are concerned, I agree that it is most likely wishful thinking. However, the 1st issue is a critical bug. It renders the product completely unusable (at least for me) since I cannot convert DNG files to any printable format. I do hope that P1 will fix this.
That said, has anyone else on this forum had a similar experience with DNG files?
-Gene0 -
Gene,
1) Bug verification and response to problems can only occur via a Support Case:
Technical Support Site: http://support.phaseone.com
Include all details, and file attached and it can be tested. If Bug is confirmed, then all the Case History notes and information is logged to R&D and helps them determine a fix.
Release Notes: Known Issues at time of shipping:
Currently DNG read and write is not supported for Fuji S5,S3,S2 Pro, Nikon D1X or sRAW files from Canon cameras.
a) Release Notes: Known Issues at time of shipping:
At the lowest recommended screen resolution you have to hide the Toolbar to get full access to the Curve tool.
b) the Capture One cache folder is only created within folders you have selected with the program. Don't select = no folder added.
Typically, the Known Issues remain priority to be resolved by Developers with the next update.
* Happy Holidays * K C0 -
[quote="Keith Carpenter" wrote:
b) the Capture One cache folder is only created within folders you have selected with the program. Don't select = no folder added.
K C
Keith,
What kind of answer is this? To process RAW images I have to select the folder!!! Therefore every folder with RAW images (that I process) is littered with these cache files. No matter how you slice it, it’s a horrible “feature†regardless if the Mac version has always down this and nobody’s complained.
More importantly there’s a simple and obvious solution that almost all other image processing software provides and it’s called CHOICE. It’s such a simple thing to code. Give us the choice to add cache files to the image folder or a scratch folder location. That along with the Develops folder which is basically the same issue in reverse.
Honestly, of all the things that have changed these two issues are the primary reason why I’m looking for a new converter and they are the simplest things to fix/add in the code. I know I’m not alone and it’s a shame that you development team is either to lazy to sunburn or just plain blind that they’d leave out a few lines of code at the expense of you user base.
Rob0 -
[quote="rkircher" wrote:
Honestly, of all the things that have changed these two issues are the primary reason why I’m looking for a new converter and they are the simplest things to fix/add in the code. I know I’m not alone and it’s a shame that you development team is either to lazy to sunburn or just plain blind that they’d leave out a few lines of code at the expense of you user base.
Rob
Rob, that is what really mystifies me out of all of this. The 2 most common complaints, i.e. the ones you mentioned, would seem to be trivial to incorporate.
It's not that any of us are slating the quality of the conversions or anything major.
Instead of losing a number of users, why don't they just say, 'OK guys, we'll put these very simple requests into the next dot version'?
A total mystery!0 -
[quote="imacken" wrote:
[quote="rkircher" wrote:
Honestly, of all the things that have changed these two issues are the primary reason why I’m looking for a new converter and they are the simplest things to fix/add in the code. I know I’m not alone and it’s a shame that you development team is either to lazy to sunburn or just plain blind that they’d leave out a few lines of code at the expense of you user base.
Rob
Rob, that is what really mystifies me out of all of this. The 2 most common complaints, i.e. the ones you mentioned, would seem to be trivial to incorporate.
It's not that any of us are slating the quality of the conversions or anything major.
Instead of losing a number of users, why don't they just say, 'OK guys, we'll put these very simple requests into the next dot version'?
A total mystery!
The only viable answers considering the refusal to comment from PO, is arrogance on the part of the development group who doesn’t understand their users, or features held back for the Pro version. Or even a mix of both. I’m leaning towards feature held back for the Pro version. Note that all the features that have been removed directly impact the productivity of the software; productivity features that IMHO would have to be part of a Pro version for it to even be considered professional level software.
As to simplicity, basically, it requires code to support a couple of added dialog controls, code for writing the setting to the registry, and code to retrieve the settings from the registry. All very basic code snippets that are commonly used just about all software out there. And come to think of it the same simplicity is involved with bringing back many of the preferences we used to have in 3x. If it were open source, a half skilled programmer could add the features back in about 10 – 15 minutes. I’d bet it actually take more time to locate the proper location in the base code then it would to actually write the code to support the features. In any event almost all the features could be added back into well structured code within a couple of days and then add about 3-5 for testing and we could have a .1 release in about a week to 10 days (ok I’ll give you 3 weeks to a month for proper QA and regression testing.) A release that would go a long way to making everyone very happy.
Rob0 -
Hi Keith,
Thanks for your responses. Please, see below.[quote="Keith Carpenter" wrote:
Gene,
1) Bug verification and response to problems can only occur via a Support Case:
Technical Support Site: http://support.phaseone.com
...
Release Notes: Known Issues at time of shipping:
Currently DNG read and write is not supported for Fuji S5,S3,S2 Pro, Nikon D1X or sRAW files from Canon cameras.
Already done as of Friday. I submitted case # 38472 through the support web site. Since this issue is a show stopper for me I would really appreciate a reasonable turnaround on this.[quote="Keith Carpenter" wrote:
a) Release Notes: Known Issues at time of shipping:
At the lowest recommended screen resolution you have to hide the Toolbar to get full access to the Curve tool.
b) the Capture One cache folder is only created within folders you have selected with the program. Don't select = no folder added.
Typically, the Known Issues remain priority to be resolved by Developers with the next update.
I think that both of these problems make the tool significantly less usable. I am looking forward to them being addressed in the next update.
Re: A), I understand that I need to change my screen resolution but is not acceptable to me because there are many other things that I happen to do on my computers other than running CaptureOne that require a high resolution and it is a pain to change it back and forth. I am sure that other people on this forum would agree.
Re: B), I don't understand your point. Folder selection is a pre-requisite for Raw File Selection in the Library Tool in C1, is it not? I think that it would have been much better if the cache folder were configurable just as the MoveTo and Output folders are. Again, judging from previous posts on this forum, I am sure that many other folks would agree with this.
-Gene0 -
I got my answer from support for the Samsung DNG RAW files not being processed:
http://forum.phaseone.com/viewtopic.php?t=49240 -
[quote="rkircher" wrote:
More importantly there’s a simple and obvious solution that almost all other image processing software provides and it’s called CHOICE. It’s such a simple thing to code. Give us the choice to add cache files to the image folder or a scratch folder location. That along with the Develops folder which is basically the same issue in reverse.
I agree that users should have the choice about where to put the cache files.
However, I can offer an argument in defense of the current implementation:
By putting C1 cache files and settings files within the active directory, the archiving process is simplified--assuming that you want to archive C1 data along with your original RAW files. If I stick with v4 (they need to improve the UI first though), I'll archive everything together.
If you have a huge batch of files, say 1000 in a single directory (probably a bad idea regardless, but hey, to each his own), if you ever wanted go back in there, C1 would have to re-create all the cache files (assuming enough time has gone by and the cache has been cleaned out). Obviously this would take time.
If you archive both the cache files and the settings files with your RAWs, C1 can immediately get up and running weeks/months/years later.
The cache files seem small enough that I don't mind archiving them along with my original RAWs so I do like this change from v3.x.
Are most people agreed though that automatically storing the settings files with the images is a good thing? That's about the only UI/behavior change that I like in v4.
I can understand though that many people will want more control over the cache files. They definitely should give users the option to change this behavior.0 -
I got the following response from P1 support and it seems to work fine for me:
"You need to apply a camera profile to your DNG files. If you go to the quick tool (first one after the folder navigation window pane) you can select either Pentax K10D Generic, Phase One No color Correction, or Adobe DNG File Neutral. One the file has an input ICC Prolfile connected to it, you should be able to process it."
Cheers,
-Gene0 -
It works !!!! Amazing 😂
Tnxs for the tip !!!0 -
It works here too. Thanks Gene /berg. I was able to help someone else in the CO4 Mac forum with the same problem. 0 -
My pleasure! I am glad this helped.
This resolved the major problem that I had with the tool.
Now, we will have to see what P1 will do about the other usability issues that I raised in my original post.
1. I understand that some folks prefer to have cached files in the same directory as the edited files. My preferance would be for C1 to make this optional. In other words, I would suggest the following implementation of the feature that would be flexible and would satisfy both "camps" 😉
C1 provides a global setting that identifies the location of the cache folder. If this setting is not set (the location is not identified), the cached images are stored in the same directory as the edited files. Otherwise, the cached images are stored in the specified folder. Just my $.02.
2. As far as inability to use Curves tool at the resolution of my setting... Well... It is a very poor UI design choice and should hopefully get fixed.
Cheers,
-Gene0 -
I would be marginally happy with a clear cache on exit option. 😉
Gene,
Just for my curiosity what is your screen resolution?0 -
[quote="SteveCa" wrote:
IGene,
Just for my curiosity what is your screen resolution?
On my laptop it is 1280x800.
-Gene0
Post ist für Kommentare geschlossen.
Kommentare
15 Kommentare