Page 1 of 1
illegal sample loop ?
Posted: Mon Jul 11, 2005 10:21 am
by clipperer
hella everybody
ive got a strange thing going on. everytime i render something in live 4.1.1 and throw it in sound forge i get this message : "this file contained an illegal sample loop. the loop has been corrected"
and in audio file there are 2 sustaining loop markers, dont know how they got there..
anybody?
Posted: Mon Jul 11, 2005 11:47 am
by dub
hey clip,
this happens to me as well, don't know why...
Posted: Mon Jul 11, 2005 12:29 pm
by arar
..and me..strangely I dont seem to hear any difference after getting the message..
Posted: Mon Jul 11, 2005 2:42 pm
by tom b.
happens me too ....... would love to know what means
Posted: Mon Jul 11, 2005 3:10 pm
by amo
All I know it has to do with the loop marker you can see in soundforge once you opened the file. I guess the live loop marker doesn't fit in soundforge, and soundforge interprets it and places it a the end of the file. Nothing to do with the sound to my understanding.
Cheers,
amo
Posted: Mon Jul 11, 2005 3:24 pm
by elemental
yeah i get this too, doesnt seem important tho ...
btw I thought this post was about copyright!!
Might want to change the title to alert the Abes if need be.
Posted: Tue Jul 12, 2005 12:28 am
by Jonsama
Happens to me too- dont think it has any effect on the file though. By the way- do you guys normalize in live when you render? Is it a good thing to do?
Posted: Tue Jul 12, 2005 7:42 am
by dub
well i never normalize in live, i do all the master editing operations when i have my track rendered and clean.
Posted: Tue Jul 12, 2005 8:29 am
by amo
dub wrote:well i never normalize in live, i do all the master editing operations when i have my track rendered and clean.
Same for me, though I don't know exactly why... Yes, one of the reasons is I never know exactly what is the max volume of my track, then, by not rendering into live, I can have a look in soundforge before I normalize...
Regards,
amo
Posted: Tue Jul 12, 2005 12:28 pm
by DJRetard
HA HA
Im a sound forge user and this has happened since version 1.
Im not worried about it, but theres a reason for this
Ableton?