Hi,
Found a small bug in Jamstix 4, which is stopping me working on a tune.
I've got a song that has 8 bars of verse, in 4/4 time, then one bar of 2/4 "break", then 8 bars of 4/4 chorus.
I can't create that structure, in the pattern builder on the left.
I can make a verse section, that's 4 bars, repetitions 2, to get to 8 bars of 4/4
I can make a chorus section, that's also 4 bars, repetitions 2, to get to 8 bars of 4/4
But if I try to add a part between those, called "Bridge", that's length 1 bar, 1 repetition, of 2/4 time, I can add the part, but double click to check it, and it's been changed to 4/4 time. I change it back to 2/4 time, it changes itself back to 4/4 time
This is in Tracktion Waveform 9. In the host DAW, the first 8 bars are 4/4 time, then there's a one bar change to 2/4 time, then 8 bars of 4/4 time.
If i play the host DAW, and watch the parts in Jamstix, it either plays Verse, Bridge for 4/4 time, then Chorus, or sometimes plays Verse, jumps to Chorus, then back to Bridge, then back to Chorus, if I don't start at bar 1, when i hit play.
Hope that explains how to replicate this.
Time signature bug (edit - not actually a bug)
-
worldof_chico
- Posts: 22
- Joined: Tue Jan 23, 2018 11:07 am
-
worldof_chico
- Posts: 22
- Joined: Tue Jan 23, 2018 11:07 am
Time signature bug (edit - not actually a bug)
Just tested in Reaper to rule out the host. Same problem in Reaper, the "bridge" part cannot be changed to 1 bar of 2/4 time, it changes itself back to 4/4 time, in Jamstix.
-
worldof_chico
- Posts: 22
- Joined: Tue Jan 23, 2018 11:07 am
Time signature bug (edit - not actually a bug)
Well, I feel stupid ...
I've just found the "Allow time sig changes" bit in Options. That was greyed out, presumably the default.
Turned that on, apparently I now can create a part that's in 2/4 time.
So .... not a bug after all, user error.
CARRY ON, NOTHING TO SEE HERE
I've just found the "Allow time sig changes" bit in Options. That was greyed out, presumably the default.
Turned that on, apparently I now can create a part that's in 2/4 time.
So .... not a bug after all, user error.
CARRY ON, NOTHING TO SEE HERE