Details profiles in build 2533
-
- Posts: 1194
- Joined: 10 Jul 08 13:18
Details profiles in build 2533
Since updating to build build 2533, applying a Details profile to one image doesn't apply all the changes. If I select multiple images, all of the changes are applied. Beware that it might be the same on your system.
Windows 10
Windows 10
Re: Details profiles in build 2533
Just came back from a vacation importing hundreds of images and I have problems applying detail profiles while importing images
PSUServer 2024.x, PostgreSQL 12.x
My homepage http://www.michaelweidner.com
My homepage http://www.michaelweidner.com
Re: Details profiles in build 2533
V3.3 contains many fixes in detail profiles. Best to recreate your profiles when your old ones don't work anymore.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
-
- Posts: 1194
- Joined: 10 Jul 08 13:18
Re: Details profiles in build 2533
Does saving the profile to a file with a different name constitute recreating it?
Re: Details profiles in build 2533
Will try and report back here...
PSUServer 2024.x, PostgreSQL 12.x
My homepage http://www.michaelweidner.com
My homepage http://www.michaelweidner.com
Re: Details profiles in build 2533
same issue with the newly created profile...
I will email my profile to support and a screenshot
I will email my profile to support and a screenshot
PSUServer 2024.x, PostgreSQL 12.x
My homepage http://www.michaelweidner.com
My homepage http://www.michaelweidner.com
-
- Posts: 1194
- Joined: 10 Jul 08 13:18
Re: Details profiles in build 2533
I saved the profile to a newly named file and the problem remains.
I'm not a programmer or a technologist of any kind, but it stymies me after months of beta testing that changes that were designed to improve the program resulted in making it worse at least in some areas.
I'm not a programmer or a technologist of any kind, but it stymies me after months of beta testing that changes that were designed to improve the program resulted in making it worse at least in some areas.
Re: Details profiles in build 2533
The profile should be recreated. Delete the old file and create a new one from scratch. If used in a download profile, create a new download profile.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: Details profiles in build 2533
Download profile too? Well, that is not very convinent...
I have several DL profiles, Detail profiles...
I am not venting, but I just came from vacation (combination of three different cameras, five profiles and thousands of images)
I have several DL profiles, Detail profiles...
I am not venting, but I just came from vacation (combination of three different cameras, five profiles and thousands of images)
PSUServer 2024.x, PostgreSQL 12.x
My homepage http://www.michaelweidner.com
My homepage http://www.michaelweidner.com
Re: Details profiles in build 2533
[OFF_TOPIC}
(It would be interesting to know how many people participated in the beta and how many reported bugs. Btw, I applaud Hert's beta initiative and I'm sorry I couldn't join it, due to pressing issues.)
OTOH, if the reuse of existing profiles was a known (potential) issue, a brief note of caution in the release notes and in the forum would have been good.
I appreciate that's paradoxical and frustrating, but I can tell you (as a technologist of some kind) that thoroughly testing an application as complex as Supreme is notably challenging.Mike Buckley wrote: I'm not a programmer or a technologist of any kind, but it stymies me after months of beta testing that changes that were designed to improve the program resulted in making it worse at least in some areas.
(It would be interesting to know how many people participated in the beta and how many reported bugs. Btw, I applaud Hert's beta initiative and I'm sorry I couldn't join it, due to pressing issues.)
OTOH, if the reuse of existing profiles was a known (potential) issue, a brief note of caution in the release notes and in the forum would have been good.
-
- Posts: 1194
- Joined: 10 Jul 08 13:18
Re: Details profiles in build 2533
Agreed.vlad wrote: OTOH, if the reuse of existing profiles was a known (potential) issue, a brief note of caution in the release notes and in the forum would have been good.
Re: Details profiles in build 2533
I did that and the issue still exists...Hert wrote:The profile should be recreated. Delete the old file and create a new one from scratch. If used in a download profile, create a new download profile.
PSUServer 2024.x, PostgreSQL 12.x
My homepage http://www.michaelweidner.com
My homepage http://www.michaelweidner.com
Re: Details profiles in build 2533
Perhaps it is helpful if I provide some background info on this:
Because this is the first version that natively supports the DarwinCore I did quite a bit of beta testing. I experienced a lot of issues with my previous profiles, but assumed that was because I was using my previous "corrupted" profiles. FYI - migrating to PSU from IDI I noticed that complex, structured custom profiles were not fully portable from IDI to PSu. With my imported IDI profiles PSu was corrupting my metadata. I am now still working to fix thousands of files. Clearly PSU is not to blame, I should have noticed earlier that my IDI custom profiles were not working.
Now: I did a lot of testing and I had to re-create ALL my profiles, which was quite a bit of work. I still experience some issues with using macro-codes for copying content, but assumed this was because my profiles had been corrupted. Reading your comments here now, I believe there might still be some things amiss. I have not been using the importer a lot, because the migration process took up so much room. So I have not had the opportunity, for example, to test if profiles work with importing...
Of course I have no idea, who else downloaded and used the beta and reported back to Hert. I am sure though that Hert was convinced these issues had been resolved, when he released version 3.3.
Because this is the first version that natively supports the DarwinCore I did quite a bit of beta testing. I experienced a lot of issues with my previous profiles, but assumed that was because I was using my previous "corrupted" profiles. FYI - migrating to PSU from IDI I noticed that complex, structured custom profiles were not fully portable from IDI to PSu. With my imported IDI profiles PSu was corrupting my metadata. I am now still working to fix thousands of files. Clearly PSU is not to blame, I should have noticed earlier that my IDI custom profiles were not working.
Now: I did a lot of testing and I had to re-create ALL my profiles, which was quite a bit of work. I still experience some issues with using macro-codes for copying content, but assumed this was because my profiles had been corrupted. Reading your comments here now, I believe there might still be some things amiss. I have not been using the importer a lot, because the migration process took up so much room. So I have not had the opportunity, for example, to test if profiles work with importing...
Of course I have no idea, who else downloaded and used the beta and reported back to Hert. I am sure though that Hert was convinced these issues had been resolved, when he released version 3.3.
Re: Details profiles in build 2533
Frank, I am frankly very surprised (impressed) that Hert implemented full suport for DarwinCore. You can count yourself lucky - or incredibly persuasive! (May we hire you as a lobbyist for other features? ) Here would be some fun trivia: how many people use DC in general and how many benefit from it in Supreme?fbungarz wrote: Because this is the first version that natively supports the DarwinCore I did quite a bit of beta testing.
I'm wondering if a script for automatically recreating profiles would be feasible. Maybe not (too complex or unreliable?)Now: I did a lot of testing and I had to re-create ALL my profiles, which was quite a bit of work.
Re: Details profiles in build 2533
Yes, I know. I have been using IDimager products for decades now. So, I guess we go way back. And: we had our ups and downsFrank, I am frankly very surprised (impressed) that Hert implemented full suport for DarwinCore. You can count yourself lucky - or incredibly persuasive!
I have a had time accepting the transition from IDI to PSu, when some of its features critical to my workflow were no longer supported. But now PSu has matured so much, that it has become a far better product than IDI ever was. I think, a lot of programmers would have become quite fed up by my criticism. Instead Hert provided solutions that worked and I do give him a lot of credit for this!
Well, if you want some trivia: Millions of people use DC, which stands for the DublinCore and was one of the first, if not the first, metadata standards ever established. I guess you were referring to the DarwinCore (DwC) though, which indeed targets a bit of a niche audience (scientists working with natural history collections), though I do hope it'll grow. ExifTool fully supports it already, some Linux software too, and now PSu.Here would be some fun trivia: how many people use DC in general and how many benefit from it in Supreme?