file:///Applications/Filmulator.app/Contents/Resources/qml/filmulator-gui/Import.qml:119:13: QML Connections: Cannot assign to non-existent property "onEmptyDirChanged"
objc[20602]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9f27a1d0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1102f5dc8). One of the two will be used. Which one is undefined.
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
libc++abi.dylib: terminating with uncaught exception of type Exiv2::BasicError<char>: tiff directory length is too large
And this is recent trying to import a folder with misc raws:
Warning: Exif tag Exif.NikonPreview.JPEGInterchangeFormatLength not encoded
Warning: Exif IFD NikonPreview not encoded
importFile SearchID: 2590b0a6f2ee3606890824629e6ffcc20001
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.
libc++abi.dylib: terminating with uncaught exception of type Exiv2::BasicError<char>: tiff directory length is too large
I see what I needed to do is update more things… and I am trying to figure out how libraw19’s install names got changed. Thanks for testing…
We’re having a network outage here so it might be a few more hours until the fixed one can be uploaded.
Imported the dreaded misc raw folder into filmulator b3, and without a hickup all went in… RAFs and ORFs!!! included; so SUPER )) (( Thank you kindly
@CarVac I’m a bit confused; when CA correction is orange (slider to the right) it is off, right?
Also, those pink HL need to:
disappear
or be able to change colour, then is a “choice” from the developeer {read with frozen duck acent} and so an autistic, I mean artistic choice; le attitude - pic below
do a beautifully nothing
And thank you for porting filmulatrix to mac, one more program to torture, jua jua jua
{cheap electronic echo}
OT: as a curio, the image right above does not exist anymore; absolutely nothing to do with filmulator; human error; I synced the wrong direction and lost ~100 already culled images… thank god I realised and stopped; could have been worse… and two hard boiled eggs
CA correction is active when orange and off when gray.
I’m working on highlight reconstruction at the moment. The function in RawTherapee seems to be a bit less standalone than the demosaicing ones are.
I plan to have a 4 step slider: no highlight recovery with post-WB clipping, turn off clipping so that you can get the most out of a raw file with no raw channels clipped, recover one clipped channel, and recover two clipped channels.
Currently it’s in the second mode: if you don’t clip your highlights it’ll give you the full range of highlights captured by your camera; if you have a deep red subject you’ll likely have no clipped channels at all as long as the green channel isn’t clipped.