Hi,

a quick search for "bash to windows shell converter" on google lead to:

http://stackoverflow.com/questions/3200018/how-do-i-convert-a-bash-shell-script-to-a-bat-file

wich seems to explain nearly all parts, you need to "translate" the bash
scrip from Jan Stary into a .bat file.

regards,
Erich

On 10.12.2016 23:28, Dr. Mark Bugeja MD wrote:
> Well not all. Many files are "releases" and these would play at the end
> of the corresponding main file (the moment a MIDI keyboard key is
> released). That amounts to 75% of the files. So loops will need to be
> created and checked for only 25% of those approx 500 files and they can
> be processed literally over a few minutes with LoopAuditioneer including
> pitch information insertion. Checking the loops will take a few days.
> But I've been doing this regularly for thousands of files often having
> an average of 6 loops per sample! It is tiring and might cause damage to
> the ears with time, sadly.
> 
> Merging is the big job. I'd be happy if I can automate this process. If
> you cannot solve it because you are not versed with Windows, how am I
> expected to sort that out when I don't even come close to understanding
> the "logic" behind your string of characters and why it should be
> different in Windows? I think I can safely state that I would be far
> more confident performing a heart transplant than to play around with
> this code business. :-D Consider me dylexic for coding!
> 
> Regards,
> 
> Mark
> 
> 
> On 10/12/2016 22:53, Jan Stary wrote:
>> On Dec 10 11:18:05, marcusfb@gmail.com wrote:
>>> Hi all,
>>>
>>> What you are saying is right. I did find one pair of files that have
>>> different lengths of audio. This surprised me somewhat. Generally,
>>> the files
>>> are identical in length and carry the loop marks in exactly the same
>>> place.
>>>
>>> Irrespective of any differences, I would still like to merge all the
>>> pairs
>>> of files into stereo. It should not be such a difficult task recreating
>>> loops again and inserting pitch tuning data. LoopAuditioneer does all
>>> that
>>> quite fast and what is left is to check that the loops do not present
>>> clicks.... again.... I can do pretty well and efficiently having done
>>> the
>>> job so often.
>>>
>>> So, forget loops and marks and other data as the issue is complicating
>>> itself unnecessarily.
>> It seems to me that this is the gist of your problem.
>> Merging the mono files int ocorresponding stereo files
>> is a triviality. Losing the loops and marks means
>> you will _not_ have what you want anyway.
>>
>> Do you intend to process each and every of the 2000 resulting
>> files manually in LoopAuditioner to recreate the loops?
>>
>>
>> ------------------------------------------------------------------------------
>>
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today.http://sdm.link/xeonphi
>> _______________________________________________
>> Sox-users mailing list
>> Sox-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/sox-users
>>
> 
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> 
> 
> 
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/xeonphi
> 
> 
> 
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
>