I already spent two days in analyzing this issue and I'm willing to help to provide more information, if I can. I went back to Lightroom Classic 11.3.1, where everything works fine in the same scenario. I can reproduce these issues in 100% of all cases when exporting several thousand images. Then obviously you also can't stop the export via the X button. In some cases it sends a crash report (which I submitted under my info(at)LRTimelapse email address) in some cases it just closes.Īnother scenario that I observed a couple of times is that the plugin stops logging and updating the progressbar but the export actually continues in background (filling up the export folder). With 4000 images for example, often after 10 images Lightroom closes. The more images I export, the faster and more often the crash happens. This simple plugin, also crashes when used to export several thousand images, you can use it to reproduce the issue: To exclude the chance of any programming errors in my rather complex LRTExport plugin, I coded a very simple, basic custom export plugin. The system cannot find the file specified The Visual Preview is still getting loaded, but very very slowly (I do have 576 images in this timelapse, but still. I could reproduce the reports from my users on my machine (Windows 10), latest NVidia drivers, etc. There is no problem, with shorter sequences of several hundreds of images, as it appears. This happens on Windows and Mac machines. Symptom: Exporting sequences of multiple thousand images via a custom export plugin consistantly makes Lightroom Classic 11.4 (and later prereleases) crash. But they do have a downloadable API, the SDK, that allows anyone with the appetite for such things to access the contents of the catalog in a programmatic way.This issue was reported to me by multiple LRTimelapse users that use my LRTExport Lightroom Plugin to export their timelapses. I think its the case that Adobe don't openly document the format of the Lightroom catalog. There's an interesting middle ground in things like the Lightroom SDK. Examples of closed file formats that have been reverse engineered by third parties include Microsoft's Office files, and the SMB file access protocol. This is a process that is fraught with both technical and occasionally legal difficulties. This forces programmers who wish to fondle a file contents to reverse engineer the data. In contrast, a closed standard would be one in which the binary file format is not publicly available. And any reasonably competent programmer ought to be able to read Adobe's spec., and produce such an API library. The unit also uses a different compression. Similar APIs would be needed by programmers in C, Lua, COBOL or anything other language you can think of. This happens because the raw files not full resolution are not of the actual raw files. That's as open as it gets.Ī Java API is a programming library written in a specific language that provides a method for a Java programmer to access the file without their having to read the actual spec. Here's my evidence.Īdobe will tell you the binary format of a DNG file. I suppose I should get on some Adobe forums next but I'm interested to hear any comments you folks might have. I hate to be ringing alarm bells but I do find it curious and slightly disconcerting. The software's pretty clever and I'm inclined to think his problem is real. Unfortunately Adobe doesn't provide a proper Java API." Unfortunately I couldn't manage to find a way to read / write metadata from / to DNG. thats a good idea, and I suppose it would work, if LRTimelapse were able to work with DNG. I found the following remark from the developer via the forum: I tried a great piece of software currently in beta called LRTimelapse and was surprised to discover it did not work with DNG. So I was quite surprised to find an example of DNG not being completely open: I keep backups of the CR2 but look forward to the ISO and manufacturers all coming together to stop the proprietary RAW madness(drip drip). I've always liked the idea of DNG and have adopted it, converting all my CR2 files on import.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |