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

HIRAM · September 15, 2018, 11:11am

Behold the beta 1 Filmulator_1.0.0b1.zip (52.0 MB)

Example filmulations:
Output:

IMG_2975-output5202×3465 8.34 MB

Raw: IMG_2975.CR2 (23.1 MB) released under CC BY-NC-SA license.
======
Output:

IMG_1932-output3465×5202 7.25 MB

Raw: IMG_1932.CR2 (25.0 MB) released under CC BY-NC-SA license.

Update 2: filmulation works with some intermittent bugs.

Update 1: Import and thumbnails aok. Now onto getting the meat and potatoes to run.

I got pretty deep into bundling @CarVac’s Filmulator for the Macintosh series of personal computers.

Filmulator-GUI uses the Qt GUI front end, making the build pretty easy, or at least easy enough to figure out.
see also:

https://github.com/CarVac/filmulator-gui/issues/71

thanks *

CarVac · September 28, 2018, 12:02pm

Thanks for all your help!

HIRAM · September 28, 2018, 3:28pm

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

chroma_ghost · September 28, 2018, 3:57pm

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)

film_moj_01_web

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 found

HIRAM · September 28, 2018, 4:06pm

You 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.

CarVac · September 28, 2018, 4:09pm

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.

chroma_ghost · September 28, 2018, 5:08pm

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!

HIRAM · September 28, 2018, 5:26pm

Awesome!! Thanks for testing, @chroma_ghost!

Jacal · September 28, 2018, 5:38pm

You are most certainly not alone, experiencing this!

HIRAM · September 28, 2018, 7:25pm

Word.

CarVac · September 28, 2018, 10:38pm

@HIRAM

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.

HIRAM · September 29, 2018, 1:49am

@carvac Thank you, I have re uploaded.

CarVac · November 16, 2018, 6:16pm

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.

chroma_ghost · November 16, 2018, 7:40pm

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?

CarVac · November 16, 2018, 10:21pm

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.

HIRAM · November 16, 2018, 11:17pm

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 + 13

CarVac · November 17, 2018, 12:03am

That’s the same error this person was getting. Hmm…

HIRAM · November 17, 2018, 12:32am

I wonder if I exiv2.27 works any better.

HIRAM · November 17, 2018, 10:06am

@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