Still not fixed, jpg and png files are read & written in 4KB chunksĪd 9. Confirmed fixed, "List" view works as intendedĪd 8. I didn't check if you changed it or not.Īd 7. Still no information ANYWHERE that it doesn't support converting animated gif to animated webpĪd 6. Not fixed, XnView just crashes, i sent you a crash reportĪd 5. XnViewMP portable asks where to store ini and other files on first run. It adds very small delay to overall conversion process, but it's negligible.Īd 3. Confirmed fixed, but there is one small issue, just after writing the resulting file, xnconvert opens and closes source file multiple times before it removes it (You can see this in Process Monitor). Just add lots of debug logging to that part of your code and let me test itĪd 2. Not fixed, I told you to make me some debug build. This isn't really a very big issue since most of the time we are limited by cpu speed, but writing files in small chunks is just not a good practice. You can see this in that screenshot above, Write operations write to that file in 4096 bytes chunks. When saving files to disk they are written in "4 KB" chunks. Can you add "simple" list view so it will not load details and thumbnails when adding files?Ĩ. When I added 40000 files it took about 1 minute to load them to the table with 1 thread, but after they were loaded it started using 2 threads for about 4 minutes with ram usage slowly rising to 1.5 GB to load thumbs and details. Output log should display errors at the end. There is no information that it doesn't support converting gif to animated webp.Ħ. It will cancel conversion without any confirmation!ĥ. Pressing Esc key closes XnConvert regardless of what it is doing. Portable version stores ini in AppData\Roaming\XnConvert\xnconvert.ini.Ĥ. This is so wrong! You can't remove source file before writing destination file, what if there was some error during write operation (bad sector, device removal, etc)? You loose the source file.ģ. After this you can see creating new png file and writing to it. After that file is closed (CloseFile operation) so Windows immediately removes that file. First the whole source file is read to memory (not shown here), then it clearly shows that webp file is accessed (CreateFile operation) with intent to remove it (Desired Access: Delete, Delete On Close).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |