I’ve been trying to paste files whose BPM I already know to be 70 BPM, however once I set the projects tempo to 70, the files are being timestretched as if they are being recognized by the app as being 120BPM by default, or 95 BPM by default with some other 70 BPM files/tracks, it’s all a bit random, and none too desirable.

I recognize that the app makes no mention or using lengthy loops/files (in this case, full song files of 3 or more minutes in length), so can you please clarify if there are limitations as to the apps ability to handle full song length clips/files/loops ? And if so, how would one force the app to recognize the pasted files TRUE BPM ? Am using an 3rd gen iPod touch, iOS 4.3, pasting from a Sonoma pasteboard supporting app (audioforge). Basically would like to use the app to create a seamless mixtape of tracks of a predetermined tempo - hope you can help…

Duh… found the means to correct this, by simply editing the files BPM setting in My Recordings, accessed from the main project view by pressing the small loops waveform in the bottom right hand corner of the screen. Now we’re cuttin’.

Cool. Thanks for your smartness! :^)

It’s my only gripe (lack of any HELP bundled with app). Was on the verge of giving up on the app, but am pleasantly taken with it’s functionality now that I figured out how to edit the BPM tagging. Looking forward to where you guys can take this app (is there no volume automation at all?).

Bring on the fades. And in app iPod/music import, for to make ones own loops etc.

My only problem in the way of BPM is that it takes a few pokes to get the BPM thing to let me change it. /: Anybody else having this problem or do I just need to poke harder? xD

The displayed bpm won’t refresh until you have entered the correct BPM, exit the loop directory (by pressing the little waveform image to return to the project page) and then re-enter the loop directory AND touch on the loop (to begin preview), at which stage the user defined BPM will replace the generated BPM… actually in my experience, maybe not always what you defined, but a close approximation of it (I type in 70, and the app corrects it to 69, 70 or 71, most likely what it’s bundled algorithm calculates what the BPM of the track/loop “should” be, I guess by calculating the user defined tempo against the rendered peak file, for accuracys sake.

Thanks. Yes, sometimes it is hard to poke things on the small screen. We will continue to try and make things easier to poke :^).