Fisherman's Friend

I really don't want a plugin folder full of phoning home Dlls. The idea of auto-update-plugins may be interesting, especially for the developer, but as a user I reject it. Besides the fact that it annoys me, it opens a new realm for bugs, freezes and crashes. I suggest to drop the update-idea and -system, and I also request other plugin authors to not adapt the idea. And as a side note, some pictures to show the effects in the first post would be nice and of use.

Would it be possible to change the plugin so that it doesn't discard all the metadata? The point here is: The best use for HD Photo is saving edited Digital Camera pictures. Paint.NET includes a lot of effects for improving the quality of your photos, especially via plugins. Now, if I edit my photos I don't want to loose any quality when saving them. With JPEG, I usually save it in a way that the filesize becomes larger than the original, and still I'm not sure wether I loose quality. With HD Photo, I think, you can keep the quaility and even reduce the filesize. Also, It has a lossless mode

I use this plugin a lot, usually with PNGs. Sadly, there seems to be a bug. Sometimes, directly after the file is saved, the entire apllication freezes. You can't do anything, even the "X" to close Paint.NET doesn't work. Clicking the Paint.NET window results in error sounds. I always have to close Paint.NET via the Task Manager. It happens frequently, but unforseen. There is no crash log, and I also failed to see a pattern in the behaviour. I really have no clue. My system is Vista SP2, x86 Intel. I use the most recent version of Paint.NET. I don't know wether the proplem is limited to me,

I assume you accidently deleted Tanel's plugin, which goes by that name. Link

May I suggest moving Polygonal Transparency to the "Object" submenu? I honestly see no use for a new submenu if it includes only one entry. The meaning of submenus should be to produce a clean user interface and to avoid an overcrowded one. We do not know if this submenu is "accepted" like Object, Tools and Color. Considering that general transparency effects rather go in "Adjustments" I see the possibility that half a year in the future this submenu will still feature only one single entry. Now that I mentioned this, I also think a "Transpareny" submenu may confuse the users. By compiling

It is my pleasure to confirm that the plugin seems to work properly now. At least I failed in reproducing the error shown above. Thanks for the quick fix. Just out of interest, did the old version of the plugin use the luminace or RGB based method?

Seconded. But the plugin has a major rendering issue. It happens apparently when you enlarge the image till it is shown larger than the Paint.NET window. As a consequence, the result does not replace the original, it is rendered inside the picture. Original: Plugin used in "window" picture size: Plugin used (same settings) with the picture larger than the window (in my example, I enlarged it to 100% - 1024x768 - with the window around 890x630, the following image shows the result zoomed out to display the effect): Users of Windows Vista and Windows 7 may restore the old plugin vers

Eerm... Not meant as any kind of flaming, but isn't this already "built" into Paint.NET? Just save the image with high JPEG compression... :shock:

I suggest that you provide some sample images for mosaic painting in your first post - like those flowers. That will help the users, as they can play around with your plugin and get an impression how it fits their needs. And indeed, this plugin looks amazing. Thanks!

I for one do. HD Photo is at the moment the best choice when saving your file in Paint.NET - as long as you are on Vista or Seven. Combining - and improving - all the advantages of JPEG and PNG, including rich metadata, alpha and lossless mode, HD Photo does the job. One of the few things I looked forward to when I got Vista. JPEG is fail. Without options like GIMP, it produces crappy results even on "100", it has been discussed and shown on this forum. I really don't get why I should spend hours and days on artwork and then save it as ruined file in a format which is actually out of date. O

~2500X1900 px, 150dpi.

I recently edited a bunch of digicam photos and encountered one memory error after another using this plugin. I have an x86 PC with 3 GB RAM and my pagefile can expand to at least 6 (?) GB. No other plugin caused problems, it was only this one, and it did it frequently and rather randomly. So I guess there's a mistake in the code. This is one of the exception logs Paint.NET showed when the plugin crashed: Datei: C:\Program Files\Paint.NET\Effects\IncreaseLocalContrast.dll Effektname: MeeSoft.Paint.Net.Plugins.IncreaseLocalContrast.EffectPlugin Vollständige Fehlermeldung: PaintDotN

Thanks. I'd also ask you to add the publishing date of the current version to your first post, like 2009/03/23, instead of just a version number like 1.0.1.1. It's pretty hard to say if something has changed if it's like 1.0.1.0 to 1.0.1.1. Especially imagine someone has holidays, comes back and cannot tell wether something has changed or not. If you see that the current version was published on, say 09/03/30, you won't have to guess.

I'm afraid there's a rendering bug. I used it on a 1280x8xx image and aftwerwards it looked like it was splited in parts and put together in a wrong way. Apparently it happens when your zoom is set to 100%. The bug was reproduceable, but sometimes you need to look closely.

Could anyone please write the correct string for the Photo submenu? I mean the localizeable version.