![]() ![]() ![]() I think after the paid alpha and beta tests(Luminar 4 and Lumniar AI) and the really big amount of community requests for specific features, we finally get the full product - but with no backward compatibility. LUMINAR 4 VS LUMINAR AI VS LUMINAR NEO FULL This forces us to buy or templates again. I think this is nothing more or less than a hidden subscription model. No one at Skylum can tell me that it is not possible, to give us a converter for existing templates or make them compatible with Luminar NEO. There was the same procedure for Luminar 4 and Luminar AI.Īnd when Luminar NEO is based on the predecessors Luminar AI, why should the AI templates not work with Luminar NEO? A converter must already exist, because installed templates will migrate to Luminar NEO. In my experience, and to put it simply, only an internal adaptation of the function calls and the paramerter transfer would be required. Similarly, the templates of Luminar 4 were changed when importing to Luminar AI, which can also be seen very nicely in the source code of the templates in the direct comparison. You can even modify templates internally or create new ones in this way. The next issue will arise, when the new core engine is just another version of the chromium engine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |