<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.psl.dev/index.php?action=history&amp;feed=atom&amp;title=Avid_Media_Files_re-pointing</id>
	<title>Avid Media Files re-pointing - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.psl.dev/index.php?action=history&amp;feed=atom&amp;title=Avid_Media_Files_re-pointing"/>
	<link rel="alternate" type="text/html" href="https://wiki.psl.dev/index.php?title=Avid_Media_Files_re-pointing&amp;action=history"/>
	<updated>2026-07-25T02:58:33Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://wiki.psl.dev/index.php?title=Avid_Media_Files_re-pointing&amp;diff=11226&amp;oldid=prev</id>
		<title>Stephan Krause: Created page with &quot;Create a Symbolic Link to another folder   Scenario: Avid requires that the Avid MediaFiles folder live at the root level of the hard  drive in order for it to read the media,...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.psl.dev/index.php?title=Avid_Media_Files_re-pointing&amp;diff=11226&amp;oldid=prev"/>
		<updated>2015-12-03T13:20:33Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Create a Symbolic Link to another folder   Scenario: Avid requires that the Avid MediaFiles folder live at the root level of the hard  drive in order for it to read the media,...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Create a Symbolic Link to another folder &lt;br /&gt;
&lt;br /&gt;
Scenario: Avid requires that the Avid MediaFiles folder live at the root level of the hard &lt;br /&gt;
drive in order for it to read the media, however a situation may present itself &lt;br /&gt;
where that is not the case. Avid will not be able to read the media because the MediaFiles folder is buried in &lt;br /&gt;
subfolders. Creating a Symbolic Link is a way to trick Avid into thinking the MediaFiles folder lives at the root of &lt;br /&gt;
the drive. &lt;br /&gt;
&lt;br /&gt;
Use the Terminal command: ln -s (source) (destination) &lt;br /&gt;
&lt;br /&gt;
An example:&lt;br /&gt;
&lt;br /&gt;
On DRIVE_XYZ there is a folder named Archive_05. &lt;br /&gt;
Inside Archive_05 is an Avid MediaFiles folder. I want Avid to access the media that is &lt;br /&gt;
inside this folder. &lt;br /&gt;
&lt;br /&gt;
In Terminal, I type: &lt;br /&gt;
ln -s and drag the source folder (ie, DRIVE_XYZ/Archive_05/Avid MediaFiles/MXF) into the Terminal window. Then, I drag the destination folder into the Terminal window. (ie, DRIVE_XYZ/Avid MediaFiles)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It should look something like:&lt;br /&gt;
&lt;br /&gt;
ln -s /Volumes/DRIVE_XYZ/Archive_05/Avid\ MediaFiles/MXF /Volumes/DRIVE_XYZ/Avid\ MediaFiles&lt;br /&gt;
&lt;br /&gt;
(I colored the Source Path yellow and the Destination Path orange for clarity)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When you press Enter, you should see a folder &lt;br /&gt;
named MXF appear inside the Avid MediaFiles folder at the root level of DRIVE_XYZ. This new MXF folder will have an &lt;br /&gt;
Alias icon on it as it is now a shortcut to the MXF folder inside DRIVE_XYZ/Avid MediaFiles&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Warning: Any media that you create and send to &lt;br /&gt;
DRIVE_XYZ will get placed inside the Archive_05/Avid MediaFiles/MXF folder, so if &lt;br /&gt;
that is not your intention remember to kill the Linked folder before writing &lt;br /&gt;
any media to the drive. You can kill the &lt;br /&gt;
link by Trashing the shortcut folder.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
DO NOT TRASH THE ORIGINAL MXF FOLDER!!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
psl example&lt;br /&gt;
&lt;br /&gt;
psledit13-08:~ admin$ ln -s /Volumes/pslsrv10/Projects/_Restored/MCQ14_FLM01_Telekom_AZ_2.0_Film/MCQ14_FLM01_Telekom_AZ_2.0_Film/MC15F01_Material/MC15F01_Material/AVID/Avid\ MediaFiles/MXF  /Volumes/PSL_7TB_ARECA/Avid\ MediaFiles&lt;/div&gt;</summary>
		<author><name>Stephan Krause</name></author>
	</entry>
</feed>