# Introducing pluguzu, a plugin to run Tidal natively in a DAW **URL:** \ **Category:** Announcements\ **Created:** [30 June 2025 14:46 UTC](https://uzu.lurk.org/t/introducing-pluguzu-a-plugin-to-run-tidal-natively-in-a-daw/5758 "2025-06-30T14:46:02Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![tristanC](https://uzu.lurk.org/user_avatar/uzu.lurk.org/tristanc/32/3010_2.png) [@tristanC](https://uzu.lurk.org/u/tristanC)\ **Post date:** [27 January 2026 20:48 UTC](https://uzu.lurk.org/t/introducing-pluguzu-a-plugin-to-run-tidal-natively-in-a-daw/5758/12 "2026-01-27T20:48:21Z")
Hello, happy new year! Here is a change to simplify pluguzu by using a fixed cycle count instead of continuous arcs over the whole project. Previously, the events were rendered as needed, and while it allowed the patterns to play infinitely, this was complicated to do efficiently. This also caused annoying delays when seeking quickly, especially with multiple instances running in parallel. So what I'm proposing to do is to process the events statically for a fixed duration and loop over them. This prompted me to revisit the cycle position implementation to match the host transport, and the new code now properly support bpm modulation by using a tolerance threshold to make the sliding range continuous. This part remain complicated and I wonder if it wouldn't be better to use a midi sync instead when available. Anyway, I'm looking forward to integrate this modification, and I'd be happy to get feedback before merging the PR: > **[Implement fixed cycle count](https://codeberg.org/TristanCacqueray/pluguzu/pulls/19)** > > This change simplifies pluguzu by using a fixed cycle count instead of continuous arc over the whole project. Previously, the events were rendered as needed, and while it allowed the patterns to play infinitely, this was complicated to do... Take care:) --- _[View the full topic](https://uzu.lurk.org/t/introducing-pluguzu-a-plugin-to-run-tidal-natively-in-a-daw/5758)._