That is depending on the mode you’re in. You have a scale per pattern mode, where the scale is the same for all tracks:
The left 16 = number of steps which are looped, the right 16 = total number of steps of the pattern (determines how many pages you have with 16/32/48/64).
if you press Fn+YES, you can now do this per track:
The MASTER LEN, will determine when all tracks will restart looping (no matter what their individual scales / lengths are), so that is probably what you are encountering with the double trigger.
It automatically saves any changes to your saved song, so if you accidently mess something up and then go to load the song, it loads with the errors you just made. The only way to get it back is if you saved your project when the song was correct.
Specific example:
-Song made, named, saved, project saved (and write protected).
-In edit mode for that song, turn knob accidentally to change the pattern and change back which erases your muting settings so it’s back to the default for that pattern (wish that didn’t happen either tbh).
-Say oops, go right to song mode load screen and load the song (that was saved when the song was correct).
-Go back to edit mode only to see that the mistakes you made have not been restored by loading.
-Load project, song is restored to correct state.
This has happened multiple times on different songs and is reproducable.
Thanks (love the song mode btw!)
Update: According to support this is intended behavior! Not my fav cause it’s very easy to mess up a song by accident and then not notice until you’re performing, but they said they might add a “reload from project” option in the future.
I made something nice on Bank D pattern 1. I coped it to Bank D pattern 2. Was really rocking with it, made something I really liked. While doing so, I noticed something strange: I could record “trig modifiers” only into one page even though two pages were enabled. OK, whatever.
Then I was ready to live record without quantization to another track. MIDI input on track 14 (auto). I checked the metronome because I wanted a count-in. On the metronome screen, maybe I hit Rec-Play. Pattern gone. Gone! Including the new sounds I made on the new tracks.
Luckily(?) pattern 1 is still there, but pattern 2 got wiped somehow. What a bummer!
Is this a bug? I don’t know. Recording retrigs was weird/buggy, then I lost my whole pattern. Shrug?
Gotta always Func-Yes between every operation I guess? Unfortunately I don’t have that much time for music to be losing the things I make that I like.
I think I found a bug while copying a sound from an analog track (9-12) to a digital track (1-8). All the parameter are copied correctly, exact the SYN page of course, since the corresponding analog machine does not exist on the digital track.
After copying the sound the volume of the digital track (destination) is super quiet, even with track volume and AMP volume set to max. I found no way to recover from this state apart from loading a previous save.
To reproduce:
Copy sound from analog track [TRK] + [9-12] + [REC]
Paste to digital track [TRK] + [1-8] + [STOP]
Play sound on digital track (destination)
Copy-Paste of sound from digital to analog track works without any issue.
(I am on firmware v1.20)
IMO it shouldn’t be possible at all to copy a sound from a digital to an analog track or vice versa. It does’nt make sense to me or am I overlooking something?
I’m glad you mentioned this! I thought it was a Reason 10 bug. I can only get my Keystep 37 to play track 1 regardless of what midi channel I configure it to play on. Overbridge mode here too. Only way to play other tracks is via USB/midi mode.
Not sure if this has been mentioned, but loading a song and hitting play will often play the first pattern of the song with the wrong pattern mutes. I think it’s picking the pattern mutes by mistake, not the song-step mutes. Pressing Stop and then Play again fixes it.
If you are 100% of a bug, you can report it to Elektron. If nobody reports a bug to them, they may not work on it. This topic doesn’t suffice. The more it is reported, the more you have chance to have a bug correction.
That is to say ? You can also clear the sound, eventually.
It seems memorized with the Sound (I saved and reloaded it in another track, or copy pasted it with same low level sound)
I couldn’t reproduce it.
If you could list required steps please…
New project with a pattern that has only a few tracks muted purple (pattern mutes). Let’s say it mutes only tracks 1, 2 and 3, leaving reagls 4-12 unmuted.
Create a new song that plays that pattern. The first line of that song should have only, say, track 7 playing.
Make sure song mode is activated and then save the project.
Restart Syntakt and reload the project. Syntakt will then load the project with song mode activated.
Press play. Notice how more than track 7 is playing.
Press Stop and Play again. Notice how only track 7 is playing.
I’ve confirmed with Elektron support that OS 1.20 can have some subtle UI latency when using Control All, even standalone. For me it happens all the time, whenever I use Control All on any parameter. They were able to replicate on their reference unit, so I don’t know why more users aren’t experiencing it. Hopefully it’ll be addressed in 1.20A.
(love the song mode btw!)
that need ‘optimization’.