Viveza 2 save file problems12/31/2023 The simplest solution is to make Viveza consistent with the other plugins. It may be trying to save to the old 0.9.5. It may not load due to memcard incompatibilities between playground and 0.9.5. Viveza should behave like the other plugins.Īctually, there’s a shared responsibility between iMatch (which doesn’t identify its own metadata as such), DPL (which exports to the Nik plugins without verifying that the file doesn’t contain metadata that could generate trouble in the plugins that DxO is also owning) and the user who has to decide whether he lets iMatch modify the RAW files (a practice that is well known for generating trouble when using multiple image processing applications). Have you tried removing the old memcard file, but not the savestates, and then save from a save point in the game using the states. Take for example the Shadow slider in Viveza 2. Part of the problem is that we tend to be victims of our own thinking. Even if you do use Viveza for your image adjustments, you might not be achieving the best results. So, there’s here an obvious consistency problem that should be fixed. This advanced plug-in for Lightroom and Photoshop is perfect for naturally enhancing your photographs. Viveza obviously reads these data and gets into trouble. Now, on the plugin side, we know that all Nik plugins with exception of Viveza are ignoring the iMatch data and accept the TIFF file. So, it has no good reason to remove whatever metadata are present in this file. It’ doesn’t know what will be done to the image file in that external app. DPL is “third-party application agnostic”, so to say. I doubt that they have written 2 different routines. ![]() The DPL export routine used to send an image to a Nik plugin is the same as the routine used to export to any other third-party application. So these data are received as general XMP data by external applications and this obviously a source of problems. Here again, we have an inconsistent behavior of Viveza in comparison with the other plugins which do not have this problem. This is enough for Viveza to reject the file as an unsupported file type. It should because these data are generated for its own use. This metadata field is transmitted to the TIFF file generated by DPL 3 when calling Viveza. The initial problem is that iMatch doesn’t identify the XMP data that it adds to the image metadata as iMatch specific. It’s just copying old xmp data to a new file during the conversion. For all I know (I haven't tested it), this might work with SOME other plugins also. However, if you've done anything in the Viveza window (even just a click) you first have to click on the top Viveza title bar to give it focus before the F key works. The "F" key toggles full screen on and off without changing the size of the X7 program. I don't suppose you know of a way to make the viveza plugin show full screen to at least increase the real estate?ĮDIT UPDATE: I just learned how to increase the size of the Viveza plugin when you open it in X7 on a Windows machine. ![]() Unfortunately, the problem then is that with large images you're only seeing a portion of the image. And when I set it to 33% that setting seems to stick for future use. Just ran across this thread, and it works as you say with X7, WIN 8.1 32 bit. I have tried this successfully on both my desktop and laptop and thank goodness it's finally fixed. Once you get it at 33% you'll see the opposite happen - the main screen shows the correct saturation while the Navigator screen becomes desaturated. Set the screen magnification to 33% (use the and toggles to set it). Jan Shim wrote:After years of frustration, I recently found a way to get images in Viveza 2 to display their actual saturation.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |