- whitebox-dev - ml.whitebox.aero

[update] 2026-03-11~13
by milos＠whitebox.aero 17 Mar '26

17 Mar '26

Heya, #503 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/503 Ready for review #503 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/511 Ready for review #438 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/438 Still investigating this, not sure yet how to tackle it

2 1

Re: FFmpeg v360 Vulkan filter development
by milos＠whitebox.aero 13 Mar '26

13 Mar '26

Just a heads up, it seems the ML issue is still there - https://ml.whitebox.aero/archives/list/dev@ml.whitebox.aero/thread/RE7TNLBL…, so this reply will end up on the ML but probably in a separate (new) thread. Thanks, I'll get back with the results when I try it out On 9. 3. 2026. 23:43, Lynne wrote: > Hi, > > Thanks for sorting the email issue out. > > I think you should definitely rerun the test on 6.13 (I presume this > uses the mesa panfrost/panvk driver) and use the latest FFmpeg git > master. 8.1 which will ship next week has a ton of improvements. > > Just in case, could you post the log by adding -trace at the start? > > On 09/03/2026 22:26, milos(a)whitebox.aero wrote: >> Hey Lynne, >> >> Your emails should go through instantly now. >> >> I've tried running that filter, but I couldn't get it working, >> neither as part of our current pipeline, nor standalone (using only >> the filter from your sample). Pasted my results here: >> https://gitlab.com/whitebox- aero/whitebox/-/snippets/5967510 >> >> I see that Vulkan has had considerable driver improvements in kernel >> 6.13, and we're currently running on 6.1 - would upgrading be a >> requirement to running this (whether Vulkan, or the latest FFmpeg >> version in some way)? I'll try to get up to speed with the driver >> replacements later this week to verify that as well. >> >> @Xavier @Avinash Does any of this ring any bells, have you maybe >> tried using Vulkan on OPi before? It seems there's also Armbian for >> Orange Pi 5 Plus, but they ship it with 6.1 and 6.11, so I guess that >> wouldn't really bring benefits here >> >> On 6. 3. 2026. 16:43, milos(a)whitebox.aero wrote: >>> Hey, I did receive it on my email, so I assume the ML also got it, >>> but I think it requires approval to be posted on there. I don't have >>> access to that, so when Xavier comes around he'll do it. I've sent >>> him an email. I could technically just reply to your email here, but >>> I think that'd open a new thread. >>> >>> Also thank you for the test instructions! I'll run them over the >>> weekend and let you know how it went >>> >>> On 6. 3. 2026. 14:51, Lynne wrote: >>>> Was my reply received? I don't see it on the ML. >>>> >>>> On 06/03/2026 13:28, Lynne wrote: >>>>> Hi all, >>>>> >>>>> Certainly, a Vulkan version would likely speed the pipeline up. >>>>> GPUs are good at interpolating, and very large amount of the time >>>>> spent on the CPU version of the filter is spent doing that. >>>>> >>>>> Would you be able to test whether Vulkan is setup correctly? Try >>>>> adding: >>>>> `hwupload,avgblur_vulkan=planes=0,hwdownload,format=yuv420p` >>>>> after the v360 filter. The output should not change, and the >>>>> slowdown shouldn't be too significant. >>>>> You need to use current git master of FFmpeg, not any release branch. >>>>> >>>>> I highly suggest using the panfrost Vulkan drivers from Mesa, >>>>> rather than some outdated vendor-provided inactively developed >>>>> drivers. They support RK3588, but you'll need to look into how to >>>>> enable them (they require using the mainline kernel panfrost >>>>> module, rather than mali). >>>>> >>>>> The previous work done by Paul isn't really helpful, as we're >>>>> currently rewriting all the Vulkan codecs and filters to compile- >>>>> time SPIR-V in order to eliminate dependencies on large external >>>>> libraries, and to speed up the code with offline optimizations. >>>>> I'd be interested in being contracted to write a modern Vulkan >>>>> filter with enough capabilities for your particular use-case, if >>>>> you agree. >>>>> >>>>> On 06/03/2026 12:37, milos(a)whitebox.aero wrote: >>>>>> Hey Lynne, >>>>>> >>>>>> Adding our conversation from IRC: >>>>>> >>>>>>> <libmilos-so> Hello Lynne, I'm Milos, contributor to https:// >>>>>>> whitebox.aero . We're looking for a FFmpeg developer for >>>>>>> assistance with filter development, and Paul B Mahol gave us >>>>>>> your contact as an expert in Vulkan development. We are building >>>>>>> an SBC-based device which needs to run the v360 filter on it, >>>>>>> however the CPU filter's performance is starting to be our >>>>>>> bottleneck, and we're looking to explore a GPU-based approach to >>>>>>> it. Paul started working on `v360_{opencl,vulkan}` filters a >>>>>>> while back, but it wasn't finished, and the `libavfilter` has >>>>>>> changed since, requiring more development to get them working. >>>>>>> Here's a link to the mailing list's previous discussion: >>>>>>> https://ffmpeg.org/ pipermail/ffmpeg-devel/2024- June/330229.html >>>>>>> >>>>>>> >>>>>>> <libmilos-so> Our use case is to convert dual-fisheye videos to >>>>>>> equirectangular in real time, we're basically only doing this >>>>>>> for now: `v360=dfisheye:e:ih_fov=193:iv_fov=193` >>>>>>> >>>>>>> <libmilos-so> Currently we are running it for a single video >>>>>>> feed, but we're close to hitting resource limits. As we'd like >>>>>>> to extend to multiple videos, we think that GPU-based >>>>>>> acceleration would provide us the performance improvement we >>>>>>> need. Considering your FFmpeg expertise, we were wondering if >>>>>>> you'd be interested for contracting to help us get this >>>>>>> implemented for our use case? >>>>>>> Our mailing list is at https://ml.whitebox.aero, and if that'd >>>>>>> be alright with you, I'd like to copy the contents of this >>>>>>> conversation to the mailing list later. If you're interested in >>>>>>> the contractual work, it'd be great if we could then continue >>>>>>> the conversation on the mailing list to keep the team in the loop >>>>>>> >>>>>>> <libmilos-so> Thanks! >>>>>>> >>>>>>> <Lynne> sure, I'd be happy to help >>>>>>> >>>>>>> <libmilos-so> Thanks! Could you give me your email address and >>>>>>> I'll cc you on the thread? >>>>>>> >>>>>>> <Lynne> the filter which paul wrote years ago needs quite a bit >>>>>>> of work, since currently we're rewriting all vulkan filters to >>>>>>> compile- time spir-v generation >>>>>>> >>>>>>> <Lynne> sure, [redacted] >>>>>>> >>>>>> For context, we are taking H.264/H.265 dual-fisheye videos from >>>>>> Insta360 cameras, both from live feeds, and when recorded from >>>>>> file recordings, and processing them using FFmpeg to produce >>>>>> equirectangular videos which would then be suitable for playback >>>>>> in browsers. We are currently using Pannellum player for this, >>>>>> given our current equirectangular format. If there are more >>>>>> efficient options on the backend side to achieve the same effect, >>>>>> we're open to exploring those as well, although frontend clients >>>>>> would also be phones and tablets, so no heavy operations should >>>>>> take place on them. >>>>>> >>>>>> We are currently developing on RK3588 (on Orange Pi 5 Plus), >>>>>> which by the documentation supports OpenCL 2.2 and Vulkan 1.2. It >>>>>> has H.264 and H.265 hardware encoders and decoders, which we've >>>>>> tried using, but v360 filter ended up being the biggest bottleneck. >>>>>> >>>>>> Here's one example of how we're currently using this filter: >>>>>> >>>>>>> return [ >>>>>>> "ffmpeg",# Decoder settings >>>>>>> "-fflags","+genpts+discardcorrupt", >>>>>>> "-flags","low_delay", >>>>>>> >>>>>>> "-f","h264", >>>>>>> "-i","pipe:0",# input from stdin "-r","30", >>>>>>> >>>>>>> # Filter settings "-filter_complex", >>>>>>> f"[0:v]scale=1440:720,v360=dfisheye:e:ih_fov=193:iv_fov=193[out]", >>>>>>> "-map","[out]", >>>>>>> >>>>>>> # Encoder settings "-c:v","libx264", >>>>>>> "-preset","ultrafast", >>>>>>> "-tune","zerolatency", >>>>>>> "-pix_fmt","yuv420p", >>>>>>> "-profile:v","main", >>>>>>> "-level","3.1", >>>>>>> >>>>>>> # Bitrate settings # This ensures that keyframes are pushed >>>>>>> frequently enough to keep the # streaming latency low >>>>>>> "-g","30",# keyframe interval "-keyint_min","30",# minimum >>>>>>> keyframe interval "- sc_threshold","0",# disable scene change >>>>>>> detection "- muxpreload","0", >>>>>>> "-muxdelay","0", >>>>>>> >>>>>>> "-f","flv",# output format "-rtmp_live","live", >>>>>>> >>>>>>> # e.g.: rtmp://srs-dev/live/livestream output_target, >>>>>>> ] >>>>>> >>>>>> By my understanding, we likely need a GPU-based v360 filter as a >>>>>> drop- in replacement for the standard CPU-based v360. I think >>>>>> that the GPU- based filters would also require `hwupload`/ >>>>>> `hwdownload`(?), but I don't have experience with it. Personally >>>>>> I'm new to FFmpeg, so feel free to correct me if something sounds >>>>>> off. >>>>>> >>>>>> The code would ideally be released under a copyleft license, I'll >>>>>> let Xavier pitch in on this. >>>>>> >>>>>> Does this sound like a proper approach to it and something that'd >>>>>> be interesting for you to work on? >>>>>> >>>>>> Thanks! >>>>>> >>>>> >>>> >

2 3

Re: FFmpeg v360 Vulkan filter development
by Lynne 13 Mar '26

13 Mar '26

Hi, any progress on sharing the logs? Did you manage to get the FFmpeg Vulkan code running yet? On 10/03/2026 22:56, Lynne wrote: > Err, accessing the snippet requires login for some reason? > > What tests? > All you need to do to run the filter is to init a hw device (- > init_hw_device "vulkan=vk:0" at the beginning), use the hw device (- > filter_hw_device vk before -vf), and replace the v360 filter with the > vulkan v360 filter (hwupload,v360_vulkan,hwdownload,format=nv12). > > I have enough old SoCs that I'd rather not add one more to the > collection for now, plus I'll be moving away soon anyway. > > On 10/03/2026 22:35, milos(a)whitebox.aero wrote: >> Hey Lynne, >> >> Can't link directly to the file itself, but I've updated the >> previously linked snippet, added a new file named `run with trace`: >> https:// gitlab.com/whitebox- aero/whitebox/-/snippets/5967510 >> >> I've never worked with Vulkan before so I kinda expected this test to >> be a drop in replacement, but looking into all this I feel I'm a bit >> far from understanding exactly how all these fit in, and being >> confident I'm actually giving you accurate feedback information. Would >> it be alright to include these tests in the scope of your contract as >> well so we can get the development going faster? >> >> We are running on Orange Pi 5 Plus [1], and we're open for both you >> sourcing the components yourself and invoicing it, or us arranging >> shipping for you. We have hardware setup instructions [2] for getting >> started quickly if you'd want to start from our current environment >> (the other listed components should not be needed to get started, just >> for full operation). >> >> Would you be interested in this? >> >> [1] http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/ >> details/Orange-Pi-5-plus.html >> >> [2] https://docs.whitebox.aero/hardware_setup/ >> >> On 10. 3. 2026. 13:28, Xavier Antoviaque wrote: >>> Hi Lynne, nice to meet you! >>> >>> Sorry it took me some time to get up to speed here, the mailing-list >>> issues got in the way - we are still solving them btw, but you can >>> mostly ignore them on your side, just keep Milos and my email in CC >>> besides the ML and we should be fine :) >>> >>> And thanks for helping with this, anf for being interested in >>> contracting on the topic. How would you like to setup the contract >>> work on this? Generally we pay hourly, agreeing on a hourly rate and >>> a rough estimation of the time it will take you - then if it looks >>> like you might need more time, you check with me and we rediscuss? If >>> you want to keep anything confidential (eg rate, personal info, >>> etc.), you can also write to me directly (xavier(a)whitebox.aero) - >>> just keep the non-confidential info in the public thread here so that >>> others can follow the rest. >>> >>> Looking forward! >>> >>> Xavi. >>> >>> On Tue, Mar 10, 2026, at 11:14, Milos Petkovic via whitebox-dev wrote: >>>> Just a heads up, it seems the ML issue is still there - >>>> https://ml.whitebox.aero/archives/list/dev@ml.whitebox.aero/thread/ >>>> RE7TNLBLOSH6CC5HAJFZ2E4B6UZT32AL/, >>>> so this reply will end up on the ML but probably in a separate (new) >>>> thread. >>>> >>>> Thanks, I'll get back with the results when I try it out >>>> >>>> On 9. 3. 2026. 23:43, Lynne wrote: >>>>> Hi, >>>>> >>>>> Thanks for sorting the email issue out. >>>>> >>>>> I think you should definitely rerun the test on 6.13 (I presume this >>>>> uses the mesa panfrost/panvk driver) and use the latest FFmpeg git >>>>> master. 8.1 which will ship next week has a ton of improvements. >>>>> >>>>> Just in case, could you post the log by adding -trace at the start? >>>>> >>>>> On 09/03/2026 22:26,milos@whitebox.aero wrote: >>>>>> Hey Lynne, >>>>>> >>>>>> Your emails should go through instantly now. >>>>>> >>>>>> I've tried running that filter, but I couldn't get it working, >>>>>> neither as part of our current pipeline, nor standalone (using only >>>>>> the filter from your sample). Pasted my results here: >>>>>> https://gitlab.com/whitebox- aero/whitebox/-/snippets/5967510 >>>>>> >>>>>> I see that Vulkan has had considerable driver improvements in kernel >>>>>> 6.13, and we're currently running on 6.1 - would upgrading be a >>>>>> requirement to running this (whether Vulkan, or the latest FFmpeg >>>>>> version in some way)? I'll try to get up to speed with the driver >>>>>> replacements later this week to verify that as well. >>>>>> >>>>>> @Xavier @Avinash Does any of this ring any bells, have you maybe >>>>>> tried using Vulkan on OPi before? It seems there's also Armbian for >>>>>> Orange Pi 5 Plus, but they ship it with 6.1 and 6.11, so I guess that >>>>>> wouldn't really bring benefits here >>>>>> >>>>>> On 6. 3. 2026. 16:43,milos@whitebox.aero wrote: >>>>>>> Hey, I did receive it on my email, so I assume the ML also got it, >>>>>>> but I think it requires approval to be posted on there. I don't have >>>>>>> access to that, so when Xavier comes around he'll do it. I've sent >>>>>>> him an email. I could technically just reply to your email here, but >>>>>>> I think that'd open a new thread. >>>>>>> >>>>>>> Also thank you for the test instructions! I'll run them over the >>>>>>> weekend and let you know how it went >>>>>>> >>>>>>> On 6. 3. 2026. 14:51, Lynne wrote: >>>>>>>> Was my reply received? I don't see it on the ML. >>>>>>>> >>>>>>>> On 06/03/2026 13:28, Lynne wrote: >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Certainly, a Vulkan version would likely speed the pipeline up. >>>>>>>>> GPUs are good at interpolating, and very large amount of the time >>>>>>>>> spent on the CPU version of the filter is spent doing that. >>>>>>>>> >>>>>>>>> Would you be able to test whether Vulkan is setup correctly? Try >>>>>>>>> adding: >>>>>>>>> `hwupload,avgblur_vulkan=planes=0,hwdownload,format=yuv420p` >>>>>>>>> after the v360 filter. The output should not change, and the >>>>>>>>> slowdown shouldn't be too significant. >>>>>>>>> You need to use current git master of FFmpeg, not any release >>>>>>>>> branch. >>>>>>>>> >>>>>>>>> I highly suggest using the panfrost Vulkan drivers from Mesa, >>>>>>>>> rather than some outdated vendor-provided inactively developed >>>>>>>>> drivers. They support RK3588, but you'll need to look into how to >>>>>>>>> enable them (they require using the mainline kernel panfrost >>>>>>>>> module, rather than mali). >>>>>>>>> >>>>>>>>> The previous work done by Paul isn't really helpful, as we're >>>>>>>>> currently rewriting all the Vulkan codecs and filters to compile- >>>>>>>>> time SPIR-V in order to eliminate dependencies on large external >>>>>>>>> libraries, and to speed up the code with offline optimizations. >>>>>>>>> I'd be interested in being contracted to write a modern Vulkan >>>>>>>>> filter with enough capabilities for your particular use-case, if >>>>>>>>> you agree. >>>>>>>>> >>>>>>>>> On 06/03/2026 12:37,milos@whitebox.aero wrote: >>>>>>>>>> Hey Lynne, >>>>>>>>>> >>>>>>>>>> Adding our conversation from IRC: >>>>>>>>>> >>>>>>>>>>> <libmilos-so> Hello Lynne, I'm Milos, contributor to https:// >>>>>>>>>>> whitebox.aero . We're looking for a FFmpeg developer for >>>>>>>>>>> assistance with filter development, and Paul B Mahol gave us >>>>>>>>>>> your contact as an expert in Vulkan development. We are building >>>>>>>>>>> an SBC-based device which needs to run the v360 filter on it, >>>>>>>>>>> however the CPU filter's performance is starting to be our >>>>>>>>>>> bottleneck, and we're looking to explore a GPU-based approach to >>>>>>>>>>> it. Paul started working on `v360_{opencl,vulkan}` filters a >>>>>>>>>>> while back, but it wasn't finished, and the `libavfilter` has >>>>>>>>>>> changed since, requiring more development to get them working. >>>>>>>>>>> Here's a link to the mailing list's previous discussion: >>>>>>>>>>> https://ffmpeg.org/ pipermail/ffmpeg-devel/2024- >>>>>>>>>>> June/330229.html >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> <libmilos-so> Our use case is to convert dual-fisheye videos to >>>>>>>>>>> equirectangular in real time, we're basically only doing this >>>>>>>>>>> for now: `v360=dfisheye:e:ih_fov=193:iv_fov=193` >>>>>>>>>>> >>>>>>>>>>> <libmilos-so> Currently we are running it for a single video >>>>>>>>>>> feed, but we're close to hitting resource limits. As we'd like >>>>>>>>>>> to extend to multiple videos, we think that GPU-based >>>>>>>>>>> acceleration would provide us the performance improvement we >>>>>>>>>>> need. Considering your FFmpeg expertise, we were wondering if >>>>>>>>>>> you'd be interested for contracting to help us get this >>>>>>>>>>> implemented for our use case? >>>>>>>>>>> Our mailing list is athttps://ml.whitebox.aero, and if that'd >>>>>>>>>>> be alright with you, I'd like to copy the contents of this >>>>>>>>>>> conversation to the mailing list later. If you're interested in >>>>>>>>>>> the contractual work, it'd be great if we could then continue >>>>>>>>>>> the conversation on the mailing list to keep the team in the >>>>>>>>>>> loop >>>>>>>>>>> >>>>>>>>>>> <libmilos-so> Thanks! >>>>>>>>>>> >>>>>>>>>>> <Lynne> sure, I'd be happy to help >>>>>>>>>>> >>>>>>>>>>> <libmilos-so> Thanks! Could you give me your email address and >>>>>>>>>>> I'll cc you on the thread? >>>>>>>>>>> >>>>>>>>>>> <Lynne> the filter which paul wrote years ago needs quite a bit >>>>>>>>>>> of work, since currently we're rewriting all vulkan filters to >>>>>>>>>>> compile- time spir-v generation >>>>>>>>>>> >>>>>>>>>>> <Lynne> sure, [redacted] >>>>>>>>>>> >>>>>>>>>> For context, we are taking H.264/H.265 dual-fisheye videos from >>>>>>>>>> Insta360 cameras, both from live feeds, and when recorded from >>>>>>>>>> file recordings, and processing them using FFmpeg to produce >>>>>>>>>> equirectangular videos which would then be suitable for playback >>>>>>>>>> in browsers. We are currently using Pannellum player for this, >>>>>>>>>> given our current equirectangular format. If there are more >>>>>>>>>> efficient options on the backend side to achieve the same effect, >>>>>>>>>> we're open to exploring those as well, although frontend clients >>>>>>>>>> would also be phones and tablets, so no heavy operations should >>>>>>>>>> take place on them. >>>>>>>>>> >>>>>>>>>> We are currently developing on RK3588 (on Orange Pi 5 Plus), >>>>>>>>>> which by the documentation supports OpenCL 2.2 and Vulkan 1.2. It >>>>>>>>>> has H.264 and H.265 hardware encoders and decoders, which we've >>>>>>>>>> tried using, but v360 filter ended up being the biggest >>>>>>>>>> bottleneck. >>>>>>>>>> >>>>>>>>>> Here's one example of how we're currently using this filter: >>>>>>>>>> >>>>>>>>>>> return [ >>>>>>>>>>> "ffmpeg",# Decoder settings >>>>>>>>>>> "-fflags","+genpts+discardcorrupt", >>>>>>>>>>> "-flags","low_delay", >>>>>>>>>>> >>>>>>>>>>> "-f","h264", >>>>>>>>>>> "-i","pipe:0",# input from stdin "-r","30", >>>>>>>>>>> >>>>>>>>>>> # Filter settings "-filter_complex", >>>>>>>>>>> f"[0:v]scale=1440:720,v360=dfisheye:e:ih_fov=193:iv_fov=193[out]", >>>>>>>>>>> "-map","[out]", >>>>>>>>>>> >>>>>>>>>>> # Encoder settings "-c:v","libx264", >>>>>>>>>>> "-preset","ultrafast", >>>>>>>>>>> "-tune","zerolatency", >>>>>>>>>>> "-pix_fmt","yuv420p", >>>>>>>>>>> "-profile:v","main", >>>>>>>>>>> "-level","3.1", >>>>>>>>>>> >>>>>>>>>>> # Bitrate settings # This ensures that keyframes are >>>>>>>>>>> pushed >>>>>>>>>>> frequently enough to keep the # streaming latency low >>>>>>>>>>> "-g","30",# keyframe interval "-keyint_min","30",# minimum >>>>>>>>>>> keyframe interval "- sc_threshold","0",# disable scene change >>>>>>>>>>> detection "- muxpreload","0", >>>>>>>>>>> "-muxdelay","0", >>>>>>>>>>> >>>>>>>>>>> "-f","flv",# output format "-rtmp_live","live", >>>>>>>>>>> >>>>>>>>>>> # e.g.:rtmp://srs-dev/live/livestream output_target, >>>>>>>>>>> ] >>>>>>>>>> By my understanding, we likely need a GPU-based v360 filter as a >>>>>>>>>> drop- in replacement for the standard CPU-based v360. I think >>>>>>>>>> that the GPU- based filters would also require `hwupload`/ >>>>>>>>>> `hwdownload`(?), but I don't have experience with it. Personally >>>>>>>>>> I'm new to FFmpeg, so feel free to correct me if something sounds >>>>>>>>>> off. >>>>>>>>>> >>>>>>>>>> The code would ideally be released under a copyleft license, I'll >>>>>>>>>> let Xavier pitch in on this. >>>>>>>>>> >>>>>>>>>> Does this sound like a proper approach to it and something that'd >>>>>>>>>> be interesting for you to work on? >>>>>>>>>> >>>>>>>>>> Thanks! >>>>>>>>>> >>>> _______________________________________________ >>>> whitebox-dev mailing list --dev(a)ml.whitebox.aero >>>> To unsubscribe send an email todev-leave(a)ml.whitebox.aero >>> -- >>> Xavier >>> Whitebox.aero<https://whitebox.aero/> >

