Defaulter Package Bugs
Hi there, this is a great script. However, I'd like to have the possibility of selecting the clips with both fade ins and outs. At the moment it seems to select the clips with the fade in only, but omits the portion where the fade out is. Also, sometimes the script "forgets" to process those clips that actually have zero fades. Any ideas?
Also, for me, I've modified this script so it selects "creates individual files" as opposed to "creates continuous files." As it seems to work just a bit better for me - although i've honestly don't see much of a difference being fair.
Christian Scheuer @chrscheuer2020-12-14 13:37:30.400Zcc'ing @poterukha here who made the package :)
Christian Scheuer @chrscheuer2020-12-14 13:43:06.281Z@Denis_Estevez – it's very likely that our "do for each clip" algorithm needs to work slightly differently.
Unfortunately, it was a hugely complicated action to make, one that we had to test for weeks, because we're trying to make it work without having complete information from Pro Tools, so we're piecing it together from multiple incomplete sources.
The one thing that it doesn't do a very good job of is handling fades, unfortunately.There is a chance that you might get a better, more customizable result, by rolling your own algorithm to iterate through the selected clips. In newer PT versions, you can Ctrl+Tab to the next clip. That implementation may prove to be closer to what you want here.
I think in the future, we'd probably want to improve upon the do for each algorithm, but the thing is it takes sooo much time which would take away from more universal features. In any way, it would be extremely helpful if you can share a tiny session with clips – you don't need to share the audio files, just a session with a single track, where the clips are laid out and can reproduce the issue. If you could then also show us a short screen recording of the script in action and how it doesn't work as expected, then we can save it in our bug bank and make sure to address it.
The reason why this kind of approach is needed, is that once we change something in that algorithm, it will have a ton of side effects. So we'll need to very, very thoroughly vet it. And there's also a chance that we won't be able to make changes to it, as it would adversely affect existing scripts.
But it would be a great starting point to understand better if there's something we can improve today.
- DDenis Estevez @Denis_Estevez
Ok, I have an idea: instead of modifying the current SF algorithm which you know works well for some already, why not create a different new one that includes the fade out portion? I'm happy to try rolling my own macro with Ctrl-tab, but it will be nothing like an actual SF algorithm like sf.proTools.ui.ClipDoForEachClipInTrack O:-)
Vladimir @poterukhaHi Denis! Thanks for your interest in Defaulter package.
As @chrscheuer said the group of "do for each... selected clip/clip on the selected track/s" scripts are very complicated under the hood. It Is a killing feature having the ability to ignore fades for such actions. When I published it for the first time it was stable with Pro Tools 2019. I'm not happy how it works in PT2020 and I know it crashes on tracks with a lot of clips and fades. Also, Quite Art updated Defaulter to work with LKFS. I will update the package soon to meet both Defaulter 2 and SoundFlow Command Templates, making it easier for users to select Audio Suite processing input options and type of action applying for clips. For now, I will change the main action to stable but not compatible with fades "Ctrl+Tab".- DDenis Estevez @Denis_Estevez
Thank you @poterukha. That will be most helpful. I'm also using the LKFS feature, so I guess I'm on Defaulter 2.0 as well.
Re. "It Is a killing feature having the ability to ignore fades for such actions"
I agree! I think it's well worth the while to preserve this feature @chrscheuer. Which is why I suggested to keep that algorithm untouched, and create a separate new one to encompass the entirety of the clip with fades.I have no programming idea, otherwise I'd venture out to try a macro with some Ctrl+tab commands.. but i don't think it will work with my idea of key presses, because clips with different fade variables will require different tab presses depending on the clip variables of clips with fade-in, fade-out, and fade-in+out. (as they may require less or more tab presses depending on how many fades the clip has). So it becomes a bit more complex than it seems at first...?
- Christian Scheuer @chrscheuer2020-12-14 16:28:04.029Z
I would love to add such a feature, but I'm not sure we can with the current integration. I remember it being extremely hard to have complete knowledge about the fades. The algorithm ended where it did for a reason :)
That being said, having some visual documentation from you would be crucial in visualising what the issue is and how to potentially improve it. Can you share the actual experience right now versus how it should be? As screenshots with comments for example?
Whenever something is complicated, it helps tremendously to visualize it – at least for me :)- Christian Scheuer @chrscheuer2020-12-14 16:28:56.428Z
And yea, I hear you on keeping the current algorithm regardless.
- Vladimir @poterukha
@Denis_Estevez I have just pushed a new version to the store. Now the script uses Ctrl+tab to skip fades and applies the Defaulter for clips on the timeline. I changed the algorithm so, now you must have "fire macro keys" enabled at the plugin settings. Hope it works well and solves the bugs.
- DDenis Estevez @Denis_Estevez
@poterukha Happy New Year & Many Thanks for pushing a new version to try! I have only gone back to the studio to try it out since we last spoke. It seems to still be skipping the fade-out on all of my clips. So the values I get are off sometimes. I don't need to modify the script now for 'individual files' settings though, so that is a huge welcome addition!