The 5th beta test of Filmulator 1.0.0 for macOS 10.10+ is here.

---- This is still for the b1 ----

A couple CLI’s output; this is like 1 month old:

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

 

---- This is still for the b2 ----
@HIRAM I get exactly the same dialog as above The 5th beta test of Filmulator 1.0.0 for macOS 10.10+ is here. - #4 by chroma_ghost also same CLI output. Mojave 10.14.1 and Filmulator_1.0.0b2

@chroma_ghost multi page tiff perhaps? They are not yet supported by Exiv2. http://dev.exiv2.org/issues/1124

They tried the new one and now it crashes on startup:

Termination Reason:    DYLD, [0x1] Library missingApplication Specific Information:
dyld: launch, loading dependent librariesDyld Error Message:
 Library not loaded: /opt/local/lib/libraw_r.16.dylib
 Referenced from: /Users/USER/Desktop/Filmulator.app/Contents/MacOS/filmulator
 Reason: image not found

Yes I forgot to unrevert my libraw. Am fixing.

Application Specific Information:
dyld: launch, loading dependent librariesDyld Error Message:
 Library not loaded: /opt/local/lib/liblcms2.2.dylib
 Referenced from: /Users/ccurzio/Desktop/Filmulator.app/Contents/Frameworks/libraw_r.19.dylib
 Reason: image not found

:point_up: same

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.

HOW OUTrAGEous!!! :stuck_out_tongue_winking_eye:

 
 

{ here intro text}… and two hard boiled eggs

 

 
PS
Meanwhile, I’ll be hidden under the bed

When you get a chance, I updated the Macstack branch to support Fuji X-Trans.

Ok, @CarVac @chroma_ghost the latest edition is finally here! Sorry about the delay.

[old link removed]

Updated filmulator-gui and librtprocess

2 Likes

Imported the dreaded misc raw folder into filmulator b3, and without a hickup all went in… RAFs and ORFs!!! included; so SUPER )) :+1::+1: (( 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:

  1. disappear
  2. 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
  3. 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

 


Images used for artistic connotation only

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.

1 Like

They’re now having a different exiv2 error.

0   libsystem_kernel.dylib            0x00007fff6dc00b86 __pthread_kill + 10
1   libsystem_pthread.dylib           0x00007fff6dcb6c50 pthread_kill + 285
2   libsystem_c.dylib                 0x00007fff6db6a1c9 abort + 127
3   libc++abi.dylib                   0x00007fff6b1ec231 abort_message + 231
4   libc++abi.dylib                   0x00007fff6b1ec3b5 default_terminate_handler() + 241
5   libobjc.A.dylib                   0x00007fff6c9f5c8f _objc_terminate() + 105
6   libc++abi.dylib                   0x00007fff6b1f7dfe std::__terminate(void (*)()) + 8
7   libc++abi.dylib                   0x00007fff6b1eb86e __cxa_rethrow + 99
8   libobjc.A.dylib                   0x00007fff6c9f3b6e objc_exception_rethrow + 40
9   com.apple.CoreFoundation          0x00007fff408e0ac3 CFRunLoopRunSpecific + 618
10  com.apple.HIToolbox               0x00007fff3fb79b35 RunCurrentEventLoopInMode + 293
11  com.apple.HIToolbox               0x00007fff3fb79774 ReceiveNextEventCommon + 371
12  com.apple.HIToolbox               0x00007fff3fb795e8 _BlockUntilNextEventMatchingListInModeWithFilter + 64
13  com.apple.AppKit                  0x00007fff3de35eb7 _DPSNextEvent + 997
14  com.apple.AppKit                  0x00007fff3de34c56 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362
15  com.apple.AppKit                  0x00007fff3de2ecb9 -[NSApplication run] + 699
16  libqcocoa.dylib                   0x000000011408da8d 0x114064000 + 170637
17  org.qt-project.QtCore             0x00000001104590a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418
18  org.qt-project.QtCore             0x000000011045dc62 QCoreApplication::exec() + 402
19  filmulator                        0x000000010f42b4dd main + 3133
20  libdyld.dylib                     0x00007fff6dac208d start + 1

I wonder if this is a qt thing, and if going to 5.12 might fix it… there are issues with macos dark mode…

Yeah, that stack trace doesn’t mention exiv2 at all unlike the earlier ones.

Qt 5.12 is coming out later this month? I should probably test the beta…

edit: unlike 5.11 which required some changes, 5.12 seems to work just fine.

@CarVac @chroma_ghost

Here is a build with qt5.12.0b4
https://filebin.net/8fvnlsbl8tjuhqxt/Filmulator_1.0.0b4.zip?t=60u1hhyb
Out of the box Qt 5.12.0b4 comes compiled for 10.12 using the 10.14 sdk.
So this build is limited to macOS ≥ 10.12

1 Like

It looks like qt5.12 depends on NSNotificationName which only shows up in macOS version 10.12 and higher.

It seems that this new version didn’t change anything.

The stack trace is the same save for a few of the offsets.

@CarVac or @chroma_ghost could you get the output in Mojave for

QT_DEBUG_PLUGINS=1 /Applications/Filmulator.app/Contents/MacOS/filmulator-gui

Thanks

FL_QT_DEBUG_PLUGINS_out.txt.zip (2.4 KB)