XOR Userforum

Full Version: [FIXED] Track clock setting bug?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
NerdSEQ 2.02A

If I set a track's clock to "MAPPING" and then trigger it from the Mapping Screen (using "TICK" pattern ticks) all works as expected. 

However, if I then set the track clock to any multiple (*2, *4 etc.), the track will be reset to normal (no multiple) whenever playback is started. 

This only occurs for track clock multipliers, and only after setting the track clock to MAPPING. Divisions work as expected.
(02-05-2025, 08:16 PM)trevormeier Wrote: [ -> ]NerdSEQ 2.02A

If I set a track's clock to "MAPPING" and then trigger it from the Mapping Screen (using "TICK" pattern ticks) all works as expected. 

However, if I then set the track clock to any multiple (*2, *4 etc.), the track will be reset to normal (no multiple) whenever playback is started. 

This only occurs for track clock multipliers, and only after setting the track clock to MAPPING. Divisions work as expected.

Yes found that one. It happens if you don't enter the pattern first (doesn't matter if it has been MAPPING or whatever) and it will take over the settings of the last entered pattern track.
A fix will be online in the next days.
Hey

How do I set up a track's clock to mapping?
(07-14-2025, 07:51 AM)ohho Wrote: [ -> ]Hey

How do I set up a track's clock to mapping?

In the track setup of the track.
wow this is the best discovery ever, thanks!