![]() ![]() They all have a slight tail on them, that is always a problem. All of the songs are at 140, and I looked at them closely. Thank you for posting one for me to hear it and study.ĮphyMusic : Thu 13th Aug 2015 : 8 years ago Please take this as no offense, but only an effort to assist you in returning to uploading loops. So in conclusion - yes, I understand where Looperman is coming from, especially considering there had been many loops with audible problems. There are a lot of considerations to keep a loop playing well without clicks or gaps. ![]() But really, the ideal solution is to remove or lower the wet mix of the effects (reverb, delay, all of that). Then the tail is there for people to use, and they can overlap the second half to the same effect without the clicks. It will loop on tempo, and the tail should remain intact without a click. The first two bars, and the last two bars, both with their tails, in a four bar loop. A simpler and better solution would be to upload this loop in two pieces. Then you can place both the first and second half in the playlist in parallel. Then select the second half exactly, be sure it is at a zero crossing. Then record the mixer channel using edison set to "On Play." This will give you a recording, which when trimmed to the marker will be twice the loop length, with the tail in the second half. A slightly better solution would be to place the pattern in the playlist with an empty pattern of the same length placed after it. You could lightly fade, or "declick" the end and/or beginning of the loop, but this may add another problem, which would be a gap. My first question - Did you chose "cut remainder" or "wrap remainder" when rendering? A simple render of a wav file will not necessarily take into account zero crossing at the beginning and end of the loop. FL studio is not always to be relied upon to do this automatically. The link to the forum thread above gives some good tips on making a tail loop properly. I hear this click prominently when playing it looped. These two issues add up to a very long tail which is sometimes difficult to have loop without an audible click. I would say the reason that this loop would be flagged is due both to the note decay and the very wet effects that are present. ![]() With all of this in mind, I knew that the loop would have an audible problem. I'm guessing since you take FL's word for it on tempo, that you chose the correct tempo when you uploaded. Opening this in audacity and playing it as a loop, I think that the length is pretty much fine for a four bar loop. Okay, I agree with promenade2239 that this loop is a 4/4 loop. Spivkurl : Thu 13th Aug 2015 : 8 years ago ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |