Rick Brewster

What can I say, if it ain't a BMW ... why bother? (2008 BMW 550i)

If you install a font while Paint.NET is still open, then you must restart it in order for it to 'detect' your new fonts.

It helps to have a 64-bit system with gobs of RAM when authoring something like that. I think the total layer count was 20 or 30 or something (most of it was for the brush).

Had a press-related inquiry for these, so I figured why not make them available for everyone. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 2.5 License. Permission is granted to use the logo and icon artwork in ways that discuss or promote Paint.NET (e.g. blog and news posts about Paint.NET, "Made with Paint.NET" watermarks or insets). Tiny (no alpha channel goodness): Small: Large (96dpi, 1550 x 389 pixels, 164KB) http://www.getpaint.net/images/pdn30logo_96dpi.png Huge (300dpi, 4844 x 1216 pixels, 1.01MB) http://www.getpaint.net/images/pdn30logo_300dpi.png Have fun. (No I will not publish the .PDN)

Yup. Look at last year's results when the Core 2 was fresh on the market, http://blogs.msdn.com/rickbrew/archive/ ... 64890.aspx

That's actually something we're hoping to make a lot simpler in a future release of Paint.NET. What we're seeing is that 99.9% of effect plugins just need to specify a few input parameters and are fine with having some default UI associated with them. I've actually been experimenting with some code for creating an HD Photo plugin. I've not had enough time to really bake it properly, but the notion of having a more declarative model for creating a configuration UI is proving to be a very good way to do things. For example, the following code defines the properties that configure the HD Photo codec, along with default, minimum, and maximum values for each: List properties = new List(); properties.Add(new ScalarProperty(PropertyNames.AlphaDataDiscardLevel, 1, 0, 4)); properties.Add(new ScalarProperty(PropertyNames.AlphaQualityLevel, 1, 0, 255)); properties.Add(new BooleanProperty(PropertyNames.CompressedDomainTranscode, true)); properties.Add(new BooleanProperty(PropertyNames.FlipHorizontal, false)); properties.Add(new BooleanProperty(PropertyNames.FlipVertical, false)); properties.Add(new BooleanProperty(PropertyNames.FrequencyOrder, true)); properties.Add(new ScalarProperty(PropertyNames.HorizontalTileSlices, 0, 0, 4095)); properties.Add(new BooleanProperty(PropertyNames.IgnoreOverlap, false)); properties.Add(new ScalarProperty(PropertyNames.ImageDataDiscardLevel, 1, 0, 3)); properties.Add(new ScalarProperty(PropertyNames.ImageQualityLevel, 0.9f, 0.0f, 1.0f)); properties.Add(new BooleanProperty(PropertyNames.InterleavedAlpha, false)); properties.Add(new BooleanProperty(PropertyNames.Lossless, false)); properties.Add(new ScalarProperty(PropertyNames.OverlapLevel, 1, 0, 2)); properties.Add(new ScalarProperty(PropertyNames.QualityLevel, 1, 0, 255)); properties.Add(new EnumProperty(PropertyNames.Rotation, Rotation.Rotate0)); properties.Add(new ScalarProperty(PropertyNames.SubsamplingLevel, 3, 0, 3)); properties.Add(new BooleanProperty(PropertyNames.UseCodecOptions, false)); properties.Add(new ScalarProperty(PropertyNames.VerticalTileSlices, 0, 0, 4095)); ... This actually should work better for Effects. Given a list of these properties, a default UI can be generated on the fly with a simple mapping of property type -> UI handler.

I've published more benchmark results along w/ commentary, http://blogs.msdn.com/rickbrew/archive/ ... cores.aspx

Woops, yeah my bad. I should've read more carefully before replying.

Wow, that's really cool Dan! Lots of layers in those PDN files. I'm sure you're in a love-hate relationship with the Layers window UI by now

There's a tutorial for "exploding planets" over in the Tutorials section, I think that's what you want.

It's just a realistic attitude and honest response. I could just as easily get your hopes up and say, "Oh yes, I will bend over backward and spend a lot of time to optimize this!" after which either 1) I do, and sacrifice a lot of free time in order to accomplish it, or 2) I don't, in which case I'm a liar and a jackass. (2) isn't very nice, and (1) takes away time from my time allocated for things like beer, video games, girls, and teasing my cat. I'm not trying to be patronizing or anything. Paint.NET is distributed for free, which is awesome for everyone, but it removes a certain level of obligation on my part. It isn't designed to be perfect for every scenario or market segment. I don't have a business plan that lays out a strategy for making inroads on Photoshop's marketshare. So compared to them (the Photoshop crew), it does seem weird for me to be referring you to "competing" software.

It's not lying: you are out of memory. Just because you have 1GB doesn't mean you have infinite memory and are exempt from out of memory conditions. Work with smaller images.

Make sure to post in the correct section of the forum. Moved to Bugs & Troubleshooting

Ok I'm bringing out the big guns here. Yes, that's 8-cores and 8GB of RAM. PdnBench v3.0.2573.22452 Running in 64-bit mode on x64 OS Processor: 8x Intel(R) Xeon(R) CPU X5355 @ 2.66GHz Memory: 8190 MB Using 8 threads. Loading image ... (1024 x 768) done Rotate/Zoom at 0.00 degrees (3x) ... 81 milliseconds Rotate/Zoom at 70.00 degrees (3x) ... 81 milliseconds Rotate/Zoom at 140.00 degrees (3x) ... 100 milliseconds Rotate/Zoom at 210.00 degrees (3x) ... 74 milliseconds Rotate/Zoom at 280.00 degrees (3x) ... 99 milliseconds Rotate/Zoom at 350.00 degrees (3x) ... 81 milliseconds Oil Painting, brush size = 1, coarseness = 10 (1x) ... 51 milliseconds Oil Painting, brush size = 1, coarseness = 85 (1x) ... 51 milliseconds Oil Painting, brush size = 4, coarseness = 10 (1x) ... 107 milliseconds Oil Painting, brush size = 4, coarseness = 85 (1x) ... 130 milliseconds Blur with radius of 2 (1x) ... 46 milliseconds Blur with radius of 4 (1x) ... 39 milliseconds Blur with radius of 8 (1x) ... 122 milliseconds Blur with radius of 16 (1x) ... 110 milliseconds Blur with radius of 32 (1x) ... 394 milliseconds Sharpen with value of 1 (1x) ... 61 milliseconds Sharpen with value of 4 (1x) ... 138 milliseconds Auto-Levels (50x) ... 241 milliseconds Clouds, roughness = 81 (2x) ... 263 milliseconds Clouds, roughness = 27 (2x) ... 123 milliseconds Clouds, roughness = 9 (2x) ... 85 milliseconds Median, radius 4 (1x) ... 130 milliseconds Median, radius 16 (1x) ... 116 milliseconds Median, radius 64 (1x) ... 450 milliseconds Unfocus, radius 4 (1x) ... 96 milliseconds Unfocus, radius 16 (1x) ... 280 milliseconds Unfocus, radius 64 (1x) ... 303 milliseconds Motion Blur, Horizontal (1x) ... 172 milliseconds Motion Blur, Vertical (1x) ... 204 milliseconds Resize from 1024x768 to 512x384 ... 8 milliseconds Resize from 512x384 to 1024x768 ... 25 milliseconds Resize from 1024x768 to 1536x1152 ... 57 milliseconds Resize from 1536x1152 to 1024x768 ... 25 milliseconds Resize from 1024x768 to 2560x1920 ... 157 milliseconds Resize from 2560x1920 to 1024x768 ... 26 milliseconds Resize from 1024x768 to 3584x2688 ... 308 milliseconds Resize from 3584x2688 to 1024x768 ... 26 milliseconds Linear reflected gradient @ 4096x3072 (5x) ... 164 milliseconds Conical gradient @ 4096x3072 (5x) ... 560 milliseconds Radial gradient @ 4096x3072 (5x) ... 244 milliseconds Compositing one layer, Normal blend mode, 255 opacity (20x) ... 27 milliseconds Compositing one layer, Normal blend mode, 128 opacity (20x) ... 60 milliseconds Compositing four layers, Normal blend mode, 255 opacity (20x) ... 128 milliseconds Compositing four layers, Normal blend mode, 255 (layer 0) and 128 (layer 1-3) opacity (20x) ... 180 milliseconds Compositing four layers, Normal blend mode, 128 opacity (20x) ... 180 milliseconds Compositing three layers, Normal+Multiply+Overlay blending, 150+255+170 opacity (20x) ... 159 milliseconds Transform simple surface, no transform, nearest neighbor resampling (25x) ... 30 milliseconds Transform complex surface, no transform, nearest neighbor resampling (25x) ... 29 milliseconds Transform simple surface, no transform, bilinear resampling (25x) ... 370 milliseconds Transform complex surface, no transform, bilinear resampling (25x) ... 366 milliseconds Transform simple surface, 45 deg. rotation about center, bilinear resampling (25x) ... 632 milliseconds Transform complex surface, 45 deg. rotation about center, bilinear resampling (25x) ... 635 milliseconds Transform simple surface, 50% x-scaling 75% y-scaling, bilinear resampling (25x) ... 144 milliseconds Transform complex surface, 50% x-scaling 75% y-scaling, bilinear resampling (25x) ... 143 milliseconds Zoom out, rotated grid multisampling, 66% (1000x) ... 900 milliseconds Zoom out, rotated grid multisampling, 28% (1000x) ... 271 milliseconds Zoom 1:1, straight blit (1000x) ... 1061 milliseconds Total time: 11288 milliseconds

I don't understand ... why the eye-rolling?

It's isn't a bug, it's a precision issue because there isn't a 1:1 mapping between RGB and HSV -- there's a post in Bugs & Troubleshooting about it somewhere.

Sorry, there is no written down roadmap for future releases. There will be more releases though, of course. Trust me, even it was at feature-for-feature parity with Photoshop, people would still say this

I wish I were psychic, but I'm not. I'd wish to be a tech support person, but that would be a lie. Moved to Bugs & Troubleshooting

Collage, not "cologe".

Not in XP Home. It does not support the file system security features, iirc (or at least, the UI for it).

Please make sure to post in the correct part of the forum. Moved to Bugs & Troubleshooting

phunkydizco, Can you do me a favor? Can you e-mail me the original image, the "broken image", and a list of instructions for "breaking" the image? You said that you tagged it in Windows Vista, for instance, but it would really help me if I had a dummy-proof list of instructions (pretend I'm having my mom go through the steps or something). If this is a problem in Vista then I would like to file a bug on them* and track it. The e-mail to send it to is paint.net@hotmail.com * Remember: I work for Microsoft. I can do this quite easily

Yes, I have a bug filed for that. It's an easy fix, it's just a matter of finding enough little bugs to fix to warrant a 3.01 update. And by that I mean that this one little bug does not by itself warrant going through the process of packaging and releasing a 5mb update to hundreds of thousands of users But luckily (?) for us I have some other bug fixes I need to push out, so you should see this fixed fairly soon (within a few weeks).

Screenshot please ... I've tested this myself and it was always fine.

Wow apie44, thanks so much for not reading the rules. Thread closed