I’ve been meaning to add this feature for a while, but didn’t have time to do it until recently. Now the script can automatically calculate the “Scale Multiplier” for you. Just enable the Auto Calculate button and enter the proxy/transcode resolution and the raw/grade resolution.
It should be available in the Logik Portal now.
Hi John, did you get a chance to update your script on the Logic Portal? I’ve just downloaded what’s supposed to be the last version (from the 2023 folder), and the files are a few months old (April 2022), and the UI on my Flame says v1.91… Maybe I’m doing something wrong… I’ve downloaded them by FTP (address found in the Logic Portal script), since my Flame doesn’t have internet access, company’s policies.
I’ve never used your script before, but I saw it advertised in the last Logic Live and I was eager to try it.
Thanks for your work.
Hi David. Yes, version 1.93 is in the Logik Portal, but I’m including it here too. Let me know how it goes for you.
premiere_xml_mediahub.zip (17.2 KB)
Thanks goes to @KuleshovEffect for the original script and upgrades.
Great, John, this one shows as 1.93 in my Flame. I’ll definitely try it on my next job (99% of the XMLs we are receiving nowadays are Premiere’s). One more question: should I keep these 2 files in their own subfolder when putting them in the opt/autodesk/shared/python folder, or should they be directly under /python/ ? (That’s what I did, and it works, but I actually would prefer to keep it more tidy…).
Thanks again for your help.
Cool. Glad it’s working for you. I keep mine in a subfolder named “premiere_xml_mediahub.” And if you were able to install it from the portal, that’s what it would do too.
First of all thank you for the script.
I do have a weird thing here , all the actions are fine but they all bug around scaling relative to timeline res and not source res unless I
copy the tlfx and paste it again over itself? in which case its fixed? I dont get it hoenstly.
what seems to happen that by default the camera in action is somewhere in nirvana (on the Z axis) while when I copy paste the action the camera resets to the default value of 1483.6 … ?!
actually it often fixes itself when I add and delete a green tlfx, sometimes changing the tagged colorspace makes it snap back to reality…
that is mighty weird and looks like a bug 
sadly if I export a aaf from premiere it has no scale/repo effects at all?
That weird thing happens to me, too - I can’t tell if it’s the script.
Things that sometimes fix it:
Possibly related to this?
-Ted
god to know I am not alone, this is mighty annoying , Ill see if one can use the api to somehow refresh the clip or whatever happens when you do this kind of stuff?
I can only imaging the action is somehow stuck in the resolution of the timeline and its not correctly refreshing once a clip with a new resolution is conformed? I can only guess but ill try a few more things to see if I can somehow kick flame into getting its act together with whatever
Maybe you are working for a source TL from the library and the Flame pref is set to protect those clips.
what is a source tlfx from the library?
this happens just when I import the xml without doing anything else , all of the tlfx actions behave the same
file.xml (167.7 KB)
i have submitted a bug report with a video and this fixed-by-the-script-xml to adsk
If the clip is in the Library and you have the PROTECT FROM MEMORY on in prefs/general then you cannot edit or change the clip in anyway.
So move the sequence to the desktop and open it as a sequence or turn off the pref
I have this issues with Premiere XML as well. Every time… with out without John’s script. I’ve been meaning to put in a bug report but I don’t know exactly how to describe it.
One work-around I’ve found is to add a source effect to the segment (the Green version of Image) and then it will pop to the correct ‘source’ res.
it seems extremely random also sometimes copy pasting the clip fixes it, other times it doesnt, wtf is going on
I just tried to confork my sequence like 10x and 10x different stuff happens
its not in the libray
I made a video of it and sent it to adsk…
this has to get fixed.
Does your XML reference source clips of a resolution different than your sequence?
yes.
This is a thing we run into regularly with AAF. At one point we had it logged as FLME-60206 and FLME-61276. My workaround is to flail around copying the segment between tracks, removing the Action on the copied segment and then copying the original Action to it.
Yes the current issue is the same as the issues you have logged. It is an problem for AAF and XML related to Mixed resolutions content.
well.
I have 180timelines at 2min each to conform and so anything manual sadly wont do
its like THIS close to just be a one click conform if the action wasnt bugging out …
from what I hear tlfx actions are a bit of a minefield.
so far… from what I have tried
aaf from premiere has no repos
aaf from resolve has no repos
fcpx-xml from resolve has repos comming in as as 2D transform (which obviously does not work).
xml from premiere has repos as action tlfx and after this fixing script they are accurate (given the scale factor of the proxy vs rushes and how the premiere setup was done.
whats gotten very common here is premiere users working with fullres proxy media so prores proxy but in source 6K or whatever res on a HD timeline, you then have 2 options
if you just drop a 6K clip into your timeline premiere with just “center” crop as default resize
“set to frame size” scales the clip down to fit into timeline res (letterbox scale) by putting in numbers in a scale effect. so each clip will have a scale applied to it, this only makes any sense if proxy res == rushes res otherwise those numbers dont make sense at all.
“scale to framesize” on the other hand is doing a letterbox scale without touching the scale effect.
This us a crucial and often overlooked thing that in premiere it really matters how stuff is set up for scales to even have the chance of working.
So now lets say someone has choosen option 1 “set to framesize” and a clip has a scale of 32%, this is now relative to the clips resolution because its the same operation as a resize in flame set to crop but then scaled 32% which you cant do in the resize node m because “crop” has no additional scale options and everything larger than timeline res gets cut off. So thats why we have to use action.
In Action the idea is that just by throwing in a 6K file into a tlfx action it should behave exactly like a “center crop” operation, which it does! usually… without this bug at least. So when you then apply a axis node on the surface a d set it to 32% scale it will match whatever was done in premiere - cool.
Option B ( scale to frame size ) gives you scales relative to timeline resolution, so you could totally do it all in a resize node by using letterbox and then put in the additional scale values used (the will most likely be positive or above 100%) .
Also when using this the resolution of the proxys are a none issue, ideally its the same aspect ratio as the source however.
I prefer optionB, much cleaner imho. but somehow everyone does set to framesize and its always problematic
