WARBLE!!! WHEN RECORDING AUDIO!!

[guitarguruguy35]

For the first time I have discovered a MAJOR glitch in this software!
I use a Digi 002, a suped up laptop and live!
So far so good until today.
The warble was so present that Iwas looking for a chorus plug in I over looked.
Has anyone else had this problem?
Yes I increased the buffer size and still had the problem.
I really want live to be my be all end all program. Can someone help?!

[mdb]

Sounds like the file is "warped", Remove the warp on the clip and you should loose the flutters and other strange side effects.

If the clip isnt warped then i don't know what to tell you man.. Sounds like maybe your monitoring the track and playing back at the same time? Just a guess..

Good Luck

[Angstrom]

or put it back to the tempo you recorded at, or switch to 'complex' warp.

[guitarguruguy35]

I tried all the things mentioned. Its is really present when I play long sustained chords. Warp is off, loop is off..........can't figure out what would cause this.
Thanks for the help.

[feyshay]

Warble should absolutely be because of warping.
That's very strange.
I haven't heard others having that problem.
Have you rerecorded guitar into arrangement (without loop or warp) to see if you get the same warble?

[James Cater]

I had a couple of tracks that I recorded through the digi 002 that lost some samples in the middle. I couldn't find the problem, but when I re recorded the tracks the problem vanished. Due to the high CPU usage of Ableton I now try touch nothing whilst recording.

Bring on that perfromance patch ASAP

[guitarguruguy35]

Thanks everyone for the attention to this matter. I've been on the forums for Protools, Kontakt and Reason and I got to tell ya its great to get immediate feedback.
This is a well put together forum.

I havent solved my problem so now I record my acoustic guitar parts in protools and import them into live. I spend alot of time messing with the markers when I do this and dont get me started on those markers.......
What was the thinking on the subdivison of those markers. Clearly it would have been easier if they refered directly to actuall beats and what about moving those markers individually. What a pain. It really is an amazing program dont get me wrong its just that creativity often doesnt wait for troubleshooting. Another thing is adding effects,rendering to disk and reimporting. I find that live often is wrong in its BPM guessing.wierd
Live loops often always start on the one ......... so I record the loop over 8 or 16 bars with the loop starting on the 5th bar or later which is a marker nightmare.
Do you guys have anything you would like to add or discuss.
Im going over to tips and tricks to try and get some good advice/techniques.

[Angstrom]

re Tips and Tricks section - good luck, you will mostly find it is 90% threads like : "how can I mix mongbeat with numbtechno"

Warpmarkers - there are a lot of tips for handling them, click on one and use ctrl-A (or mac equiv) to select them all and move them as one. Often useful for puttin gan in-time riff on the beat.
click one and press the right arrow to nudge it right.
click one and press 'ctrl&an right arrow' to pick the next one
click one and use 'shift & arrow' to add to the marker selection (ie select more warp markers)
etc ...


If you are recording in time in PT and bringing in big chunks of audio , just ignore the autio warp ,it's no use to you. Set the live project to the tempo you recorded at, click an annoying auto marker then Ctrl A and hit delete!,
Now dbl click and make a marker on the first beat, right click and choose 'warp from here at **correct tempo**' so if you recorded at 120 bpm , set live to 120bpm and just tell it - "warp this at 120bpm fom here"
auto warp is for DJs IMO


Why dont they relate to 'beats'? by beats I guess you mean auto warp latching onto played notes, because they do relate to beats. The marker named 1.3.1 relates to the start of the 3rd quarternote of bar one. It's easy once you understand these arent 'hitpoints' or slice markers, imagine that you are bending time underneath the riff.

[awhwalker]

Hi I've read some postings in this forum and this thread is as close as I've seen to dealing with strange things that occur as a result of warp markers.

I have a adjusted my buffer with the test tone to remove all clicking etc. All tests fine. I import a track that is recorded on 87bpm. MY project tempo is set to 91bpm so by warping this track up 4bpm, I shouldn't have though there would be much danger in screwing around with the original.

I warp mark it beatifully thanks to supster's Rock Solid Warp Markers Tutorial 101. and the whole track sounds great agains a 4/4 kicker reference beat. But when I go to actually make this track form part of a set, the soft, ambient pads are ruined by what I can only describe as a pulsing sound throughout. if I turn Warping off, the flat, sustained note returns from the original.

If I leave warping on, and slow down the project tempo to 87bpm (the same as the original track I'm using) the pulsing fades to 0!!! So can someone please explain.

I have an old pentium 4 1.4Ghz with Soundblaster Live Value! and 256MB RAM. CPU Utilisation hovers around 4% but I know because its an old system, the page file is quite active (peaked at 851MB). Could this be the problem?

Adam

[longjohns]

no way it's at 4% while it's running.

256RAM is as far as i'm concerned totally insufficient to even boot into windows. and your 1.4 P4 is on a 200FSB, your ram pc133....etc etc, you know your comp is no powerhouse

anyways, try some other warp modes. complex is the best sounding but you've not got much processing power to spend, so you may have to compromise

[awhwalker]

I actually have one of those rare beasts: Intel 850chipset which did NOT employ PC133 DRAM as you suggested, rather RDRAM which had far better ECC and throughput than the "cheaper and more prevalent DRAM".

That said, i invite you to view my screen dump of Live. (recording while warping is enabled) The CPU utilisation as you can see is 11% (ok I exaggerated a little with the 4%) but really if its above 50% then theoretically I should be worried.

I'm going to do some event monitoring of my pagefile during warping /recording and see if that peak represents realistic element playing a part in the pulsing I mentioned to begin with.

http://members.optusnet.com.au/~awhwalk ... n_dump.bmp (hi-res 3MBytes)

[longjohns]

ok rambus. that's good that it's much faster. i'd still be worried about 256mb

11% for playing one clip like you've got going there i suppose is about right.

anyways, good luck with your page file experiments. but what warp mode are you using? try complex if you're not

[awhwalker]

Complex warping type worked a treat.
What are the implications elsewhere I should be aware of for using type "complex" over "beats"

you are a champion. the pulsing disappeared as soon as I chose complex warping. there didn't appear to be any other audible change to the track so this sound as though my problem is solved.

I wouldn't mind your advice about the impact of complex overall.

Kind regards

Adam

[longjohns]

it's as you'd expect: the improved accuracy comes with the cost of cpu usage. probably a good plan is to use complex until you get into trouble with your processing power, then either selectively render the warped tracks at the new tempo and then disable the warping, or move to another warp mode, at least temporarily.

i mean you could use a less expensive warp mode as a 'working' mode, then switch clips to complex warp when it's time to render.

try some of the others on your pad sounds, i think 'texture' is made for this. and you can alter the parameters of all the modes (except complex) to strike a balance between sound and performance.