Library-related error message -- what does it mean?

MikeArst

• 11. Februar 2008 01:50

I opened CaptureOne v4 (not 4.0.1) for the sole purpose of ensuring that a few image files previously loaded into the processing queue would be retained between sessions. I immediately closed the program and heard the familiar Windows error beep. A dialog box containing the following message appeared:

Insert into user log failed, error: [Library used incorrectly
library routine called out of sequence]

Well, I have called no "library routine" that I am aware of from the user interface. Is this error message directed at the end-user or at some programmer, indicating a bug to be fixed? If it's to the end-user, what action is it recommending (or warning against)?

I re-opened the program and then closed it again. This time the error message did not appear. But why did it appear the first time? What had gone wrong?

0

• 

  MikeArst

  • 11. Februar 2008 01:59

  [quote="MikeArst" wrote:
  I opened CaptureOne v4 (not 4.0.1) for the sole purpose of ensuring that a few image files previously loaded into the processing queue would be retained between sessions.

  
  Well, this turned out to reveal an interesting flaw in the program design that I had not noticed before. I had purposely placed the queue into "stop" mode before I closed the program the first time. But when I re-opened it with files still in the queue (as described in the previous message), C1 -- without any query or warning -- began processing the images. At that point I had not yet selected the final output folder, nor the final output parameters; all images went into the wrong folder and were saved with the wrong parameters; and of course each time the image is processed, its icon disappears from the queue.
  
  I deleted the incorrectly saved images from that wrong location, then had to start over adding them to the queue.
  
  I'm sorry, but this is incredibly thoughtless program design, and I am about at the end of my tether. Does obtaining a version with a decent interface necessarily require waiting some months and then spending $500 on the 'pro' version? No, thank you.
  
  As frustrated as I have been, like other users, with certain flaws in the program, I have also been trying to give it the benefit of the doubt in many respects -- certainly in terms of the quality of the output. But user interfaces also matter -- A LOT -- and as I say, I'm reaching the end of my tether w.r.t. these serious design flaws.

  0

Post ist für Kommentare geschlossen.