chrisle

rbxport GitHub Overview: Lightweight DJ Library Prep for USB and PRO DJ LINK rbxport by chrisle: chrisle/rbxport rbxport is a focused open-source DJ library manager built around fast preparation and export. This overview explains how its Rust-based core works with an existing analyzed track library, why the smaller feature set keeps memory use low, and where the tool fits alongside a primary DJ suite. You’ll see the release and macOS access context, the read-only library connection, the database-locking caveat, playlist and cue-point handling, and the features deliberately left out: performance playback, stem separation, and cloud synchronization. The workflow then moves through simultaneous export to two USB drives, Max Compatibility conversion for older CDJ hardware, automatic safe eject, and PRO DJ LINK streaming over Gigabit Ethernet. TimeStamps: 0:00 Why a focused export utility 0:56 Getting rbxport and macOS access 1:40 Library loading and database locking 2:23 Focused interface and memory footprint 3:05 Dual-USB export and Max Compatibility 4:11 Safe eject and gig-ready drives 4:28 PRO DJ LINK over Ethernet 4:48 What rbxport leaves you ready to do 🧰 Lightweight library preparation with an optimized Rust core 💾 Simultaneous export to two USB drives 🔌 PRO DJ LINK streaming for compatible standalone players For DJs who already analyze tracks in a primary library manager, rbxport’s value is a narrower preparation path: keep playlists, cues, and beatgrids available while avoiding the overhead of a full performance suite. The main tradeoff is intentional scope—analysis and performance features remain outside this utility. #rbxport #DJSoftware #PRODJLINK [es-US] YNAS ynp_6bd585fc82958b9e cinemático Carga de entorno de prueba de automatización privada. Identidad del paquete: ynp_6bd585fc82958b9e; salida: cinematográfica. [fr-FR] YNAS ynp_6bd585fc82958b9e cinématique Téléchargement de l'environnement de test d'automatisation privé. Identifiant du package : ynp_6bd585fc82958b9e ; sortie : cinématique. [hi] YNAS ynp_6bd585fc82958b9e सिनेमैटिक निजी स्वचालन स्टेजिंग अपलोड। पैकेज पहचान: ynp_6bd585fc82958b9e; आउटपुट: सिनेमाई। [id] YNAS ynp_6bd585fc82958b9e sinematik Unggahan staging otomatisasi pribadi. Identitas paket: ynp_6bd585fc82958b9e; output: sinematik. [it] YNAS ynp_6bd585fc82958b9e cinematic Caricamento di automazione privata. Identità del pacchetto: ynp_6bd585fc82958b9e; output: cinematografico. [pt-BR] YNAS ynp_6bd585fc82958b9e cinemático Upload de teste de automação privada. Identidade do pacote: ynp_6bd585fc82958b9e; saída: cinemática.

👋 Welcome to r/RBXport - Introduce Yourself and Read First! Hey everyone! I'm u/biz-nm, a founding moderator of r/RBXport. This is our new home for all things related to RBXport software. We're excited to have you join us! This is a community for DJs using RBXport, the free, fast library manager and USB/LINK exporter that works directly with your existing rekordbox library. We are NOT associated with Triode or RBXport in any way but wanted to create a space for people to discuss things here regarding the software. Whether you've just downloaded it or you're exporting to four sticks at once before every gig, you're in the right place. RBXport is independent and not affiliated with or endorsed by Pioneer DJ / AlphaTheta. What to Post - Help. Stuck on something? Ask! No question is too basic BUT there is also a public discord channel this is quite active discord.com - Workflow/Tip. Show us how you prep sets, organize playlists or handle exports. - Hardware Compatibility. Tell us what worked, or didn't, on your players. - Discussion. Comparisons, questions, ideas and general library-management talk. Please flair your post and give it a descriptive title. "LINK export not showing on XDJ-RX3 (macOS 14)" will get answers much faster than "help!!!" What NOT to Post - Feature Request. Use Discord or Github - Bugs - 🐛 Found a bug? Please report bugs on GitHub: github.com/chrisle/rbxport/issues Search the existing issues first, and include your OS, RBXport version, hardware, and steps to reproduce. Not sure whether it's a bug or a setup problem? Ask here with the Help flair and we'll help you figure it out. Useful links - 🌐 Website and downloads: rbxport.com - 🐛 Bug reports: GitHub Issues - 💻 Source code and contributions: GitHub - 💬 Real-time chat: TRIODE Discord Say hi! 👇 Introduce yourself in the comments: - What gear do you play on? - How big is your library? - What made you try RBXport? Thanks for being part of the very first wave. Together, let's make r/RBXport amazing.

Some thoughts on all the vibing out there I think it's great that there are so many new individual authors putting out new software, but I want to caution on some things I've noticed, background I'm a senior dev with 20+ years of experience. - AI has a weird fetish for reimplementing literally everything from scratch when you tell it to go nuts, this results in subpar results and occasionally insane things - 99% of the time someone has already done something you're trying to do, so the first step is always "for this feature please search the web and see what others are doing" - AI makes a lot of mistakes, CI, linters, and review agents need to be part of your pipeline, as well as reviewing code - Your code is only as good as your testing, so ensure that you test test test and you have hundreds of songs in your test cases For an example, I need beatgrids for my AZ. So I started trying to work on that. It ended up being a several day thing now involving me testing hundreds of tracks... - Vinyl rips can have different BPMs throughout the track as the BPM drifts, sometimes linearly sometimes not - Some songs have weird BPM changes from splicing stuff together - It's common for methods to become confused if there are offbeats or tempo changes I reached for what looks like the current AI based SoTA (Beat This! from 2024). However I noticed that it struggled with things like vinyl rips, despite having high accuracy during things with tempo changes, and occasionally there was drifting error for no reason at all, probably because it's a NN. Aside from my software gitlab.com We have two competing implementations of beatgrid detection in the past two weeks alone posted here: - github.com/jwilkins/booth/blob/main/proto/musicai… - github.com/chrisle/rbxport/blob/main/src-tauri/sr… (I checked them both and they both fail a number of my tests cases...) And likely there are several more on github in the past week, as I found a bunch more but didn't look into them closely. I've been chipping away at my test datasets for a while now and building iterative improvements, but... every aspect of this software can require some thought, investigation, and hundreds of test cases. So please take care and time and investigate your features deeply and see what others have done. An hour asking the LLM "who has done this before, and how successful were they? are there papers?" will save you days or weeks of fighting broken ad hoc implementations of things that have previous solutions. I won't guarantee my solutions are perfect either 🙂 Still in progress, and always, dependent on the amount of test data and the time I have to annotate it... Best of luck and keep creating!!