PhaseOne could sort things out by ...
... simply extending the option to override rendering. I am talking about for those of us that use alternative tools such as NX.
The problem with things now is that you are forced to view things using PhaseOne's rendering which is not welcome as a non-C1 user.
There is already the "Use built-in Thumbnail (if available)" option which actually shows the NX edits as a thumb and what is needed is a "Use built-in Preview (if available)" option to go with this.
With this, support for alternative tools will be restored as this selecting this along with the thumb option will display the edits from the preview and everybody stays happy.
For an NX user like me, MP will display the NX thumb (as it currently does) and the NX full size preview in such a case.
The current option to use the embedded preview works fast and would be OK, if it didn't first render this differently and just used whatever is there. I can understand that some might want it rendered (ie. behave as it currently does, but adding an option to skip the rendering done here can't be a big ask can it?
At the moment, I have the strange situation where, since I have set it up to always use the embedded thumb, I get the NX generated thumb but once I click through to a full sized version, I get something totally different.
Watching my language, I just have to shake my head and wonder what sort of person decided this is a workable option by any stretch of imagination.
Knowing that the people at PhaseOne can't be idiots, the only conclusion possible is that only the needs of C1 users were on the table at development stage and the fact that there is a healthy number of non-C1 users just did not register as much as it should have done.
I can see that a developer testing the concept within a C1 setup would have seen no issues at all.
"Select use thumb" => "Fine, thumb shows OK"
"Select create previews" => "Fine, loads fast and shows preview consistent with thumb"
"Conclusion" => "Everything is fine and passed for implementation"
I can't imagine anyone working at PhaseOne doing this as would have had to be if users of alternative tools were considered ...
"Select use thumb" => "Fine, thumb shows OK"
"Select create previews" => "Fine, loads fast but shows totally different preview from what thumb shows"
"Conclusion" => "Everything is fine and passed for implementation"
The question now is whether MP is going to become just a DAM for C1 users. Nothing wrong with this but it sure would be nice to know so people can cut their losses and make decisions accordingly.
I would like to think this oversight on the previews can be rectified quickly ... as in, the very next release.
We shall see.
The problem with things now is that you are forced to view things using PhaseOne's rendering which is not welcome as a non-C1 user.
There is already the "Use built-in Thumbnail (if available)" option which actually shows the NX edits as a thumb and what is needed is a "Use built-in Preview (if available)" option to go with this.
With this, support for alternative tools will be restored as this selecting this along with the thumb option will display the edits from the preview and everybody stays happy.
For an NX user like me, MP will display the NX thumb (as it currently does) and the NX full size preview in such a case.
The current option to use the embedded preview works fast and would be OK, if it didn't first render this differently and just used whatever is there. I can understand that some might want it rendered (ie. behave as it currently does, but adding an option to skip the rendering done here can't be a big ask can it?
At the moment, I have the strange situation where, since I have set it up to always use the embedded thumb, I get the NX generated thumb but once I click through to a full sized version, I get something totally different.
Watching my language, I just have to shake my head and wonder what sort of person decided this is a workable option by any stretch of imagination.
Knowing that the people at PhaseOne can't be idiots, the only conclusion possible is that only the needs of C1 users were on the table at development stage and the fact that there is a healthy number of non-C1 users just did not register as much as it should have done.
I can see that a developer testing the concept within a C1 setup would have seen no issues at all.
"Select use thumb" => "Fine, thumb shows OK"
"Select create previews" => "Fine, loads fast and shows preview consistent with thumb"
"Conclusion" => "Everything is fine and passed for implementation"
I can't imagine anyone working at PhaseOne doing this as would have had to be if users of alternative tools were considered ...
"Select use thumb" => "Fine, thumb shows OK"
"Select create previews" => "Fine, loads fast but shows totally different preview from what thumb shows"
"Conclusion" => "Everything is fine and passed for implementation"
The question now is whether MP is going to become just a DAM for C1 users. Nothing wrong with this but it sure would be nice to know so people can cut their losses and make decisions accordingly.
I would like to think this oversight on the previews can be rectified quickly ... as in, the very next release.
We shall see.
0
Post is closed for comments.
Comments
0 comments