Firealpaca vs clip studio paint8/23/2023 ![]() In other words, even Adobe products can’t read all PSD files properties.įor more information, see Help for the specific Adobe applications.Īnd Adobe ask you to read doc of (Adobe) software on which you import PSD file to determinate what is or is not compatible… ![]() For more information, see Help for the specific Adobe applications.Īs you can see, most of Adobe product can directly import PSD files and preserve many Photoshop features. ![]() Because of the tight integration between Adobe products, other Adobe applications, such as Adobe Illustrator, Adobe InDesign, Adobe Premiere, Adobe After Effects, and Adobe GoLive, can directly import PSD files and preserve many Photoshop features. Photoshop format (PSD) is the default file format and the only format, besides the Large Document Format (PSB), that supports all Photoshop features. IMO that is better than just explaining how and why it won’t ever be 100% compatible. Some pointers of where to look can go a long way when desperately needing to use psd. That way people can at least check if that is the problem and have a better starting point to fix a problem? How about including a line about how anything higher than 8bit can cause issues? That’s like saying “For some reason Americans are still like using the imperial system instead of the metric system” Right now the extract about *.psd feels more like a non-liability clause of how Krita isn’t responsible for any compatibility issues arising from using that format.įor some reason, people like to use it as an interchange format, even though it is not designed for this. That’s just closing off your eyes to the reality of the given situation just because in theory it shouldn’t be a standard in the first place, but it is what it is.Īt least a trouble shooting guide on what to look out for that isn’t just “use ORA, lol” would help. Not acknowledging the fact that *.psd is being used as an exchange file standard even though it technically isn’t one doesn’t help anyone! I still think that having at least some information about known compatibility issues is better than nothing or at least give some pointers on what to try if a problem like this arises. So what is stopping us fron starting something similar with psd compatibility? I am of course talking abou the tabket hardware compatibility table in the manual. Personally i wouldn’t have looked at wikipedia for this information so a hint like that would be helpful in the manual too!Īlso it’s not like we don’t have something like compatibility table already in the manual! I have have heard ppl (friends even) drop krita for less critcal reasons and if we already have this knowledge, why not use it as a start for something that grows over time into a database that is centralised in the manual or at least link that compatibility chart you found on Wikipedia in the manual. The more stream lined it is to find a solution for such problems the better! While i agree that it isn’t necessarily Kritas job to watch out for other softwares short comings, trouble like this can result in users abolishing krita over paid software simply because of the still widely spread belief that open source software isnt ready for doing serious work.īeing able to adapt to your clients wishes without doing hours of research in forums but instead being able to look up a solution in a manual is part of that.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |