Blenheim Orange wrote:
Maybe someone can explain the difference for everyone between raster editors and parametric editors (better than I could).
Mike
A parametric editor works by creating and saving an instruction or recipe list for how to process the image. This is literally a text file and can even be readable and make sense. Here's a fragment from a DXO PL parametric recipe file:
Sidecar = {
Date = "2019-11-18T22:04:34.4118568Z",
Software = "DxO PhotoLab 3.0",
Source = {
CafId = "C43412a",
Items = {
{
Albums = "",
CreationDate = "2019-11-18T22:02:06.5292200Z",
ModificationDate = "2019-11-18T22:04:34.4088502Z",
Name = "IMG_1808.CR2",
OutputItems = {
}
,
ProcessingStatus = 1,
Rank = 0,
Rotation = 0,
Settings = {
AppliedPresetDisplayName = "1 - DxO Standard",
AppliedPresetUniqueName = "1 - DxO default.preset",
Base = {
ChannelMixerActive = false,
ChannelMixerRed = 0,
ChannelMixerYellow = 0,
ChannelMixerGreen = 0,
ChannelMixerCyan = 0,
ChannelMixerBlue = 0,
ChannelMixerMagenta = 0,
ChromaticAberrationActive = true,
ChromaticAberrationIntensity = 100,
ChromaticAberrationIntensityAuto = true,
ChromaticAberrationPurpleActive = false,
ChromaticAberrationSize = 4,
ChromaticAberrationSizeAuto = false,
ChromaticAberrationLateralActive = true,
HazeRemovalActive = false,
DehazingValue = 50,
ColorAccentuationActive = false,
VibrancyIntensity = 0,
ColorModeSaturation = 0,
ColorRenderingActive = true,
ColorRenderingIntensity = 100,
ColorRenderingIntent = 25,
ColorIntentAutoActive = true,
ColorRenderingType = "Original",
ColorRenderingICCProfile = "",
ColorRenderingDCPProfile = "",
ContrastControlGroupActive = false,
ColorModeContrast = 0,
LightingV2LocalContrastAmount = 0,
MicroContrastAuto = true,
ContrastEnhancementActive = false,
ContrastEnhancementGlobalIntensity = 0,
ContrastEnhancementHighlightIntensity = 0,
ContrastEnhancementMidlightIntensity = 0,
ContrastEnhancementLowlightIntensity = 0,
VignettedBlurActive = false,
VignettedBlurCenterPoint = {
0.5,
0.5,
}
,
VignettedBlurBlendFactor = 100,
VignettedBlurRadius = 0,
VignettedBlurVignetteSize = 100,
VignettedBlurRoundness = 50,
VignettedBlurTransition = 50,
VignettedBlurMode = "Vignetting",
ArtisticVignettingActive = false,
ArtisticVignettingCornerAttenuation = 0,
ArtisticVignettingMidFieldAttenuation = 50,
ArtisticVignettingRoundness = 50,
ArtisticVignettingTransition = 0,
ArtisticVignettingCenterPoint = {
0.5,
0.5,
}
,
CropActive = true,
CropAuto = true,
CropRatio = 0,
CropRect = {
0,
0,
1,
1,
}
,
DistortionActive = true,
DistortionType = "Auto",
DistortionTypeAuto = true,
DistortionIntensity = 1,
DistortionKeepRatio = false,
EdgeTexturingActive = false,
EdgeTextureID = "fuitelum1",
EdgeTexturingOpacity = 0.5,
EdgeTexturingSeed = 0,
EdgeTexturingPosition = "Random",
EdgeTexturingApplyToning = false,
When a parametric editor is working it displays for you a comp of what the recipe will create from your original image. Your original image is otherwise never altered. When you want an image to print or load on the internet you have the parametric editor export that for you by applying the recipe and creating a JPEG or TIFF image as a separate file.
A raster editor actually opens your image file and loads the pixels into memory where it can manipulate individual pixels. It gets confusing in that a good raster editor like PS can work at least partially parametrically. PS's smart filters for example. However a raster editor holds your original image in pixel form in memory and has the ability if you instruct it to overwrite your original.
Because a raster editor works by loading your original image in pixel form into memory it can't load and process raw files. If you try and open a raw file in PS it's sent to ACR where it opens. Adobe Camera Raw is not Photoshop proper and when you finish in ACR a pixel (raster) version of your image is created and passed over to Photoshop where it's loaded into memory for editing.
Two very different approaches with different capabilities.
Joe