![]() It’s very difficult to select RT-spot handles, especially for rectangular spots. I don’t know whether this is expected behavior, but it appears strange to me. Only 1 single ‘L ab* Spot created’ record is registered in the history, showing the ID-number of the last created spot. If multiple spots are created one after the other, without any other actions between those creations, there are no individual history records for each creation. the spot remains visible in the Preview window). If one changes the Visible-value manually in the pp3 file from true to false, the entry in the table will change from ‘Visible’ to ‘Invisible’, but it doesn’t have any impact (i.e. There is a ‘Visible’ attribute in the RT-spot table that seems to do ‘nothing’. So, next to the assumed ‘out-of-sync’ for the pp3-files, also the History seems to have synchronization issues with the Locallab module. they remain in the RT-spot table, and remain visible in the Preview window). 2 spots, and then you returns in the History to an action before the spot additions, those spots don’t disappear (i.e. It appears that the History is not synchronized with the create/delete actions in the table with RT-spots. Is this is problem with the build, or have these settings been eliminated? These parameters are not available in the Preference dialog of the latest build. In that same document, I read that it is possible to define a number of Locallab parameters via the Preference dialog box ('Show spot delimiters checkbox, default for ‘Global Quality’, …). As a test, I could create 510… Has the limit been removed? I found in the Local Lab Controls document on Rawpedia that there should currently be a (theoretical) limit at 500 RT-spots for one image. ![]() In its current status, I'm afraid that the Locallab version is not yet really suitable for 'normal' use. Unfortunately, as said above, I made the switch to Locallab only very recently, so I have no clue about how this worked in the 'mip'-era. in the RT-spot table, or via the UI of the Preview window), but I get the impression that this synchronization is not yet working properly (which can be a cause for many other problems of course). I don't know at which events the pp3 data should be synchronized with user actions (e.g. I've read somewhere that the RT-spot data has been ported recently from previous 'mip'-textfiles towards the regular pp3 files. When the system crashed, I tried to verify the Locallab data in the pp3 file, and I have the impression that the information about the RT-spots is not really in sync with what is visible in the UI. When the system crashes, it happens in 2 flavors: either Rawtherapee closes, of the active picture closes, but Rawtherapee remains active. I also noticed the following issues/problems: * I've witnessed many system crashes, especially when creating or deleting RT-spots (no pattern detected yet, seems a bit random, I will continue to search.). ![]() ![]() Unfortunately, I’ve not been very successful yet, and I encounter exactly the same problems as mentioned in the post above (right click behavior, switching between images whereby spots become visible in the other document, but not maintainable, …). I’ve used Rawtherapee for more than 2 years now (always the ‘official’ standard version), and, after the recent release of 5.5, I decided to start using the Locallab branch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |