merarischroeder

Newbies
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

3

Profile Information

  • Gender
    Male
  • Location
    Geelong, Australia

Contact Methods

  • Website URL
    http://alivate.com.au
  • Skype
    alivate.hq

Recent Profile Visitors

578 profile views
  1. The "Copy Merged" function seems like a step in the right direction, that underpins future enhancements. 1. Copy Merged, for now 2. File -> Export - would show a Export As file dialog, the [Copy Merged] function would be able to copy to a virtual file-tab in the background, and save to the Export As location, then close the virtual file-tab.
  2. I agree with an "Export to file..." feature, that's a common feature in image editing software.
  3. While it's certainly possible to workaround the lack of an "export" behaving function, I believe there is strong merit to add this feature. It's a very common feature found in rastered image editing software (for good reason) There are clear use cases where such a feature is preferred - such as frames in animation. Another one is for quick review - I personally do a lot of work with web, where I'm adjusting dimensions, and rapidly testing 4-7 times in my web browser inside a web site or web app. "Export" is what users intend: save a copy, then continue on the current "file" as is with layers, and without a "Merge Layers" step in their file history after saving the file. I suggest the simplest implementation might be: Open a new file-tab Copy the contents from layers in the original file-tab Merge-down Save the file Show to the user The user can close that file-tab if they want Even better, if the source tab can send the new tab a merged-down version in the first instance: Open a new file-tab Copy the merge-down content from the original file-tab Save the file Show to the user The user can close that file-tab if they want
  4. I think OP was about "selection" of layers. This is a transient operation. I actually needed something like this today. Initially, this could be limited only to moving the whole layer only (not pixel selections within the selected layers). This doesn't mean I think it's easy to code, but the clarification of the problem and requirements for implementation might reveal an easier implementation path.
  5. I wasn't trying to colour-correct, I was trying to stylise. In this case I accomplished a monochrome filter to make the colourful photo fit in with a convervative colour palette in my web app. If there are optimised "manual" ways to do this in Paint .Net, I'm always happy to learn. The closest description of the feature I propose would be "Instagram Filters". Or perhaps something you can playwith easily - https://photomania.net/editor The appropriateness to directly include this into Paint .Net would be a subjective decision: NO - because it's already possible with turning knobs and dials with existing core functionality and plugins. NO - because that kind of thing should only be accomplished with a plugin, not a core feautre YES - although it's possible to do with knobs and idals, creativity requires a person to quickly enumerate a range of different directions and simply judge what works for their situation. YES - there are products dedicated to this kind of thing, which proves the value. "Instagram Filters" merely brought this idea to the mainstream. YES - colour filtering should be thought of as a major key featureset for editing rastered images, it's absence requires users to do it the hard and long way instead, resulting in fewer users bothering to engage with the software. My philosophy here being, allow users to do it the quick and easy, then let advanced users do it the hard manual way for greater control. YES - it would be a gateway feature. People download and install Paint .Net to apply colour filters to their photos, then they also start using other features, and decide to use Paint .Net instead of other software they've used in the past.
  6. I would like to be able to apply a range of pre-defined colour filters onto existing photos. Photo colouring seems to be an elusive art, that could be made more accessible by direct photo colour filtering tools within Paint .Net. It might just be a matter of mastering levels, but I would prefer a more intuitive approach. See my tutorial below. It would be handy to enter one or two colours to recolour a photo. This feature would need a lot more input from graphic artists to gather a full compliment of requirements, but I think this would be a feature for the masses. There may be existing plugins and tutorials for this, I could find them myself, so please point me in the right direction if there are. Even if there are plugins, I think this is a feature that needs to be baked in. see
  7. I got a stock image for a website. I tried putting it in directly as is, but it didn't work. Although the gold/yellows are complimentary to the blues I have in the site, there was too much yellow. I decided to try and colour filter the image so that it would blend in a bit nicer. see Tutorial.jpg - You can see the original [1], the mask layer [2], and the final result [3]. It's quite a simple process: Find out the HSV values of your chosen colour by entering the HEX into the Paint .Net colour picker. My colour was #183C5E, and the HSV was 209, 74, 36 Make a copy of the original image on a new layer above, this will be the Mask Layer Adjust that mask layer using Adjustments > Hue / Saturation, using the HSV values from [1] Double click on the new layer to show the Layer Properties In the Blending section, adjust the Mode, to Glow, You might want to back off the opacity lower than 255 Finally click OK In my situation, this ends up as monochrome, but not black and white. The blue target colour is subtle, and the yellow in the light is faintly there. I'm not sure if there's an easier or more creative way of doing this. Please let me know. I use Paint .Net a lot, and I think Photo Colour Filtering is a missing direct feature.
  8. MODERATOR'S NOTE: This plugin may not be compatible with Paint.NET 4.0+. Download - http://alivate.com.au/BatchProcessAutomater.zip Please donate even $5 if this helps you - it took me about 10-14 hours to complete, and saved me 1 hr manually processing my 154 images... $USD $ GBP £ EUR € JPY ¥ CAD $ AUD $ -------------------------------------------------------------------------------------------------------------------------------------- It bothered me that I couldn't automate the AutoLevel Effect on a folder full of pictures, so I spent the weekend and created a solution. I'm sure the future version of PDN will include such a batch automation feature, but I couldn't wait. So here it is. It leverage's pyrochild's ScriptLab plugin to actually apply a consistent set of plugins on each file, so make sure that's installed first. You will need to create your scripts inside PDN as usual with just the ScriptLab plugin. (The pyrochild plugin pack has a few dlls, you only technically need the ScriptLab.dll [copied into the Effects folder], but I'm sure you would copy them all) This Batch Process Automater, iterates through a given folder and then applies the ScriptLab plugin and therefore in turn, one or more effects. The plugin is open-source, so feel free to fork it - https://bitbucket.org/merarischroeder/pdn-batcher Instructions: 1. Create a ScriptLab Script of the effects you want to apply. Simply open PDN, Go to Effects > Advanced > ScriptLab, and do what you have to do, before clicking Save and then cancelling out of the dialog box. 2. Close PDN 3. Open BatchProcessAutomater.exe 4. Specify the Source and Output folders, these will default to your Pictures folder for your profile. 5. Specify the ScriptLab Script to run on each file. 6. Click Run You will then see Paint.Net open, and each file will be opened one at a time with effects being applied and the updated file saved. I could hide Paint.Net, but decided to keep it visible, you can then see the outcome and perhaps make notes as the system processes through the files. You can of course modify the Search filter which defaults to *.jpg, but at the moment the system will only save as JPG at 100 percent quality. Plenty of opportunity for improvement in the future. But I won't make any changes for a few weeks - feel free to ask for improvements or better still, send me patches to apply to the open source code base. The next change, if any, will be the ability to supply these parameters via command line arguments, this would be quite trivial to accomplish, the Form calls a static function on the class Automation, with the parameters. Command line input would be as simple as enumerating the arguments and passing them as parameters to this same function (although this should be done from the Form load event, as the main thread needs to be running for the function to work). Anyone want to give it a go? Try and help me on the open source code? I see opportunities for enabling the automation ofcanvas resizing image resizing (although you can use the rotate/zoom plugin) layer creation region copying (from source layer, to destination layer plus position) text generation I'm in no hurry though, and lets see what the new version of PDN will bring.