| |||
| |||
|
You are logged in as a guest. ( logon | register ) |
How many subrows are there? Jump to page : 1 Now viewing page 1 [25 messages per page] | View previous thread :: View next thread |
reViSiT - Tracking Software for VST hosts -> Testing & Development | Message format |
vze26m98 |
| ||
Member Posts: 9 Location: GWB | Hi all- I noticed in the Preferences (reVisit 1.6 beta8) that the initial resolution can be set to 255: But when I set the resolution via the "Axx" command, it appears I get 32: I know I sound greedy ;-) but how can I get more via "Axx"? (Actually, 32 at 120 bpm is pretty impressive resolution!) Best wishes, Charles | ||
chrisnash |
| ||
Developer Posts: 746 Location: England | Hi Charles, Welcome to the forum! The max resolution is currently 32 - the initial resolution setting should have a maximum of 32 too, which I'll fix in 1.6. It's possible the maximum resolution could have been higher in pre-subrow editions, and I might look at upping this limit, though the UI's currently limited to two digits (e.g. 64 or 99). In the meantime, you'll have to do the ol' trick of bumping the host's tempo to get more resolution. Best, Chris | ||
chrisnash |
| ||
Developer Posts: 746 Location: England | Heh - actually, in the current version, initial resolutions above 32 do result in >32 subrows (you need to refresh the sync data - play the song or Ctrl-F5). However, *DO NOT* set this above 100, as there is only space for 2 digits in the UI, and reViSiT 1.5 will crash if you try anything higher! The Axx command was already limited to 32 (00 to 20). The logic being to reserve values above 32 for a possible future host tempo controller. I will make it so that reViSiT 1.6 has a maximum initial/Axx resolution of 100. Note, however, that you'll need to maximise the window to be able to get to higher subrows (the auto-scroll isn't really designed for subrows). Chris | ||
vze26m98 |
| ||
Member Posts: 9 Location: GWB | So this is certain to start a flamewar. ;-) I took a WAV file that had a single-sample impulse in it, plus 7 trailing samples of silence. Sequenced it as fast as I could in Renoise64 on OSX, and compared with reVisit 1.6 running in Reaper32 (running in Win7-64 via VMware Fusion for Mac!). Looks like reVisit's the speedier of the two: (I know the width of the reVisit impulses look fatter. I'm not sure how reVisit knows what pitch the sample is supposed to be. So C4 on reVisit might have slid the pitch down a bit on the impulse.) EDIT: I was a bit stumped about why reVisit should be twice as fast, but here's the math: Renoise - 44,100 samps/sec * 60 sec / 999BPM / 64 LPB = 41.38514 samps/line reVisit - 44,100 * 60 / 960BPM / 4 LPB / 32 subrows = 21.5332 samps/subrow Best, Charles Edited by vze26m98 2012-01-05 7:41 PM | ||
chrisnash |
| ||
Developer Posts: 746 Location: England | Coolness. From now on we'll have to refer to reViSiT as "Full HD" and Renoise simply as "HD ready"! Plus, you're missing a trick - you can adjust reViSiT Pro's LPB setting too ("Rows per Quarter" in Preferences, F12), which should quadruple the maximum resolution... reViSiT Pro 1.5 - 44,100 * 60 / 960BPM / 16 LPB / 32 subrows = 5.3833 samps/subrow And, of course.... reViSiT Pro 1.6 - 44,100 * 60 / 960BPM / 16 LPB / 100 subrows = 1.7227 samps/subrow (you can also get this in 1.5 Pro by using initial resolution @ 100 and removing any preceding Axx effects) As you guessed, reViSiT doesn't detect pitch, which may partly explain the width of the spikes, but it might also be partly to do with the lower (and thus perceptually wider) peaks. Chris | ||
vze26m98 |
| ||
Member Posts: 9 Location: GWB | Hey Chris- Thanks for the other speed hints! As you guessed, reViSiT doesn't detect pitch, which may partly explain the width of the spikes, but it might also be partly to do with the lower (and thus perceptually wider) peaks. So dumb question: if there's no pitch detection, reVisit has to relate its "piano keys" to pitch shift up/down in semitones: ... -3 -2 -1 0 1 2 3 ... So which pitch is considered zero? Or, what pitch are all sound files considered to be? Doesn't sound like C4 is it. Best, C. | ||
chrisnash |
| ||
Developer Posts: 746 Location: England | Nearly - the assumed pitch is C5. You can transpose pitches in one of two ways: * Change the SPEED of the sample, in the Sample List (F3). * Change how the instrument uses PITCH, in the Instrument List (F4), either... - by transposing the keymap. - by fiddling with the pitch settings / envelope. Chris | ||
vze26m98 |
| ||
Member Posts: 9 Location: GWB | Ah! If I'd gotten up just a little earlier, I'd have beat you to the answer. C5 it is... Thanks for the pointers to other pitch-ing alternatives. Charles | ||
Jump to page : 1 Now viewing page 1 [25 messages per page] |
Search this forum Printer friendly version E-mail a link to this thread |
(Delete all cookies set by this site) | |