Librarian: duplicates waves??
20 Jan 2006, 23:21Hi all, (long post, my apologies in advance)
I was finally starting to fool around with the V-Synth Librarian (1.0, that's the latest version correct?). I wanted to start putting together a custom project.. works OK, but I notice it's quite inefficient in its use of wave slots.
Example:
Say I take a patch, let's call it "Foo". It uses two Oscillators, both PCM waves; let's say waves 1 and 2.
Now I make a variant patch called "FooVar", that also uses two Oscillators, waves 1 and 2.
These patches are both in project 'A'. I create a new project 'B', and drag both patches 'Foo' and 'FooVar' into project 'B'. I end up with waves 1-4. Waves 3-4 are the same as waves 1-2.
Problems:
1) The librarian isn't an editor, so I can't tell it to re-assign the waves used by 'FooVar' to the same waves as 'Foo' (since they can use the same copy);
2) The librarian should have noticed that the waves used by the second patch, 'FooVar', are already present in project 'B', from when I first dragged in 'Foo'.
From a programmer's perspective, I think I know why they didn't do this; Waves that have differing contents could have identical names (coming from different projects), or they could have different names, but have the same contents (aliasing one another).
But, then again, from a programmer's perspective, I know they could take the MD5 or SHA1 hash of waves to get a 'signature'. This would allow them to detect duplicates, and re-direct patches to use a single copy, thus saving wave slots in a project.
I guess I'm too 'anal' -- it bugs me to have duplicate waves sitting in my project, when they aren't strictly necessary. And I don't want to sit there for an hour deleting the duplicates, then fixing the patches back on the V-Synth to use the single copy of the desired wave.... sigh.
Hey Roland, if you're listening, tell your programmers to take hashes of waves in a project and resolve duplicates!
Anyone got docs on the .prj internal format? I guess I should crack out the Delphi and start writing my own librarian, hmm?
Like I don't have enough projects already!
Error 144 - Reboot? Y/N
I was finally starting to fool around with the V-Synth Librarian (1.0, that's the latest version correct?). I wanted to start putting together a custom project.. works OK, but I notice it's quite inefficient in its use of wave slots.
Example:
Say I take a patch, let's call it "Foo". It uses two Oscillators, both PCM waves; let's say waves 1 and 2.
Now I make a variant patch called "FooVar", that also uses two Oscillators, waves 1 and 2.
These patches are both in project 'A'. I create a new project 'B', and drag both patches 'Foo' and 'FooVar' into project 'B'. I end up with waves 1-4. Waves 3-4 are the same as waves 1-2.
Problems:
1) The librarian isn't an editor, so I can't tell it to re-assign the waves used by 'FooVar' to the same waves as 'Foo' (since they can use the same copy);
2) The librarian should have noticed that the waves used by the second patch, 'FooVar', are already present in project 'B', from when I first dragged in 'Foo'.
From a programmer's perspective, I think I know why they didn't do this; Waves that have differing contents could have identical names (coming from different projects), or they could have different names, but have the same contents (aliasing one another).
But, then again, from a programmer's perspective, I know they could take the MD5 or SHA1 hash of waves to get a 'signature'. This would allow them to detect duplicates, and re-direct patches to use a single copy, thus saving wave slots in a project.
I guess I'm too 'anal' -- it bugs me to have duplicate waves sitting in my project, when they aren't strictly necessary. And I don't want to sit there for an hour deleting the duplicates, then fixing the patches back on the V-Synth to use the single copy of the desired wave.... sigh.
Hey Roland, if you're listening, tell your programmers to take hashes of waves in a project and resolve duplicates!
Anyone got docs on the .prj internal format? I guess I should crack out the Delphi and start writing my own librarian, hmm?
Like I don't have enough projects already!
Error 144 - Reboot? Y/N
Error 144 - Reboot? Y/N