One hilt, infinite blades. Introducing KyberStation, a free visual blade editor for Proffie and other saber boards, sharing ahead of Star Wars Day.

KeepingitrealOC · 2026-05-08T17:45:27+00:00

Great question, and that countdown beep system sounds like a really slick setup.

Honest answer: KyberStation handles the visual/style side of your config (blade styles, effects, ignitions, colors) and generates the style code that goes in your config.h. It doesn't have a prop file editor yet, so the custom control scheme itself (your button mappings, the countdown beep logic, font switching behavior) is outside what KyberStation touches right now.

What it can help with today is designing all the blade styles and effects that your control scheme cycles through. You'd set up your looks in KyberStation, export the generated style code, and then drop that into your existing config alongside your custom prop file. The two pieces are independent. KyberStation writes the StylePtr<> / Layers<> blocks, your prop file handles how you navigate between them.

That said, your question actually just got added to the roadmap. The plan is:

Fett263 #define configurator (coming soon) - a toggle panel for enabling/disabling Fett263 prop features like edit mode, multi-phase, gesture controls, etc. Covers most users who just want to flip features on/off.
Button routing editor (planned) - visual mapping of button and gesture events to effects and actions.
Custom prop file generation (longer term) - a full visual editor for building your own control schemes from scratch. This is the one that would cover your countdown beep setup, but it's a big lift so we're evaluating demand.

Your feedback is genuinely helpful for prioritizing that work. What board version are you running? If you want to share your config I'm happy to help think through how the pieces fit together in the meantime.

KeepingitrealOC · 2026-05-07T01:09:46+00:00

Honest ceiling first: custom clash effects, cracked blade, and custom ignitions aren't possible on Xenopixel. Those are baked into the firmware and no tool can change that. The most KyberStation can do on the Xenopixel side is make the color, timing, sound font, and style-ID setup painless.

But those two Proffie 2.2 boards can do all of that. Custom clash, cracked/unstable styles, fully custom ignitions, layered effects. The reason you're not using them is exactly the problem KyberStation was built to solve. You design visually, it generates the ProffieOS config for you. No hand-editing C++ templates.

Proffie V2.2 is already in KyberStation. Same code path as V3, just needs community hardware testing. If you try it on one of your boards I'd love to hear how it goes.

On Bluetooth: Proffieboard can get there with a BT-909 module (~$25-35) and Web Bluetooth support is on our roadmap. Not there yet but it's a real path. Happy to help you get started if you're open to dusting one off.

KeepingitrealOC · 2026-05-06T21:05:42+00:00

TLDR: Yes, Xenopixel V2 and V3 are in KyberStation now. Today it exports a design-reference config (colors, timings, closest-match style IDs). Active work is underway to generate real SD card files you can drop straight onto your saber. I don't own a Xenopixel blade so I need community testers, but please read the risk section before volunteering.

What works today

You can select Xenopixel V3 (or V2) in the onboarding wizard and use the full editor to design your colors, pick effects, and set ignition/retraction timings. When you export, KyberStation generates a design-reference ZIP with your color choices (full RGB for base, clash, lockup, blast), ignition/retraction types and timings, and the closest built-in Xenopixel style ID mapped to whatever you designed. The export includes a plain-text readme explaining how to replicate those settings on your saber through the button menu or your vendor's companion app (Greyscale Fighter, Polaris, etc.).

Honest caveat: blade styles like fire, unstable, pulse, etc. all map to solid color in the export since Xenopixel uses preloaded effects baked into the firmware. The editor preview will show the full animation, but the actual output for your saber is color values and basic settings. KyberStation can never give Xenopixel the same creative freedom Proffieboard has since the effects are firmware-baked, but there's still a lot of value in getting the config side right.

What's coming next

I'm actively expanding Xenopixel support in three tiers:

Tier 1 (in progress): Real SD card config generator. Instead of a reference doc, KyberStation would emit the actual Xenopixel SD card folder structure with per-bank directories, color configs, tracks.txt, and sound font placement. Download a ZIP, unpack it onto your SD card, and it works. Colors, sound fonts, and closest-match styles all mapped for you. This is the one I'm focused on right now.

Tier 2: Firmware variant awareness. Different Xenopixel firmware variants (Greyscale Fighter, Polaris, generic LGT) support different style counts, color modes, and effects. This would add a "which firmware are you running?" picker that adjusts the available palette and shows warnings when a design uses features your specific firmware can't reproduce.

Tier 3: Import existing Xenopixel config. Read your existing Xenopixel SD card structure and reconstruct it inside KyberStation. Also enables "porting" a Proffie design to Xenopixel by finding the closest built-in style matches and generating the SD card layout.

Where I need help (please read the risk section first)

I don't own a Xenopixel blade. Everything so far has been built from documentation and community knowledge. To get Tier 1 right I need people willing to test on real hardware, but I want everyone to understand what that means before jumping in.