1 0

Back from the Nose Reboot - Work Resuming Soon
by Avinash Sah 12 Mar '26

12 Mar '26

Hey, Quick update, I finally got discharged today after the surgery. Everything went well, though I still need to take it a bit easy for a few days so the body can recover properly. Apparently, I had been breathing in 420p all these years without realising it. After the surgery, I’m already at about 2K, and the doctor says in a few weeks I should be hitting 4K :D! I’ll be resuming work starting Monday (16th March). Until then, I’ll mostly be resting and letting my body finish its recovery cycle. Looking forward to getting back into things and catching up with everything next week. Thanks, Avinash S.

2 1

Re: Setting resetting on its own?
by Xavier Antoviaque 12 Mar '26

12 Mar '26

We don't want everyone to subscribe, but we need able to loop in some external people on some threads. Non-member posting on mailing lists is a standard feature since forever, we are counting on it. Again if the issue is spam, with the posts going through the moderation queue we do discard them by hand and let only the legitimate emails in - that's what we have always done until now, and I don't think you had any issue from us? If not, could you please allow this at least the time for us to migrate?This issue is quite cripling to some of the current conversations. -- Xavier Whitebox.aero <https://whitebox.aero/> On Tue, Mar 10, 2026, at 21:05, MailmanLists Support wrote: > Hello Xavier > > Pretty much any sort of online "forum" requires user registration of > some kind in order to post. > > I can add an exception for your list that: rejects messages from > non-members and notifies them that they need to subscribe to the list in > order to post. > > Let me know if that suits. > > Regards > Gadi > > > MailmanLists Support > support(a)mailmanlists.net > Tel: +61 2 7255 9924 > Sydney, Australia (UTC +10:00) > > --------- Original message ------------------ > Received: 2026-03-10 12:11 UTC > From: Xavier Antoviaque <xavier(a)whitebox.aero> > For: Mailmanlists Support <support(a)mailmanlists.net> > Subject: RE: Re: Setting resetting on its own? > >> Unfortunately we need to be able to include others in discussions we hold on the mailing-list, and have their emails appear on the mailing-list. So discarding those emails isn't going to work for us. :/ If you are worried about spam, we had those posts going through the moderation queue, and we were filtering out the few spams by hand. Could you consider allowing at least that option, if not the approval by default? >> >> If this isn't possible, we will unfortunately need to cancel our plan and migrate. :/ Which would be huge pain, especially without advance warning - maybe you could give us time to migrate before enforcing this option? >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/>

2 2

Re: ML approvals
by Xavier Antoviaque 11 Mar '26

11 Mar '26

You mean you sent an email with a non-member email and it didn't go through? Actually, checking the settings again it looks like the mailing list reverted its setting to discarding non-member posts on its own again. I don't think you can access the admin, right, so it did that on its own? I have tried setting that to a different setting, but double-checking after a minute it had reverted also. So I've written to the support about it. I've CC'ed the mailing-list, and also on the current thread, so that others know. -- Xavier Whitebox.aero <https://whitebox.aero/> On Mon, Mar 9, 2026, at 22:30, milos(a)whitebox.aero wrote: > Just did! The test took quite a bit and it didn't even succeed yet :| > > Btw I was talking about this: > > - > https://ml.whitebox.aero/archives/list/dev@ml.whitebox.aero/thread/QFOEZ7EO… > > - > https://ml.whitebox.aero/archives/list/dev@ml.whitebox.aero/thread/6A7FKYZP… > > It happened before as well, with your emails too, I'm not sure if it's > somehow missing the message ID or is there something else, just trying > to figure out if there's any way to avoid it, it'll be a pain to search > stuff in the future if we reply directly on the mailing list (which is > sometimes very convenient - but I guess I can stop that if we cannot > figure it out) > > On 9. 3. 2026. 13:01, Xavier Antoviaque wrote: >> Sorry, I just saw your message on the ML from Friday - all good :) >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/> >> >> On Mon, Mar 9, 2026, at 12:02, Xavier Antoviaque wrote: >>> Ping on this: >>> >>> On Fri, Mar 6, 2026, at 18:04, Xavier Antoviaque wrote: >>>> Don't worry the mailing list software (mailman) know how to deal with >>>> this - just reply all every time, you won't break anything. >>>> >>>> That said thanks for letting me know about the answer, because I didn't >>>> get the email in the moderation queue - actually I looking at the >>>> settings, it was set to discard non-members. Not sure how or who might >>>> have set this, it has to be something recent since it wasn't before. If >>>> you can reply all with the full history of the previous emails below >>>> your response, that would allow me to read it next time. I have changed >>>> the setting to accept emails from non-members. >>>> >>>> -- >>>> Xavier >>>> Whitebox.aero <https://whitebox.aero/> >>>> >>>> On Fri, Mar 6, 2026, at 16:48, milos(a)whitebox.aero wrote: >>>>> Lynne replied, I guess you can see it in the pending approvals. >>>>> Technically, I could reply to it again and break the direct email chain, >>>>> but from the previous similar situations, I think that'd open a new >>>>> thread on the mailing list which can quickly become a mess to read and >>>>> track, both for us and for them. Is that a configurable option we could >>>>> maybe tweak, or maybe our clients' misconfiguration? This is my first >>>>> time using a mailing list so I'm not sure what's up with that, but if >>>>> you want I can test around a bit to figure it out >>>>> >>>>> I've let them know it's pending approval and will come up soon >>>>> >>>>> On 6. 3. 2026. 12:52, milos(a)whitebox.aero wrote: >>>>>> Hey, >>>>>> >>>>>> Paul sent a reply (all) the other day but it didn't end up on the >>>>>> mailing list yet, not sure if you need to approve it. I've CC'd Lynne, >>>>>> not sure if they'll reply to me or all, just a heads up >>>>>>

2 4

[update] 2026-03-10
by milos＠whitebox.aero 11 Mar '26

11 Mar '26

Milos to ATC, #412 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/412 Preliminary investigation, ordered some components for electronics testing #511 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/511 Figured out the root cause, implementation next #503 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/503 Mostly addressed review, should be done for re-review by EOD today

1 0

Re: Setting resetting on its own?
by Xavier Antoviaque 10 Mar '26

10 Mar '26

Unfortunately we need to be able to include others in discussions we hold on the mailing-list, and have their emails appear on the mailing-list. So discarding those emails isn't going to work for us. :/ If you are worried about spam, we had those posts going through the moderation queue, and we were filtering out the few spams by hand. Could you consider allowing at least that option, if not the approval by default? If this isn't possible, we will unfortunately need to cancel our plan and migrate. :/ Which would be huge pain, especially without advance warning - maybe you could give us time to migrate before enforcing this option? -- Xavier Whitebox.aero <https://whitebox.aero/> On Tue, Mar 10, 2026, at 12:24, MailmanLists Support wrote: > --------- Original message ------------------ > Received: 2026-03-10 08:52 UTC > From: Xavier Antoviaque <xavier(a)whitebox.aero> > For: Mailmanlists Support <support(a)mailmanlists.net> > Subject: RE: Setting resetting on its own? > >> Hi, >> >> I am experiencing issues with one of the settings on our mailing list (dev(a)ml.whitebox.aero) hosted on your services. When I try to set this setting to anything else, it just reverts to "Discard": >> This is very disruptive for us, as we have threads that include non-members, and their emails are silently discarded - which is problematic and very confusing to everyone. Could you fix that? We need anyone to be able to write on the mailing-list, preferrably accepting them immediately rather than going through the moderation queue, which can take time to be processed. >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/> >> > > Hi Xavier, > > Users must be subscribed to a list (be a member) for their posts to be > accepted. Posts from non-members are discarded. > > The default for members is their posts are accepted without moderation. > > It is a recently added policy on all lists. It's purpose is to assist > in reducing the number of unwanted emails that members receive. > Complaints of unwanted email lead to the server getting blacklisted. > > See: FAQ What settings are enforced on all lists? - > https://mailmanlists.net/en/faq/07 > > Regards, > > Mark > > MailmanLists Support > support(a)mailmanlists.net > Tel: +61 2 7255 9924 > Sydney, Australia (UTC +10:00)

1 0

Setting resetting on its own?
by Xavier Antoviaque 10 Mar '26

10 Mar '26

Hi, I am experiencing issues with one of the settings on our mailing list (dev(a)ml.whitebox.aero) hosted on your services. When I try to set this setting to anything else, it just reverts to "Discard": This is very disruptive for us, as we have threads that include non-members, and their emails are silently discarded - which is problematic and very confusing to everyone. Could you fix that? We need anyone to be able to write on the mailing-list, preferrably accepting them immediately rather than going through the moderation queue, which can take time to be processed. -- Xavier Whitebox.aero <https://whitebox.aero/>

1 0

[update] 2026-03-09
by milos＠whitebox.aero 09 Mar '26

09 Mar '26

R2D2's *beep boop*, #525 - https://gitlab.com/whitebox-aero/whitebox/-/work_items/525 Ready for review, M.2 vendor agnostic Tried doing a Vulkan helloworld on the OPi but I've had issues getting it up, details in the Vulkan-related thread

1 0