there are times when i slip-edit audio in the arrange window that a message appears on the screen for a short time :
‘realtime algorithm has been deactivated because pitch or or stretch factor lies outside the limits of the current preset.’
i supposed that it would refer to some sort of audiowarp, but the message appears even when i slip-edit a clip that has no audiowarp modifications made to it.
what causes this ?
is there something i should be doing that i’m not ?
this is starting to get really SUPER annoying… the message appears on the screen whether the track is in musical mode or not. it will appear any time i do anything with an audio clip that i’ve subjected to warping – and that includes just moving the clip from one place to the next [i.e., don’t even have to be editing it]. and it KEEPS REAPPEARING, whether i’ve made new changes or not. the message has also popped up – bizarrely enough – even when i’ve edited MIDI tracks. HOW CAN I MAKE THIS GO AWAY ?? to be frank, i really don’t give a damn whether or not one of the clips conforms to some sort of preset, but i hate it when i’m getting up close and personal with a clip and this message appears ad nauseum, blocking my view !
I may have a solution. Well, it has stopped with me and also the crashes seem to have stopped which were happening when I tried to open the wave form in the main editor as opposed to the lower zone editor. This actually started to crash when I opened the midi editor too. Both midi and wave were working in lower zone, just when I opened the full editor it crashed. Fingers crossed it has stopped.
I went into media pool ctrl + p then changed all audio event algorithms that were not Standard Solo to Standard Solo. Many of mine were set on Elastique - Time.
me too, in c10.5 and c11
and it is not only super annoying, it is also actually hindering me from working as fast as I should be for my clients, as it blocks my view and also it takes about a second every time I mark a track to warp it.
Can’t believe they haven’t got rid of this in several YEARS!!!
I’m getting this error in C12 too. I found out that I’ve one warp interval that is too small such that it exceeded the limitation of the time warping algorithm. After moving the warp marker a little bit to make the interval larger solved the problem.
Edit: it ends up that the error message is not very clear about what is going on. I kept thinking if there is any warp marker that lies outside of the event… And there is no way the reported error will let you know which interval caused the error.
I love the oud. Same error here. Doesn’t seem to have any negative effects on the work…except just piss me off. So tired of trying to find solutions to problems I didn’t create. :}