I have renoise 2.5. The vibrato command 0Fxy is consistently out of time with any song no matter what speed it is set to. Has this issue been fixed in 2.6?..I really want to use vibrato without using a workaround.
Could you give an xrns as example?
He is talking about the problem as outlined here.
Assume you are aware of this workaround (which you’ve stated you don;t want to do.)
hi kazakore. thanks again for the quick response. yes thats it. the workaround using chorus is good but im doing kind of chip style stuff and really need the vibrato pattern effect commands so that i can change the speed and depth of vibrato easily and quickly rather than by using automation. i used to only use milkytracker, now i only use renoise. obviously, renoise is better in almost every way but the out of time vibrato is the one thing that really bugs me. i know a lot of people have used the vibrato command and the fact that it cycles out of time can be barely noticeable but i would really love to see that fixed. seems like a small but very necessary thing to do…it doesnt look good for renoise if one of the main pattern effect commands is buggy…2.6 seems to have some excellent new features such as sample autoseek but i dont see the vibrato fix mentioned anywhere on the 2.6 launch page. so just wondering if this problem has been fixed or not? sorry if im going on about this too much. thanks for all your help.
Seems to me very strange it wasn’t linked to lines anyway, as that is how most of the pattern commands seem to work. Unfortunately no comment by The Man himself in that thread. Backwards compatability may be a little worry but as Renoise knows what version a Song was last saved in surely it can ask on opening whether to do these “fixed” things in the old or new way upon opening…
its true, it must work differently in some way to the other pattern commands. i think it must be a relatively easy thing to fix and as you said renoise could know what versions vibrato to use for songs written on differnt versions of renoise. hope they will give it some attention…fingers crossed that it will be fixed in the next version…