Compiling MacFlim's flimmaker on ARM - Raspberry Pi?

[avadondragon]

So I finally decided to play around with MacFlim today and man is it AWESOME!

I wanted to try converting my own videos so I thought I would try compiling flimmaker on my PiSCSI so I could just create the flim files right where I was going to use them. Everything seemed to go smoothly but once everything compiled it seemed like the binary created was the wrong architecture perhaps?

When I tried to run ./flimmaker it returned the following:
bash: ./flimmaker: cannot execute binary file: Exec format error

 

[sfiera]

What does file flimmaker say about the file type?

 

[avadondragon]

What does file flimmaker say about the file type?

Welp there's the problem.
It says x86-64

 

[Melkhior]

There's an x86-64 binary is the src/ directory on GitHub which you want to ignore.
In src/ you simply do 'make ../flimmaker', then the aarch64 binary should in the top-level directory (provided you have the dependencies installed such as libavformat).

 

[avadondragon]

There's an x86-64 binary is the src/ directory on GitHub which you want to ignore.
In src/ you simply do 'make ../flimmaker', then the aarch64 binary should in the top-level directory (provided you have the dependencies installed such as libavformat).

Thank you.

 

[avadondragon]

Well turns out this was a lost cause. I guess flimmaker needs too much memory. I watched it fill up the RAM and the SWAP then it died. It might work on the 8GB version of the pi 4 I guess.

 

[just.in.time]

@avadondragon did you ever get this working on a raspberry Pi 4gb model? I also am running into an issue with it. Reads around 4100 frames then crashes in Terminal or the entire Pi freezes.

 

[avadondragon]

I eventually gave up. It eats up HUGE amounts of RAM. I ended up running it on a Linux machine with 16GB and it used most of it.

 

[just.in.time]

Thanks for the quick reply! Okay sounds good, I’ll give it a try on another system.

 

[robin-fo]

I eventually gave up. It eats up HUGE amounts of RAM. I ended up running it on a Linux machine with 16GB and it used most of it.

Sounds like a memory leak or inefficient programming

 

[just.in.time]

This was an adventure. Tried installing WSL on an existing Windows 10 Bootcamp install on my old MacBook (16gb RAM). For whatever reason something wasn’t working right with it, strange errors and never got it to get to point of encoding video frames.

Ended up installing Linux Mint on a spare SSD in my gaming computer (which has 32gb RAM, so I figured it should cover it). This setup worked great. While it was running the first few test runs I kept watch on “top” in a separate terminal window and saw it using up just under 12gb of RAM (explains why the raspberry pi kept failing like you said @avadondragon ).

Only strange thing I noticed with the Linux code (not sure if issue is in macsrc version as well, didn’t bother to check), is that the program tries to download the video using both yt-dlp AND youtube-dl, when it should only be using youtube-dl as a fallback if yt-dlp failed/errored. The result is that the program would then exit since YouTube-dl is no longer current (at least on my Pi or Linux Mint install) and errors out.

My solution to this issue was to navigate to src and open flimmaker.cpp , comment out line 650 (“exit( EXIT_FAILURE );”), save changes, and rerun “make” command. If I really wanted to clean it up well I could completely remove all YouTube-dl related code and the fallback conditions, but this at least stops the program from closing out without completing.