Can't seem to recall insert presets with Teezio's Plugin Loader
As the title suggests, I can manage to open up a plugin however, I can never get the "Preset Name" to actually follow through the entire way. Is there something I'm missing?
For reference, I'm running this on a non HDX system!
Appreciate any and all help! :)
Kindest,
Eric
Eric Huergo @Eric_HuergoAdditionally, this is what I see after it successfully loads the plugin!
My guess is that this might have something to do with the formatting of the text but I've still run quite a few tests and gotten no positive results unfortunately!
Eric Huergo @Eric_HuergoUpon further revision, I think this might be due to the fact that Pro Tools can't detect the preset window for Blue Cat's PatchWork. Is there any way around this? I have a bunch of VSTs and AUs that don't have an AAX Version and would really like to be able to pull them up on the fly!
Kitch Membery @Kitch2022-03-04 02:57:27.228ZHi @Eric_Huergo,
To understand more about what you are trying to do, can you take a screenshot of the Teezio's Plugin Loader preset you are trying to run.
And then take a screenshot of the Plugin windows Preset path.
I do not have "Blue Cat's PatchWork" but it should be no different to recalling presets on other plugins.
Thanks in advance.
- Eric Huergo @Eric_Huergo
Thanks Kitch!
My preset looks like this at the moment:
Likewise, the plugin window's preset path looks like this:
I should mention that while I can easily access various UI elements for many other plugins I do have trouble clicking them for this particular plugin. When I do a Click UI this is all I get even if I'm hovering over the preset popup menu.
- Kitch Membery @Kitch2022-03-04 03:33:21.994Z
Interesting. Thanks for that info.
Can you use the new "Pick" button in the SoundFlow Editor to get the path to the "" popup menu?
Then copy / paste the reference path is fruits in this thread.
- Eric Huergo @Eric_Huergo
Okay bizarre. First off, thank you - I seem to have been able to select the popup menu path this time using the pick feature (fucking awesome addition, i just learned something insanely useful - so thank you, truly!)
This is what I got:
sf.ui.proTools.windows.whoseTitle.is("Plug-in: Blue Cat's PatchWork").first.popupButtons.allItems[3]I get the feeling that this means I should create specific scripts for any of my "Blue Cat" plugins? Or is there by any chance a way to get this to work with Teezio's Plugin Loader?
Needless to say, I'm already happy just about learning about that new function! :)
EDIT: Another development - for some reason, I've discovered that both the pick and click ui functions are somewhat tempermental - only working sometimes with this plugin. Any idea what could be causing this issue? :s
- Kitch Membery @Kitch2022-03-04 05:12:58.854Z2022-03-04 05:25:17.437Z
Yes it's a great feature for sure, glad I could impart some knowledge.
There may be a way of getting it working with the Plugin Loader.
Try this...What happens when you run the following code when the patchwork plugin is the only plugin open?
sf.ui.proTools.appActivateMainWindow(); sf.ui.proTools.pluginWindow.popupButtons.whoseTitle.is("Librarian menu").first.elementClick();Does it open the "factory default" menu?
- Eric Huergo @Eric_Huergo
Yes, thank you!!!
This does in fact open the menu but it doesn't yet select a preset.
What do you think would be the best way to go about achieving this? Ideally using the "Preset Name" field from the tezio preset but if that's too tricky, anything will do! Seriously appreciate it! :)
- Kitch Membery @Kitch2022-03-04 07:34:47.672Z
Awesome! That's great news if that opened the menu.
I think I know what the issue is. If you could bump this thread tomorrow evening, I'll see if I can implement a fix over the weekend.
I think it has to do with the apostrophe in the plugin name that needs to be (escaped) / accounted for.
I may need you to test a couple of things, but hopefully we can get it working without too much fuss. :-)
- Eric Huergo @Eric_Huergo
Sweet! There's a chance I might have a long day tomorrow (in which case I might not be able to run some tests) but hopefully it stays on the short side - I'll do my best to bump but thank you kindly sir! :)
- Kitch Membery @Kitch2022-03-04 10:01:54.365Z
Hi @Eric_Huergo,
I downloaded the Demo of the plugin and checked it. The preset functionality is working fine.
As I mentioned a few days ago, adding the plugin width to the end of the "Plugin Name" property is not supported by the plugin loader.
In your Preset's "Plugin Name" property, you've added " (stereo)" to the end. This is what is causing the issue.
I do see a potential way to make it work with the loader. It's literally one line of code that I have ready to go but requires a round of testing with all the possible scenarios. I'll keep you posted but should be able to sort it in the next week or so.
- Eric Huergo @Eric_Huergo
Oh snap, that does make sense!
Unfortunately, for my use-case (not in this instance but often enough) I use plugins that change from one track width to another in more formats than mono/stereo so the only way I was able to get them to load correctly was by making decks liike such:
Pressing a plugin like "SketchCassette II" would take you to the following:
Then clicking any of those would run a script that basically looks like this:
All in all, this ends up making my arsenal of plugins I've collected over the years way more accessible and intuitive to browse through (although admittedly, most of the track widths higher than stereo don't function natively yet with TPL - still really useful though to be able to really quickly see what plugins have what track width conversions and so on!
By the way, do to an unforseen change of plans I will have a slower day today so I could potentially run any tests whenever you have a moment!! :)
- Eric Huergo @Eric_Huergo
Hey Kitch, just bumping in case you're around but was wondering if you might have some time this evening to give the tests a spin!
- Kitch Membery @Kitch2022-03-06 08:54:51.551Z
Hi @Eric_Huergo,
I've added the preset loading workaround to the latest version 1.4.6. Fingers crossed it doesn't cause any widespread issues. In my head and from the tests I've done locally it seems to work ok.
Let me know how it runs for you.
- Eric Huergo @Eric_Huergo
Works. like. a. charm!
Thank you so much @Kitch - this fixed my issue and I really appreciate you going so far to make it work (even if it was just one line of code!).
Gah, geeked out - thank you so much!!!!!! :)
I hope you have an absolutely great day, you already made mine so much better - still owe you a pint sometime btw! :p
- Kitch Membery @Kitch2022-03-06 22:16:16.850Z
You're welcome Eric!
Rock on! :-)
- In reply toEric_Huergo⬆:Kitch Membery @Kitch2022-03-04 03:03:10.462Z
Also note that the Plugin Loader recalls Presets from the popup menu in as seen in the following image;
- Eric Huergo @Eric_Huergo
Ah, yeah - I've been trying! My best guess at the moment is that there's something going on in the backend on behalf of Avid particularily restricting control around Blue Cat's PatchWork and potentially also DDMF or any AAX VST/AU Hosts.
Seems a bit far-fetched to be honest, but that's all I can muster - I truly am drawing a blank here! :p
In reply toEric_Huergo⬆:Kitch Membery @Kitch2022-03-04 02:45:16.658ZHi @Eric_Huergo,
Please see this link for how to best get help with SoundFlow.
In particulare: 3. Getting help with Packages from the SoundFlow Store. (4:18)
For now I'll move this into the Package forum. :-)
- Eric Huergo @Eric_Huergo
My bad, but yes absolutely! :)
- Kitch Membery @Kitch2022-03-04 03:03:59.531Z
No worries. :-)
In reply toEric_Huergo⬆:Ben Rubin @Ben_Rubinhey @Kitch, i wanted to jump on this thread as i am noticing that my presets fail when a plugin window is already open.
Like the OP, the package will open the new plugin on the correct slot, but fails to load a specified preset. I've reproduced this with several different (TPL) presets.
I am running the preset within a larger script (hence why i need that opt-c for "copy command id:"!) But even when I run the preset directly, it fails at Line 1.
Am I the only one seeing this happen?
- Eric Huergo @Eric_Huergo
Hey Ben, not sure if you've tried this already but I managed to get it sorted by updating my TPL version to the newest (1.4.6) - if you haven't tried that it may be worth a shot!
- In reply toBen_Rubin⬆:Kitch Membery @Kitch2022-03-09 18:40:11.748Z
Hi @Ben_Rubin,
Thanks for reporting this.
Are you running the latest version of "Teezio's Plugin Loader" ie Version 1.4.6? And if so, did your plugin presets only stop working since this update?
Ben Rubin @Ben_Rubinhey ktich, yes i have updated to 1.4.6 and I think the behavoir predates it. it's just now I've figured out "why it doesn't work everytime".
- Kitch Membery @Kitch2022-03-09 20:07:06.573Z
Hi @Ben_Rubin
Can you share a screenshot of the preset that you are trying to use, so I can how the properties are set up.
Thanks :-)
- Ben Rubin @Ben_Rubin
this is an example. the issue was repeatable with multiple presets and plugin manufacturers.
- Kitch Membery @Kitch2022-03-09 22:53:10.491Z
Thanks for that @Ben_Rubin,
Assuming that the spelling and capitalization of the Plugin Name & Category properties in the preset match the Plugin menu items it should be working. Also check for blank spaces at the end of the property values (this will cause it to fail).
To rule out any human error, can you try making a preset that looks like this;
And of course before running the preset, create a dummy preset in a mono/stereo instance of the D-verb and call it "VERB". Then, remove the plugin from Plugin Slot 10 and run this preset again.
If that works and there is no typos etc, we'll need to did a little deeper.
It would also be great to know what your full workflow is that you are trying to achieve, as there may be a better option for loading plugins the way you suggested in your original post (possibly by recalling track presets).
Either way let me know. Hopefully we can resolve this issue for you. :-)
Rock on
- Ben Rubin @Ben_Rubin
Hi Kitch, thanks for your reply. Sorry if I wasnt being clear, but these presets (including the one posted) WORK JUST FINE if there is not another plugin window open on the screen. ALL TPL presets that have the Preset Name filled in fail when there is another plugin window open. Make sense?
My workflow is simply adding inserts to tracks via a stream deck as needed.
Thanks as always.
- Kitch Membery @Kitch2022-03-09 23:12:35.595Z
Ahh I see, I overlooked that detail. Let me test that out :-)
- In reply toBen_Rubin⬆:Kitch Membery @Kitch2022-03-09 23:15:44.077Z
Is the plugin window covering the selected tracks Insert slot by chance? I ask, because the plugin insert menu must be accessible for the loader to work.
- Ben Rubin @Ben_Rubin
No, it happens no matter where the plugin window is located.
- Kitch Membery @Kitch2022-03-10 07:29:34.474Z
Hi @Ben_Rubin
Would you be able to do a screen recording of it failing... I feel like there is something I missing as I can't make it fail here and I've not received any other reports of this. (Note: Eric was experiencing an issue that we've since established is unrelated to what you are seeing)
Just to clarify... From your initial post, I'm gathering the following;
- When running a "Teezio's Plugin Loader" preset that has the "Preset Name" property filled out.
- Opens the correct plugin
- On the correct track
- In the correct insert slot
But if there is a plugin window already open before running the preset it;
- Fails at Line 1
- Does not open the AAX Plugin preset from the Pro Tools preset library popup menu? (The popup menu is marked in the image below.)
Are by chance, the AAX plugin presets you are trying to open, ones that are stored in another place other than the preset menu shown above? As opening presets within the plugins GUI is not supported.
When doing the screen recording it would be great if you could make a preset with an Avid plugin as an example so I can reproduce it here.
Another couple of things to check would be;
- Make sure you have "Link Track and Edit Selection" activated.
- Make sure that in the Pro Tools Preferences, the language is set to "English".
- Make sure that in the Pro Tools Preferences, the "Tool Tips" checkboxes are enabled.
- Make sure nothing is covering the insert slots on the selected track.
- Make sure all the TPL' Preset's "Plugin Name", "Plugin Category" & "Preset Name" properties are filled out exactly as they appear in the plugin and plugin library popup menus.
Hopefully, from a Screen recording, I can work out what is going on. Failing this I'll need to get a bug report so that I can see what is going on in the log files.
- Ben Rubin @Ben_Rubin
Hey @Kitch,
Im back and still having this issue. Your recap of the issue is correct except that it is failing at line 306 of Teezio's Plugin loader. (I am actually running the TPL via command id in another script. So for the Screen Recording, I am running the preset straight off of TPL. I run the same preset on the same track via key command. As you can see, when no plugin window is open, the script runs as expected. When I run the script again, with the first plugin window open, the plugin opens but fails to open the correct preset (Line 306). (Also, this is with all controllers off in the Peripherals window.) (And I checked PT language etc)https://www.dropbox.com/s/x3mwmu87fkrv0kd/IMG_2760.MOV?dl=0
thanks for your help!
best
b- Kitch Membery @Kitch2022-03-27 21:31:07.340Z
Thanks @Ben_Rubin,
So I can reproduce the issue, can you take a screen shot of the 2 presets you are using in the screen recording?
- Ben Rubin @Ben_Rubin
Sure, it's only one preset tho. And the default.
- Kitch Membery @Kitch2022-03-28 01:50:29.395Z
Hi @Ben_Rubin,
Sorry, I should have been more clear... I mean the TPL preset. :-)
- Ben Rubin @Ben_Rubin
- Kitch Membery @Kitch2022-03-28 17:55:28.069Z
Hi @Ben_Rubin,
Are are the above screenshots the presets you used in the screen recording you shared? As the screen recording looks like you are opening 2 instances of EQ3 7-Band.
Thanks.
- Ben Rubin @Ben_Rubin
in the video, just the EQ3 preset 2x.
- Kitch Membery @Kitch2022-03-28 22:50:58.543Z
Hi @Ben_Rubin,
I've created a TPL preset and a EQ3 7-Band preset exactly the same as in your above post.
When I run it multiple times. I'm unable to make it fail.
I can't really tell from the video, but does the track you are trying to load the plugin on have a width other than mono or stereo? (as noted in the package description, the plugin loader only works on Mono and Stereo tracks.)
If not, could you try.
- Quitting SoundFlow from the SoundFlow Icon and restarting it from your applications folder.
- Rebuild the "EQ 7-Band" TPL preset from scratch and try running it again.
If it still fails, would you be able to log a bug report?
- Ben Rubin @Ben_Rubin
The track I am trying to load is a mono or stereo track for sure. I've tried quitting SoundFlow. I created the Eq3 preset just for this demo. To be clear, i have the same behavior with all presets. In the video, the first time I run the preset it works. Then all i do is run the same preset with the previous window open (but not covering the inserts.) This time, with the other plugin window open, the preset fails to open the plugin preset ie, TEST 1.
Sounds like I need to log a bug report.
Thanks, @Kitch
- Kitch Membery @Kitch2022-03-29 02:02:39.598Z
Yeah looks like I'll need a bug report.
Just so you know it's working here, and maybe you can see a difference in your settings that I'm overlooking...
Thanks for hanging in there. Hopefully we can work it out.
Rock on!
- Ben Rubin @Ben_Rubin
Yes, I see yours works just fine, (and your computer is faster!)
So, interesting thing just happen. when there was a "blank" plugin window open (see pic) then the script works as expected. When there is a "populated" plugin window open, the preset fails to open the plugin preset.
does that mean anything to you? also, what is line 306 of TPL? That's where it's failing for me.
thanks
b
- In reply toEric_Huergo⬆:Ben Rubin @Ben_Rubin
Hey Kitch, thanks for the detailed reply, but it wont be for a few days as I'm going on vacation. Another complication that may be causing this somehow is that I have my FaderPort in slot 1 and Mulligan in slot 2 of my Peripherals settings. Will turn those off to see if it makes a difference.
cheers!