[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sox-users
Subject:    Re: [SoX-users] Fwd: Re: merging mono files
From:       "Dr. Mark Bugeja MD" <marcusfb () gmail ! com>
Date:       2016-12-12 20:06:16
Message-ID: 28c41445-1b8d-288b-61cf-a170d6447cd8 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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.
>
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><font face="Calibri">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.<br>
      </font></p>
    <p><font face="Calibri"> </font>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.</p>
    <p>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.<br>
    </p>
    <div class="moz-cite-prefix">Thanks. For all intents and
      purposes..... Mission Accomplished!<br>
      <br>
      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. <br>
      <br>
      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!<br>
      <br>
      Well done!<br>
      Mark<br>
      <br>
      On 12/12/2016 20:02, Jeremy Nicoll - ml sox users wrote:<br>
    </div>
    <blockquote
      cite="mid:f6b349527ee29dc489cb3481823c2d20@wingsandbeaks.org.uk"
      type="cite">
      <pre wrap="">On 2016-12-12 18:35, Dr. Mark Bugeja MD wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">I ran the script. It seems to have merged the files in the \
subfolders but not those in the main folder!
</pre>
      </blockquote>
      <pre wrap="">
I don't think you described files being in a main folder.  Your example 
showed
that they were in eg

   \Basson16L\relnnnnn\
&amp; \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\
&amp; \~mainfilesR\relnnnnn\

simply because that would have kept the file structure the same for all 
of them,
&amp; 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.


</pre>
    </blockquote>
    <br>
  
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: \
99%;' /> <table style='border-collapse:collapse;border:none;'>
	<tr>
		<td style='border:none;padding:0px 15px 0px 8px'>
			<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient">
  <img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast \
logo" />  </a>
		</td>
		<td>
			<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; \
font-size:12pt;'>  This email has been checked for viruses by Avast antivirus \
software.  <br><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient">www.avast.com</a>
  </p>
		</td>
	</tr>
</table>
<br />
</body>
</html>



------------------------------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic