Fixx

+1.    I love Affinity photo,  but please do not commit commercial suicide by attempting to bring ANOTHER NLE to market.
There are already dozens at both the professional and non-professional level (Adobe, Avid, Edius, Final Cut, Vegas Pro, Davinci Resolve, Lightworks, Hitfilm, etc.), and they are cheap to buy and in some cases free.  Some are decades old and have 100's (1000's ? of programmer years of coding already.)   It is  technically challenging both to make and support, and the level of user expertise required is quite high.    
If forum members need convincing, I suggest downloading DaVinci Resolve (free) and taking a good look at it.  Read some forum posts.   Still think Affinity should compete with this?

I noticed that a number of automatic adjustments such as auto levels and auto contrast are rather hidden in the menus, and that when they are used, they are applied to the pixel layer selected, without creating an adjustment layer. I think it would be useful for a lot of users to have an auto - button on (at least some of) the adjustment settings window(s). I realize this may not always provide the desired settings, but in many cases may at least be a good starting point for further fine tuning.

I did try a few optimizers. Results so far:
XnConvert – quite full featured, can resample, add operations (like sharpen filter), rename. Clunky, ok quality.
JPEGmini – ok quality, no features, no resample, only JPEG originals.
PhotoShrinkr – very good quality/size ratio, can take many formats, very fluid operation. No resampling.
Squash – good quality/size ratio, can take many formats, adjustable quality/size ratio, fluid operation, funny sounds and animation. No resampling.
ImageOptim – ok quality, adjustable quality/size ratio, No resampling, no  formats support, bit clunky.
 
I would use XnConvert if resampling is needed, and PhotoShrinkr if I am making resampling in AP. No perfect solution yet, and my quality test was not very extensive.

I did try a few optimizers. Results so far:
XnConvert – quite full featured, can resample, add operations (like sharpen filter), rename. Clunky, ok quality.
JPEGmini – ok quality, no features, no resample, only JPEG originals.
PhotoShrinkr – very good quality/size ratio, can take many formats, very fluid operation. No resampling.
Squash – good quality/size ratio, can take many formats, adjustable quality/size ratio, fluid operation, funny sounds and animation. No resampling.
ImageOptim – ok quality, adjustable quality/size ratio, No resampling, no  formats support, bit clunky.
 
I would use XnConvert if resampling is needed, and PhotoShrinkr if I am making resampling in AP. No perfect solution yet, and my quality test was not very extensive.

Illustrator CAN do this. It's called Transform Each. Fantastic tool! We need it badly.
Inkscape can do it too.
 

It is going to be a long long longlonglong summer 

Yep... (irfan is very lightweight, and has a quite good batch processing solution inside it)  I knew about these (and a bunch more )  , but Fixx wanted apps for Mac (sadly, i don't have a Mac at my room. Would love to. But so, I don't know well the Mac OSX apps "market" ) .... The two I mentioned are very pro, even if we were considering windows-only. But require a lot of trying of settings (specially Imagemagick) till you get the best solution. Is not like a tool made for optimizing a specific format -ie jpg- , where all is set as default with the best values, or almost. Yet, when you are offered a lot of methods and flexibility, you get to do really advanced and high end exports....
I have had always specialized converters, both in 2D and 3D.  In video, etc..... You need them sooner or later. The main packages are great and all, but some specialized utilities end up being needed at some stage.
What I don't see in this case is a export being a reason for using AP or not. If that is a reason, then, there wasn't really a deep intention on using it. Professional pipelines require very often to combine several tools, so, if you have a main app that makes a 80% of the work (ie AP or AD or both, or ...PS.  ) that's pretty much what anyone would do working at the company, even being too generous with the integration package percentage.

easy cheat 

Although it cannot be created in Affinity Photo, you can use a file such as the one attached to this post to add text on a path to your project.

For all who do not understand the point of the Develop Persona, I urge you to view 
You will notice that in the Develop Persona the moderator concentrates on spreading the tones across the histogram without losing any details in the highlights and the shadows, and states that he will do more detailed work with tone curves in the Photo Persona.
Basically, in the Develop Persona I try to extract as much detail out of the RAW as possible.  It's in the Photo Persona that I then produce an image for a particular purpose.  If I want an image to print, I'll start with a Soft Proof adjustment layer in which I select a profile for my printer and paper and turn on gamut checking.  All the other adjustment layers will go underneath it, e.g., for adjusting tone, exposure, contrast, brightness, etc.  This allows me to refrain from any adjustments that will produce colors that I will have difficulty printing.  I might also prefer subtlety to dramatic impact, especially if I'm producing a large print.  If, on the other hand, I want to produce an image for a web page, or for sharing, I might want something more dramatic and less subtle than for printing, something with much more contrast, saturated colors, etc.
What I produce in the Develop Persona is a good starting point for both, and probably for anything else I might want to produce in the future.

Hi all, on Photoshop, if I hit Ctrl+Del it will fill the whole canvas with the foreground color, Alt+del fills with the bg color. This is a feature I used all the time but now flood filling with a color is a relatively time consuming effort. The reason I use it is that I create an adjustment layer that I want to affect only a small area so then I have to check that my swatches are correctly set, get the fill tool and fill it with black. Am I missing something or is this just a feature I need to be requesting?
Thanks,
Phil

I'd go one step further, and add these as a fill option. Then add multiple noise functions, allow for layering of various noise variants and embossing. Look at PhotoLine for inspiration.
Another option is FilterForge, but the plugin doesn't work in Photo, which is a crying shame. No issues in Photoshop or PhotoLine.
In Photo I receive this error: a <class XFW::ArgumentError> The handle 000000C5C3BED9C0 is not a valid window handle.
FilterForge has a multitude of interesting noise and texture generators. The stand-alone version does work, but it would be great if it worked as a plugin in Affnity Photo.

I think the OP means a 1-bit black-and-white image. I would like this facility in AP.
John

I've found and read the bkwine article several times.  The author has found a 'least bad' solution, but not a good solution.
At this point in time there is not a DAM on the market that meets all the needs of a professional photographer.
I've been thinking a lot about photo management.
I'm starting to avoid the word 'DAM' as it increasingly refers to industrial sized software costing tens or hundreds of thousands of dollars. So let's look at what I mean by a photo manager:
Browser Pix initially come in in bunches, and as such they go somewhere in some folder structure on your computer. Many people will use some combination of Year/Month/ and string to describe event. Often remember that the shot took place on your trip to Italy, or that it was the Smith & Brown wedding is sufficient.
Tagger But what do you do when you are looking for the closeup of a butterfly. It was an incidental pic on some holiday, but which one. Now metadata comes into play. If all your holiday shots are tagged 'Holiday' and your program can search existing metadata, your problem is solved. Search for holiday and focal distance less than 5 feet. You still may have a bunch to wade through. If, in addition to some general keywords for the batch you add a few per image you have a big win. E.g. "Butterfly"
Tagging is hard. You want to tag it with multiple things. E.g:
Describe the scene. Identify the location. GPS is fine, but "Lock Ness, Scotland" or Kensington market, Toronto, Ontario, Canada is easier to visualize. ID the people in the scene. Classify them more generally. (Woman with child; Young boy...) Describe the technical aspects -- close up, high/low key, lighting One or more classes of description about the scene -- weather, mood. These are facets. I prefer to go through a set of images several times, concentrating on one of these at a time. Sometimes a facet is irrelevant. Weather makes no sense for an interior shot. If you do facets, you need a way to search for images that don't have an entry for facet X. You also need a way to mark a facet as irrelevant.
Crudely you can implement these with constructs like WEA:Cloudy but then you still have to be able to search for images that don't have WEA:* as a keyword. And you have to decide on what to do where it's not relevant. WEA:N/A
Having some kind of support for actual facets would be a big win.
Searcher No point in tagging if you can't search the data. Two programs I trialed, Mylio and Photoshop Supreme, had no provision to search exif data -- where the stuff like time of day, and focal length, and camera model is kept. One program allows you to search for only one tag at a time. I can search for Holiday. Or I can search for butterfly. But I can't search for shots that have both "Holiday" and "butterfly" Ideally you want full boolean search support with and, or, not, parentheses for grouping, and wild cards for partial matches.
Version tracker A photograph for a professional may have a long history. You often have a shot, then export it in some altered form (cropped, resized, sharpened, colour adjusted, watermarked) Nice to be able to find the original 5 years from now. One recommended practice I ran into had the following:
Master image was Raw. Archive version was digital negative. Processing version was 16 bit tiff or PSD Delivered version was tiff or jpeg. This requires a minimum of 4 versions. Add to that: * Watermarked versions. * Reduced resolution versions for web pages. * Colour matched versions for specific printing environments. * Cropped versions for mobile web pages.
So that's the base case. Implementations differ, and they refine this somewhat.
Online resources
Impulse Adventure (site: https://www.impulseadventure.com/photo/) Unfortunately out of date. But still several good articles.
Catalogs and Multiple versions. https://www.impulseadventure.com/photo/flow-catalog-versions.html
Important Features of Catalog Software. https://www.impulseadventure.com/photo/flow-catalog-features.html
Controlled Vocabulary (site: https://www.controlledvocabulary.com/ )
Using Image Databases to Organize Image Collections http://www.controlledvocabulary.com/imagedatabases/ Also has a good forum/mailing list.
Requirements:
Server requirments
I can see implementing this in one of two ways: Either as a stand alone program or as a local web server. The latter has the advantage that it would scale for family or small photo business.
Cloud services are slow when you are talking about 10-12 Mbyte files. My network connect takes several seconds per MByte. Cloud services for metadata have to be well optimized -- you really don't want to issue 3000 keyword change requests individually when you change the spelling of a keyword. So:
Not cloud based. Runs on Mac or on local apache web server. Keyword handling
Fast keywording. Aperture allows drag and drop from a list, multiple sets of hotkeys for words used frequently, copy paste of keywords from one photo to another, and keywords organized in folders. It also allows search for a keyword, and a list matching what you typed so far appears. Other programs that have good keywording include IMatch and Photomechanic. One of the key aspects of this is to have multiple ways to do things. Full access to standard metadata: EXIF, ITPC, subject to limits of the file format. Controlled vocabulary. I want an extra step to add a new keyword to my list of keywords. This helps with the the Sommer Vacashun problem. Hierarchial vocabulary. E.g. Separate entries for Birds -> raptors -> falcon and Planes -> fighters -> falcon. Parents are stored with keywords. Moving a keyword in the master list, or changing spelling, corrects all usage in photos. This can be done as a background task. Parent items are automatically entered as keywords. (With the correct database linkage, this comes free as a side effect of the point above. Synonyms -- I can define "Picea glauca" as a synonmym for "White Spruce" entering one, enters the other. Facets: For a set of pictures I want to be able to define a set of facets or categories for collections or folders. Facets would be things like: Weather; Who; Where; Ecosystem; Season; Lighting Not all collections would have all facets, but a collection having a facet would nag me to put it in. A facet would have a negation for not applicable (Weather isn't applicable inside a house; Who isn't applicable in a landscape shot.) Facets allow me to go through a collection in multiple passes and get the missing keywords. Searching
Complex searches: Find all shots between 2012 and 2015 shot in December or January, shot with my Nikon D70, with keyword "snow" rating of 3 or better shot after 3pm in the day. (Yes, I do use searches like that) Saved Searches. These are the equivalent of smart albums in Aperture. As new pix meet the standards they would be shown. Version Tracking
Version tracking If a lower resolution, cropped, photoshopped, composited or a black and white image is produced from a master, the system should show that it's a derived image, and allow access to the master. A master should be able to list derived images. Derived images are not linear but form a multi-branched tree. If my camera produces JPEG and Raw versions, I want the JPEG to be shown as being derived from the Raw version. Metadata applied to a master should propagate down to derived images. Some form of exception handling for this: e.g. -keyword to prevent a people identifier being applied to an image where that person was cropped out. Ability to track through external editing programs. E.g. If I edit a program in photoshop, it will mark the PSD file as being derived, restore as much of the metadata as the PSD format allows. If Photoshop is used to create a jpeg image, that too is tracked. Data robustness
All metadata is indexed. Metadata is also written to sidecar files. Where possible metadata is written to the image file itself. (optional -- can stress automated backup systems) Through file system watching, name changes and directory reorganization are caught. Relevant sidecars are also renamed, and the database updated with new file location/name. Sidecar contents include the name of their master file. Should be possible to rebuild entire database from images + sidecars. Should be able to restore all file metadata from database. This requires a lot of under-the-hood time stamps to determine which has priority. All database actions should be logged and journaled, so they are reversible. Reasonable speed with catalogs of more than 100,000 images. Support for previews of all common image formats and most raw formats. Previews and thumbnails are treated as versions of the master. They inherit metadata. Nice to have:
Simple non-destructive editing -- crop, brightness, contrast. Rating system Smart albums Drag and drop functionality with other mac apps. Suggestions?
Notes on current state of the art:
Nothing I've found supports version tracking, especially through an external program. Lightroom and Aperture both support simple versions -- different edits on same master. Aperture supports Stacks -- a group of related pictures. Lightroom: Doesn't support PNG, very clunky interface, slow on large catalogs; Mylio home version doesn't support hierarchical keywords; doesn't index exif information, does not allow or syntax for searches, Photomechanic is fast for keywording and culling, but has very limited search capability. IMatch. Possible contender, Requires MS windows box. Photo Supreme: Erratic quirks. Crashes. One man shop. Can't search Exif in useful way. Fotostation: AFAIK no underlying database. Has to read metadata from images/sidecar files on startup. Slow after 10K images. (They have server based software too that is big bucks.) Luminar: A DAM has been promised Real Soon Now, but no demos, storyboards or feature lists have been published. There is a claim that it is in beta, but no one on their fairly active forum will admit to being part of the beta group. Affinity: Similar to Luminar. Commandline tools
Much of the special features for version tracking could be implemented with scripts using calls to these programs.
ImageMagick -- good for whole-image conversions, also can read/write internal metadata and sidecars. Exiftool -- read/write exif data reads most makernotes. fswatch -- not really an image processor, but hooks into the operating system and can alert when files have changed -- modified, renamed, moved. Enterprise level
WebDAM No real information about capabilities on web site. Extensis. Expensive. Bynder. Joke program. Cloud based set of shoeboxes. WIDEN. Cloud only. Asset Bank. Starts at $500/month for up to 50 users. Metadata Storage
There are three places metadata can be stored:
In the image. In a database. In a separate file for each image (sidecar file) Typically these files have the same name as the primary file, but a different suffix. If at least some cataloging information is written to the image, then you can reconnect a file to your database. In principle this can be a single unique ID.
This saves you from:
You moved or renamed an image file. If you can write more info into the file -- keywords, captions -- then you are saved from:
Your database is corrupted. You upgraded your computer and your database program doesn't work there.
Sidecar files allow you to recover all your metadata if your database crashes.
Downsides of storing data in the image
Writing to the original files can corrupt the file. Most RAW formats are well understood enough now to at least identify and replace strings of metadata with the same length string. If you tell your camera to put the copyright string
Copyright 2018 J. Random Shutterbug Image XXXX-XXXX-XXXX-XXXX-XXXX-XXXX Then as long as the DAM keeps that string the same length you are golden.
Keeping all metadata (or as much as you can) in the original images makes for very slow access. Your program has to read at least the first few blocks of every image. Depending on the file structure, adding too much data may require rewriting the entire file. Any program that moves the boundaries of data sub blocks better be well tested.
Writing data back is time consuming.
Some file formats don't have any metadata capability.
Some file formats (Photoshop PSD) are noted for mangling metadata.
A glitch during the write process can corrupt the image file. The alternative, writing a new file, then replacing the old file requires that the entire file be both read and written, rather than just a chunk of it. This has serious performance issues.
Downsides of Databases
Databases are fast, but they are blobby, and you are writing into the middle of blobs of data. If the implementation of the database is solid, there isn't much to worry about. But hard disks have errors, and a single error can make a database partially or fully unusable. Good database design has redundancy built in so that you can repair/rebuild.
Databases are frequently proprietary. Data may be compressed for speed. Getting your data out may be tricky. (Problem for people using Apple Aperture)
Databases frequently are optimized in different ways. In general robustness is gained at the cost of performance and complexity. One compromise is to write all changes first to a transaction file (fast...) and then a background process does the database update in the background. This slows down access some: Have to check both the main database and the transaction file, but unless the transaction file gets to be bigger than memory, this shouldn't be noticeable.
Downsides of Sidecars
You have to read a zillion files at startup.
If you do a batch change (Add the keyword "Italy" to all 3000 of your summer holiday trip shots) the catalog program has open, modify and write back 3000 files.
If you rename a file, and don't rename the sidecar file too, your meta data is no longer connected to your image.
Best practice
Opinion only here: Sorry.
You want a unique asset tag that resides in the image. This can be an actual tag like the copyright one mentioned above, or it can be a derived tag from information in the image. This could be the EXIF time stamp (Not unique -- multiple shots per second, multiple cameras.) If your program reads makernotes, the best one is Camera model + Camera serial number + timestamp + hundredths of a second.
You want a database for speed. It, of course has the unique ID
You want sidecars for rebuilding your database, and for data portability. They have the unique ID.
If the database crashes, it can be rebuild from the sidecars.
If a sidecar is corrupted, it can be rebuilt from the database.
If an image is renamed the ID can be used to reconnect it to the sidecar, and to fix the database.
To make this work, you have to use a lot of timestamps. If the sidecar is more recent than the latest time stamp in the database record, then the sidecar is the authoritative record.
You also have to have internal checks on data integrity. The record for an image (sidecar or database) needs a checksum to verify that that data isn't corrupt.
Given the relatively fragile nature of raw files, best practice is a system that only writes zero or once to the Raw file. This is why the exif time stamp + hundredths, copyright work well. You can include the camera model and serial number in the copyright so that now the copyright message is unique to the camera. At this point you have the ability to create, and recreate a unique ID for each image. If the DAM has the ability to modify the file, you can create this ID once. This saves some time if you ever have to rebuild the database.
Having as much of the metadata in the file as possible means taht it travels with the file. This is a win, but comes with the risk of potential corruption. Possibly the best strategy is to leave the original intact, and for clients who need raw data, either add metadata to a copy, or to a derived full data equivalent (e.g. DNG)
Sidecars don't need to be updated in real time. The slick way to do this would be that whenever the database makes a change to a record:
Make a new record that duplicates the old record in the database.
Make the change in the new record.
New record is flagged, "not written to sidecar" Old record is marked "obsolete" Another thread writes the sidecar files out, writing out the new one, then deleting the old one (or renaming the new one to the old one's name). Periodically you run a cleanup on the database removing obsolete records older than X days. This gives you the ability to rollback changes. This is not complete: It doesn't address the issue of non-destructive edits. Many programs now allow the creation of multiple images from the same master file, and do not create a new bitmap, but rather a file with a series of instructions for how to make the image from the master. AFAIK all such methods are proprietary. This results in a quandary as the apps that do a good job of tracking metadata may not be able to deal with the non-destructive edits. This can be critical if you crop a person out of an image, crop to emphasis a different aspect, and receive a different caption, etc.
The workaround is that you always write out a new bitmap image from a serious edit. Ideally you have a script that looks for new NDEs and writes out an image based on this, copying the metadata from the master and at some point bringing it up for review for mods to the metadata.
Robustness against external programs.
I like having an underlying file structure organization. I like the idea that if I produce a bunch of cropped, watermarked, lower resolution, etcetera versions of an image that my catalog will track that too.
But if the underlying file structure is exposed to Explorer or Finder, then you have the risk of a file being renamed or moved, and the database is no longer in sync with your file system.
To budnip answers of the form "This is impossible" here's how to "Finder-proof" your image database.
When an image is edited, a file system watcher notes that the file was opened. The file goes onto the 'watch' list. (the program fswatcher does this on mac. I use it to update my web page when my local copy has been edited.)
When a new file appears in a monitored directory tree, it's noted.
When a file is closed, this is also noted. If there has been a new file created it is checked for metadata. If the new file's metadata has a match for an existing file, then existing file metadata is used to repopulate missing data in the file. (Photoshop is notorious for not respecting all metadata.)
Database is updated with the new file being marked as derivative of the original file.
optionally a suffix may be added to the new file's image number, showing whether it derives directly from the original or from another derivative.
To make this work, the two components are a unique id that can be calcuated from the master, and a file system monitor program that catches create, move, change, and rename events.

Am new to this site....and am looking for software that I can use to enhance 3D architectural models created in other programs.     Does this program have available elements to include in the file such as people, trees, cars, etc.    If not, how can I find, import and include in the JPEG, BMP or TIFF files.  
Am doing some research before I buy a photo editing program.  
Thanks

No, like this: 
 
or rather, like this: 
 
(except I use metric. Also there are lots of variety between countries how to present dimensioning.)

I would love to see Designer have the ability to work in scale and able to use call outs and measurements. would come in very handy.

It is going to be a long long longlonglong summer 

It is going to be a long long longlonglong summer 

Hello everyone,
Going to keep it short since I can go on forever about the newly released iPad Designer which I absolutely love!
I would like to request a feature for the range of Affinity products which is an addition to the HSL adjustment which is the Range sliders for each hue "channel" (ie: red, yellow, green, cyan, blue, magenta; the slider found at the bottom of the attached image which you can isolate and slide the hue range by degrees).
I would like to offer the suggestion alongside the idea of actually being able to input the values of degree with keystrokes as well as the sliders themselves. They sliders in photoshop can be a total pain and never understood why they couldn't add something so seemingly easy.
Lastly, being able to isolate to a 12 color hue range would be amazing as well! (Red, Orange, Yellow, Yellow/Green, Green, Green/Cyan, Cyan, Cyan/Blue, Blue, Blue/Magenta, Magenta, Magenta/Red)
All the best and keep up the amazing work team!
 

I'm excited that Affinity is developing a DTP application.
From the various rumours and snippets I can't tell what Affinity Publisher (AP) will be like.
My simple (but important imho) request is this - that AP must not be a fancy page layout application designed for posters and small pamphlets, but must be usable for larger books and technical publications.
Right now there is a gaping hole in the market. Indesign and Quark seem to have de-emphasised the serious / technical book publisher or author, leaving the space to the extremely expensive systems like ArborText (link).
What would this mean for AP? It would mean workflows - workflows that allow users to create masterpages/templates and design elements like styles and partially complete objects like callouts and tables .. which are not placed on a page but in a sequence which is assembled and typeset to a final layout, the ability to cross-reference between sections, and even multiple books. 
Taking this user-centric view we can see, and be puzzled, as to why software like MS Word in 2018 still can't apply styles to images (try applying a style which sets inserted images to 70% if the text width.. it's not possible). But a book designer would need to be able to adjust how figures in a book work with ease and elegance.
 
Please don't release a glorified Affinity Designer with fancy linked text boxes ... !!

ID isn't very intuitive for a novice. Neither is Scribus, PagePlus, or Viva Designer. And our beloved Ventura wasn't either. Of these, I only find Scribus obtuse in use even over a period of time. It's an application built by committee.
APub can only be more intuitive at its inception. As its capabilities grow to even approximate that of the mature applications, it will become less so.
Here's some screen shots from Q. I have two different paragraph styles, one using TNR and the other using Arial. I have applied bold & bold italic to two words. Initially both paragraphs have the Mikey style applied and it is defined as using TNR. Cursor is in the second paragraph.

Now I am going to use the Mikey Two style which will both change the font to Arial and apply text shading.

The font switches and is proper in the bold & bold italic instances.
Now, I am going to change part of the paragraph to use Courier locally like so:

And now I am going to reset that paragraph back to Mikey Two style using the right-click option I mentioned previously:

So while Q doesn't work like ID in that a character style used for the bold, etc., attributes will retain the font as defined in the c.style when the base paragraph definition is changed, it does work well.
As I have written on the closed FB group, in the Q forum, directly to the people at Quark and here, I would prefer that how text styles work should follow Adobe's method because it is simpler. But that doesn't mean Serif's (which is similar to Q's method already) also cannot work. And as I mentioned, how styles work is being worked on and hopefully how they work will move more towards ID's.
 

A gargantuan "vertical purpose" plug-in piled on top of the most cluttered, scattered, and cumbersome Bezier drawing interface on the planet? No thank you.
I'm all for technical drawing support. That's my pet desire for Affinity Designer, too. But 2D drafting and axonometric drawing are not rocket science, and it's way past time to take them out of the conceptual confines of the mechanical engineering department (i.e., vertical market). There's no reason the full functionality needed can't be cleanly integrated into the standard feature set of a welcoming, unintimidating, elegantly designed  interface for mainstream general-purpose Bezier-based drawing without overtly screaming "Drafting Mode!" at the beginning user or the stylistically-versatile expert illustrator.
And that's more of what I hope (and suspect) the Affinity dev team has in mind.
JET

It is going to be a long long longlonglong summer 

Point taken Fixx (-:
Just remember I'm an artist, and even if I have worked a lot with HTML coding and large sites, I'm absolutely not a tech guy (-:
When I worked with my large canvases and acrylic paint, I have to admit that the artwork was not always kindly treated. They were stuffed into vans to bring them to exhibitions and so on, and not much better inside my studio. But I can tell you that when paintings were sold for ten thousand USD and upwards - the gallery treated them like fragile glass when bringing them to the art collectors. A friend who is a curator at the Munch Museum in Oslo told me that Edvard Munch used to lay his paintings out in the garden, open air where wind, rain or snow could give them what Munch called patina. Well it's not as easy when I make my artworks digitally today, my printer is sitting on my shoulder asking for a specific standard, so when I hear compressed, I get the shiver, just because I don't know enough tech stuff )-:
So sorry for ranting about what maybe should be basic knowledge when working digital, but I'm not all there yet - so thank you for your patience and help, all of you, it's highly appreciated (-: