March 2026 - whitebox-dev - ml.whitebox.aero

Re: Meeting notes & video: Maps MR - Steps to merge & customization demo by Quinn
by Xavier Antoviaque 01 Apr '26

01 Apr '26

Sounds good for the 2h to bill and for sending the list next week 👍 Thanks Quinn! -- Xavier Whitebox.aero <https://whitebox.aero/> On Tue, Mar 3, 2026, at 21:43, Tracestrack wrote: > Hey Xavier, > > Thanks for the update. I’ll help with the MR review promptly and come up with a ticket of improvement for DevX next week. I will bill two hours for these. Hope that’s okay with you :) > > Best regards > Quinn > >> On 3 Mar 2026, at 12:03, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >> >> Forwarding to you Quinn as I don't think you are on the mailing-list - FYI. >> >> Also note that Avinash is going through an emergency medical operation, so he hasn't been able to look into your MR as planned this week. He should hopefully be back on his feet next week! And in any case I'll make sure we complete the next steps on the MR decided last week. >> >> And we can also move forward with discussing and scheduling the list of improvements you would suggest to the developer experience, as soon as you are ready to post the ticket listing them. >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/> >> >> On Mon, Mar 2, 2026, at 14:27, Xavier Antoviaque wrote: >>> Video for the demo on how to customize map styling by Quinn available at: https://www.youtube.com/watch?v=olQofyT-oqA >>> >>> >>> On Tue, Feb 24, 2026, at 17:47, Zoom wrote: <https://zoom.com/> >>>> >>>> Meeting assets for Maps MR - Steps to merge & customization demo by Quinn are ready! >>>> >>>> Recording >>>> <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> >>>> Duration: 00:10:12 >>>> Shareable link: https://us02web.zoom.us/rec/share/gqF2FJ6bEx1HQfFMcTajyFgj7S1El1AfN5sRM3bza… >>>> Watch recording <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> Share <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fr…> >>>> Cloud recordings will be deleted automatically after they have been stored for 90 days. >>>> >>>> >>>> Meeting summary >>>> >>>> >>>> >>>> Quick recap >>>> >>>> The team met to review Quinn's work on map implementation and styling, which included demonstrating how to use MapLibre and Protomaps for rendering vector maps and customizing styles through JSON files. Avinash and Milos confirmed that the map implementation looked good and was ready for merging, though they noted some remaining work on plugin changes and routing. The team agreed to merge Quinn's work to a feature branch before integrating it into the main repository, with Avinash taking the lead on coordinating the merge process. Quinn also shared his experience with developer onboarding and offered to create a ticket with suggestions for improvements to the documentation and contribution process. >>>> >>>> Next steps >>>> >>>> • Qing: Double check what's left in the current merge request, close any remaining issues, and update the target branch to a feature branch for further collaboration. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Avinash: Handle creation and coordination of the feature branch, and work with Qing to merge the plugin and related changes into the feature branch. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Avinash: Take on the remaining plugin changes, including investigating and implementing a solution for the proxy/hostname issue, starting in the coming sprint. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Qing: Update the README with instructions on how the GeoJSON files for country borders were generated. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Qing: Open a ticket listing suggestions for improving developer onboarding and documentation, based on recent experience, and discuss with the team in the ticket. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Team (Avinash/Miloш): Review and approve the merge request(s) in the next few days after Qing's final checks. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> • Qing: (Optional, if needed) Provide support or feedback to Avinash/Miloш on any remaining scripting bugs or improvements found during further work. <https://us02tasks.zoom.us/?meetingId=vEGFdsaaTZm5o9mFH3tHHQ%3D%3D&stepId=57…> >>>> Summary >>>> >>>> Merge Request Review and Setup >>>> >>>> The team discussed the status of a merge request review, with Quinn demonstrating the setup and testing of a new machine for map data processing. Xavier encouraged the team to review any outstanding issues from the merge request before dividing the remaining work between Avinash and Miloš. Quinn also offered to show the team how to customize the theme and styling of the maps, though this portion of the meeting was not recorded. >>>> >>>> Map Plugin Merge Discussion >>>> >>>> The team discussed merging a map plugin and associated changes. Avinash reviewed the demo and found it mostly complete, with only minor issues to address in the coming sprint. Qing and Miloš agreed to merge the plugin first, followed by the main changes. They discussed the need to document routing and hostname configurations. Avinash and Qing also reviewed the country border data and agreed to update the README with instructions for generating GeoJSON files. >>>> >>>> Map Styling and Code Merging >>>> >>>> The team discussed merging code to a feature branch to keep the master branch clean, with Avinash and Miloš taking on the remaining work. Qing demonstrated how to use Maputnik to style maps, including changing colors, adjusting contour lines, and modifying elevation data. They agreed to have a follow-up workshop on map styling, which Xavier offered to record. >>>> >>>> Protomaps Map Rendering System Demo >>>> >>>> Quinn demonstrated a new map rendering system using Protomaps and MapLibra, which allows for flexible styling and dynamic style changes. Miloš asked questions about the system's functionality, including how it handles data and styles, and Quinn explained the components and their interactions. Xavier suggested improving developer onboarding for contributing to Whitebox, and Quinn agreed to review documentation and provide suggestions. They decided to create a ticket to discuss developer experience improvements. >>>> >>>> >>>> >>>> AI can make mistakes. Review for accuracy. >>>> >>>> Please rate the accuracy of this summary. feedback good <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> feedback bad <https://us02web.zoom.us/meeting/summary/feedback?meetingId=vEGFdsaaTZm5o9mF…> >>>> Edit summary <https://us02web.zoom.us/launch/csd?origin=https%3A%2F%2Fus02web.zoom.us%2Fu…> >>>> >>>> Thank you, >>>> Zoom Support Team >>>> https://support.zoom.us >>>> LinkedIn <https://www.linkedin.com/company/zoom/> >>>> X <https://twitter.com/zoom> >>>> Instagram <https://instagram.com/zoom> >>>> Facebook <https://www.facebook.com/zoom> >>>> YouTube <https://www.youtube.com/@Zoom> >>>> Blog <https://blog.zoom.us/> >>>> Zoom.com <https://zoom.com/>55 Almaden Blvd >>>> San Jose, CA 95113 <https://www.google.com/maps/place/55+Almaden+Blvd,+San+Jose,+CA+95113/@37.3…> >>>> +1.888.799.9666 <tel:1-888-799-9666> >>>> >>>> © 2026 Zoom Communications, Inc. >>>>

1 1

Your meeting recap - Sprint planning & retro - Whitebox
by Fred from Fireflies.ai 31 Mar '26

31 Mar '26

1 0

Notification: recording Sprint planning & retro - Whitebox
by Fred from Fireflies.ai 31 Mar '26

31 Mar '26

1 0

FFmpeg 8.1 released
by Xavier Antoviaque 31 Mar '26

31 Mar '26

Hi Milos, You might have already seen this, but FFmpeg 8.1 has been released and has some useful news for us it seems: > March 16th, 2026, FFmpeg 8.1 "Hoare" > > A new minor release, FFmpeg 8.1 "Hoare" <https://ffmpeg.org/download.html#release_8.1>, is now available for download. Here are some of the highlights: > > • Decoders: xHE-AAC Mps212 (experimental) MPEG-H decoding via libmpeghdec > • EXIF Metadata Parsing > • LCEVC: support for parsing and forwarding metadata > • Vulkan compute-based codecs: ProRes encoding and decoding, DPX decoding > • D3D12: D3D12 H.264/AV1 encoding, scale_d3d12, mestimate_d3d12, deinterlace_d3d12 filters > • **Rockchip H.264/HEVC hardware encoding** > • IAMF: Projection mode Ambisonic Audio Elements muxing and demuxing > • Formats: hxvs demuxer > • Filters: drawvg, vpp_amf > > This release features a lot of internal changes and bugfixes. The groundwork for the upcoming swscale rewrite is progressing. The Vulkan compute-based codecs, and a few filters, no longer depend on runtime GLSL compilation, which speeds up their initialization. > > A companion post about the Vulkan Compute-based codec implementations has been published on the Khronos blog <https://www.khronos.org/blog/video-encoding-and-decoding-with-vulkan-comput…>, featuring technical details on the implementations and future plans. > > We recommend users, distributors, and system integrators to upgrade unless they use current git master. > https://ffmpeg.org/index.html#pr8.1 See also https://www.khronos.org/blog/video-encoding-and-decoding-with-vulkan-comput… -- Xavier Whitebox.aero <https://whitebox.aero/>

