Its nearly 3 o’clock in the morning and I am pi$$ed because it took me so long to figure out, so I keep this short. but I guess a few people are interested in that too.
render your patterns/songs/tracks/whatever from renoise. you will most likely end up with an odd bpm.
load up audition, load your wav files.
go to the multitrack environment (f12), insert your wav there.
in the lower right there is a bpm-field, enter the value nearest to the “real” bpm renoise tells you. (like 93 bpm for 93,3625 bpm)
rightclick on your wav, choose “clip timestretch properties” (3rd from the top). choose a method you want, I’d go for resample with high quality.
rightclick on the timeline on the bottom, make sure “snap to ruler (coarse)” is switched on and change the view to “bars and beats”.
go to the end of your wav file, select the timestretching tool and the clip at the lower right edge (the one with the lines) and drag it to the nearest :1 marker (the beginning of a full bar) (left if the bpm you entered is higher than the real bpm, right if the bpm is lower).
right click again on the wav file, choose “convert to unique copy”, rightclick again, choose “edit waveform” (which brings you back to the editview) and save your wavfile. viola, you just created a wavfile with rocksolid bpm timing, perfect for live or any other application.
I hope this is not too geeky for you, I cant explain it any better at the moment, I am tired, I have a gig tomorrow and I have about 50 wav files left to convert in that way.
no, this is to be able to use renoise-loops/sequences which are 93.00 bpm and not 93.1873 or similar. I make my music with speed set to 16 to have a much finer resolution for grooves and stuff, by doing that my songs always have a very odd bpm-count, which makes it really hard to work with those loops in ableton live or logic or similar.
maybe I am the only one having this problem, but I was looking for an easy way to get my renoise-loops to a straight bpm and I finally found it.
no offense, but setting your speed to 16 is the opposite of what you wrote.
you may not have meant that, but it makes me curious.
that would give you much less line resolution, but would give you more space in each pattern to have long wav files, manipulating them would be a chore for sure. maybe thats what your running into? using that speed would make you have to give up any editing precision what so ever.
for example, if you used a sample that was recorded as 4 bars using a speed of 6 you wouldnt be able to even control it with your config, because it would be inside 1 or 2 lines right?
remembering you are using this method for a live installation, makes me realize how much more time you have to work with so i guess in theory you wouldnt need to have more than one pattern. you could just use 1 and reprogram it everytime it loops. not a bad idea. i imagine your definetly one pushing for subtick timing. that sucks tho that your having those bpm troubles. i wonder if the devs fathomed this type of usage. the margin for bpm error is very large i bet using these settings. i would speculate that they didnt
plan for this type of use an maybe the bpm value variables dont go as deep as you would need them to in your situation. i would think if this was looked at it could improve bpm timing overall.
if you make a music in renoise with bpm set to 100 and speed set to 6, the song is actually 100,0454 bpm and not 100bpm. now if you render this to a wav file and mix it in logic or live with a 100bpm loop, the renoise loops gets out of sync after a while. thats why I needed a way to get my renoise-wavs to exact 100 bpm.
also, I dont use speed 16 with 100 bpm, to get 100 bpm I use 267bpm at speed 16. the song then runs at 100.1059 bpm (odd again), but for drumrolls and grooves I can use the D Command (notedelay) in the panning column with a range of 0-F.
well, as I said this might be a very special workaround that only very few people need… but I worked with alot of other people lately, using logic or cubase and I badly needed a way to get my loops right … as I said, if you have no idea what I am talking about you dont need it (and can be happy )
If you’re using Live, why do you still prefer applying a permanent timestretch to your Renoise rendered wav? Have you run into some kind of nuisance when just setting the appropriate timing for the Renoise wav in Live?
there are definately problems arising when you just stretch the loop in live. actually I dont trust any “realtime” timestretching software, this is a task which takes alot of cpu-power if it is meant to sound good. also my live-sets consist of quite a few tracks (6-10) and applying timestretch to all of them really hugs the CPU.
I am really happy with this solution above, even if its only a “resample” solution, but the changes in the pitch are not really audible.
yeah yeah the real bpm prob … i use renoise either as last instance or without exception (exclude rudimentary vsts). and for external stuff, use eXT and midiox to get the delay for your parts.
but the best thing (for live) is to cut it up.
but in ULTRA-tiny pieces - “to get your own granularity”
I have to say I did only very few tests with live and its realtime-timestretching abilities, but I wasnt satisfied at all. Its seems that especially with those small bpm-differences (100.256 to 100.000 bpm or something) live started to swallow the attack of samples.
Anyway, I really didnt mean to bump on live or start a flame or something, if you are happy with live by all means use it.
About timestretching however : I still use the very old prosoniq timefactory, it does a great job for everything within the +/-30% range and a good job for everything else. and it takes about 75% realtime for each sample.
every other program/plugin I tried so far was not able to reach that quality.