Do we still need to be doing this in 2020?
For what reason? Its the OS file system.
Mounting Folders, Why?
Forum rules
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
To ensure that your support issue or bug report is dealt with properly and in good time, please use the link to the tech support request form page on the Merging website.
Make sure to let us know what version you are using when you send your mail. THANKS!
The Merging Technologies team cannot be held responsible for support queries logged on the public forums. If a support query is logged here and only here, it may not be found and dealt with by the appropriate team.
To ensure that your support issue or bug report is dealt with properly and in good time, please use the link to the tech support request form page on the Merging website.
Make sure to let us know what version you are using when you send your mail. THANKS!
Mounting Folders, Why?
David Spearritt
Classical and Acoustic Music, BNE, Australia
Classical and Acoustic Music, BNE, Australia
Re: Mounting Folders, Why?
Hey David,
For most all of us who work by ourselves or who think that having 400 files open is a lot, the mounting thing doesn't make sense. In the below-mentioned context and a few others, it makes a lot of sense.
Scenario:
You are part of a team that shares network resources among multiple workstations.
Operator A and B are both working on the same project
Operator A is doing sound-fx or some similar task that needs access to gazillions of files on the SFX section of the company's file server.
Operator B is sweetening the mixes and requires access to relatively few files.
Should operator B have to deal with operator A's set of directories and any related GUI-sluggishness, etc.?
What if operator B is an intern and shouldn't have access to certain media elements, if only for the protection of said data from accidents or worse?
Sure, these things can be sorted with networking strategies and an IT dept...But in lieu of that there is 'mounting directories'.
Cheers,
Graemme
For most all of us who work by ourselves or who think that having 400 files open is a lot, the mounting thing doesn't make sense. In the below-mentioned context and a few others, it makes a lot of sense.
Scenario:
You are part of a team that shares network resources among multiple workstations.
Operator A and B are both working on the same project
Operator A is doing sound-fx or some similar task that needs access to gazillions of files on the SFX section of the company's file server.
Operator B is sweetening the mixes and requires access to relatively few files.
Should operator B have to deal with operator A's set of directories and any related GUI-sluggishness, etc.?
What if operator B is an intern and shouldn't have access to certain media elements, if only for the protection of said data from accidents or worse?
Sure, these things can be sorted with networking strategies and an IT dept...But in lieu of that there is 'mounting directories'.
Cheers,
Graemme
Graemme Brown
Zen Mastering
1460 Wild Rose Drive
Gabriola Island, BC
Canada V0R 1X5
+1.604.874.9096
"A Horus, A Horus; My Kingdom for a Horus!"
Zen Mastering
1460 Wild Rose Drive
Gabriola Island, BC
Canada V0R 1X5
+1.604.874.9096
"A Horus, A Horus; My Kingdom for a Horus!"
Re: Mounting Folders, Why?
Thanks Graemme, all noted. But what does mounting actually do? Are the file paths stored in an array/memory for fast lookup in PMX code or something else? File systems, network access and speed are vastly improved since 2005 and network servers don't seem to need to "mount" folders.
David Spearritt
Classical and Acoustic Music, BNE, Australia
Classical and Acoustic Music, BNE, Australia
Re: Mounting Folders, Why?
When I first started using Pyramix I was baffled by the folder mounting thing.
Now that I'm used to it I find it really helpful, especially for complex projects which may reference a bazillion files spread across many locations.
Having just the relevant directories mounted keeps things tidy, relieves the burden of having to manually keep track of where everything is located (a significant task if you work on many different projects a day) and saves a lot of time hunting through the OS file system.
Best,
- J.
Now that I'm used to it I find it really helpful, especially for complex projects which may reference a bazillion files spread across many locations.
Having just the relevant directories mounted keeps things tidy, relieves the burden of having to manually keep track of where everything is located (a significant task if you work on many different projects a day) and saves a lot of time hunting through the OS file system.
Best,
- J.
Re: Mounting Folders, Why?
Yes, that is useful, just having project media folder references in one place, like the "Bin" in video editing. But to wait for PMX to "mount" or read or whatever it is doing to the hundreds of files in a mounted folder is baffling. A folder reference is all that should be needed I would have thought.
Liked a "mapped drive" or "quick access" folder link in a corporate network.
Liked a "mapped drive" or "quick access" folder link in a corporate network.
David Spearritt
Classical and Acoustic Music, BNE, Australia
Classical and Acoustic Music, BNE, Australia