![]() Repeatedly saying this, but PNG or JPEG formats are for the final viewing image file. Select "FireAlpaca (*.mdp)" under "File Type" in the dialog window at saving. The file quality will get deteriorated.Īlways save a working file in "a dedicated format". JPEG (JPG) format - Layer information will be lost. A file size is larger than JPEG format. PNG format - Layer information will be lost. PNG and JPEG formats don't hold the layer information. These formats are only for "viewing an image", and are not suitable for drawing and saving an in-progress working image. Diagram: JPEG image shown in Windows Exploreīut, you will have a bitter experience if you save an image data in these formats only because you know of. These are the most popular formats that are available to view in Windows, Mac, Smartphone, or any standard apps. I am of course talking abou the tabket hardware compatibility table in the manual.An image file is a file that contains an image data. 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. Looking official adobe specifications, there’s currently 93 different image resource type across 11 Photoshop versions (3.0, 4.0, 5.0, 6.0, CS, CS2, CS3, CS4, CS5, CS6, CC)Īnd not even sure this specification is complete because ASL data seems to not be defined in this documentation.Ĭomparing produced files from Gimp and Krita, you might see that Gimp doesn’t export some information ?Īnd, basically, doing a such conversion KRA(Kirta) > ORA(Krita) > ORA(Gimp) > PSD(Gimp), you might have some information lost in the process (especially because ORA file don’t manage all Krita specificity)Īnother case could be, Gimp is not able to manage CMYK files, only RGB.įor example, if file has been produced from Krita as a CMYK 32bit float color space, converted to a 8bits RGB from Gimp that’s normal the size is smaller…īut that’s only an example, we don’t really know properties of your original file. PSD file format is a very complex file format, in which many many type of information can be stored. The psd’s i made with krita were roughly 30MB in size while the one’s i made in GIMP were less than 7MB!Ĭoncerning produced file size difference between Krita and Gimp, the. If it is a known bug are there any plans on fixing it? Seems like GIMP while also being open source has the better reverse engineered exporting algorithm so why not work from there? Is this a known bug? Because i couldn’t find another thread here with this topic ![]() Has anyone else tried exporting to *.psd with Krita and then tried opening it in other Software? None of the aforementioned Apps except GIMP are able to open *.ora files so that is only in theory a good option to share projects. I didn’t give up though and I was able to find a hot-fix!īy first converting the *.kra file into an *.ora file then opening that *.ora file in GIMP and then using GIMP to export the *.ora file into a *.psd file worked!Īnd before anyone mentions to use instead *.ora: Imagine if my client would have used FireAlpaca or Medibang while still working on their own other projects! They could have lost their work too! Only GIMP was able to safely open the *.psd I created in Krita! Instead of not opening, both of those Apps crashed immediately! The results were even more catastrophic with FireAlpaca and Medibang! I checked back by trying to open the *.psd i created with Krita in Gimp, FireAlpaca and Medibang. The client wanted to use it with Clip Studio Paint which to our dismay just refused opening it. I recently tried to transfer a drawing as *.png and *.psd file to a client as agreed so that they could still have access to layers and further work with the commission. I am using the Krita 4.4.1 64-bit stable build on Windows 10 Pro 64-bit Just to give some information on my System beforehand:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |