|
admin
|
 |
« on: September 15, 2009, 03:44:00 PM » |
|
http://www.ddisoftware.com/qimagev2009.269 09/15/09 Priority: Med v2009.269 fixes the ability to load/save JPEG 2000 photos and improves color consistency when using ICC profiles. Mike
|
|
|
|
|
Logged
|
|
|
|
Alexander N
Newbie
Posts: 1
|
 |
« Reply #1 on: October 04, 2009, 05:15:31 PM » |
|
Dear Mike Chaney, I have read about Qimage on "The Luminous Landscape" and "Digital Outback Photo" and I was curious to know how good it meets my requirements and my workflow, that's why I have installed the demo of Qimage v2009.269 I'm saving images, which I have processed in Photoshop CS and which are ready to print for reasons of disk space as 16-bit Jpeg 2000 (jpf) files in Adobe RGB color space. Unfortunately these pictures aren't shown in the folder preview of Qimage. What might I'm doing wrong  ? Or could it be an incompatibility between jpf-files generated by Photoshop CS and Qimage? Yours sincerely Alexander |
|
|
|
|
Logged
|
|
|
|
|
Fred A
|
|
« Reply #2 on: October 04, 2009, 07:22:18 PM » |
|
print for reasons of disk space as 16-bit Jpeg 2000 (jpf) files in Adobe RGB color space.
Frankly I never heard of a JPF until your post. Did a little research and found a very interesting paragraph mentioning its use. It seems to be some file type that is barely recognized by many image editing apps. When CS uses/needs a plug in to save as a JPF or open a JPF, you can assume that is a token of recognition. The solution is simple. Save as something else...in JPEG 2000, you can save as a JP2, and Qimage will read that suffix as a JPG 2000. See quote from the article: (below) How do you use a .JPF file? Support for JPEG 2000 is growing, but editing is, as of this writing, only supported in top-of-the-line design applications like Photoshop CS or CS 2.0. But even Photoshop CS requires a plugin to open or save .JPF files. |
|
|
|
|
Logged
|
|
|
|
hedwards
Newbie
Posts: 29
|
|
« Reply #3 on: October 04, 2009, 11:51:31 PM » |
|
Jpeg 2000 was basically DOA, but it is nice to have support, I'm sure that there's a few niche applications where it's used. If it was going to be at all big it would've been somewhat mainstream by now. And I should point out that it's not the only designated replacement for JPEGs but it is the one with possible submarine patents on it. But that's neither here nor there.
The problem is most likely just a matter of the file extension, I'm not seeing it as one of the more or less approved extensions for the format and as Windows knows nothing of things like ELF and magic numbers that's where it gets its information about what a file is. I wouldn't surprise me if Qimage goes along with that sort of standard.
Any of the following ought to work: .jp2, .j2c, .jpc, .j2k, .jpx as they're sort of agreed upon albeit not totally.
|
|
|
|
|
Logged
|
|
|
|
|
Seth
|
|
« Reply #4 on: October 05, 2009, 01:33:22 AM » |
|
I have never seen it saved that way either. I would use JP2 if I used it; that is the general norm.
Unfortunately, if the camera manufacturers don't use it, it will probably fade away, although archives are using it. Kind of a hybrid (in simplistic terms) between jpeg and tiff.
|
|
|
|
|
Logged
|
Seth
<CWO4 (FMF) USN, Ret.>
|
|
|
lumacraft
Newbie
Posts: 5
|
|
« Reply #5 on: October 05, 2009, 09:02:59 PM » |
|
I have never had a problem with QImage before, but today I updated my studio edition from 2009.267 to 2009.269, and now every time that I go to the editor (Ctrl-E) to fine tune my crop, it crashes. I tried two very different image files, with the same result.
Can you advise?
The message on starting up again suggests checking that my Canon i9900 print driver is up to date; it is.
I am running on Vista Home Premium x64 SP2. Hardware is Intel Q8200 on Asus IPIBL-LB, with 8192 MB RAM.
David
|
|
|
|
|
Logged
|
David A. Gilmour LPPO
Lumacraft Photography
|
|
|
|
Fred A
|
|
« Reply #6 on: October 05, 2009, 10:25:38 PM » |
|
I updated my studio edition from 2009.267 to 2009.269, and now every time that I go to the editor (Ctrl-E) to fine tune my crop, it crashes As you can see from the link I pasted below, that there were no significant changes made to Qimage Studio that would affect your condition. What happens, if instead of using CTRL E, you right mouse click the thumbnail and select click on send to photo Editor? (Ctrl E could be a hot key set for something else too.) Also it would be a good idea to recheck the Editor setup and make sure that your selected path and application is correct. Would also help if you could define "crashes"? Can you determine if there is an attempt to access the editor? Any extra information might help. We have had times where an anti virus protection program was scrutinizing and invasively checking any file movement, and would spoil the transition. You might try disabling that part of any AV software. Fred http://www.ddisoftware.com/qimage/news.htm |
|
|
|
|
Logged
|
|
|
|
lumacraft
Newbie
Posts: 5
|
|
« Reply #7 on: October 06, 2009, 12:07:08 PM » |
|
Fred,
Right-clicking and choosing Full Page editor from the popup menu also causes the crash. So does clicking the "Full Page Editor" icon on the main screen.
You were correct that the path to my editor was not defined. I am not sure whether that was because I had never previously defined it, or might the link have been broken when I accepted the new location for settings which was offered when I installed this version? In any case, it made no difference with respect to this problem. After setting the path, the crash occurred just as before.
In terms of describing the application crash, it occurs immediately after selecting the full page editor. I get a pop up window headed "Microsoft Windows" that says: "QImage.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." Is there a log or other information that I can provide to better describe the crash?
If I "Disable active protection" in my antivirus application, which is Sunbelt Vipre, there is no change. The crash occurs as before. I am using the same AV app as I did when successfully using 2009.267; only the definition files have changed.
Is there something else that I can try?
Thanks for your help!
- David
|
|
|
|
|
Logged
|
David A. Gilmour LPPO
Lumacraft Photography
|
|
|
|
Fred A
|
|
« Reply #8 on: October 06, 2009, 12:20:08 PM » |
|
So does clicking the "Full Page Editor" icon on the main screen. David, Let's slow down for my sake. CTRL E is the keyboard set to get you to your photo Editor (like CS3 or CS4 or PSP) when you right click on thumbnails. If you have images in the queue and you right mouse click on those, then CTRL E will change to be the hot key to send you to the Full Page Editor in Qimage. So let's sort out when and how you get the error. Since you mentioned that you went from .267 to version .269, did you alter anything in terms of install folders or change locations of any part of the install? Fred. |
|
|
|
|
Logged
|
|
|
|
lumacraft
Newbie
Posts: 5
|
|
« Reply #9 on: October 06, 2009, 12:27:56 PM » |
|
Hi Fred,
Yes, to be clear, I am referring to a problem that occurs when accessing the full page editor that is built into QImage, for fine tuning my crop. Any of the three methods for accessing the function that I described will cause the crash.
Yes, I accepted the two suggested locations for the application files and settings when installing this version. Whether this altered the location for the settings I am not sure, but I expect so, since my understanding was that revising the location for the settings was a benefit provided by 2009.268. Would the installer have automatically moved my old settings to the new location that was suggested, or would is it necessary to manually recreate the settings in this case?
- Dave
|
|
|
|
|
Logged
|
David A. Gilmour LPPO
Lumacraft Photography
|
|
|
|
Fred A
|
|
« Reply #10 on: October 06, 2009, 12:48:03 PM » |
|
Not to my knowledge....
It is my understanding that the installer that Qimage uses remembers the previous install paths, and does not change anything.
The new migration routines were introduced in version .250 on May 8, 2009.
Nothing has been changed in that department.
How about an uninstall/reinstall?
Otherwise, we should wait for Mike to check in and advise...
Fred
|
|
|
|
|
Logged
|
|
|
|
lumacraft
Newbie
Posts: 5
|
|
« Reply #11 on: October 06, 2009, 02:49:47 PM » |
|
Fred, following your suggestion, I uninstalled, rebooted, and reinstalled. I'm still having the problem. I hope that Mike can help.
- David
|
|
|
|
|
Logged
|
David A. Gilmour LPPO
Lumacraft Photography
|
|
|
Peter_Corser
Newbie
Posts: 15
|
|
« Reply #12 on: October 06, 2009, 03:06:36 PM » |
|
Hi Fred
I wonder whether the .jpf designation is someone's (some company's) version of jfif (jpeg file interface format? - standardised jpegs which all current cameras use AFAIK) which should open happily as .jpg or .jpeg. AIUI the jfif does away with all (or most) of the variables which could be introduced into the .jpg and had to be written to the file on generation and decoded on decompressing.
Peter
|
|
|
|
|
Logged
|
|
|
|
|
Fred A
|
|
« Reply #13 on: October 06, 2009, 04:05:50 PM » |
|
Peter,
The bit of research that I did led me to understand that JPF was someone's customized JPEG 2000. JP2 and JPE are already recognized.
I have not found a reason to adopt JPF over the existing JP2 and JPE if you are working with the "lossless" JPG format.
Fred
|
|
|
|
|
Logged
|
|
|
|
|
Fred A
|
|
« Reply #14 on: October 06, 2009, 04:38:25 PM » |
|
Fred, following your suggestion, I uninstalled, rebooted, and reinstalled. I'm still having the problem Try this: Open Qimage. Click HELP, and then RESET all program settings. The only possibility left is that one of the INI files was corrupted. Doing the above will fix that. Fred |
|
|
|
|
Logged
|
|
|
|
|
Qimage registration expired? New lifetime licenses are only $59.99!
