The first method is the correct one; unbind() won't remove a transition. What's the memory leak problem you encounter?
> how do I find the arguments list for methods, since there is no documentation?
Look in PProPanel, and if usage isn't exercised there, ask.
While a couple of screen movie tutorials are being worked on, no further documentation is currently planned. Hopefully, a comforting thought; there are >140 panels in the wild, and none of them had more documentation than you do.
Below is the thread where you mentioned the qe dom as being "un-recommended" -- which is why I took a crack at it with the "normal" dom. This is actually mission-critical in this case. I need a way to reliably remove all transitions on all sequences in the open project. I can't ask the editors to close/open Premiere to clear the memory because their projects are too complex w/effects etc (they take 5 to 10 minutes to open).
Thanks for the init command. Didn’t help in this case, but I’ll keep it up my sleeve. Looks like there’s lots of useful stuff in the qe dom, too bad about the refreshing issue!
Yep; unreliable refreshing of DOM objects is the primary reason QE DOM is un-recommended.
qe.project.init() can often 'jiggle the handle', enough to get your changes noticed.
Hi again bbb,
Quick question for you: is there a way to clear memory in Premiere?
I’m having an issue where I can run the removeTransitions (video) function in your purginator panel once, but it won’t work again until I restart Premiere. A clue: when I open a different Premiere file & ask the api for the number of tracks in the active sequence, it gives me the number of tracks in the document I’ve closed.
The QE DOM remains officially unsupported and unrecommended. It's also the only way to do some things.
I've sent a (hopefully) relevant sample panel, directly to you.