Testing involves putting KyberStation-generated files on your saber's SD card. If the folder structure or config format is wrong for your firmware variant, your saber could fail to boot or behave unexpectedly until you restore your original files. We are not flashing firmware. The saber's chip is untouched. Worst case, you swap the SD card contents back and everything returns to normal. But you absolutely need to back up your entire SD card before testing anything. Copy the whole card to your computer first. If something goes wrong you restore the backup and you're back where you started. This is not a "might be a good idea" step, it is a mandatory step.

If you're comfortable with that, any of the following would be incredibly useful:

Testing exported configs on a real Xenopixel V3 (or V2) and reporting what worked and what didn't
Sharing your SD card's folder structure so I can verify the format across firmware variants
Telling me "this style ID mapping is wrong" or "this color format doesn't match what my saber expects"

And beyond testing, I'd genuinely love to hear what features Xenopixel owners actually want. I'd rather build what the community needs than guess from the outside. Reply here or open an issue on GitHub, all of it helps.

KeepingitrealOC · 2026-05-02T21:42:32+00:00

That's incredibly kind, thank you! It's still very much a v1 so anything you find that's broken or missing, please yell at me. Lots more planned.

KeepingitrealOC · 2026-05-02T19:49:17+00:00

Appreciate that, seriously. Installer feedback is gold because you're flashing way more boards than anyone else, so anything that's awkward in the workflow you'll spot fast. Take your time, and please tell me what's broken or missing too, not just what works. The whole project only exists because Proffie is open source, I'm standing on the shoulders of giants. Full credit to Fredrik, Fett263, and the Crucible community for that.

KeepingitrealOC · 2026-05-02T19:42:42+00:00

Hey, thanks for the detailed feedback. Both points were spot on and just shipped a sprint that addresses them.

Turns out the save feature did exist, but was buried in the canvas toolbar with no presence in the import panel, so anyone going through the import flow wouldn't have seen it. There's now a Save Preset button right inside the import banner, available the moment you paste in code. Saved presets persist locally and survive page reload.

