Light weight version?

[1ln1x]

Wondering if there are any plans for dynaframe to be run on Rpi zero?
(light weight version of dynaframe perhaps?)

[Geektoolkit]

There's no plans for this project. Dynaframe is meant to be feature rich with experiences like full web control, motion and gesture sensing, transitions, video and photo playback. The pi zero is incredibly constrained (even the pi3A struggles).
To make a light version would be an entirely different undertaking. Simone else can certainly attempt it and probably should, I get questions about it from time to time. For me I'd prefer to work on features like better sync support and cloud updating of content to enhance this project. I do wish I had unlimited time, I'd definitely do both!

[bosbruce]

I was hoping for the same. Given Pi Zero 2 W is nearly identical in CPU/GPU to Raspberry Pi 3, I gave it a shot and it works with the older 2.13 version of Dynaframe , even with a full desktop version of latest RPi OS (despite having 1/2 the RAM of rPi 3). It takes longer to boot than on rPi 400 (with much faster CPU/GPU and 8x the RAM) and transitions at default 1.6 seconds speed are not smooth but it works once through image list, then crashes (though web server continues so I can click on reboot to get it going again)...

FWIW, I started with version 2.24 on rPi 400 but that was getting sqlite permissions errors (there was no sqlite file in the Pictures dir), then went to 2.23 (just killed running processes, removed /home/pi/Dynaframe dir, and ran the 2.23 install.sh ... Same sqlite permission errors so I then went to 2.13 since that was in the youtube videos and it works without significant issues.

I will tinker with using and older and minimal version of rPi OS, as the form factor of rPi Zero 2 W is awesome given it can take power from USB on several of my TVs and is small enough as to be unseen behind them.

While I like some of the options Dynaframe has including web control, etc... I'd much rather have a simpler setup with no wifi that just does slides from an SD card. I already have approaching 100 wifi + network wired devices in my home and each is a potential security threat if not carefully updated/managed. I might play with some of the more advanced features for a TV in my home theater but expect the simpler the better for my use cases.

I don't have tons of time to apply to this (haven't even gone to looking at what parts of your code might be hogging CPU/RAM as right now I think the high order bit is more likely Pi X Desktop making it so slow), but any thoughts on what version I might consider forking from as I suspect your newer versions are more resource intensive or other basic design concepts would be helpful.

I'm an experienced software developer and know Linux/Pi/Python/shell scripting/Java/C/... so can probably grasp most of what's going on here though I haven't looked much into the sources yet.

[Geektoolkit]

Thank you that's an awesome rundown!
I'll give a better answer when not on a phone but a few ideas:

If you're looking for just a slideshow setup then running feh may be the way to go.

Dynaframe 1 was pure python and used a combination of feh, omxplayer and provided a web ui. It ran much leaner but you lose transitions. It's still in git

Pi3d is a webgl python library and has a webgui and more transitions

2.13 is a good one to fork from if you continue with dynaframe. Later builds I started getting into SQLite stuff and then realized I was making essentially a very different product. I created dynaframe pro from this code base but it targets a pi4 and is going much higher end. It also required me to sit down and wrangle this code into a proper design.

That's just some options...I'd rather not see you try to wrangle this code if your goals can be met easier with other code. That being said if you do decide to fork I will help however I can

[bosbruce]

Thanks for the comprehensive response (and for dynaframe, and for making it a single bundle install that runs out and grabs all necessary bits)! Dynaframe 1 sounds like perhaps the best way to start if the pi zero 2 w is my ultimate target though not sure how I'll like it without transitions. I'll take a look at df 1 when I get a chance this week and see how that goes. My son is huge into anime and I must admit some of anaglyphs and animation are cool but guessing that needs more horsepower, not to mention more of my time finding/creating the animations. Cheers, Bruce

…

On Fri, Jan 21, 2022, 11:11 AM Joe Farro ***@***.***> wrote: Thank you that's an awesome rundown! I'll give a better answer when not on a phone but a few ideas: If you're looking for just a slideshow setup then running feh may be the way to go. Dynaframe 1 was pure python and used a combination of feh, omxplayer and provided a web ui. It ran much leaner but you lose transitions. It's still in git Pi3d is a webgl python library and has a webgui and more transitions 2.13 is a good one to fork from if you continue with dynaframe. Later builds I started getting into SQLite stuff and then realized I was making essentially a very different product. I created dynaframe pro from this code base but it targets a pi4 and is going much higher end. It also required me to sit down and wrangle this code into a proper design. That's just some options...I'd rather not see you try to wrangle this code if your goals can be met easier with other code. That being said if you do decide to fork I will help however I can — Reply to this email directly, view it on GitHub <#142 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNABXHAWWTJYIVDPQXL2N3UXGASLANCNFSM5COTMJPA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Geektoolkit]