2 1

Re: Fwd: Re: Re: FFmpeg v360 Vulkan filter development
by Xavier Antoviaque 31 Mar '26

31 Mar '26

Hi Lynne, That sounds all good to me! Your rate and the 35 hours work - if you see that you might need more, let me know before reaching that point. It will in any case be a good occasion to see where we stand. If you would like to send an invoice for an initial deposit to start the work, that would be fine. For the drivers, it would be good to be able to run the newer drivers - even if we have to apply patches & recompile manually for now, as long as the code used is eventually being merged into the upstream mainline, it is fine as it will not be necessary to apply any newer changes manually once they have propagated. We have to make sure they do make it upstream, though. -- Xavier Whitebox.aero <https://whitebox.aero/> On Thu, Mar 26, 2026, at 14:40, Lynne wrote: > Hi, > > I hope Milos have time to look into this. > I would have no issues writing the filter, my hourly rate is 150 EUR, > and I estimate it would take about 35 hours. I would be able to complete > it by the week after the next, if you accept. > > The concern I have is whether you would be able to switch the software > to newer drivers, capable of handling the Vulkan code. > The SoC ecosystem, which the OrangePi is a part of, has been moving to > open-source drivers and mainline kernel versions. But these changes take > time to propagate and enable by default, and in the case of the > OrangePi, require extra steps after installation to activate. > > The newer open-source drivers will soon be able to handle hardware > decoding of the video to reduce even more CPU usage and latency. The > Vulkan filter is capable of interoperability with hardware decoding, > which would also eliminate the need to upload video frames. > So I think that you should look into using the Mesa drivers to avoid > being locked out of new features in the future. > > On 24/03/2026 11:02, Xavier Antoviaque wrote: >> Hi Lynne, >> >> Thanks for your replies - Milos is off this week, in case he hasn't set an autoresponder. He will be back next week and look into this. >> >> Btw if you want to start charging for the time you spend helping Milos, it would be fair. >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/> >> >> On Fri, Mar 20, 2026, at 08:59, Lynne wrote: >>> Those drivers are incredibly old. >>> Did you have any chance running the panfrost drivers from Mesa? >>> >>> On 20/03/2026 03:30, milos(a)whitebox.aero wrote: >>>> Not sure what's going on with the emails, I didn't receive the original >>>> email, just got this reply. I've run it again with `format=yuv420p`, >>>> still getting practically the same result - created new file in the >>>> snippet named: `run with trace and format=yuv420p`: >>>> >>>> https://gitlab.com/whitebox-aero/whitebox/-/snippets/5967510 >>>> >>>> I've tried looking at the logs but I'm not sure what I'm doing >>>> wrong. Here's also a diff between the first and second outputs if that >>>> helps, left one is the previous run, right one is this new run: >>>> >>>> https://www.diffchecker.com/qPET78MB/ >>>> >>>> On 19. 3. 2026. 15:32, Xavier Antoviaque wrote: >>>>> Milos -- making sure you have received and seen this email reply from >>>>> Lynne, below. >>>>> >>>>> -- >>>>> Xavier >>>>> >>>>> On Tue, Mar 17, 2026, at 18:53, Lynne wrote: >>>>>> Ah, ok. You need to add ",format=yuv420p" after hwdownload, e.g.: >>>>>> "hwupload,avgblur_vulkan=planes=0,hwdownload,format=yuv420p" >>>>>> >>>>>> Could you test again? >>>>>> >>>>>> On 17/03/2026 18:22, milos(a)whitebox.aero wrote: >>>>>>> Hey Lynne, >>>>>>> >>>>>>> I only got this email by Xavier, sorry. >>>>>>> >>>>>>> There seems to be a space inside the initial URL, maybe the email >>>>>>> client >>>>>>> mangled it somehow. I've reuploaded it to pastebin: https:// >>>>>>> pastebin.com/BjmkgkzL >>>>>>> >>>>>>> On 16. 3. 2026. 18:00, Xavier Antoviaque wrote: >>>>>>>> I did get it on my side, - Milos those emails are visible at https:// >>>>>>>> ml.whitebox.aero/archives/list/dev(a)ml.whitebox.aero/thread/ >>>>>>>> JYXZMGH7NMFPNXXNQ2KDUAGGIC6IPRZK/ (the email shown on that page, and >>>>>>>> the one that you can expand below it). >>>>>>>> >>>>>>>> And FYI, hopefully the mailing issue should be solved now, which >>>>>>>> allowed your email to show up there so I could link to it :) >>>>>>>> >>>>>>>> Btw Lynne did you get my previous email about how to contract? If it >>>>>>>> has been lost in the mess I can send it to you again. >>>>>>>> >>>>>>>> -- >>>>>>>> Xavier >>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>> >>>>>>>> On Sat, Mar 14, 2026, at 00:28, Lynne wrote: >>>>>>>>> Err, didn't you receive my 2 replies? Today, and 2 days ago. >>>>>>>>> >>>>>>>>> On 14/03/2026 00:18, milos(a)whitebox.aero wrote: >>>>>>>>>> Hey Lynne, >>>>>>>>>> >>>>>>>>>> Just wanna check if you've seen our previous emails. >>>>>>>>>> >>>>>>>>>> Thanks! >>>>>>>>>> >>>>>>>>>> On 10. 3. 2026. 22:35, Milos Petkovic via whitebox-dev 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/> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> whitebox-dev mailing list --dev(a)ml.whitebox.aero >>>>>>>>>>> To unsubscribe send an email todev-leave(a)ml.whitebox.aero

