# C16 – Split track list

**URL:** <https://forums.steinberg.net/t/c16-split-track-list/1045415>\
**Category:** Cubase\
**Tags:** issue, cubase-16\
**Created:** [November 7, 2026, 10:41am UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415 "2026-11-07T10:41:57Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 7, 2026, 10:41am UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/1 "2026-11-07T10:41:57Z")

</div>

Hello Steinberg,

Why can’t I drag the split track list all the way closed anymore? I’m referring to the four-dot handle, which used to let me pull the divider fully to the top.

Is this a change in the latest version, or is there a setting I’m missing? Thank you in advance for your help.

 ![grafik](https://europe1.discourse-cdn.com/steinberg/original/4X/1/b/2/1b28729025b771f7f08016b1915524dcf2f6cb7a.png)

---

<div class="post-metadata">

**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\
**Post date:** [November 7, 2026, 7:05pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/2 "2026-11-07T19:05:41Z")

</div>

Hi @Jonas2021 ,

you might have missed @Martin90’s reply. He pointed out that this is a GUI bug related to scaling.

> [@C 16 Spurliste Teilen](https://forums.steinberg.net/t/c-16-spurliste-teilen/1045323/6):
>
> Das scheint ein Bug zu sein, der mit der GUI-Skalierung zusammenhängt. Ich habe sie auf -25% eingestellt. Damit funktioniert das Teilen der Spurliste wie gewünscht. Wenn ich die Skalierung in den Cubase-Einstellungen auf “Standard” zurückstelle, kann ich die Trennlinie auch nicht mehr bis nach ganz oben ziehen.

I can confirm: If application scaling is set to -25% under Appearance \> User Interface than you can pull the divide list all the way up again.

Unless it’s meant to be this way…

---

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 7, 2026, 7:08pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/3 "2026-11-07T19:08:57Z")

</div>

Hi @Reco29,

I’d already sent it to Steinberg, as I can’t imagine that’s how it’s meant to be. I was hoping that perhaps someone here might have something to say about it 😉

---

<div class="post-metadata">

**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\
**Post date:** [November 7, 2026, 7:15pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/4 "2026-11-07T19:15:43Z")

</div>

> [@Jonas2021](#):
>
> I’d already sent it to Steinberg

That’s why you didn’t tag it as an issue, I see 🙂  
Who knows, maybe it **is** meant to be that way and not the other way round. Cubendo sometimes works in mysterious ways… 😉

EDIT: The king of spelling mistakes has struck again… oh man

> [@Reco29](#):
>
> If application scaling is set to -25% under Appearance \> User Interface ~~than~~ **then** you can pull the divide list all the way up again.

---

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 7, 2026, 7:16pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/5 "2026-11-07T19:16:23Z")

</div>

> [@Reco29](#):
>
> That’s why you didn’t tag it as an issue, I see 🙂

Maybe i should

---

<div class="post-metadata">

**Author:** ![Reco29](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/reco29/32/319942_2.png) [@Reco29](https://forums.steinberg.net/u/Reco29)\
**Post date:** [November 7, 2026, 7:20pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/6 "2026-11-07T19:20:18Z")

</div>

It has been reported that Steinberg prioritizes threads that are marked as an issue. Maybe this is the fast track to get an answer?

---

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 7, 2026, 7:21pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/7 "2026-11-07T19:21:04Z")

</div>

![grafik](https://europe1.discourse-cdn.com/steinberg/original/4X/6/c/9/6c9fb4c0145f04165fa92125c801373c3851a8b7.png)

Counting backwards  
😉

---

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 7, 2026, 7:28pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/8 "2026-11-07T19:28:51Z")

</div>

> [@Reco29](#):
>
> Maybe this is the fast track to get an answer?

The fastest way to C16.1.0?

---

<div class="post-metadata">

**Author:** ![Jonas2021](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/jonas2021/32/194777_2.png) [@Jonas2021](https://forums.steinberg.net/u/Jonas2021)\
**Post date:** [November 11, 2026, 9:39pm UTC](https://forums.steinberg.net/t/c16-split-track-list/1045415/9 "2026-11-11T21:39:49Z")

</div>

The Issue will be solved with C 16.1.0
