AMI Custom Protocol Handlers and the registry

Pipeline Integrations
2

Hey,
It definitely was for me but its not as bad as it sounds. You only need to register the protocol once…I ended up just registering shotgun:// so all URLs that have shotgun:// as their starting protocol get redirected to my shotgun_ami_handler.py that way I don’t have to register multiple protocols and keep bothering IT.

example .reg to register the needed protocol:
Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\shotgun]
    @="URL:shotgun Protocol"
    "URL Protocol"=""

    [HKEY_CLASSES_ROOT\shotgun\DefaultIcon]
    @=""

    [HKEY_CLASSES_ROOT\shotgun\shell]

    [HKEY_CLASSES_ROOT\shotgun\shell\open]

    [HKEY_CLASSES_ROOT\shotgun\shell\open\command]
    @="python @root\\shotgun\\shotgun_ami\\shotgun_ami_handler.py %1"

replace @root with whereever/whatever server you decide to have your handler.

then you can create infinite action menu items that all get filtered through that handler, and fire off different scripts/actions

Curious to see if there’s a more updated approach to this, as I implemented this workflow 2-3years ago.

-Ross

5 Likes