Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Table BPM setting annoyance
#1
Not sure if it's a bug but it's pretty annoying anyway to mention here:

Say you have a track at 130bpm and you create a table. If you scroll through the effects and go pass by the BPM effect the track's BPM goes down to 1 and track division is set to a divider 7 and then you have to go back to the track, reset the bpm and track multiplier manually. Really tedious! Could we have the BPM value set to the the tempo of the track by default? Thanks for considering Smile

PS: I made a suggestion in the feature request that could apply to the table FX: https://forum.xor.eu/showthread.php?tid=584
Reply
#2
Oh yes sure. Didn‘t consider this yet as issue as it never happened to me nor reported, but for sure not right if i think about it! It should use the recent BPM of course just as in the normal FX. Same for scaling (though keep in mind for that it is not totally safe here since tables or patterns can play on different tracks)
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#3
Yes this happens in the normal sequencer too. If you leave it running, and browse thru the fx, the bpm will get set to 0 or it jumps to pattern 0. Both are really disruptive of the flow and requires me to stop the sequencer every time I want to do something with fx
Reply
#4
BPM is no issue in the normal FX. It doesn't go to 0 there but to the recent BPM value.

I could perhaps add a little extra for the Start next pattern, so it ends up at a unused jump.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#5
(01-18-2020, 03:46 PM)XORadmin Wrote: BPM is no issue in the normal FX. It doesn't go to 0 there but to the recent BPM value.

I could perhaps add a little extra for the Start next pattern, so it ends up at a unused jump.

Yes you are right! Tried it just now, but I guess it happened on a table then indeed. Would be nice if it didn't jump out of the pattern by accident, cheers!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)