Author Topic: Any reason why we stick with an old lilv release ?  (Read 529 times)

benh

  • Newbie
  • *
  • Posts: 37
    • View Profile
Any reason why we stick with an old lilv release ?
« on: October 25, 2021, 05:37:31 AM »
Latest is 0.24.12...

Randall (Admin)

  • Administrator
  • Full Member
  • *****
  • Posts: 217
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #1 on: October 25, 2021, 02:11:45 PM »
0.24.4 is the latest version I've tried that retains compatibility with the modep module.  As I remember, it was the "Make Python bindings more Pythonic" change introduced in 0.24.6 that broke things.

I've been hoping that blokaslabs would be updating modep by now.  It's stuck at 1.8 while moddevices is on 1.10.  I don't see any obvious signs of that upgrade on blokas community other than the experiments of some users hacking MOD 1.10 themselves to work within patchbox.  I feel like pi-Stomp needs something more official and I'd prefer to stay with modep as a proper module unless at some point it's apparent that will never happen.

benh

  • Newbie
  • *
  • Posts: 37
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #2 on: October 25, 2021, 04:56:36 PM »
Yup, I went looking a bit this morning, it looks like most of blokas "stuff" is ... stale (except midihub). They are probably too busy.

There is a guy who has a script to get pistomp to 1.10 .. but as you said it's not as "proper"...

Another option would be to take time to actually do a PR for Blokas to consider. I don't know if I"ll have time for any of that myself in the near future, tbh, i'd rather spend my time building a whole 64-bit pistomp env. with everything rebuild from scratch for ARMv8 with NEON instructions and auto-vectorisation using a more recent gcc... :)

micahvdm

  • Newbie
  • *
  • Posts: 15
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #3 on: October 26, 2021, 06:59:20 AM »
Hey Randy,
I’m almost done with a custom iso for pi-stomp.
It will be an updated patchbox with mod1.10 and everything already installed.

Do you want me to send the iso to you first for testing?
It shouldn’t require much (if any) maintenance and will still have the patchbox cli tools.

I have managed to get mod1.10 really stable now and I’m already working on mod1.11!!

Randall (Admin)

  • Administrator
  • Full Member
  • *****
  • Posts: 217
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #4 on: October 26, 2021, 11:17:27 AM »
That's great news Micah.

Yes, I would definitely like to try it out.  Also very curious to see what changes you had to make.  Have you got much (or any) response from Blokas regarding your work? 

benh

  • Newbie
  • *
  • Posts: 37
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #5 on: October 26, 2021, 04:14:48 PM »
That's awesome. I did ask Blokas on their forums, the respond was they would gladly take pull requests for such updates

benh

  • Newbie
  • *
  • Posts: 37
    • View Profile
Re: Any reason why we stick with an old lilv release ?
« Reply #6 on: October 28, 2021, 07:22:20 PM »
Out of curiosity as I only had a cursory glance so far... what does 'MODEP' add to the moddevices original stuff ?

So far, I looked at Blokas repo, and mostly I see debian packaging around old versions of moddevices components, is there more ? Is there actual code / logic I'm missing or it's just a convenient way of packaging moddevices components (mod-host, mod-ui...) on debian based distros ?