Actually you may pull off the animations as long as they're mp4 and a format omxplayer supports. The bigger limitation is memory...this just takes a bit. DF1 and this both use omxplayer so if you stay in raspbian buster you should be good to go (bullseyes the latest and breaks..everything).
Also protip...there are sites that can download Instagram videos and a number of artists on there doing motion art, so if it's just personal use you could mine that for content

[bosbruce]

Hi Joe, Again, thanks for responding. I found that feh requires X and didn't want all the overhead of that (memory, disk, boot time) and was extremely pleased with how lightweight, simple, and yet feature rich enough "fbi" is. It even does semi decent transitions on the meager rpi zero 2 W. I could easily get fbi to work from ssh connection and via nohup backgrounded (no tty), using -d /dev/fb0 (and tried with/without -T 1 and using explicit timing intervals...) , but it was a royal PITA to get it to run from an rc script. I easily got "fim" to run from an rc script (rc5.d/S01runfim linked of course to init.d actual script) but it produces garbage on the console, and I don't like it as much as fbi. After I disabled tty1 getty ( good link here : https://yingtongli.me/blog/2016/12/21/splash.html ) I did get it to work, but it is a bit wonky, and I never got things working with the newer "splashscreen.service" control file, still using the legacy /etc/init.d script approach. And kinda would like the option to use keyboard though I can currently ssh in to change images/restart fbi, etc... So I was just wondering what you did (if anything; maybe by virtue of feh running with X you don't care about console tty etc) to get your display bits working at boot. If you have some good pointers I'd appreciate them! I'll be tracking some of your work for my rPi 4 /400 etc as TVs/ monitors are soooo cheap these days I do like the idea of having lots of them coordinating things but my day job doesn't leave me enough time to do all the tinkering I'd have to do with that right now :). Keep thinking of putting 3 or 4 50-65" TVs in portrait mode on basement walls with window like frames and then coordinating movies of sunny beach images to cheer us up in the winter but that requires both physical *and* technical work so not likely to happen soon. Cheers, Bruce

…

On Sat, Jan 22, 2022 at 9:38 PM Joe Farro ***@***.***> wrote: Actually you may pull off the animations as long as they're mp4 and a format omxplayer supports. The bigger limitation is memory...this just takes a bit. DF1 and this both use omxplayer so if you stay in raspbian buster you should be good to go (bullseyes the latest and breaks..everything). Also protip...there are sites that can download Instagram videos and a number of artists on there doing motion art, so if it's just personal use you could mine that for content — Reply to this email directly, view it on GitHub <#142 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNABXE4JCNR7OVI4PECQ53UXNSYXANCNFSM5COTMJPA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[Geektoolkit]

Oh yeah I went down that road it was messy.

Check out the install.sh file and Dynaframe.desktop. Super simple way to get stuff to work on boot and it happens after the graphics portion is initialized. I tried RC and crib and all of that with no luck and then autostart worked great. Maybe it will for you as well!

[bosbruce]

Hi Joe, Thanks... Looks like a much cleaner route you took, but also looks like it depends upon some X11 desktop window manager to start things in /home/pi/.config/autostart ... I guess since I've basically got things working with fbi without X using init.d script I'll keep going that route for now. I might compare memory/CPU footprint of using fb0 vs X at some point and maybe overhead isn't too bad. echo -e "${GREEN}Setting it up to autostart ${NC}" mkdir -p /home/pi/.config/autostart sudo cp dynaframe.desktop /home/pi/.config/autostart Time to go check on the snow blower for the upcoming storm! ...Bruce

…

On Fri, Jan 28, 2022 at 1:13 PM Joe Farro ***@***.***> wrote: Oh yeah I went down that road it was messy. Check out the install.sh file and Dynaframe.desktop. Super simple way to get stuff to work on boot and it happens after the graphics portion is initialized. I tried RC and crib and all of that with no luck and then autostart worked great. Maybe it will for you as well! — Reply to this email directly, view it on GitHub <#142 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXNABXF765UUWURHAF2IM6LUYLMGPANCNFSM5COTMJPA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>