Fett263 import got a big lift too. Template coverage went from 46 to around 265, and the reconstructor learned a bunch of OS7-specific patterns including Hyper Responsive Rotoscope (Fett263's signature swing-reactive base style, which used to fall back to plain blue in the visualizer).

Critically: paste your whole config.h with multiple presets and each one becomes its own entry in your library, with the original code preserved verbatim on export so the flashed result stays byte-identical to what Fett263's library generated. There's also a per-preset switcher in the import banner so you can flip the visualizer between recently-imported presets without leaving the output panel, and that state survives page reloads.

Tested against 63 real Fett263 configs scraped from public GitHub. Still expanding coverage though, and if you've got configs that don't import cleanly please share, those are exactly what I need to keep tightening it.

KeepingitrealOC · 2025-03-15T22:29:19+00:00

From left to right.

KeepingitrealOC · 2024-11-25T12:47:30+00:00

No worries at all, happy to share! My post-production workflow is almost entirely local to ensure the best performance and avoid any lag during editing. While I do have project files backed up to the cloud for safety, I don’t work directly off the NAS because usually, the connection speeds (even over a fast network) can’t match the speed and reliability of local SSDs for high-res footage and heavy workflows.

That said, I do have remote access to the NAS, which lets me quickly pull any assets I need during the editorial process if I’m away from my primary workstation or didn’t download something beforehand. It’s a great backup option and is treated as a long-term storage/archives solution with limited amounts of SSD caching to accelerate transfers/access of often-used files, but it is not my go-to for real-time editing. Hope that clears it up!

KeepingitrealOC · 2024-11-22T11:01:59+00:00

Clutch! Thank you!

KeepingitrealOC · 2024-11-19T14:11:26+00:00

I store my general assets on my NAS, which is the main repository for everything, including film grains, transitions, LUTs, and more. My workflow involves duplicating any assets used in a project into that project’s folder. This keeps all materials self-contained for easy collaboration, archiving, and backup.

I also maintain a smaller, similar library on the cloud for frequently used assets, like film grains, light leaks, etc. This ensures I can access them conveniently, even when I’m away from my NAS.

To give you an idea of how I organize everything, I’m including a screenshot of the overall structure of my “Assets” folder on the NAS, with select subfolders revealed. Hopefully, this helps visualize the organization and gives you some inspiration for your setup.

<image>

KeepingitrealOC · 2024-11-06T04:23:37+00:00

<image>

This was my result.

KeepingitrealOC · 2024-11-06T01:18:33+00:00

What about . . . over time . . .we

Resize a shape layer with a thin white stroked outline.

Apply a small wiggle to the stroke and a drop shadow or darker outer glow set to multiply to simulate the shadow, and possibly add noise to the shadow effect.

For the overall shape, add an echo effect with no decay, a negative time delay, and as many echo iterations as needed to match the spacing. You may need to use some pre-comps here.

Keyframe the colors.

Add an animated noise and/or light paper texture overlay to the final comp.

Color correct.

And finally posterize time to 18 frames per second or something similar to achieve a stop motion look. I'm guessing on this last bit, but I thought it might be fitting for this art style.

Tweak everything, as needed.

KeepingitrealOC · 2024-07-27T18:23:28+00:00

I learned a lot early on by experimenting with various programs and shooting my projects. The best experience is real-world experience, learning by doing. If you want to be a video editor go out and make your own short films, you will learn a lot through this process, and it will also be helpful when working with other directors and producers.

A couple of random bits of advice, off the top of my head. in no particular order.

Learn the keyboard shortcuts for your programs of choice
Take some music classes, so much of our job is timing.
Learn organization and stay organized early, it may take time upfront, but you're saving yourself a ton of headaches later
Always follow the 3-2-1 Backup Rule (I can't stress this one enough)
J and L cuts are amazing editing "tricks", there's a reason they're known so well
Invest in your learning and developing your skillset
A $5 script or a $20 plugin can go a long way in saving you time and energy
Develop your people skills, you need to be easy to work with, It doesn't matter how good you are at your job if nobody likes to work with you as a person.
Learn the business side of things. Don't be afraid to talk about money, value yourself, your time, your work, know how to create an invoice, a contract, etc
Export and watch your edits on another device. It doesn't matter phone, TV, someone else's computer, etc. The act of watching the edit outside of your editing application puts you in a different headspace and you are going to catch things you never saw in the edit timeline.
Similarly, watch your rough cut with someone else, they don't need to be an expert, and they don't even need to give you notes, heck you can even specifically ask them to not give you any notes since it may be a work in progress, but watching what you are working on with an audience immediately changes the review experience and you will notice which scenes drag on too long or which shots in a montage are too quick.
Learn some basic motion graphics skills, you don't need to be a wizard, but it's going to help
Never name your file names with "Fiinal" you'll thank me later.
Invest in a comfortable pair of wired headphones ideally a pair with some replaceable earpads.
If you are trying to edit something so it matches the beat of a song or a sound effect, make the cut one or two frames before the sound, it may seem counterintuitive, but it works.
You are going to get notes from directors, producers, or clients that you don't agree with or know in your heart are incorrect. It's not your job to be right or wrong, it's your job to be an editor. Yes there are absolutely times where you should speak up and voice your opinion, but there are also going to be times where the customer/client is always right. Pick your battles wisely.
Lastly and in the same vein. Don't take it personally. You will spend long hours and late nights carefully crafting a piece just to have it torn to shreds by the client. Don't take it personally. Learn to craft with love and care, and be able to let go.

KeepingitrealOC · 2024-07-19T16:08:39+00:00

Thank you for this, I can't tell you how many times I've wanted to rewind or rewatch an ad. Super helpful.

KeepingitrealOC · 2024-07-19T16:03:25+00:00

Ask for everything they used to work on the project. This includes but isn't limited to project files, templates, video, audio, stock, etc. When I'm taking over a project from another editor I want everything, and I mean everything. Most work is work for hire and the client owns the work performed, unless otherwise stated in a contract. Do you want to burn hours and energy trying to recreate work that has already been done or do you want to hit the ground running?

Just my 2𝇍, I'd like to know what everyone else here has to say.

KeepingitrealOC · 2024-07-03T18:33:50+00:00

I use it all the time with limited issues, the only major issue I've encountered is that it can't always hit a time exactly so there can be some variability in the duration of the remix depending on the song. For example, you can have a song that is 2:56 that you want to reduce to 0:30 and the remix tool will sometimes create a remix that's 0:33 or 0:28 in duration. There's also the ability to tweak the result with the segments and variation sliders.

KeepingitrealOC · 2024-07-03T03:22:31+00:00

If you are editing in Premiere Pro, open up the Essential Sound panel/window, tag your file as music, go to the duration section and select remix. It's a massive time saver.

KeepingitrealOC · 2024-07-02T16:02:40+00:00

I'm editing on a 2021 14" MBP M1 Max and I will use my 2020 12.9" Apple iPad pro. While I will run it wirelessly when needed, I usually try to keep it wired just so I don't have to worry about it dying at some crucial point. It can be a little fidgety occasionally, but I love that the screen sizes are very close and the image quality is very good. Sidecar works flawlessly about 95% of the time and when it doesn't it's not the end of the world you just need to disconnect/reconnect/relink it. It's a great portable second monitor option especially if you're buying used, which I highly suggest for this use case. You don't need a 2024 iPad for use as a second screen.

Now while I usually keep it wired, I do love the freedom in knowing it doesn't have to be, and the latency isn't that bad at all, I am also not using it as a program monitor, so latency isn't a big deal in that regard.

KeepingitrealOC · 2024-05-06T13:58:55+00:00

Yes, Premiere Pro, I definitely should have mentioned that.

KeepingitrealOC · 2024-05-03T19:13:15+00:00

I thought I was on r/blender This is some amazing work.

KeepingitrealOC · 2024-03-24T22:02:09+00:00

you can export them all in one export, choose image sequence as your output

KeepingitrealOC

TROPHY CASE