Thanks for all your help!
1 Like
No problem / congratulations on a successful 15 day mac 
port. Hopefully someone nails down a good bug or two with macOS Filmulator 1.0.0b1 
1 Like
Thank you guys!! 
GT’s dialog between a cat and a grill was supeb, didn’t understand a thing but nevertheless.
Filmulator does not start in 10.14 (mojave), I’ll try later in 10.11 (capitan)
when trying execs got this
$ /Applications/Filmulator.app/Contents/MacOS/filmulator
dyld: Library not loaded: @rpath/libiomp5.dylib
Referenced from: /Applications/Filmulator.app/Contents/MacOS/filmulator
Reason: image not found
--------------
$ /Applications/Filmulator.app/Contents/MacOS/filmulator-gui
dyld: Library not loaded: /Users/tune/librtprocess/build/librtprocess.dylib
Referenced from: /Applications/Filmulator.app/Contents/MacOS/filmulator
Reason: image not foundYou downloaded before I could update. Just had built librtprocess but macdeployqt had no idea where to find it. 
updated build above
Try this, it should work… If running from a console, execute Filmulator.app/Contents/MacOS/filmulator-gui unless you have exported the environment variables set in filmulator-gui. The binary gets renamed to filmulator for the reason we have to pass a few variables to the app. Another way is thru the Info.plist although there is no input plist for qmake bundling yet.
2 Likes
Just as a note to those trying it right now: highlight rendering is not final and the highlight recovery slider does not operate at all; I still need to add highlight reconstruction to librtprocess.
It also does not support X-Trans at this time; that also needs to be added to librtprocess and properly handled in Filmulator.
It’s only version 1.0.0 because it’s a breaking change in that images may turn out differently from previous versions, not because it’s finished.
2 Likes
the Filmulator-1.0.0b1-2 did the trick, CLI not needed 
{little confession} I’ve always wanted to use a slider called drama 
I’ve got sooooo many questions… but I’ll will explore thsi new planet for a bit first.
Merci once again, great work guys!!!
PS
Bkgd image (released under the CC BY-NC-SA license). is @Carmelo_DrRaw 's ; you can find it here Macro Photography - PHOTORAMA
and within pixls, here - Show your best Macro shots! 
3 Likes
You are most certainly not alone, experiencing this!
3 Likes
Word.
I just fixed an infinite loop that occurs when you change the CA Correct switch or the Highlight Recovery slider. Although highlight recovery still does nothing.
1 Like
Can someone test this on Mojave? Someone I know is trying it but it’s crashing in exiv2, after writing JPEGs, upon trying to write metadata to the files.
1 Like
I’m in latest mojado, 10.14.1 and Filmulator seems to export ok both tif and jpg. Tested it with a CR2, RW2, ARW, ORF (crashed the app) and DNG, RAF and NEF. I would not say the app is super stable but once the file is enqueued, it exports it right away.
What else do you need to be tested @CarVac?
For this person it was refusing to complete an import because it couldn’t write metadata to the JPEG thubnail; upon rebooting Filmulator it could be selected from the queue, but once it finishes loading in the editor it would also crash for the same reason.
I don’t know why it might work on one mac and not another.
I have occassional exiv2 crashes on import in 10.12.6 Sierra, but it seems to work O.K. after deleting filmulator’s cache folder: ~/Library/Application\ Support/filmulator
Here’s what I get:
Thread 6 Crashed:: QThread
0 libexiv2.26.dylib 0x0000000105d7c32f Exiv2::ExifParser::encode(std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >&, unsigned char const*, unsigned int, Exiv2::ByteOrder, Exiv2::ExifData const&) + 5055
1 libexiv2.26.dylib 0x0000000105dd8ff7 Exiv2::JpegBase::doWriteMetadata(Exiv2::BasicIo&) + 10295
2 libexiv2.26.dylib 0x0000000105dd66ab Exiv2::JpegBase::writeMetadata() + 811
3 filmulator 0x0000000105b7467f imwrite_jpeg(matrix<unsigned short>&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, Exiv2::ExifData, int) + 1551
4 filmulator 0x0000000105ba0c5b ThumbWriteWorker::writeThumb(QString) + 715
5 filmulator 0x0000000105b8b644 createNewProfile(QString, QString, QDateTime, QDateTime, Exiv2::ExifData, Exiv2::XmpData) + 2260
6 filmulator 0x0000000105b846b3 ImportWorker::importFile(QFileInfo, int, int, QString, QString, QString, QDateTime, bool, bool, bool) + 5571
7 filmulator 0x0000000105ba4ad2 ImportWorker::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 514
8 org.qt-project.QtCore 0x0000000106f89964 QObject::event(QEvent*) + 788
9 org.qt-project.QtWidgets 0x0000000107845f12 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306
10 org.qt-project.QtWidgets 0x00000001078472ed QApplication::notify(QObject*, QEvent*) + 573
11 org.qt-project.QtCore 0x0000000106f6054f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159
12 org.qt-project.QtCore 0x0000000106f61722 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 850
13 org.qt-project.QtCore 0x0000000106fb65b9 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 73
14 org.qt-project.QtCore 0x0000000106f5c0a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418
15 org.qt-project.QtCore 0x0000000106da6101 QThread::exec() + 113
16 org.qt-project.QtCore 0x0000000106daf657 QThreadPrivate::start(void*) + 359
17 libsystem_pthread.dylib 0x00007fff96e2d93b _pthread_body + 180
18 libsystem_pthread.dylib 0x00007fff96e2d887 _pthread_start + 286
19 libsystem_pthread.dylib 0x00007fff96e2d08d thread_start + 13That’s the same error this person was getting. Hmm…
I wonder if I exiv2.27 works any better.
@CarVac @chroma_ghost & beta testers:
- Here is a newer build with exiv2.27 to test:
https://filebin.net/nc63t2a6gtvqfzkc/Filmulator_1.0.0b2.zip?t=bagvaqer
1 Like
---- 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