| 00:34 | Spirit532 | left the channel |
| 00:34 | Spirit532 | joined the channel |
| 09:45 | aombk2 | left the channel |
| 09:45 | aombk2 | joined the channel |
| 12:57 | anuejn | ok some more news from my side: axiom-recorder now also has a CinemaDngFrameserver node that can be plugged at the end of a pipeline and exposes the output of the pipeline as a webdav share with dng files in it
|
| 12:58 | anuejn | this can then be mounted and used e.g. in davinci resolve
|
| 12:58 | vup | uiuiui webdav
|
| 12:59 | anuejn | that makes it unnescessary to have the data laying around twice (e.g. for converting raw12 to cinemaDNG or doing some operations like fpn removal
|
| 12:59 | vup | always these mac users with shitty fuse implementation :P
|
| 12:59 | anuejn | yup seemed easier to implement that nfs and fuse sucks on macos
|
| 12:59 | anuejn | so I went for webdav ;)
|
| 12:59 | vup | anuejn: does this work with non random access sources? (A/B frame decoding?)
|
| 13:00 | anuejn | nope (how could it?)
|
| 13:00 | vup | a big cache?
|
| 13:00 | vup | not sure
|
| 13:01 | anuejn | but I think we might want to add an option to the A/B frame decoding node for creating a small index of which frames to combine and then be random access
|
| 13:01 | anuejn | then it could be used for this workflow
|
| 13:09 | vup | yeah maybe, otoh, maybe we just don't care and never actually store A/B frames and always only store the combined version
|
| 13:09 | vup | I don't really see good reasons to store them in A/B form anyways
|
| 13:10 | vup | and a frameserver in combination with a streaming source like the webcam source seems pretty infeasible, unless you specify like a maximum number of frames or so
|
| 13:10 | anuejn | yup, same
|
| 13:10 | vup | (and then hold all the frames in memory)
|
| 13:10 | anuejn | maybe because ffmpeg is actually a bit more stable than the axiom-recorder ;)
|
| 13:17 | anuejn | what would be also cool now is an openEXR frameserver
|
| 13:18 | anuejn | so that we could in addition to raw images share pre-developed images with the axiom-recorder tooling
|
| 13:18 | anuejn | in case we can provide a better starting point than davinci :)
|
| 13:19 | anuejn | and maaaaybe some tool to expose multiple clips using one program
|
| 13:19 | anuejn | but that requires some architectural rethinking
|
| 13:22 | aombk2 | left the channel |
| 13:30 | se6astian_ | very cool!
|
| 13:32 | se6astian_ | please also add documentation how to use this cool new feature to the github readme
|
| 15:25 | aombk | joined the channel |
| 15:38 | Guest26 | joined the channel |
| 15:39 | Guest26 | left the channel |
| 16:40 | aombk | left the channel |
| 16:40 | aombk2 | joined the channel |
| 16:52 | balrog_ | changed nick to: balrog
|
| 16:54 | anuejn | se6astian_: updated the docs accordingly
|
| 16:59 | se6astian_ | many thanks!
|
| 17:00 | se6astian_ | MEETING TIME, who is here?
|
| 17:00 | anuejn | is here
| | 17:01 | Bertl | is here ...
| | 17:01 | se6astian_ | anuejn you basically already did a full report before, anything to add or anything else?
|
| 17:02 | anuejn | nope
|
| 17:02 | anuejn | thats it from me
|
| 17:03 | se6astian_ | right
|
| 17:03 | se6astian_ | Bertl: any news from your side?
|
| 17:04 | Bertl | Well, I ordered and received the RP2040 chips and Pico Pis
|
| 17:04 | Bertl | I also started some testing on the Pico Pi to get an idea how the toolchain works and that seems to be rather straight forward so far
|
| 17:05 | Bertl | the next step there will be using/testing SWD and how to boot/program one Pico from another
|
| 17:06 | Bertl | There also has been some preliminary feedback from INT/LAM but they are currently evaluating their data, so nothing really new there
|
| 17:06 | se6astian_ | perfect, the context to add here is that we are evaluating using two pico pi chips as coure CPU for a new AXIOM remote prototype
|
| 17:06 | Bertl | Other than that, nothing new from my side
|
| 17:08 | anuejn | se6astian_: any news from the enclosure production?
|
| 17:09 | se6astian_ | well, nothing really new, still waiting for oscar to send the prepayment
|
| 17:09 | se6astian_ | but the order has been placed basically
|
| 17:09 | anuejn | nice :)
|
| 17:09 | anuejn | that sounds very good
|
| 17:10 | se6astian_ | on another front we are retiring the lab as phabricator is EOL, please review as many tasks we had there if they are still relveant/work keeping and create new ones on github projects
|
| 17:11 | se6astian_ | and we also need to do something about apertus.org as drupal 7 is also making trouble
|
| 17:11 | anuejn | is voting for just a static website generated by some static site generator
| | 17:12 | anuejn | thinks that all the interactive content is anyways not used very much
| | 17:12 | se6astian_ | yeah I also want to reduce the dynamci/interactive stuff mostly, maybe a very simple CMS...
|
| 17:12 | aombk | joined the channel |
| 17:13 | BAndiT1983_ | it still involves some work on th layout side, to get proper one for desktop and mobile, but we could evaluate some options
|
| 17:13 | aombk2 | left the channel |
| 17:13 | anuejn | there is still some drafts from me that i did some time ago during my "internship"
|
| 17:13 | anuejn | we could revive them :)
|
| 17:14 | se6astian_ | yes I remember them :)
|
| 17:15 | se6astian_ | I dont think we want to go down the drupal route once again with drupal 10, but a custom small static or minimal CMS setup that is easy to maintain and does not require any constant security patches would go a long way
|
| 17:15 | se6astian_ | also easy to backup/store revisions...
|
| 17:15 | se6astian_ | ok any other topics/things to discuss?
|
| 17:15 | BAndiT1983_ | headless CMS is an option, like strapi or directus, to hold the data, the frontnd doesn't need much logic, have tested both backends with vue.js before, but the selection is vast
|
| 17:17 | anuejn | I think static site generators can bring us a long way since it would enable us to have a website that works without JS :)
|
| 17:17 | BAndiT1983_ | we need a list of requirements, to narrow down possible solutions
|
| 17:18 | anuejn | also I wouldnt bother with moving all the old news entries but rather make a static copy of the current website and host it under the current urls
|
| 17:19 | se6astian_ | that would be a good idea yes
|
| 17:20 | anuejn | we could then just gradually move content to some new thing as we see need
|
| 17:20 | anuejn | but the website actually has not _that_ much content
|
| 17:27 | se6astian_ | thats OK I guess
|
| 17:27 | se6astian_ | regarding GSoC, who would be interesting in mentorng this year if we find ace student candidates?
|
| 17:28 | anuejn | I would throw zola (https://www.getzola.org/) into the ring of static site generators
|
| 17:29 | anuejn | my local hackspace uses it and it seems quite usable
|
| 17:31 | se6astian_ | great, lets discuss this soon separately
|
| 17:31 | se6astian_ | any thoughts on gsoc?
|
| 17:35 | se6astian_ | ok, probably motivation is a bit low on that topic considering the gsoc disaster last year, please think a bit more about it but I see no trouble if we don't apply this year, we can reconsider next year
|
| 17:35 | se6astian_ | MEETING CONCLUDED
|
| 17:35 | se6astian_ | BAndiT1983_ and anuejn, can you start a spreadsheet (google or other online repo) to compare CMS/sitegenerators
|
| 17:36 | se6astian_ | pros and cons, requirements on server, features
|
| 17:36 | se6astian_ | and a tab with requirements we can start to collect
|
| 17:36 | BAndiT1983_ | we can try to do gsoc for remote, would be ok to mentor again
|
| 17:36 | se6astian_ | great
|
| 17:39 | BAndiT1983_ | we can create a small table under projects on github, markdown should be enough
|
| 17:44 | se6astian_ | perfect
|
| 18:18 | aombk2 | joined the channel |
| 18:19 | aombk | left the channel |
| 19:15 | aombk2 | left the channel |
| 19:17 | aombk | joined the channel |
| 19:40 | aombk2 | joined the channel |
| 19:40 | aombk | left the channel |
| 19:48 | aombk2 | left the channel |
| 19:48 | aombk | joined the channel |
| 19:54 | aombk2 | joined the channel |
| 19:56 | aombk | left the channel |
| 20:27 | balrog | left the channel |
| 20:31 | balrog | joined the channel |
| 20:44 | illwieckz | left the channel |
| 20:45 | illwieckz | joined the channel |
| 22:09 | aombk | joined the channel |
| 22:11 | aombk2 | left the channel |
| 22:33 | aombk2 | joined the channel |
| 22:36 | aombk | left the channel |
| 23:29 | aombk | joined the channel |
| 23:30 | aombk2 | left the channel |