Using ACID w/ a Beta-Monkey on my back.

  • Thread starter Thread starter jwarv
  • Start date Start date
J

jwarv

New member
Hi gang,
Anybody out there use the above combination?
If so, how does one compensate for super fast tempo loops that, when slowed down, an unwanted flange/chorus effect results?

Also, some loop samples were recorded at tempos ranging in the thousands.
ACID cannot work with these files.

Perhaps I'm missing some fundamental piece of info, but I'm not sure how to resolve this one.

Thanks,
Jason
 
...how does one compensate for super fast tempo loops that, when slowed down, an unwanted flange/chorus effect results?

You can't. If you change the tempo too much, it starts to sound weird. As the ACID Help file states, "Time compression and expansion is performed on all of the loops in a project so that they match the project tempo. Although the compression/expansion algorithm is very good, there are some limitations: you will probably not be able to make a 120 bpm loop sound great at 60 bpm." It's in the nature of what you can do with audio data. It's a little bit like resizing a digital photograph. The bigger you try to make it, the fuzzier-looking it gets.
 
That's what I thought.

Good answer.

Any word on the superly-duperly high speed tempos? (1000+)
Are there any programs that can make sense of these otherwise useless files?

Thanks,
Jason
 
Tempos in the thousands of bpm are ludicrous. Sure, they can be mechanically constructed following the rules, but what's the point? If you had quarter notes at 1,000 bpm, the time between the notes would be so brief as to be nearly indetectable, not to mention eighth notes or sixteenth notes. Certainly unplayable by humans, and it would just sound like complex slurring if constructed by machine.

But there is a solution to your dilemma. Simply this: quarter notes at 1,000 bpm = eighth notes at 500 bpm = sixteenth notes at 250 bpm. It's a matter of deciding what's a beat and what's a subdivision of it. While there's a common-sense way of picking what's a beat and a subdivision at humanly-playable tempos, it's going to be totally arbitrary for crazily fast tempos. So why not just look at them as very small subdivisions of a beat at an actual musical tempo?
 
Seems they may have been "acidized" wrong. I have the same problem with a few of the loops on the "Bun E. in a Box" disc. But Beta Monkey is a really good company, and I'll bet if you emailed Chris (I think that's his name) he would accomodate you somehow.
 
Interesting Suggestions

Thanks guys,
I think I came up with a simple solution.
I discovered that these files are playable in Sonic Forge. (Or any other wav player, for that matter).
What I can do is, if I find a sample I like, play it on say, Windows Media, and then real time record it on Sound Forge or the like. Clip off needless space at the beginning and end, and then throw it into the pit of ACID.
A whole new wav file recorded at a totally different rate should do the trick, don't you think? Wait a minute, I'm gonna try it...

Hmmmm, weird. It worked and it didn't. I managed to record it into Sound Forge and create a new wav file, but when I dragged it into ACID it played fine, but it was also accompanied by a continuous cricket noise. HUH? WHA?

By the way, I did write to BETA-MONKEY via there website. They don't seem to respond through that medium. I'll try Chris directly.

Ciao for now,
Jason
 
Back
Top