Music Production > MilkyTracker Bug Reports

[confirmed?] Replayer bug, protracker mode

(1/1)

djinn:
You are forgetting to "reset" the portamento note, which in all NT2 compatible replayers is actually set everytime a new note is issued, regardless instrument/effect. In your case, the note is only set when a 3xx command is issued for that same note, causing a persistent portamento to show up where it shouldn't.

Bug example:

C-3 01 -- ---
---  --  -- ---
E-3 --  -- 304
---  --  -- 300
---  --  -- ---
C-3 01 -- ---
---  --  -- ---
---  --  -- 300   <-  !

In Milky, this will erroneously slide with the last portamento'd speed, 4, to the last portamento'd note, E-3, while in all NT2 compatible replayers this does nothing (it slides to the last issued note, C-3, to be technically correct).

Navigation

[0] Message Index