Developer
Posts: 746
Location: England | Hi generic,
Welcome to the forum!
Currently, the 4 rows per beat setting is fixed. This is done because reViSiT is designed to synchronise with the host in a manner that can be "intuitively" related to the host's own music. This means that playback is driven by beats (and tempo), instead of "frames" (sub-divisions of a single row). 4 rows per beat was the initial choice because this opens up the majority of common time signatures and allows easy access to music at semiquaver level, though a finer time control is obviously useful in many genres.
To this end, the "frames" still exist - they are the intervals at which tracker effects are processed. Using the Axx (Set Resolution) effect, it is possible to set the resolution of these (potentially very) fine divisions. Currently, these frames are only addressable through special row effects (SDx, SCx, Qxy, etc.), but a forthcoming version of reViSiT is planned where you will be able to edit these sub-row frames as though they were simply rows themselves. In addition to this feature, there might be another that simply allows you to set a global use <X> rows per beat setting.
See: http://www.nashnet.co.uk/forum/forums/thread-view.asp?tid=3106&posts=17&start=1
Currently, I'm planning my attack on this and a number of other new features, that should appear in reViSiT in the coming months. 'Hope this helps, Chris |