02-28-2018, 07:08 PM | #1 |
Human being with feelings
Join Date: Jan 2015
Location: New Jersey
Posts: 52
|
Automation on items bug? (FIXED)
Hi folks
I tend to use quite a bit of parameter automation on items. I will split a section of audio, insert an item fx and then automate one or more parameters. For example, I might add reaEQ to an item and automate the lopass frequency down to tame a noisy guitar at the end of a tune. Recently, after the last update(s), I have found that this is not working. The envelope and fx are on the item but the envelope had no effect. I generally set the automation to "read" so I can watch the event take place. But it doesn't seem to matter whether it's trim/read or read. It does not work at all. I can set it up like normal on a new project will no results and I can open up old projects where I had automation. The automation envelope is there but no result of the envelope. The basic fx will work... but no automation... I usually set up the item fx/automation, get it to do what I need and then glue the item to cook in the desired effect. But on the ones where I did not glue, I have to go back and do entire track automation rather than a small item/section... then render/freeze to cook in in place. I was very comfortable with the item workflow. Hopefully this will be fixed in the next update... Anyone else notice this? later rich Last edited by rjwillow; 03-25-2018 at 02:53 PM. Reason: solved |
03-14-2018, 04:45 AM | #2 |
Administrator
Join Date: Mar 2007
Location: NY
Posts: 16,498
|
I can't reproduce this. Can you possibly create a minimal project that reliably demonstrates the problem, or a screencap?
|
03-14-2018, 04:20 PM | #3 |
Human being with feelings
Join Date: Jan 2015
Location: New Jersey
Posts: 52
|
Sure thing... here is a project
[URL="https://drive.google.com/drive/folders/1R2w_zrtioceJDl9WRMdPb50hAKCLEyOV?usp=sharing"] For a second I thought it was fixed as the EQ automation item seemed to work as planned But I guess I was wrong The pitch automation example does not track correctly. It seems that points are not being recognized. Or at least at the right location. As you may see in the project, I have a point where I want the pitch automation to start. Yet the automation starts early. It seems to end correctly. I really can't tell at this point if the EQ automation is really working and tracking accurately as it is harder to hear the "smoothness" of the transition. Let me know if the project does the same for you. Thanks rich https://drive.google.com/drive/folde...OV?usp=sharing Last edited by rjwillow; 03-14-2018 at 04:22 PM. Reason: link not showing? |
03-14-2018, 04:21 PM | #4 |
Administrator
Join Date: Mar 2007
Location: NY
Posts: 16,498
|
No project attached?
|
03-14-2018, 04:50 PM | #5 |
Human being with feelings
Join Date: Jan 2015
Location: New Jersey
Posts: 52
|
I posted a link. Maybe it didn't work.
Here is a direct attachment |
03-14-2018, 06:00 PM | #6 |
Administrator
Join Date: Mar 2007
Location: NY
Posts: 16,498
|
Thanks for posting the project. The bug is confirmed, when using automation on take FX on a media item with a take offset (start in source is not zero) or a custom take playrate, and the FX has latency. Fixed for the next build!
|
03-14-2018, 06:36 PM | #7 |
Human being with feelings
Join Date: Jan 2015
Location: New Jersey
Posts: 52
|
Thank you VERY much!!! I rely on this workflow too much to lose it...
rich |
03-25-2018, 02:52 PM | #8 |
Human being with feelings
Join Date: Jan 2015
Location: New Jersey
Posts: 52
|
Solved in latest update
Done deal! This issue HAS been fixed in v5.78
Thank you VERY much rich |
Thread Tools | |
Display Modes | |
|
|