2 1

2026-03-26 Update
by Avinash Sah 27 Mar '26

27 Mar '26

Hey, #515 https://gitlab.com/whitebox-aero/whitebox/-/work_items/515 Continued working on this. Thanks, Avinash S.

1 0

2026-03-25 Update
by Avinash Sah 26 Mar '26

26 Mar '26

Hey, #241 https://gitlab.com/whitebox-aero/whitebox/-/work_items/241 Comments addressed. #515 https://gitlab.com/whitebox-aero/whitebox/-/work_items/515 Almost ready, minor cleanup pending. #513 https://gitlab.com/whitebox-aero/whitebox/-/work_items/513 Issue identified and resolved; testing pending before marking ready for review. Thanks, Avinash S.

1 0

Your meeting recap - Sprint planning & retro - Whitebox
by Fred from Fireflies.ai 24 Mar '26

24 Mar '26

1 0

Notification: recording Sprint planning & retro - Whitebox
by Fred from Fireflies.ai 24 Mar '26

24 Mar '26

1 0

Please sign up to invite Fireflies
by Fred from Fireflies.ai 24 Mar '26

24 Mar '26

Hi there, It appears you emailed or invited fred(a)fireflies.ai to an upcoming meeting: <div style="border-radius: 5px; border: 1px solid gray; padding: 6px"><b>[whitebox-dev] Re: Fwd: Re: Re: FFmpeg v360 Vulkan filter development</b><br></div> In order to have Fireflies record & transcribe your meetings, you'll need to first make an account for consent. If you believe you already have an account please confirm that the email of the account corresponds with the invite email.<div><a style="display: flex; text-decoration: none" href="https://app.fireflies.ai/login"><button style="border-radius: 6px; border: none; font-size: 16px; margin: 10px auto; padding: 12px 48px; background-color: rgb(110, 117, 255); color: white">Sign Up</button></a></div>Thanks, Fred Fireflies Your AI Meeting Assistant

1 0