I had a post a while ago about reverb going rogue… As set then, massive upon replay…
It’s still a lottery… I can often get something to stick, but for this time…
In the current project, and “project” is taking a bit of license… We’re just mucking about here… anyway… the file is split into three sections, to facilitate video filters, which each section having first had audio filters added…
True to form, the reverb goes nuts upon replay, this I have been able to tame, but the third section… this does not respond to anything I do… In fact, it has no reverb and no massage of the reverb filter variables can do anything to change that…
Is it just me…?
It’s just me, isn’t it…?
Last time I was in here with this I was asked to provide the application log if it occurred again…
Can’t see anywhere in here to apply an attachment, but I believe I have found and saved a log file…
If anyone is watching this… My default position from here on in is: create Shotcut file, import the movie file, export the audio section only, import this audio file to Audacity, to do whatever I think is required…
Back in the Shotcut file, detach the audio, select and delete the audio, import the audio file I just exported from Audacity, continue…
Sounds like a bit, but there is less tension around the audio file and more options…
What does “nuts” mean? Just something basic but descriptive so we know what to look for. For example, no reverb, or too much, or starts and stops, etc.
this I have been able to tame
By doing what?
but the third section… this does not respond to anything I do…
Did you try removing the filter and adding it again?
The log file did not tell me anything. The last time I tested this when you posted, I did not reproduce a problem. But I think I may have been focusing on the middle clip. Probably to fix it, we need clear reproducible steps. I did add a clip to the timeline, add Reverb, split it twice, and played each section.
I just tested it again, and I think it is working fine. This time I used a 1-hour file and focused on the last clip after splitting twice. I made adjustments, mostly to Reverb time. I did some trimming of the clips as well to see if things go wrong after trimming. Not sure what other steps are needed.
But If I could accurately reproduce the “effect”, I wouldn’t do it anymore…
The reverb goes massive on playback, like unusable, massive…
It may be fine in the app, it may not (upon playback), but if there is a problem it will be massive in the export file…
“Tame” is drawing a long bow… in the first two sections of the project this was achieved by deleting the filter and reapplying, a few times… This is what i would generally do, click and hold my breath…
The new scenario is having absolutely zero reverb in the third region I created…
If you can’t recreate the issue I experience, that is a good thing for everyone else, tick…
This might also be a clue. The next time you have this problem, save the project, close, and reopen. Does the problem persists? If so, upload a copy of the project file to this thread and we can inspect it. Also, take a screenshot of the filter panel and the keyframes panel. Maybe they will reveal something that can help us recreate the problem.
I think this effect is incompatible with seeking and scrubbing due to the time based nature of it. When you export, in advanced settings turn off parallel processing. That option causes frames and their associated audio to be processed not strictly sequential.
That is true. But I would only expect a short artifact after seeking and then the filter should work normally.
That is a good experiment to try. The design in the MLT engine is that all audio is processed in sequence and parallel processing is only applied to images. But maybe there is an unexpected bug in there. Please try this and report back.