# Beat countdown to next cue point

**URL:** <https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162>\
**Category:** Suggestions\
**Tags:** macOS, iOS\
**Created:** [July 26, 2024, 2:56pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162 "2024-07-26T14:56:25Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [October 1, 2025, 12:07am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/25 "2025-10-01T00:07:32Z")

</div>

There’s already a suggestion post on this topic. Go vote 🙂

> [@Beat countdown to next cue point](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162):
>
> Suggestion for a beatcouunter counting down to next cue point. This is excellent for phrase mixing and most dj software have it. Please add this feature slight_smile

---

<div class="post-metadata">

**Author:** ![Cuzer](https://community.algoriddim.com/letter_avatar_proxy/v4/letter/c/b487fb/32.png) [@Cuzer](https://community.algoriddim.com/u/Cuzer)\
**Post date:** [October 9, 2025, 1:58pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/26 "2025-10-09T13:58:36Z")

</div>

Hi @Slak_Jaw

As @Jay_Dizzle says, this is an open request and I’ve just voted, screengrab below is wha I was referring too, seen a few video demonstations where the beat and bar count is ver visibile and can count down to set cue points etc

 ![a363e2ba10fa15a1f2359907741e825bdf2dd8ef_2_690x455](https://community-assets.algoriddim.com/original/3X/5/0/5098790655380f8aad5acb55c70fb3ad1fb48658.jpeg)

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [October 9, 2025, 2:27pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/27 "2025-10-09T14:27:53Z")

</div>

Thanks for sharing @Cuzer. This suggestion already exists so I’ve merged yours with this one.

---

<div class="post-metadata">

**Author:** ![Flexstyle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/flexstyle/32/13032_2.png) [@Flexstyle](https://community.algoriddim.com/u/Flexstyle)\
**Post date:** [October 13, 2025, 6:22pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/28 "2025-10-13T18:22:45Z")

</div>

This feature is the single thing standing between me and a new djay subscription.

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [October 13, 2025, 6:27pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/29 "2025-10-13T18:27:11Z")

</div>

Thanks for the feedback @Flexstyle

---

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [November 13, 2025, 1:08am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/30 "2025-11-13T01:08:56Z")

</div>

Just keeping this alive. Please vote.

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [November 13, 2025, 10:08am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/31 "2025-11-13T10:08:19Z")

</div>

Thanks for bumping this topic @Jay_Dizzle

---

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [November 16, 2025, 11:49am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/32 "2025-11-16T11:49:42Z")

</div>

Make it happen 😉 @slak_jaw

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [November 16, 2025, 11:51am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/33 "2025-11-16T11:51:39Z")

</div>

Okay @Jay_Dizzle, I’ll see what I can do…

---

<div class="post-metadata">

**Author:** ![brunolima](https://community.algoriddim.com/user_avatar/community.algoriddim.com/brunolima/32/6981_2.png) [@brunolima](https://community.algoriddim.com/u/brunolima)\
**Post date:** [November 21, 2025, 7:02am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/34 "2025-11-21T07:02:34Z")

</div>

It’s actually a feature I’m not familiar with because I don’t use other apps. But if it were incorporated, it would be very helpful to see the count on the screen.

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [November 21, 2025, 2:53pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/35 "2025-11-21T14:53:19Z")

</div>

Thanks for the input @brunolima

---

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [December 2, 2025, 5:05pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/36 "2025-12-02T17:05:19Z")

</div>

I have a new “different” and "easier to implement"approach. @Slak_Jaw . I believe. Maybe if you add an option instead of - Beat counter to next cue point. Allow us to add more “Set (1)” as in “Set (2)”, “Set (3)” up to 8 (hot cues) this could be a solution. Since Djay actually counts down in minus til the 1 marker.

 ![Screenshot 2025-12-02 at 18.01.03](https://community-assets.algoriddim.com/original/3X/a/f/af8ab5fd40b0f9a69452d1bd1648beb2fef618cf.png)

As you se in the pic below the first 8 bars are in minus, counting down to the “set (1)” marker

 ![Screenshot 2025-12-02 at 17.54.30](https://community-assets.algoriddim.com/original/3X/0/e/0edf96bc9a2c152eef4574f85a9297ce6add278a.jpeg)  
🙂

Either way. The display of each bar being In minus as in -4, -3, -2 etc is an excellent way to see how much is left til the hot cue. So I hope either how you decide to implement this feature, You guys will keep use this method. There’s no need for an extra displayed Bar counter elsewhere. if that makes sense.

Just a suggestion. Since I’m running out of patience and soon giving up and moving back to rekordbox and traktor ☹

---

<div class="post-metadata">

**Author:** ![allentastic](https://community.algoriddim.com/user_avatar/community.algoriddim.com/allentastic/32/16466_2.png) [@allentastic](https://community.algoriddim.com/u/allentastic)\
**Post date:** [December 3, 2025, 8:49am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/37 "2025-12-03T08:49:48Z")

</div>

Oh dang, I didn’t know other software had a feature like this. This just became my 3rd most hopeful feature implementation, behind soundswitch and better library management

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [December 3, 2025, 10:33am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/38 "2025-12-03T10:33:23Z")

</div>

Thanks for the input @allentastic

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [December 3, 2025, 11:14am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/39 "2025-12-03T11:14:07Z")

</div>

> [@Jay\_Dizzle](#):
>
> I have a new “different” and "easier to implement"approach. @Slak_Jaw . I believe. Maybe if you add an option instead of - Beat counter to next cue point. Allow us to add more “Set (1)” as in “Set (2)”, “Set (3)” up to 8 (hot cues) this could be a solution. Since Djay actually counts down in minus til the 1 marker.

Good idea @Jay_Dizzle. Thanks for sharing. I have passed this onto the devs.

---

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [January 5, 2026, 1:12am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/40 "2026-01-05T01:12:26Z")

</div>

Thank you 🙂

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [January 5, 2026, 1:19am UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/41 "2026-01-05T01:19:36Z")

</div>

You’re welcome @Jay_Dizzle

---

<div class="post-metadata">

**Author:** ![Frank\_Vlk](https://community.algoriddim.com/user_avatar/community.algoriddim.com/frank_vlk/32/19801_2.png) [@Frank\_Vlk](https://community.algoriddim.com/u/Frank_Vlk)\
**Post date:** [January 24, 2026, 7:56pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/42 "2026-01-24T19:56:00Z")

</div>

Hi, I’d also love to have the beat counter to the next cue available in this software. Hopefully it’ll get implemented at some stage. Until then, I’ll set cue points and name them with bar count to the next one - usually 16 or 32. And then I’ll follow the timeline. 32 bars is about a minute.

---

<div class="post-metadata">

**Author:** ![Slak\_Jaw](https://community.algoriddim.com/user_avatar/community.algoriddim.com/slak_jaw/32/6517_2.png) [@Slak\_Jaw](https://community.algoriddim.com/u/Slak_Jaw)\
**Post date:** [January 24, 2026, 8:27pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/43 "2026-01-24T20:27:37Z")

</div>

Hi @Frank_Vlk, welcome to the Community! Thanks for the input. Please don’t forget to vote at the top left of this page.

---

<div class="post-metadata">

**Author:** ![Jay\_Dizzle](https://community.algoriddim.com/user_avatar/community.algoriddim.com/jay_dizzle/32/10444_2.png) [@Jay\_Dizzle](https://community.algoriddim.com/u/Jay_Dizzle)\
**Post date:** [February 12, 2026, 12:44pm UTC](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162/44 "2026-02-12T12:44:27Z")

</div>

Just keeping this thread alive. Please add this feature.

[Previous page](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162.md?page=1)

[Next page](https://community.algoriddim.com/t/beat-countdown-to-next-cue-point/28162.md?page=3)
