Release announcements

[helgeerbe]

If you all don't mind I will release a new version of picframe at the weekend.

Changes:

• update noto fonts to latest version (and License)
• Strange "flash" on the frame followed by picture repeat #119
• Image played twice during slideshow cycle if shuffle=True #139
• Older portrait images are incorrectly shown inside the "recent_n" window #144
• Enhanced home assistant integration #148
  • this will break the old home assistant integration
• Picframe stalls with error #153

As far as I can see, there are no changes to `configuration.yaml. So one can use the old one.

I described how to setup home assistant integration or upgrade the integration in the wiki

[paddywwoof]

I think I'm fine with update. Just one thought though: for some reason X started using Display :1 instead of :0 (due to some messing around I was doing for another issue probably) but the loop in DisplayOpenGL.py  https://github.com/tipam/pi3d/blob/4ddc3cd6aab139602b4283015049e372a0c3530a/pi3d/util/DisplayOpenGL.py#L71 breaks when it finds :0 even if that's not assigned to current user. So this could do with being fixed.I will have a look at the weekend but probably not worth holding up release of picframe.PaddyOn 26 Aug 2021 12:25, helgeerbe ***@***.***> wrote: If you all don't mind I will release a new version of picframe at the weekend. Changes: update noto fonts to latest version (and License)#119#139#144#148 this will break the old home assistant integration #153 As far as I can see, there are no changes to `configuration.yaml. So one can use the old one. In the wiki I have to describe how to update and install the new home assistant integration. —You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[helgeerbe]

@paddywwoof I'm not in a rush. If you like, you can do the fix in pi3d and change the version dependency in picframe first. Does the new pi3d lib support macOS now? Would be great, if I could switch back to the official pi3d release on my MacBook.

[paddywwoof]

I think I pulled your Mac fixes into the develop branch so that will be merged to master too... A good reason to fix pi3d first. Will let you know when it's updated

[jgodfrey]

A release is good by me. I'm not working on anything that's imminent, so whenever @paddywwoof gives a thumbs-up works for me.

[paddywwoof]

@helgeerbe pushed pi3d v2.47 up to pypi.org and onto master branch on github so (touch wood) OK to go.
@sapnho I did manage to find something on the conway demo in the vertex shader (-0.5 a pixel) tipam/pi3d@4dbdaa4 but I'm really sure how that will translate to 4k issues as all the images are the same size and the wrapping happens on a seemingly random basis! Anyway we can try the equivalent of adding and subtracting half a pixel here and there and seeing if it fixes it.

[sapnho]

Anyway we can try the equivalent of adding and subtracting half a pixel here and there and seeing if it fixes it.

Great, thanks. Can I update Pi3D separately without Picture Frame?

[paddywwoof]

I think so, though, once helge has changed the picframe dependencies file, updating picframe should automatically pull in the next release of pi3d without you having to do anything specific. I think anything relevant to the wrapping on 4k will be accessible either in picframe/viewer_display.py or else in the picframe shader so we will just have to test out ideas on that separately.

[sapnho]

Ok, then I'll just wait.

but I'm really sure how that will translate to 4k issues as all the images are the same size and the wrapping happens on a seemingly random basis!

My wrapping issues are actually consistent. It just wasn't always obvious to spot. It would be great if that issue can be fixed through your latest change.

[paddywwoof]

Ah, that gives me hope then. I thought you had images (i.e. the test black and white striped one) that sometimes showed the effect and sometimes didn't. If the last pixel always wraps then that's much more likely to have a solution (i.e "just" shunt the whole image one way or the other, by tweaking offsets etc)

[helgeerbe]

I released picframe 2021.08.30 (changelog).
@jgodfrey I noticed that you changed the Readme.mdfile in master. I cherrypicked your commit into dev to reflect your changes there.

[jgodfrey]

Ah, good catch @helgeerbe, thanks. Yeah, I just changed it directly on Github - probably not the best choice in hind-sight.

[helgeerbe]

Hi all,

I'm going to prepare a new release:

configuration.yaml will change

• Fix picframe does not survive short break in image availability #167
• Fix Support for selecting multiple subdirectories to display #166
  Make it configurable, that picframe follows symbolic links.
  configuration.yaml

  model:
  ...
  follow_links: False   # default=False, By default, picframe will not walk down into symbolic links that resolve to directories. Set follow_links to True to visit directories pointed to by symlinks, on systems that support them.
  

• make Exif Tag search more flexible
• Fix HEIC Images and Make tag #164

Do I have to wait for anything else?

[jgodfrey]

I do wonder what caused #169. I'm not able to reproduce it, nor do I see anything obvious in the code that could cause it. Assuming no one else can repro it either, I guess it can wait until we have something more to go on.

[helgeerbe]

Just released 2021.09.22 (changelog).

[helgeerbe]

Just released 2021.10.06 (changelog) as hotfix.

[helgeerbe]

Just release 2021.11.04 (changelog)

[helgeerbe]

Just release 2022.01.20 (changelog)

[helgeerbe]

Just released 2022.01.20.post1 (changelog)

I messed up the readme file. Hope, it's OK now

[helgeerbe]

Just released 2022.03.24 (changelog).

[helgeerbe]

Just released 2022.04.19(changelog)

[helgeerbe]

Just released 2022.06.03 (changelog)

Be aware of changes in mqtt topics and home assistant integration

[sapnho]

Great, works fine.

[helgeerbe]

Just release 2022.12.04(changelog)

[helgeerbe]

Just release 2022.12.13(changelog)

[helgeerbe]

I just released 2022.12.15.

But this is just a technical release. I updated the build pipeline to make it future proof.
So packaging could be done now with python -m build
The automatic deployment to pypi after releasing is working again.

[helgeerbe]

Just released 2023.05.17. Changelogs are now generated by github action: https://github.com/helgeerbe/picframe/releases