I often use the revert option while testing different filter and settings.
In this approach it speeds things up to record settings and rearrange them via macro. Does the Revert function reload the file from hard drive? I would think that a "Store" function to store a certain status of an image would enhance this philosophy. Reload.. An Image is restored to its initial state by reading the source file again from its location. Revert.. An image is restored to its first state after opening it or from a later stored/updated initial state. Maybe a feature request or only a thought.. Interested to hear about your thoughts. Best regards, Rainer -- Rainer M. Engel, Dipl. Digital Artist scientific|Media GbR Pichelsdorfer Str. 143 13595 Berlin -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Hi Rainer,
as far as I can say, 'Revert' in principle reads form the hard drive. But actually, files read recently are usually in the memory, either in the hard drive's cache or the disk cache of the operating system. So, unless the file is very big or there is a lot of disk activity, reading a file the second time will hardly access the hard disk and it will be much faster than reading it the first time. For the feature you suggested, you would need a third command, to store the present state. I think that this should not be done automatically on loading an image, as it may occupy a lot of memory for large images. A simple alternative: For trying things, I often duplicate an image (just press shift-D), and work on the copy. If I don't like the result of the test, I discard the copy and create a new copy. Michael ________________________________________________________________ On Mar 6, 2014, at 13:12, Rainer M. Engel wrote: > I often use the revert option while testing different filter and settings. > > In this approach it speeds things up to record settings and rearrange > them via macro. > > Does the Revert function reload the file from hard drive? > > I would think that a "Store" function to store a certain status of an > image would enhance this philosophy. > > Reload.. > An Image is restored to its initial state by reading the source file > again from its location. > > Revert.. > An image is restored to its first state after opening it or from a later > stored/updated initial state. > > Maybe a feature request or only a thought.. > > Interested to hear about your thoughts. > > Best regards, > Rainer > > > -- > Rainer M. Engel, Dipl. Digital Artist > scientific|Media GbR > Pichelsdorfer Str. 143 > 13595 Berlin > > -- > ImageJ mailing list: http://imagej.nih.gov/ij/list.html -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Hi Michael,
I do it the same way you described, having a second macro which modifies the new duplicate to the state I'm working with further on.. As I wrote "storing" a wanted state would be necessary and of course this may harm your available RAM. But having nothing stored would result in the way that revert and reload are basically the same. So nothing should be stored right away. I think this would speed up some filter testing, but you are right that there are ways to get around with it and they are not bad. This can be automated with only a few lines of macro. By the way isn't duplicating an opened image not again like storing a distinct state of the source image in the first place (speaking in terms of RAM)? I think that duplicating is some sort of similar and sometimes slower in my practice, since the duplicate would have to be brought to a state I want again. Thanks for your thoughts, Michael. Rainer Am 06.03.2014 19:30, schrieb Michael Schmid: > Hi Rainer, > > as far as I can say, 'Revert' in principle reads form the hard drive. But actually, files read recently are usually in the memory, either in the hard drive's cache or the disk cache of the operating system. So, unless the file is very big or there is a lot of disk activity, reading a file the second time will hardly access the hard disk and it will be much faster than reading it the first time. > > For the feature you suggested, you would need a third command, to store the present state. I think that this should not be done automatically on loading an image, as it may occupy a lot of memory for large images. > > A simple alternative: > For trying things, I often duplicate an image (just press shift-D), and work on the copy. If I don't like the result of the test, I discard the copy and create a new copy. > > Michael > ________________________________________________________________ > On Mar 6, 2014, at 13:12, Rainer M. Engel wrote: > >> I often use the revert option while testing different filter and settings. >> >> In this approach it speeds things up to record settings and rearrange >> them via macro. >> >> Does the Revert function reload the file from hard drive? >> >> I would think that a "Store" function to store a certain status of an >> image would enhance this philosophy. >> >> Reload.. >> An Image is restored to its initial state by reading the source file >> again from its location. >> >> Revert.. >> An image is restored to its first state after opening it or from a later >> stored/updated initial state. >> >> Maybe a feature request or only a thought.. >> >> Interested to hear about your thoughts. >> >> Best regards, >> Rainer >> >> >> -- >> Rainer M. Engel, Dipl. Digital Artist >> scientific|Media GbR >> Pichelsdorfer Str. 143 >> 13595 Berlin >> -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html |
Free forum by Nabble | Edit this page |