Skip to main content

Import and presets / nonoise

Comments

14 comments

  • Rick Sammartino Community moderator

    If you're in Browse and apply a Preset to a photo you should see that preset being applied within a few seconds, so if you apply a Preset during Import, it should also be applied and visible in Browse.

    As for NoNoise, it's not viewable in Browse anyway. The only place it's active is in Edit so while you can apply a preset containing NoNoise at any time you won't see any change until after going into Edit.

    0
  • Joshua Able

    Yes, but the preset isn't being applied during import, and then, when I select a photo to edit the preset and NoNoise run at that time..

    It's a pain to sit and wait for an image to come up when it should have had all the things done at import.

    At least if I can get NoNoise to not run until I tell it to, since it doesn't run at import... then that would help..

    -1
  • Brian Lawson Community moderator

    The applied preset has to be rendered before you will be able to see its affects on your image. The Importer doesn't call the renderer, the Browser and Editor do.

    Don't think of them being "run", that's a misnomer that leads to unfulfilled expectations. They are applied during import but rendered later.

    0
  • Joshua Able

    Then what's the point of importing any photos with a preset? This makes zero sense.

    It's faster to open a image and then do the edits than it is to deal with presets.

    By the time I get a chance to even see the image in "edit", I could have edited 3 photos in Lightroom, this can't be the way On1 is supposed to run.

    0
  • Rick Sammartino Community moderator

    Import isn't intended to be an Editor, all you do there is organize your photos by renaming, add metadata or presets if you want to. When you view the photo in Browse, that's where the photo will have the Preset  applied.

    You don't actually need to use import at all, you could just select your photos in Browse and apply the preset right there.

    1
  • Joshua Able

    Then it's meaningless to apply the preset at import, since as you say, it doesn't get applied. As I stated above. It's faster to do the exact same edits as the preset, once you go to editor.

    What's the use of even importing at this point? Can I just load images to edit directly from my harddrive without importing them?

    0
  • Rick Sammartino Community moderator

    It does get applied, it just doesn't get rendered.

    As i posted above, you don't need import at all. Once your photos are on your drive, just view them in Browse and apply presets there if you want to.

    0
  • Brian Lawson Community moderator

    All the importer does is copy the files from your SD card (or wherever) to a new location, applying the preset in the process. If it had to render each image the import would take much longer and users would complain about how slow that is. The tradeoff has to be made somewhere and from a design perspective it makes sense to keep the copying separate from the rendering which is already being handled by other other modules.

    0
  • Joshua Able

    I would much rather have it happen at import than to wait while.it does it when I want to work on the image... Also, it's faster to do it on my own than to allow the preset to do it at that time.

    Really. I sit here with a book and read a couple pages between the slow exports and the "presets".

    On1 is extremely slow, there has to be a way to make it work decently.

    0
  • Brian Lawson Community moderator

    On my system most exports happen faster than I can move from the folder containing the photo to the one holding the exported version.

    Have you added an SSD for ON1's Scratch space and the PerfectBrowseCache? It makes a significant difference in the program's performance. See Moving Scratch and Cache for an in-depth discussion on the why's and how's.

    0
  • Joshua Able

    The HD is an SSD, Lightroom was fast On1 was ...not.

    0
  • Brian Lawson Community moderator

    Lightroom and Photo RAW do not work the same way. That is a false analogy.

    It does not matter that your boot drive is an SSD. If you'd bother to read the article you'd learn it's all about separating the program's most heavily used I/O channel from all the other background I/O that is happening at the same time. I'm not interested in repeating myself on this subject again. Please go read the article before commenting about how it doesn't matter.

    -1
  • Joshua Able

    So the plan is to spend MORE money even though my system meets or beats the system requirements.

    Yeah, no.

    How about they just make the program so it actually functions as advertised?

    As for the "Lightroom and photoraw don't work the same way", that's clear. They accomplish the same thing, but one is fast and one is slow.

    0
  • Brian Lawson Community moderator

    there was a comment from another user on Facebook just today about how much faster Photo RAW is on his system than any of the other software he uses including Lightroom.

    I'm not going to argue with someone who clearly has more interest in complaining than fixing the problem. Do it or don't. Use whatever program you choose. Don't complain to people who are trying to help.

    Obviously you still haven't read the discussion. And I have to tell you, that $80 it cost me for my SSD was a real killer, drove me right into bankruptcy. You've spent more than that in the cost of your time in this discussion.

    -2

Please sign in to leave a comment.