Mike

Members
  • Content count

    126
  • Joined

  • Last visited

  • Days Won

    4

Mike last won the day on July 14 2016

Mike had the most liked content!

About Mike

  • Rank
    ftrack ninja

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

705 profile views
  1. I just want to clarify that I'd like the sticky to be stickied for everyone, not just the user who stickied it. But it would be nice to have stickies only visible to you as well. You could share private stickies between people by tagging someone in the sticky (basically creating private threads). A checkbox would allow you to see all stickies or just your own (you can use the current filter by author to narrow down sticky visibility as well)
  2. I'm using a task's note section to link to an external OneNote notebook where artists and developers can keep detailed track of an asset. It would be great if I could sticky that note to the top of the notes list
  3. Location Setup

    This is great, thanks a lot, Lucas!
  4. Location Setup

    Good to know that I'm understanding it haha. So how would I go about doing this? I'm looking at the source code and I see base, disk, and server accessors. Could I use the server module as a starting point and the disk accessor as a reference and eventually get some results? What I mean is, is there enough here in the source code that I could eventually figure this out with minimal guidance? Also, in terms of how to transfer files over the internet, where should I start? Like are there libraries, tutorials, example programs/codes that do this already so I can start to breakdown the process and see exactly what I need? Thanks
  5. Location Setup

    Hi Lucas, After getting back into locations and taking a look at the docs again, i think accessors are starting to make sense to me. A few questions/comments just to clarify: So ftrack comes with a disk accessor. In my location plugin I've setup my work and home locations with disk accessors. By doing that am I basically telling ftrack that the locations are local? If I want to transfer files over the internet do I need to set my home location to use a disk accessor and my work location to use an internet accessor? (or whatever the accessor would be called) Once those are set, I can use target_location.add_component(component, source=source_location) to easily transfer a file between the two? (as long as both locations are available)
  6. Location Setup

    I have a little time right now, so I'm revisiting locations with the new api. I think I have it sort of working. I have a quick question, does ftrack have file transfering across locations built in, or is that up to the developer to create? For example I'm able to see the my current location (home) and the main studio location (work) from the maya import plugin. If i'm at work and I have some files on my home computer, I'm expecting that when I hit transfer in the maya import plugin that it will move the file from my home to computer to my work computer. This is never the case though. Instead the plugin is just creating the file directory on my local drive with my work's file structure prefix. Basically, does ftrack have a builtin ability to transfer files over the internet? Current location plugin:
  7. I think I discovered the problem. When I updated my master version of ftrack connect it looks like some of the modules were gitignored (it's a pesky problem). So they weren't available on my release directory, but I had them in my dev directory. I'll verify this tomorrow.
  8. Hello, are there any resources/tutorials for new api location, structure, and resolver migration? I've been waiting for the new API roll out to finally tackle these, but I'm not finding enough resources on the dev portal to successfully migrate. I'm currently getting this error when my location tries to register: 2017-10-23 15:02:36,408 - ftrack_connect.ui.application.Application - ERROR - Error during login. ....... ...... ..... File "path\to\mb_plugins\hook\location\mb_firstborn_location.py", line 65, in register session.event_hub.subscribe( AttributeError: 'Registry' object has no attribute 'event_hub' My new location plugin is below. I'd also like to update my structure and resolver plugins (if that's possible yet). import os import sys import platform import ftrack_api import ftrack_api.entity.location import ftrack_api.accessor.disk def configure_locations(event): '''Configure locations for session.''' session = event['data']['session'] # Import custom structure plugin. RESOURCE_DIRECTORY = os.path.abspath( os.path.join(os.path.dirname(__file__), '..', '..', 'resource') ) if RESOURCE_DIRECTORY not in sys.path: sys.path.append(RESOURCE_DIRECTORY) from pipeline_structures import structure_plugin # Location and prefix variables. studio = os.getenv('STUDIO').lower() site = os.getenv('SITE').lower() LOCATION = '{0}.{1}'.format(studio, site) # Get mount point. disk_name = session.query('Disk where name is "{0}"'.format(LOCATION)).one() platform_name = 'windows' if not platform.system().lower() == 'windows': platform_name = 'unix' disk_path = disk_name[platform_name] PREFIX = os.path.expandvars(disk_path) # Find location(s) and customise instances. #ftrack.ensureLocation(LOCATION) # I need an updated way to do this. I've noticed the session.ensure() method, is that it? location = session.query('Location where name is "studio.site"').one() #ftrack_api.mixin(location, ftrack_api.entity.location.UnmanagedLocationMixin) # Not sure what this does, do I need it? location.accessor = ftrack_api.accessor.disk.DiskAccessor(prefix=PREFIX) location.structure = structure_plugin.mbStructure() location.priority = 50 def register(session): '''Register plugin with *session*.''' session.event_hub.subscribe( 'topic=ftrack.api.session.configure-location', configure_locations )
  9. Yes it does. Is connect intended to only work as a local installation? Are there new environment variables that I'm not setting? With the current setup that used to work, I was able to have everyone launch from connect location on a server. That way I was only managing one installation, instead of several.
  10. I download connect onto a server location then use a batch file to launch and set env variables. Does this count as a custom setup?
  11. The solution Mattias linked to worked perfectly. Not sure what went wrong with your suggestion, Marin, but it just didn't pick up everything. Thanks for the help!
  12. Thanks guys! I've tried using the auto_mock_imports variable and it's doing the trick for the most part. There are a couple of stragglers but I think I can figure it out from here. I'll try to let you know how it goes.
  13. Hello! I'm starting to figure out how to use sphinx for my own documentation. I'm using autodoc and building the documentation from the command line. I keep getting import errors for modules such as Qt.py and maya.cmds whenever I try to build my code. I'm using the correct virtual env, the modules are installed in the venv. I'm at a loss! I've seen that you guys use sphinx for your documentation, any tips? Thanks!
  14. I've successfully migrated to 2018 on my local working pipeline. I send my tool to the remote repo, then clone that onto a server location. I do all the setup to get the venv working then run ftrack. Everything is fine at this point. When I run Maya everything works as expected until I get this error: // Error: No module named collect_playblast_camera # Traceback (most recent call last): # File "<maya console>", line 1, in <module> # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\resource\maya_plugin\userSetup.py", line 18, in create_publish_menu # context_id=os.environ['FTRACK_CONTEXT_ID'] # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_pipeline\application_plugin.py", line 28, in __init__ # self.register_assets() # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_maya_publish\plugin.py", line 31, in register_assets # ftrack_connect_maya_publish.shared_pyblish_plugins.register() # File "path\to\dependencies\ftrack_connect\resource\connect-standard-plugins\ftrack-connect-maya-publish-0.5.1\dependencies\ftrack_connect_maya_publish\shared_pyblish_plugins\__init__.py", line 9, in register # import ftrack_connect_maya_publish.shared_pyblish_plugins.collect_playblast_camera # ImportError: No module named collect_playblast_camera // It's strange because there is a module named collect_playblast_camera in that location. Also, .pyc files are generated for the __init__.py and collect.py files, so it's compiling in that directory until the error. I've tried a bunch of stuff including straight up copying and pasting my working ftrack connect directory into the cloned one. I get the same error no matter what. Any thoughts? Thanks! EDIT: I think it might have to do with the file path being too long (I'm using windows). The pipeline works fine on my home computer.
  15. Not sure what fixed it exactly, but I removed all the accidental local python packages and added this line to my custom maya hook (along with a bunch of other changes): if float(application['version']) < 2017: environment['QT_PREFERRED_BINDING'] = 'PySide' else: environment['QT_PREFERRED_BINDING'] = 'PySide2' I think setting the preferred bindings was probably the key.