hi. i just messed around with the signal follower mapped to Master BPM. oh, and master bpm being automated with the automation envelope editor. oh, and LFO controlling the signal follower max amount.
selected the whole pattern, rendered, noticed that most of the time the rendering process goes down to 32bpm - which seems like there’s some code set to value bpm-automation over metadevice->bpm-control.
are we supposed to enjoy these new perks in a live situation only, or can renoise be used to record “what it plays” with render-offline?
also, i just caught renoise rendering the whole pattern, and 4 more rows of the pattern (i.e. a 64 row pattern recorded once, then 4 more rows of the pattern) rendered.
here’s a little video (no sound)
sometimes 64 row pattern + 4 rows, sometimes 64 row pattern but only 58 rows, sometimes 64 row pattern + 13 rows, sometimes 64 row pattern + 8 rows.
even after resetting the LFO at start of MasterTrack, still getting iffy recordings and stop is not “where it should be”.
Hard to explain why, but unfortunately we can’t fix that. The renderer needs to look up the tempo and stuff for a song in order to guess how long it is. It can’t do so when the source of the BPM changes within the song itself - unpredictably.
I guess it also would be a shame to disallow modulating the BPM from meta devices, so we can probably live with the quirky render behavior?
Expanding on this idea; It wouldn’t be good for this version of renoise, but I could totally see in the future the ability to create different pattern lengths for each track/group, and have them playing back at different LPBs in the pattern editor, each track scrolling at a different rate. I can totally visualize it in my head, I’m just not good with creating visuals, so I wouldn’t be able to create a little animation to show what I mean. It would be a neat alternative mode to display songs
i know! a native-to-renoise recorder device for Master, native to renoise. no poxy 3rd party plugins (sorry Jonas!), instead allowing us to both record keyjazzing in the sample editor with loop changes AND wonky BPM / LPB stuff. it’s also intelligent, so can render offline without messing up anything.
Thanks, Jenoki. Fixed the crash now, unfortunately rendering still may stop earlier or later than expected when modulating the BPM with a meta device. This is really really hard to fix for us. Can’t promise we’ll be able to solve this at all.