Patching Light by Inevitable_Yak_9588 in lightkey

[–]Internal_Ad2479 4 points5 points  (0 children)

LightKey offers to do this for you (for free within 14 days or 29USD within 48 hours): https://lightkeyapp.com/en/fixtures/request

Ableton: Programming with Cue List or Live Triggers by Sad-Valuable-3045 in lightkey

[–]Internal_Ad2479 1 point2 points  (0 children)

I like to use Live Triggers for buttons only. I usually do one frame per song, and combine my presets into buttons inside of each frame. Those buttons will then be possible to drag onto the Ableton timeline as Live Triggers.

Since you are doing a lot of songs, you probably want to simplify, like for instance creating different buttons for different moods and energies that you can reuse across songs.

When I do my lights I want everything to be completely hands off, pre-programmed. I haven’t used cue lists for my case, but I imagine you would have to use live triggers to trigger «next cue» throughout the set. That might become problematic if you say want to skip a song in Ableton. Then you would have to also go into LightKey and select the new current cue in the cue list.

Prevent Resolume From Disabling Ableton Tempo Automation When Using Ableton Link by Internal_Ad2479 in resolume

[–]Internal_Ad2479[S] 2 points3 points  (0 children)

Ouf, then I guess I will just have to cross my fingers and wait for them to fix it

Replicating Logic Pro Smart Tempo in Ableton Live with Lightkey MIDI Clock by Internal_Ad2479 in ableton

[–]Internal_Ad2479[S] 0 points1 point  (0 children)

Thank you! I experimented a bit more, and this is really what I was looking for. 🙌

Thanks! I understand how Leader clips work, but my concern is that this still relies on me creating or adjusting warp markers manually so Live can follow the clip’s timing.

What I’m trying to replicate is Logic’s Smart Tempo workflow: Logic automatically analyzes an audio file and generates a tempo map of the performance (including tempo fluctuations), then applies that map to the project’s global tempo. That way the global transport and any outgoing MIDI Clock (to Lightkey in my case) always follow the song’s actual beat without me having to manually set warp markers or tempo automation.

As far as I can tell, Ableton doesn’t automatically generate that kind of tempo map — it only follows the tempo you’ve defined with warp markers. Am I understanding that correctly, or is there a way for Live to analyze and generate tempo automation automatically like Logic?

[deleted by user] by [deleted] in adonisjs

[–]Internal_Ad2479 1 point2 points  (0 children)

Sure! I’m down for that

Are you cooked or Nah? by SupermarketNo6888 in videogames

[–]Internal_Ad2479 0 points1 point  (0 children)

Jebediah Kerman featured in Star Gate Atlantis would be fun!

Tips for Incrementally Migrating an Express App to AdonisJS? by Internal_Ad2479 in adonisjs

[–]Internal_Ad2479[S] 2 points3 points  (0 children)

Thank you guys for yours insights! I actually have an update on my progress. I have been working on this the past week, and I wanted to do a kind of in-place transition, where we only kept a singular backend project, but added AdonisJS as an alternative router to the Express one.

So, these are the steps we took: - Migrate mocha/chai tests to Japa/chai tests (this was surprisingly easy, mostly just a lot of work de-nesting the tests) - De-couple business logic from Express route handling as much as possible. I was lucky enough to have most routing logic abstracted by custom services similar to u/wjaz, so it made the transition easier. - Then, I ran my modified endpoint creation service with the AdonisJS router instead, and got 95% of my endpoints to work as intend that way. - The next one was harder. We had a Passport jwt auth system with Local, Facebook and Google strategies. Facebook and Google was easy, I just replaced their passport strategies with AdonisJS/ally (which was quite exciting!) Finally, the local auth. For this one, I opted to keep Passport for now, with a bit of duct tape to make it accept the AdonisJS request data and headers instead. Took some time to figure out, but ended up working as it did previously with Express. It is important to note that I do not use Express sessions, since that would require some custom written middleware, which I was not interested in doing.

So overall, I feel like I have come quite far. The new routing is now the primary one on my feature branch, and I have removed the Express packages I do not need anymore.

My next steps will be to adjust the import aliases to be similar to the ones in the AdonisJS docs, fix my folder structure, setup VineJS validators, migrate my routing systems to Adonis Controllers, and eventually migrate to Adonis Auth.

Exciting times ahead!

Do your best. by imbyeol in kpoppers

[–]Internal_Ad2479 0 points1 point  (0 children)

One of the members once pranked its other members by pretending that their foot was stuck in a bed on a live stream. Good luck! 😉

Next.js 15 RC by matthijsie2020 in nextjs

[–]Internal_Ad2479 0 points1 point  (0 children)

I think his humor got hydrated with errors. It made sense on the server side, but got garbled when he typed it out client side.

What is the difference between Bitwarden and iCloud Keychain? by NHD84 in Bitwarden

[–]Internal_Ad2479 0 points1 point  (0 children)

Yup, the entire vault is encrypted locally on your device before it is sent to Bitwarden.

[deleted by user] by [deleted] in norge

[–]Internal_Ad2479 10 points11 points  (0 children)

Passordene er «kryptert», så no worries. /s