Time-Stretch tempo up but not down??
I'm running across this issue and can't seem to figure out why the Time-Stretch function can stretch a loop up but not down.
Here's the example:
My song tempo is 85bpm and I bring in a loop into the drum machine that is 93bpm. I go into the editor, set the original loop tempo to 93bpm click save and when I click to match to song tempo in the process window, the tempo will NOT go less than the original loop tempo of 93bpm.
So Basically I can stretch the tempo of a 93bpm loop, to say, 110bpm but not to 85bpm!?
Anyone else run into this? Or am I missing something in the process?
Here's the example:
My song tempo is 85bpm and I bring in a loop into the drum machine that is 93bpm. I go into the editor, set the original loop tempo to 93bpm click save and when I click to match to song tempo in the process window, the tempo will NOT go less than the original loop tempo of 93bpm.
So Basically I can stretch the tempo of a 93bpm loop, to say, 110bpm but not to 85bpm!?
Anyone else run into this? Or am I missing something in the process?
Comments
The value shown at the top of the timestrech panel is the original sample tempo, and the one below is the destination tempo, which you can change to a lower or higher value (or matche the song tempo, etc).
We should probably change the panel UI a bit so that it gets easier to figure out.
Cheers,
Colin
Yes, this is exactly where it's not allowing me to turn the tempo down. In the small bpm section where there is -& + buttons on either side of the tempo value (directly left of the Complex button)
I can turn the tempo up but sliding or using the minus button it wont go down past the Original Tempo value. Also, when I click the Song Tempo button, it only sets the tempo value (the small one with the - & + buttons next to it) to the original loop tempo value only. So if the Original tempo of the loop is 93 bpm and my song tempo is 85 nothing I do will change the value of tempo (the tempo value box with tap or slide in the top of the box and - & + buttons next to it) lower than the loop Original Tempo value. Or even when using the /2 button next to Song Tempo, it doesn't go down past the origial tempo value (in the tap or slide song tempo box) but again if using the x2 button it does go up.
This started happening only after upgrading to version 2.1.2 and unfortunately the time-stretch function is one that I use frequently and need! I'm running a iPad (1st gen) 64GB 3G+WIFI iOS 4.3.1
I don't see a way to attach an image to this post but can send you a screenshot of it, if you'd tell me where to sent it to. I can take a video of this issue and send it your way. But I've used the time-stretch function plenty of times before. The time-stretch function is one the functions that I believe sets BM apart and makes a very usable sample based prodcution tool. Please help me to get this working. Thanks!!
<!-- m --><a class="postlink" href="http://www.outrecords.com/video/bm2_stretch_issue.wmv">http://www.outrecords.com/video/bm2_stretch_issue.wmv</a><!-- m -->
If the link doesn't work, please let me know and I'll email it. It's only 12MB
Thanks!
When you slow down the tempo of a sample, the new processed sample will be larger, so you need
to ensure you have enough free sample memory to hold it. The time stretcher automatically
computes the minimum possible tempo regarding the available sample memory.
Example: When stretching a 10MB sample to half its tempo, the new sample will be 20MB.
So, I recommend stretching your samples on an empty project. Also, try adjusting the memory
limit too (go to the iOS Settings and find BeatMaker 2 memory limit settings).
UPDATE: Until BeatMaker 2.1.3 is released, ensure you use a memory limit (32/64/96MB).
Cheers
Thank you.
I even tried loading the "cold beats" preset and attempted to time stretch the "loop_main beat_77" sample within the Cold Beats preset.. I got the same exact results, I can time stretch the sample higher but not lower.
I wanted to add that I downloaded bm2 on my iPhone and still am getting the same results on both devices <!-- s:( --><img src="{SMILIES_PATH}/icon_e_sad.gif" alt=":(" title="Sad" /><!-- s:( -->
I found the issue, it will be fixed in BeatMaker 2.1.3
In the meantime, set the memory limit to either 32, 64 or 96 MB.
As you can see there's a small bug when using no sample limit at all.
Thanks for reporting !
Cheers
I appreciate it.. thanks so much! <!-- s:) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile" /><!-- s:) --> !