Ok. The subject doesn't make any sense because my mad scientist brain is 
swimming with an idea and I'm just gonna write stream of consciousness. 
Something occurred to me about our problems with using samplers like structure, 
kontact, etc.
All those samplers do is to load an external file that's saved somewhere on the 
hard drive. They have extensions like .gig, .tki, .exs, etc. If logic serves, 
when a preset it saved using pro tools, that creates a .tfx file, which points 
to the above mentioned sampler file. How can we access the actual code of the 
.tfx file and learn it's hierarchy so that we can write them outside of the pro 
tools environment? If we can learn how to write them in an advanced text editor 
or compiler, can't we create an automator script to anylize a folder, get all 
the file names, and input each one into it's own .tfx file? That way, we could 
quickly create native pro tools presets of otherwise inaccessible presets. I'm 
not the only one who thought of this. Check out this link.
http://protools.ideascale.com/a/dtd/Preset-Maker-Utility/29275-3779


When I bring the .tfx files up in text edit, it's gibberish. Anyone know what 
language those are written in? Let's get some dialog going on this, because if 
we can automate the process of making these files, then we can distribute them 
to everyone, granted that they've saved the installed instruments into the 
common path. However, to take this a step further, someone could create a small 
program whereby they tell it where the instrument files are stored, which then 
alters the automator script to create the tfx files with the propper paths. Any 
thoughts? 

Have a great night.

Reeves

Reply via email to