#Wmd eurorack diptrace library windows

I can't help feeling that you might need to stress that those Level 2 names are really internal Diptrace library names that are really just an 'alias' for the. lib files as logical directories but it can become confusing when mixing the term 'directory' when it means one thing in one instance (Windows) and something quite different in the other instance (internal Diptrace library 'alias' names described to hold Diptrace Conponents / Patterns). You know and I know that by describing it as 'pretending to be a real directory' you're referring to the. lib files) without clarifying that transition here.

#Wmd eurorack diptrace library windows

lib files in a Windows directory and not the physical directories themselves it seem a bit confusing to me to relate a logical directory name (the Diptrace library name alias) to a Windows file (.eli /. Since those Level 2 names are actually internal Diptrace library names (an 'alias', if you will,) that really point to the actual Diptrace. I know what you mean but I don't know if someone who is new to this might find this a bit confusing (I did at first). In light of all this I'm wondering if you might want to revisit this section as well: This can lead to much head scratching if you take a copy of a library and make changes to it then rename it in Windows only and then share it without changing the Diptrace Library name. So those two independent and inconsistent names may lead to confusion as much as they lend flexibility. Of course this is all because Diptrace keeps the logical file name chosen at the time the library was made as part of the library file itself and it doesn't correlate to the actual Windows file name. But if you rename that actual physical file in your Pattern or Component Windows directory (where those files truly live) and reload that library in it's editor the logical file name that Diptrace displays doesn't change to reflect that name change. One can 'mouse over' one of those level 2 files in the Component or Pattern editor and when you look at the top line of the screen it shows the actual physical file and it's path so you can see what and where the file really is. The logical name is chosen arbitrarily when the library is added in the Component or Pattern editor and may or may not be chosen to be the same as the actual physical file they represent. lib files in a real physical directory, they don't necessarily need to have the same name. I think one of the more confusing aspects of the Diptrace Library file naming convention is that although those logical names in your Level 2 directory actually represent links to real physical.

you get the idea.Īnd yes, this may be painfully obvious to you or me or anyone else already familiar with Diptrace Library Groups but lets not forget that the intended audience is not and however pedantic it might seem I'm always looking for maximum clarity and reinforcement of new terms when trying to learn something new.Īnyway, I can't help but think that maybe a marked-up screenshot of a Diptrace Windows directory structure example might help. And those physical files can contain one or more Diptrace Components or Patterns depending on the library type'.

We can think of Components” as holding 5 pointers, each of which, for purposes of this discussion, point to a level 2 LOGICAL directory which actually, in reality, are just simply. “Level 1 directories point to one or more level 2 LOGICAL directories. If your going to use the logical / physical analogy, it might make more sense *to me* if it read something to the effect of: