When I return home, I just resync the mobile drive and my NAS, and pick up where I left off with my desktop. With most programs I use, I just point to that content folder and everything is the same.
#Bitmap image moho pro portable#
In this case, I have a synced copy of my production's content directory on a portable drive. In my experience, the user defined and managed content directory is what works most reliably and efficiently, even when I need to work away and then return to my studio. Of course, when it comes back, you have the problem of re-linking everything to conform to your network structure, so it's not necessarily ideal for collaboration. zip this up and send it away when the intention is to have somebody 'offline' work on it. All directory original structure is lost, but Moho knows where the files are and it's easy to. The collects copies of all the files in use and dumps them into a folder. Moho has the next best thing with Gather Media. If this method of asset management was added, I'd probably never use it, so yes I agree that it should be made optional. Even my 'small' personal animations may have dozens of Moho Project files. This can be a nightmare on productions with dozens or hundreds of Project files.
#Bitmap image moho pro update#
Having files embedded also makes it difficult up universally update shared assets. That could easily bloat the file sizes because of duplication and increase the file size of an entire production by many unnecessary gigabytes or even terabytes.
I'm not so keen on having all the assets embedded within a project file. It doesn't matter if the content directory is nested at a different level or that the path is using a different drive letter because the path is relative. This way, even if when the entire production is move to a completely different drive, so long as the hierarchy is preserved within that content directory, all I need to do is re-point the program to that content directory and everything load as before. Most animation programs I work with allow me to assign a specific directory for a given production, which works much better. I agree that Moho's content directory management is messy and easy to break.
0 kommentar(er)
