Omega protracks playback problem!

  • Thread starter Thread starter Freak Scene
  • Start date Start date
F

Freak Scene

New member
With my Lexicon Omega / Protracks package, I recorded a keyboard beat, then recorded a riff along with it. During playback, the guitar was not on time with the beat, even though I played it perfectly. It was like there was a 1 second delay...what I recorded just didn't match up in terms of time when it should have. I'm not too great with protracks and I tried everything I could.

I went back into my other protracks projects and they played back fine, so I guess it's something with the settings on this particular one. I tried restarting the program, the comp, etc, no luck. It's pretty weird. No dropouts, but the timing is off. I also noticed during playback that my level meters stutter a little...when I play, the meters on the mixer respond on time, but the meters in protracks respond slowly. I thought I should maybe reinstall the program, but since my other projects are ok, it may not be necessary. Any help would be appreciated.
 
this could be a memory probem? i doubt it, this hasnt happened before. windows xp, pentium 4, 1.80GHz, 128 MB of ram. I know im using the minimun amount of this stuff for he lexicon to run on,but it hasnt happened before. ike i said i only have one ther track running, t doesnt seem to be memory. im also having some spyware problems...could this be contributing to it?
 
freak. thats a ridiculous amount of low memory with respect.
you need minimum 512 of memory. for xp and multitracking.
what do you have in your pci slots, and who the heck sold you such a p4 with such low memory ? was it a shop ?
also youll experience probs if dma isnt enabled on your hard drive .
tell me a little about your hard drtive please. do you have dma enabled ?
i'm not surprised you have probs. peace.
 
well, this xp is from 2002...we didnt get ripped off or anything. i dont need anymore memory because it's not like im doing major projects on it, and i have enough for the pakcage, according to lexicon. i dont know about the other thing you're asking about. if i deleted some uneccesary things on my comp, could this free up some memory? and this never happened before, so why would it happen now?
 
how do i enable dma? im really not that stupid on computers but i havent heard of this. i figured the memory wasnt a big deal because i dont use a ton of tracks with a ton of effects or anything...i appreciate the replies, if you guys could keep helping me out, it'd be great. i dont wanna just buy memory and then the problem isnt fixed, but do you think it is?
 
anyone? I really need to fix this or else i can't multitrack. This all started when i copied a track, then pasted it into a whole other project. could i have hurt something there or changed a setting? ever since then i got a dropout and the out of time (even though it's recorded in time) problem. I dont think its memory because i was able to use up to nine tracks before.
 
You really do need to get ya some more memory .... it ain't that expensive and your computer will likely be more responsive.
However, seeing as you have previously been able to record without these problems, I'd say it's likely a setting you have changed.
I have no clue about Protracks, so I can't help ya with any of it's settings but I would be looking for any buffering/latency settings. Namely if the program offers the ability to detect and offset recording latency.

You say you've got a problem with spyware .... get rid of it!

There is a solution that can possibly solve your issues ....... Format the drive and reinstall everything.
It can be a daunting task for the weak at heart, but it's doable with the aid of the over abundance of info that can be Googled.

Some things to make a happier XP DAW ......
MusicXP.net
Black Viper and XP services

Oh and enabling DAM -Edit- .... it was late ... that should have read "DMA" :D
 
Last edited:
Thanks for the response man...today just outta curiosity I used system restore on my computer, and it works now! I guess I changed a setting. It all started when copied and patsted one thing from one project into aother. Who knows what i did...at least it works now. Thanks again, an ill keep what you said in mind.
 
You must log in or register to reply here.
Back
Top