wtf massive!
Forum rules
By using this "Production" sub-forum, you acknowledge that you have read, understood and agreed with our terms of use for this site. Click HERE to read them. If you do not agree to our terms of use, you must exit this site immediately. We do not accept any responsibility for the content, submissions, information or links contained herein. Users posting content here, do so completely at their own risk.
Quick Link to Feedback Forum
By using this "Production" sub-forum, you acknowledge that you have read, understood and agreed with our terms of use for this site. Click HERE to read them. If you do not agree to our terms of use, you must exit this site immediately. We do not accept any responsibility for the content, submissions, information or links contained herein. Users posting content here, do so completely at their own risk.
Quick Link to Feedback Forum
Re: wtf massive!
pirate an older version of it. the newer one uses iLOK and still busts you after a while.
Re: wtf massive!
most genius suggestion yet. cheers mate!nowaysj wrote:These types of things w/in fruity are usually a result of errantly recorded event data.
And not to solve the problem, but just to get you into the soldier mentality of just getting the job done... you can sample the line how you like it and just trigger the sample at the appropriate times (or just place the recorded audio in the playlist).
Get the track done.
Solve the problem outside the context of working on the track.
Feel me, blood?
Who is online
Users browsing this forum: No registered users and 0 guests