I did explain before that the main folders
have samples PLUS 3 folders, each with samples of their own. I
just sent a reply to highlight this fact. I am in the process of creating "main" subfolders, shifting the main files there and repeating the process. Seems to be working fine like this. The structure of the folders is how GrandOrgue and Hauptwerk
recognize the main files for a note/sound, with releases for those
notes in appropriate subfolders. There are usually 2 or 3 releases
per main file. Sometimes the longest release is part of the main
file and marked with a cue point where it starts hence the
additional 2 releases are in separate folders. The releases are of
different duration to mimic staccato (pressing a note which a
sharp tap, immediately releasing it), a portato (what you get if
you hold a note just a bit longer) and the sustained release
(which is what one would hear on keeping a note held for a longer
duration). The tails are progressively longer (measured in
hundreds of milliseconds, of course) and produce the echo heard
best in a hall or church. This is a fine detail in reproducing
notes digitally but detectable by musicians. Without the releases,
the notes sound dull or "dry" as you would get in a small carpeted
room.... no echo (no reverb) at all. Thanks. For all intents and
purposes..... Mission Accomplished!
There was no way I was going to achieve this on my own. Had I followed some advice given hear, I'd still be desperately tearing my hair out and banging my forehead on the table. I must thank in particular Kevin Conder and Jeremy Nicoll who spared me a lot of tears, bruises and a fractured skull.... not to mention a broken computer screen! Well done! Mark On 12/12/2016 20:02, Jeremy Nicoll - ml sox users wrote: On 2016-12-12 18:35, Dr. Mark Bugeja MD wrote:I ran the script. It seems to have merged the files in the subfolders but not those in the main folder!I don't think you described files being in a main folder. Your example showed that they were in eg \Basson16L\relnnnnn\ & \Basson16R\relnnnnn\ The existing script, given the path and a sample name like "Basson16" finds and merges files in subfolders of Basson16L and Basson16R. That's what I expected it to need to do, and what Kevin expected it to need to do. If you wanted it to do something else as well, you'd have needed to explain that more clearly. But more to the point, if you do have sample files in a main folder as well as sub- folders, it's hard to understand why. Do they not also correspond to a particular stop? Even if they don't, and they had to be a separate collection, I'd have put them in a dummy subfolder of their own, eg \~mainfilesL\relnnnnn\ & \~mainfilesR\relnnnnn\ simply because that would have kept the file structure the same for all of them, & thus kept the scripts simple. That "~mainfilesL" has a "~" at the start so it would appear at the start of an alphabetically-sorted list of folders.
|
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Sox-users mailing list Sox-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/sox-users