Doepfer

Hi all this is very interesting as I have an A112 on order with the uk  
Doepfer distributor!

I am a Mac OS user but hadn't realised Midi sample dumping to this  
module from Mac would be a problem.

I was hoping to use Elektron's SysEx c6 software - which is free  
shareware.

http://www.elektron.se/support-and-downloads

I have been using it to MIDI sample dump to my c64 running Mssiah.

Could anyone advise if this software will work with an A112? Reading  
the A112 manual it looks like it should?

Thanks

> I was hoping to use Elektron's SysEx c6 software - which is free  
> shareware.

Ah, yes, that can do some of the work!

So basically, MIDI lets you get one system (such as a DAW running on a computer) to talk to several others (such as the A-112 module), and there are many well-defined musically relevant commands of what the former can tell the latter to do, such as start and stop playing notes...  Sysex -- system exclusive messages -- are MIDI's way of saying "I don't know what this information is, but I'll blindly relay it to you."  So bearing in mind that some DAWs and, by the looks of things, this C6, are happy to do this blind relaying of data, that means no one needs to write a program from scratch to do that.  So that's good.

We still need to translate .wav files into the A-112's native format that runs over the top of sysex, but I'm pretty confident I can reverse engineer the DOS program.  I'll give it a waveform, see what it's sending, and see how they compare.  Hopefully it's not doing anything *too* cryptic. :)

All the best,
Zoë.

OK, to clarify a bit more about S6...

It looks like a really neat tool that can copy across .wav and .aif files over sysex, using the MIDI sample dump standard protocol, which is MIDI, and on top of that it's a type of sysex format agreed upon by several different manufacturers.

The thing is, not all samplers use this format.  Some use their own custom, proprietary, idiosyncratic format over sysex.  So both use MIDI, and both use sysex in particular, but there's another layer of abstraction above that one which is incompatible.  It sounds like a pretty safe bet that the A-112 is amongst these samplers using a non-standard method, as it's got the interesting wavetable thing going on that most samplers don't, allowing you to dump a single 305 byte cycle as well as a whole 74,909 byte full waveform.

Nevertheless, this software does let you send raw sysex information -- .syx files -- regardless of what that data happens to be (like copying a file even if you don't have an application that understands it), so all I need to do is write a simple script that converts .wav files into Doepfer A-112 compatible .syx files, then you can use S6 or any other sysex transmitting software to copy it across.

Which is easier said than done, but worth a shot if there are a good few people who would benefit from it.

Incidentally, although I have 6 to 9U's worth of wonderful Doepfer modules, the A-112 isn't among them... so if anyone would like to volunteer to try out some .syx files once I create them (which may well be weeks or months away), send me an e-mail off-list.  I could do with some beta testers. :)

All the best,
Zoë.

Hey hey,

Very nice that you are diving in this deeply so quick Zo�!
Please don't forget the OS X users :D
Go for it!

As a Max/MSP user I am still intrigued by the thought of the patch that
could do this.... oh well.


Grtz

Ernst.


On Tue, Oct 16, 2012 at 5:51 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> OK, to clarify a bit more about S6...
>
> It looks like a really neat tool that can copy across .wav and .aif files
> over sysex, using the MIDI sample dump standard protocol, which is MIDI,
> and on top of that it's a type of sysex format agreed upon by several
> different manufacturers.
>
> The thing is, not all samplers use this format. Some use their own custom,
> proprietary, idiosyncratic format over sysex. So both use MIDI, and both
> use sysex in particular, but there's another layer of abstraction above
> that one which is incompatible. It sounds like a pretty safe bet that the
> A-112 is amongst these samplers using a non-standard method, as it's got
> the interesting wavetable thing going on that most samplers don't, allowing
> you to dump a single 305 byte cycle as well as a whole 74,909 byte full
> waveform.
>
> Nevertheless, this software does let you send raw sysex information --
> .syx files -- regardless of what that data happens to be (like copying a
> file even if you don't have an application that understands it), so all I
> need to do is write a simple script that converts .wav files into Doepfer
> A-112 compatible .syx files, then you can use S6 or any other sysex
> transmitting software to copy it across.
>
> Which is easier said than done, but worth a shot if there are a good few
> people who would benefit from it.
>
> Incidentally, although I have 6 to 9U's worth of wonderful Doepfer
> modules, the A-112 isn't among them... so if anyone would like to volunteer
> to try out some .syx files once I create them (which may well be weeks or
> months away), send me an e-mail off-list. I could do with some beta
> testers. :)
>
> All the best,
> Zo�.
>  
>


[Non-text portions of this message have been removed]

This is a long shot, I realise, but... does anybody here have the A-112's DOS program, A112SDL.EXE, up and running, outputting to a physical MIDI device, and on top of that, have a second computer with physical MIDI?

I'm on OS X, and so far I've tried A112SDL.EXE in DOSBox and VMWare.  In both instances it appears to work just fine, but I can't figure out where the data's being sent.  Certainly not my breakout box...

What I could do with is for someone to load a few .wav files into A112SDL.EXE (I can provide several for this purpose, as I need to compare the originals to what gets sent), get it to send them out via MIDI, attach their computer's MIDI out to their other computer's MIDI in, and dump the data.  C6 is just fine for the latter, and a free download.

I'd be happy to talk anyone through this process via e-mail offlist, it jut needs to be someone with two computers that both have old fashioned hardware MIDI, one of which definitely has A112SDL.EXE up and running and outputting to the hardware MIDI port.

Otherwise I'll have to buy or borrow an old DOS machine with a SoundBlaster card and joystick port to regular MIDI out adapter like the old days, which is sort of a step backwards in my studio. :)

Thanks!
Zoë.

> This is a long shot, I realise, but... does anybody here have the
> A-112's DOS program, A112SDL.EXE, up and running, outputting to a
> physical MIDI device, and on top of that, have a second computer
> with physical MIDI?
>
> I'm on OS X, and so far I've tried A112SDL.EXE in DOSBox and
> VMWare.  In both instances it appears to work just fine, but I
> can't figure out where the data's being sent.  Certainly not my
> breakout box...
>
> What I could do with is for someone to load a few .wav files into
> A112SDL.EXE (I can provide several for this purpose, as I need to
> compare the originals to what gets sent), get it to send them out
> via MIDI, attach their computer's MIDI out to their other
> computer's MIDI in, and dump the data.  C6 is just fine for the
> latter, and a free download.
>
> I'd be happy to talk anyone through this process via e-mail
> offlist, it jut needs to be someone with two computers that both
> have old fashioned hardware MIDI, one of which definitely has
> A112SDL.EXE up and running and outputting to the hardware MIDI port.
>
> Otherwise I'll have to buy or borrow an old DOS machine with a
> SoundBlaster card and joystick port to regular MIDI out adapter
> like the old days, which is sort of a step backwards in my studio. :)
>
> Thanks!
> Zoë.

I'd suggest to contact Christian Assall (software@doepfer.de). He programmed
the firmware of the A-112 module (not the DOS program) and knows details
about the Sysex file structure and other things.

Best wishes
Dieter Doepfer

> I'd suggest to contact Christian Assall (software@doepfer.de). He programmed
> the firmware of the A-112 module (not the DOS program) and knows details
> about the Sysex file structure and other things.

Ah, thank you!  E-mailed.  That would indeed help.

It may interest any A-112 owners to know that someone else has already made some software for it this year.  You can read all about it over at http://www.muffwiggler.com/forum/viewtopic.php?t=50154&start=all&postdays=0&postorder=asc

It's currently Windows only, but it's still being maintained, it's free and it works, so that's a good sign!  I'll see if I can intercept the signal from that (no DOS required, yay), but even if not, there's some software available for people right now.

All the best,
Zoë.

Wow, I've got the technical document from Chris Assall already!  That was *quick*!  I love this company. :)  It's the best customer service / tech support I've ever seen!

I'll e-mail the people working on the other current tools to see exactly what they're doing, but I already have a lot of the pieces of the puzzle now.  It's looking good!

All the best,
Zoë.

> It may interest any A-112 owners to know that someone else has
> already made some software for it this year.  You can read all
> about it over at
> http://www.muffwiggler.com/forum/viewtopic.php?t=50154&start=all&p
> ostdays=0&postorder=asc
>
> It's currently Windows only, but it's still being maintained,
> it's free and it works, so that's a good sign!  I'll see if I can
> intercept the signal from that (no DOS required, yay), but even
> if not, there's some software available for people right now.
>
> All the best,
> Zoë.

Thank you. That looks pretty cool. I will see if I can find out the author
and ask for the permissing to add the file to our website for download.

Best wishes
Dieter Doepfer

Thanks to the wonderful help of Dieter Doepfer and Chris Assall (and Google Translate, hehe), I've made the first attempt at a .wav to .syx converter for the A-112.  The files are 74909 bytes each, with the right amount spent on the header, most significant bits, least significant bits and footer.  It'll probably take a while of hearing people report the result and tweaking it with trial and error to get it working perfectly, but we're definitely out of the "long shot" zone and into the "fixing bugs" one.

Thanks everyone for all your help!

All the best,
Zoë.

Hi again!

Sorry about the barrage of e-mails, but I'm guessing some of you with A-112s would like to know where things are at...

So I got a reply from Nico, who made the software that originally sparked this discussion, the http://www.rampe-d.de/Software/A-112_Sample_Dump_Tool.html program.  It turns out he got very close to finishing it, then his hard drive died and he had to revert to an old, buggy version retrieved from a backup.  He's too busy with work to finish it right now, but he's happy to upload the old version and also the source code to the Max patch, so I believe he's doing that around about now.

It turns out he'd also seen the other A-112 software mentioned earlier, that someone else was working on this year, and didn't want to contribute something redundant.  I, on the other hand, think that having too many programs to choose from is a better problem than not having a single one that can easily be used, so let's try a little redundancy! :)

All the best,
Zoë.

COOOL!

On Thu, Oct 18, 2012 at 11:41 AM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> Hi again!
>
> Sorry about the barrage of e-mails, but I'm guessing some of you with
> A-112s would like to know where things are at...
>
> So I got a reply from Nico, who made the software that originally sparked
> this discussion, the
> http://www.rampe-d.de/Software/A-112_Sample_Dump_Tool.html program. It
> turns out he got very close to finishing it, then his hard drive died and
> he had to revert to an old, buggy version retrieved from a backup. He's too
> busy with work to finish it right now, but he's happy to upload the old
> version and also the source code to the Max patch, so I believe he's doing
> that around about now.
>
> It turns out he'd also seen the other A-112 software mentioned earlier,
> that someone else was working on this year, and didn't want to contribute
> something redundant. I, on the other hand, think that having too many
> programs to choose from is a better problem than not having a single one
> that can easily be used, so let's try a little redundancy! :)
>
> All the best,
> Zo�.
>  
>


[Non-text portions of this message have been removed]

Hi again!

So I've just heard back from Ernst, who was kind enough to beta test my script for me.  Apparently the tuning's way off, so you currently need to set the knob to about 8 or 9, but otherwise it's pretty much working.  (This surprised me too, for a first attempt!)  So in order to rapidly fix this, I think I'll need to wait until I've got my own A-112 module to play with.  In the meantime, rather than leave everyone with nothing, I figure you'd probably prefer to have something you can play with right now, even if it's currently imperfect.

Here's the script as it is so far: http://bytenoise.co.uk/makedoepfer.py.txt  I'll fix the tuning issue and add proper comments and documentation in a few weeks or so, hopefully.  The script's part of a larger open source project of mine that lets you change the bit depth, sample rate and so on of wave files, split up large wave files into lots of little single hits, stuff like that.  So anyone with a decent mic, an A-112, and lots of free time, a fun weekend is assured! :D

Anyway, for any programmers on this mailing list, you can fork the project from https://github.com/ZoeB/wave-tools and play around with it, fix things and add features as much as you like.

For anyone with an A-112 who wants to send some 8-bit .wav files to it RIGHT NOW, here's a quick step-by-step guide:

* Download http://bytenoise.co.uk/makedoepfer.py.txt
* Rename it makedoepfer.py
* Install Python 3 from http://www.python.org/download/releases/3.0.1/
* Go to the command line, into the directory with makedoepfer.py and your .wav file
* Type in "python3 makedoepfer.py [whatever].wav"

You should have a new .syx file that you can plop into your sysex sending tool of choice, such as C6 or any of the others.

This should work on Windows, OS X, Linux, BSD, and so on.  Let me know of any bugs and I'll try to fix them as soon as I can.

Enjoy!
Zoë.

Actually on the A112 there is no standard position for the tuning knob. SO
it's not really off.
I am already very happy with the first results.


On Fri, Oct 19, 2012 at 4:23 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> Hi again!
>
> So I've just heard back from Ernst, who was kind enough to beta test my
> script for me. Apparently the tuning's way off, so you currently need to
> set the knob to about 8 or 9, but otherwise it's pretty much working. (This
> surprised me too, for a first attempt!) So in order to rapidly fix this, I
> think I'll need to wait until I've got my own A-112 module to play with. In
> the meantime, rather than leave everyone with nothing, I figure you'd
> probably prefer to have something you can play with right now, even if it's
> currently imperfect.
>
> Here's the script as it is so far:
> http://bytenoise.co.uk/makedoepfer.py.txt I'll fix the tuning issue and
> add proper comments and documentation in a few weeks or so, hopefully. The
> script's part of a larger open source project of mine that lets you change
> the bit depth, sample rate and so on of wave files, split up large wave
> files into lots of little single hits, stuff like that. So anyone with a
> decent mic, an A-112, and lots of free time, a fun weekend is assured! :D
>
> Anyway, for any programmers on this mailing list, you can fork the project
> from https://github.com/ZoeB/wave-tools and play around with it, fix
> things and add features as much as you like.
>
> For anyone with an A-112 who wants to send some 8-bit .wav files to it
> RIGHT NOW, here's a quick step-by-step guide:
>
> * Download http://bytenoise.co.uk/makedoepfer.py.txt
> * Rename it makedoepfer.py
> * Install Python 3 from http://www.python.org/download/releases/3.0.1/
> * Go to the command line, into the directory with makedoepfer.py and your
> .wav file
> * Type in "python3 makedoepfer.py [whatever].wav"
>
> You should have a new .syx file that you can plop into your sysex sending
> tool of choice, such as C6 or any of the others.
>
> This should work on Windows, OS X, Linux, BSD, and so on. Let me know of
> any bugs and I'll try to fix them as soon as I can.
>
> Enjoy!
> Zo�.
>  
>


[Non-text portions of this message have been removed]

I will go out and try your Python method! Thanks so much Zo�!

Greetings,

Ernst

On Fri, Oct 19, 2012 at 4:26 PM, achtung_999 <
heinrich.himmelwasser@gmail.com> wrote:

> Actually on the A112 there is no standard position for the tuning knob. SO
> it's not really off.
> I am already very happy with the first results.
>
>
> On Fri, Oct 19, 2012 at 4:23 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:
>
>> **
>>
>>
>> Hi again!
>>
>> So I've just heard back from Ernst, who was kind enough to beta test my
>> script for me. Apparently the tuning's way off, so you currently need to
>> set the knob to about 8 or 9, but otherwise it's pretty much working. (This
>> surprised me too, for a first attempt!) So in order to rapidly fix this, I
>> think I'll need to wait until I've got my own A-112 module to play with. In
>> the meantime, rather than leave everyone with nothing, I figure you'd
>> probably prefer to have something you can play with right now, even if it's
>> currently imperfect.
>>
>> Here's the script as it is so far:
>> http://bytenoise.co.uk/makedoepfer.py.txt I'll fix the tuning issue and
>> add proper comments and documentation in a few weeks or so, hopefully. The
>> script's part of a larger open source project of mine that lets you change
>> the bit depth, sample rate and so on of wave files, split up large wave
>> files into lots of little single hits, stuff like that. So anyone with a
>> decent mic, an A-112, and lots of free time, a fun weekend is assured! :D
>>
>> Anyway, for any programmers on this mailing list, you can fork the
>> project from https://github.com/ZoeB/wave-tools and play around with it,
>> fix things and add features as much as you like.
>>
>> For anyone with an A-112 who wants to send some 8-bit .wav files to it
>> RIGHT NOW, here's a quick step-by-step guide:
>>
>> * Download http://bytenoise.co.uk/makedoepfer.py.txt
>> * Rename it makedoepfer.py
>> * Install Python 3 from http://www.python.org/download/releases/3.0.1/
>> * Go to the command line, into the directory with makedoepfer.py and your
>> .wav file
>> * Type in "python3 makedoepfer.py [whatever].wav"
>>
>> You should have a new .syx file that you can plop into your sysex sending
>> tool of choice, such as C6 or any of the others.
>>
>> This should work on Windows, OS X, Linux, BSD, and so on. Let me know of
>> any bugs and I'll try to fix them as soon as I can.
>>
>> Enjoy!
>> Zo�.
>>  
>>
>
>


[Non-text portions of this message have been removed]

You're quite welcome!  It was a fun challenge, and it's nice to be helpful.  Remember my partner and I are building a digital step sequencer with CV/gate/accent out anyway. :D  This isn't too far removed from that sort of thing, in terms of the knowledge required to make it.  The most esoteric part is probably just the bitshifting.

All the best,
Zoë.

Sounds great! Will try it tonight.

Lars Bröndum, composer

email: Lars_Brondum@tele2.se
web: http://brondum.se/MuArk/Lars_Brondum.html

On 19 okt 2012, at 16:40, Zoë Blade <zoe@bytenoise.co.uk> wrote:

> You're quite welcome! It was a fun challenge, and it's nice to be helpful. Remember my partner and I are building a digital step sequencer with CV/gate/accent out anyway. :D This isn't too far removed from that sort of thing, in terms of the knowledge required to make it. The most esoteric part is probably just the bitshifting.
> 
> All the best,
> Zoë.
> 
> 


[Non-text portions of this message have been removed]

Hi!

I am trying your script for the A-114.  Sorry for a dumb question... but how do you write the command line in python to point to the makedopfer.py file?
What is the syntax?  Should it be like this if I put the wav file "Test.wav" in a folder named "A-114" (in the Applications folder) :  /Applications/A-114/"python3 makedoepfer.py.Test.wav"

Is this correct?


Thanks,

Lars




________________________________
 Från: Zoë Blade <zoe@bytenoise.co.uk>
Till: Doepfer_a100@yahoogroups.com 
Skickat: fredag, 19 oktober 2012 16:23
Ämne: Re: [Doepfer_a100] A-112 Sample Dump Tool
 

  
Hi again!

So I've just heard back from Ernst, who was kind enough to beta test my script for me.  Apparently the tuning's way off, so you currently need to set the knob to about 8 or 9, but otherwise it's pretty much working.  (This surprised me too, for a first attempt!)  So in order to rapidly fix this, I think I'll need to wait until I've got my own A-112 module to play with.  In the meantime, rather than leave everyone with nothing, I figure you'd probably prefer to have something you can play with right now, even if it's currently imperfect.

Here's the script as it is so far: http://bytenoise.co.uk/makedoepfer.py.txt I'll fix the tuning issue and add proper comments and documentation in a few weeks or so, hopefully.  The script's part of a larger open source project of mine that lets you change the bit depth, sample rate and so on of wave files, split up large wave files into lots of little single hits, stuff like that.  So anyone with a decent mic, an A-112, and lots of free time, a fun weekend is assured! :D

Anyway, for any programmers on this mailing list, you can fork the project from https://github.com/ZoeB/wave-tools and play around with it, fix things and add features as much as you like.

For anyone with an A-112 who wants to send some 8-bit .wav files to it RIGHT NOW, here's a quick step-by-step guide:

* Download http://bytenoise.co.uk/makedoepfer.py.txt
* Rename it makedoepfer.py
* Install Python 3 from http://www.python.org/download/releases/3.0.1/
* Go to the command line, into the directory with makedoepfer.py and your .wav file
* Type in "python3 makedoepfer.py [whatever].wav"

You should have a new .syx file that you can plop into your sysex sending tool of choice, such as C6 or any of the others.

This should work on Windows, OS X, Linux, BSD, and so on.  Let me know of any bugs and I'll try to fix them as soon as I can.

Enjoy!
Zoë.
 

[Non-text portions of this message have been removed]

Let me reply on-list, as you're not the first to ask, so it's likely several people want to know the answer...

Oh, that *was* on-list, hehe... OK...

You shouldn't need to open Python by double clicking on it.  You need to invoke the script / Python via your command line.  How that works depends on which operating system you're using. You'll probably need to read a quick guide about changing directories in the command prompt.  "cd .." takes you up a directory; "cd [directory name]" takes you into another one.  Navigate to where the .wav files and script are, then type in "python3 makedoepfer.py [whatever].wav" and it should make the new .syx file.

For example, if you're in OS X, go to Applications > Utilities > Terminal.  If you're in Windows, go to Start > Run then type in "cmd".  Either way, this should bring up a command prompt.

Say you've made a folder on your desktop called "a112", with my script and your waveform in it.  In OS X, you type:

cd Desktop
cd a112
python3 makedoepfer.py mywavefile.wav (or whatever your wave file happens to be called)

I'm not sure how to get to the desktop from the command line in Windows, but it should be something reasonably similar.  You can usually type in just the first few letters of a filename and press tab to make your life easier.

I'll have to look into whether I can make my script into a standalone program at some point, that you could simply drag and drop .wav files onto, but that really would take a while, and is probably best done by someone more knowledgeable in that area.  The good news is that because the program's open source, any other programmers can just dive in and add such features.

All the best,
Zoë.

Ah!  It works great.

Thanks a million Zo�! 

Lars


On Oct 20, 2012, at 5:51 PM, Zo� Blade wrote:

> Oh, that *was* on-list, hehe... OK...
> 
> You shouldn't need to open Python by double clicking on it. You need to invoke the script / Python via your command line. How that works depends on which operating system you're using. You'll probably need to read a quick guide about changing directories in the command prompt. "cd .." takes you up a directory; "cd [directory name]" takes you into another one. Navigate to where the .wav files and script are, then type in "python3 makedoepfer.py [whatever].wav" and it should make the new .syx file.
> 
> For example, if you're in OS X, go to Applications > Utilities > Terminal. If you're in Windows, go to Start > Run then type in "cmd". Either way, this should bring up a command prompt.
> 
> Say you've made a folder on your desktop called "a112", with my script and your waveform in it. In OS X, you type:
> 
> cd Desktop
> cd a112
> python3 makedoepfer.py mywavefile.wav (or whatever your wave file happens to be called)
> 
> I'm not sure how to get to the desktop from the command line in Windows, but it should be something reasonably similar. You can usually type in just the first few letters of a filename and press tab to make your life easier.
> 
> I'll have to look into whether I can make my script into a standalone program at some point, that you could simply drag and drop .wav files onto, but that really would take a while, and is probably best done by someone more knowledgeable in that area. The good news is that because the program's open source, any other programmers can just dive in and add such features.
> 
> All the best,
> Zo�.
> 
> 



[Non-text portions of this message have been removed]

Excellent, good to hear!

I'll make some improvements soon, probably starting with giving people the choice of which of the sampler's two memory pages to write to.

Yeah, it only upploads to the 1st memory location. Great if you add the 2nd location. I must say the sampler sounds so much better when upploading the sound compared to sampling with the a112. Tried last night to use it with some randomness of wogglebug and makenoise Echelon with a korgasmatron filter...nice!. Also tried the a112 with a vocoder which worked surprisingly good.  The lo-fi sounds works good with a vocoder.

Thanks,

Lars Bröndum, composer

email: Lars_Brondum@tele2.se
web: http://brondum.se/MuArk/Lars_Brondum.html

On 21 okt 2012, at 01:52, Zoë Blade <zoe@bytenoise.co.uk> wrote:

> Excellent, good to hear!
> 
> I'll make some improvements soon, probably starting with giving people the choice of which of the sampler's two memory pages to write to.
> 
> 


[Non-text portions of this message have been removed]

I can't seem to get it working. Seems like I haven't installed Python 3
correctly?
Terminal comes with this prompt everytime: -bash: python3: command not found




On Sun, Oct 21, 2012 at 1:21 PM, Lars Br�ndum <lahebr2000@yahoo.se> wrote:

> **
>
>
> Yeah, it only upploads to the 1st memory location. Great if you add the
> 2nd location. I must say the sampler sounds so much better when upploading
> the sound compared to sampling with the a112. Tried last night to use it
> with some randomness of wogglebug and makenoise Echelon with a korgasmatron
> filter...nice!. Also tried the a112 with a vocoder which worked
> surprisingly good. The lo-fi sounds works good with a vocoder.
>
> Thanks,
>
>
> Lars Br�ndum, composer
>
> email: Lars_Brondum@tele2.se
> web: http://brondum.se/MuArk/Lars_Brondum.html
>
> On 21 okt 2012, at 01:52, Zo� Blade <zoe@bytenoise.co.uk> wrote:
>
> > Excellent, good to hear!
> >
> > I'll make some improvements soon, probably starting with giving people
> the choice of which of the sampler's two memory pages to write to.
> >
> >
>
> [Non-text portions of this message have been removed]
>
>  
>


[Non-text portions of this message have been removed]

> I can't seem to get it working. Seems like I haven't installed Python 3
> correctly?
> Terminal comes with this prompt everytime: -bash: python3: command not found

Judging by the error message, yes, you're typing in the right command but it can't find Python 3.  You could try replacing python3 with /usr/local/bin/python3 or /usr/bin/python3 and see if either of them work.  Otherwise, I'd try installing Python 3 again, and make sure it includes the command line version. (I forget if it's a separate option, sorry.)

Jup I got it... Python 3 does not install Unix command line tools in the
standard install!
You need to do a custom install and choose to install those.
Next to that:
python instead of python3 is the proper command on my machine.

So I typed: python makedoepfer.py bitexloop.wav

It works like a charm!

Can you tell us what the max sample time is? It seems those sysex files
don't exceed 73k.

Thanks

Ernst






On Sun, Oct 21, 2012 at 2:22 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> > I can't seem to get it working. Seems like I haven't installed Python 3
> > correctly?
> > Terminal comes with this prompt everytime: -bash: python3: command not
> found
>
> Judging by the error message, yes, you're typing in the right command but
> it can't find Python 3. You could try replacing python3 with
> /usr/local/bin/python3 or /usr/bin/python3 and see if either of them work.
> Otherwise, I'd try installing Python 3 again, and make sure it includes the
> command line version. (I forget if it's a separate option, sorry.)
>
>  
>


[Non-text portions of this message have been removed]

Now that it works, I have been experimenting a bit...

By changing the sample rate of the file you convert to sysex you can use
more time.
Samples at 16khz end up on the A112 with having the tuning knob set just
slightly under 6.
Zo�'s samples were at 44.1khz and ended up with the tuning knob between 8
and 9.
It would be possible I guess to calculate sample time from sample rate
since the sysexfiles have a fixed size of 73kb.
This would be a nice feature to implement I think.

Grtz

Ernst











On Sun, Oct 21, 2012 at 3:18 PM, achtung_999 <
heinrich.himmelwasser@gmail.com> wrote:

> Jup I got it... Python 3 does not install Unix command line tools in the
> standard install!
> You need to do a custom install and choose to install those.
> Next to that:
> python instead of python3 is the proper command on my machine.
>
> So I typed: python makedoepfer.py bitexloop.wav
>
> It works like a charm!
>
> Can you tell us what the max sample time is? It seems those sysex files
> don't exceed 73k.
>
> Thanks
>
> Ernst
>
>
>
>
>
>
> On Sun, Oct 21, 2012 at 2:22 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:
>
>> **
>>
>>
>> > I can't seem to get it working. Seems like I haven't installed Python 3
>> > correctly?
>> > Terminal comes with this prompt everytime: -bash: python3: command not
>> found
>>
>> Judging by the error message, yes, you're typing in the right command but
>> it can't find Python 3. You could try replacing python3 with
>> /usr/local/bin/python3 or /usr/bin/python3 and see if either of them work.
>> Otherwise, I'd try installing Python 3 again, and make sure it includes the
>> command line version. (I forget if it's a separate option, sorry.)
>>
>>  
>>
>
>


[Non-text portions of this message have been removed]

btw. if you are converting files from 24 or 16 bit to 8 bit on your
computer, don't forget to use software that has a dithering function!!
I have been using Apple's Soundtracks Pro for this because (unfortunately)
my favourite wave editor, Amadeus Pro does not feature this function..




On Sun, Oct 21, 2012 at 4:13 PM, achtung_999 <
heinrich.himmelwasser@gmail.com> wrote:

> Now that it works, I have been experimenting a bit...
>
> By changing the sample rate of the file you convert to sysex you can use
> more time.
> Samples at 16khz end up on the A112 with having the tuning knob set just
> slightly under 6.
> Zo�'s samples were at 44.1khz and ended up with the tuning knob between 8
> and 9.
> It would be possible I guess to calculate sample time from sample rate
> since the sysexfiles have a fixed size of 73kb.
> This would be a nice feature to implement I think.
>
> Grtz
>
> Ernst
>
>
>
>
>
>
>
>
>
>
>
> On Sun, Oct 21, 2012 at 3:18 PM, achtung_999 <
> heinrich.himmelwasser@gmail.com> wrote:
>
>> Jup I got it... Python 3 does not install Unix command line tools in the
>> standard install!
>> You need to do a custom install and choose to install those.
>> Next to that:
>> python instead of python3 is the proper command on my machine.
>>
>> So I typed: python makedoepfer.py bitexloop.wav
>>
>> It works like a charm!
>>
>> Can you tell us what the max sample time is? It seems those sysex files
>> don't exceed 73k.
>>
>> Thanks
>>
>> Ernst
>>
>>
>>
>>
>>
>>
>> On Sun, Oct 21, 2012 at 2:22 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:
>>
>>> **
>>>
>>>
>>> > I can't seem to get it working. Seems like I haven't installed Python 3
>>> > correctly?
>>> > Terminal comes with this prompt everytime: -bash: python3: command not
>>> found
>>>
>>> Judging by the error message, yes, you're typing in the right command
>>> but it can't find Python 3. You could try replacing python3 with
>>> /usr/local/bin/python3 or /usr/bin/python3 and see if either of them work.
>>> Otherwise, I'd try installing Python 3 again, and make sure it includes the
>>> command line version. (I forget if it's a separate option, sorry.)
>>>
>>>  
>>>
>>
>>
>


[Non-text portions of this message have been removed]

Yes, you're exactly right, the A-112 has a fixed amount of memory, and a variable sample rate, so the more bytes you use up per second, the less seconds it can store.  It can store 65536 (2^16) samples in each of the two pages of memory.  The reason the files are slightly bigger is because you can't simply copy all eight bits of each byte at a time, you have to copy across the first seven bits of each byte first, then all the leftover bits later on.  This is because MIDI requires all data to be 7-bit, whereas the A-112 is an 8-bit sampler.

That reminds me, the other thing I'm not sure about yet is the zero-padding for samples that are shorter than 64kb.  Once I get my hands on an A-112, I'll verify which number I should be sending for the zero-padding.  If it's currently wrong, then the silence between when the sample finishes and when it stops playing won't have the speaker centred correctly, and so it may click at the end.

By the way, if you type in just "python" instead of "python3", then it'll probably invoke Python 2, which OS X usually comes with pre-installed.  That may give you errors to do with my Python 3 specific code, but certainly nothing to worry about.

Oh, and regarding the tuning: one of the things that gets stored in the .syx file is the sample rate, which insinuates the A-112 should compensate for this in order to make, say, the 5 position on the tune knob always the position for the original sample speed.  As it's not doing this, I can only assume I'm calculating the frequency incorrectly.  (You can't just tell the A-112 "this sample is recorded at a 44,100Hz sample rate", you have to modify that number somehow that seems to involve the number 200, so I'll use trial and error to figure this out once I have an A-112.  Then hopefully 5 should be the correct tuning for all samples.)

On that note, is "nSek" German for milliseconds?  I could really do with a translation of this if anyone would be so kind: "sondern Wert für Rückwärtszähler mit 200 nSek. Zykluszeit."

Thanks!
Zoë.

Thanks for the elaboration on this! I'll have to try and reinstall python3
again maybe. For now it works great!
nSek more seems like nanoseconds to me. Then again I am Dutch... My German
is not 100%
Zykluszeit = cycle time.





On Sun, Oct 21, 2012 at 5:09 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> Yes, you're exactly right, the A-112 has a fixed amount of memory, and a
> variable sample rate, so the more bytes you use up per second, the less
> seconds it can store. It can store 65536 (2^16) samples in each of the two
> pages of memory. The reason the files are slightly bigger is because you
> can't simply copy all eight bits of each byte at a time, you have to copy
> across the first seven bits of each byte first, then all the leftover bits
> later on. This is because MIDI requires all data to be 7-bit, whereas the
> A-112 is an 8-bit sampler.
>
> That reminds me, the other thing I'm not sure about yet is the
> zero-padding for samples that are shorter than 64kb. Once I get my hands on
> an A-112, I'll verify which number I should be sending for the
> zero-padding. If it's currently wrong, then the silence between when the
> sample finishes and when it stops playing won't have the speaker centred
> correctly, and so it may click at the end.
>
> By the way, if you type in just "python" instead of "python3", then it'll
> probably invoke Python 2, which OS X usually comes with pre-installed. That
> may give you errors to do with my Python 3 specific code, but certainly
> nothing to worry about.
>
> Oh, and regarding the tuning: one of the things that gets stored in the
> .syx file is the sample rate, which insinuates the A-112 should compensate
> for this in order to make, say, the 5 position on the tune knob always the
> position for the original sample speed. As it's not doing this, I can only
> assume I'm calculating the frequency incorrectly. (You can't just tell the
> A-112 "this sample is recorded at a 44,100Hz sample rate", you have to
> modify that number somehow that seems to involve the number 200, so I'll
> use trial and error to figure this out once I have an A-112. Then hopefully
> 5 should be the correct tuning for all samples.)
>
> On that note, is "nSek" German for milliseconds? I could really do with a
> translation of this if anyone would be so kind: "sondern Wert f�r
> R�ckw�rtsz�hler mit 200 nSek. Zykluszeit."
>
> Thanks!
> Zo�.
>  
>


[Non-text portions of this message have been removed]

okay the python thing has been solved now..
(following is assuming you have a folder called a112 in your desktop folder
which contains Zo�'s script makedoepfer.py and the wavfile you'd like to
convert).

After installing Python 3 you go to the Terminal.
Type: cd desktop
type: cd a112
type: python3.0 makedoepfer.py youwavfile.wav

The 3.0 solved the issue!

Sorry for the barrage of mails but I'd like to see more of you people enjoy
this fine script :D

Ernst







On Sun, Oct 21, 2012 at 5:09 PM, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> Yes, you're exactly right, the A-112 has a fixed amount of memory, and a
> variable sample rate, so the more bytes you use up per second, the less
> seconds it can store. It can store 65536 (2^16) samples in each of the two
> pages of memory. The reason the files are slightly bigger is because you
> can't simply copy all eight bits of each byte at a time, you have to copy
> across the first seven bits of each byte first, then all the leftover bits
> later on. This is because MIDI requires all data to be 7-bit, whereas the
> A-112 is an 8-bit sampler.
>
> That reminds me, the other thing I'm not sure about yet is the
> zero-padding for samples that are shorter than 64kb. Once I get my hands on
> an A-112, I'll verify which number I should be sending for the
> zero-padding. If it's currently wrong, then the silence between when the
> sample finishes and when it stops playing won't have the speaker centred
> correctly, and so it may click at the end.
>
> By the way, if you type in just "python" instead of "python3", then it'll
> probably invoke Python 2, which OS X usually comes with pre-installed. That
> may give you errors to do with my Python 3 specific code, but certainly
> nothing to worry about.
>
> Oh, and regarding the tuning: one of the things that gets stored in the
> .syx file is the sample rate, which insinuates the A-112 should compensate
> for this in order to make, say, the 5 position on the tune knob always the
> position for the original sample speed. As it's not doing this, I can only
> assume I'm calculating the frequency incorrectly. (You can't just tell the
> A-112 "this sample is recorded at a 44,100Hz sample rate", you have to
> modify that number somehow that seems to involve the number 200, so I'll
> use trial and error to figure this out once I have an A-112. Then hopefully
> 5 should be the correct tuning for all samples.)
>
> On that note, is "nSek" German for milliseconds? I could really do with a
> translation of this if anyone would be so kind: "sondern Wert f�r
> R�ckw�rtsz�hler mit 200 nSek. Zykluszeit."
>
> Thanks!
> Zo�.
>  
>


[Non-text portions of this message have been removed]

big congrats and many thanks to Zoe, for helping the Doepfer users community!

 
Bakis Sirros 


________________________________

 From: achtung_999 <heinrich.himmelwasser@gmail.com>
To: Doepfer_a100@yahoogroups.com 
Sent: Sunday, October 21, 2012 7:00 PM
Subject: Re: [Doepfer_a100] A-112 Sample Dump Tool
 
okay the python thing has been solved now..
(following is assuming you have a folder called a112 in your desktop folder
which contains Zoë's script makedoepfer.py and the wavfile you'd like to
convert).

After installing Python 3 you go to the Terminal.
Type: cd desktop
type: cd a112
type: python3.0 makedoepfer.py youwavfile.wav

The 3.0 solved the issue!

Sorry for the barrage of mails but I'd like to see more of you people enjoy
this fine script :D

Ernst







On Sun, Oct 21, 2012 at 5:09 PM, Zoë Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> Yes, you're exactly right, the A-112 has a fixed amount of memory, and a
> variable sample rate, so the more bytes you use up per second, the less
> seconds it can store. It can store 65536 (2^16) samples in each of the two
> pages of memory. The reason the files are slightly bigger is because you
> can't simply copy all eight bits of each byte at a time, you have to copy
> across the first seven bits of each byte first, then all the leftover bits
> later on. This is because MIDI requires all data to be 7-bit, whereas the
> A-112 is an 8-bit sampler.
>
> That reminds me, the other thing I'm not sure about yet is the
> zero-padding for samples that are shorter than 64kb. Once I get my hands on
> an A-112, I'll verify which number I should be sending for the
> zero-padding. If it's currently wrong, then the silence between when the
> sample finishes and when it stops playing won't have the speaker centred
> correctly, and so it may click at the end.
>
> By the way, if you type in just "python" instead of "python3", then it'll
> probably invoke Python 2, which OS X usually comes with pre-installed. That
> may give you errors to do with my Python 3 specific code, but certainly
> nothing to worry about.
>
> Oh, and regarding the tuning: one of the things that gets stored in the
> .syx file is the sample rate, which insinuates the A-112 should compensate
> for this in order to make, say, the 5 position on the tune knob always the
> position for the original sample speed. As it's not doing this, I can only
> assume I'm calculating the frequency incorrectly. (You can't just tell the
> A-112 "this sample is recorded at a 44,100Hz sample rate", you have to
> modify that number somehow that seems to involve the number 200, so I'll
> use trial and error to figure this out once I have an A-112. Then hopefully
> 5 should be the correct tuning for all samples.)
>
> On that note, is "nSek" German for milliseconds? I could really do with a
> translation of this if anyone would be so kind: "sondern Wert für
> Rückwärtszähler mit 200 nSek. Zykluszeit."
>
> Thanks!
> Zoë.
>  
>


[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links



[Non-text portions of this message have been removed]

Ernst said:

> okay the python thing has been solved now..

<Snip>

> type: python3.0 makedoepfer.py youwavfile.wav
> 
> The 3.0 solved the issue!

Ah, that would make sense.  Thanks, I didn't know it sometimes required the full version number!

Bakis said:

> big congrats and many thanks to Zoe, for helping the Doepfer users community!

Thank you very much, I'm glad I could help! :)

If you grab a fresh copy of my script, you should now have the option to write to the A-112's second bank using --bank=2

All the best,
Zoë.

Super!  Is it the same url?

http://www.rampe-d.de/Software/A-112_Sample_Dump_Tool.html

Thanx,

Lars Brondum

22 okt 2012 kl. 02:09 skrev Zoë Blade <zoe@bytenoise.co.uk>:

> If you grab a fresh copy of my script, you should now have the option to write to the A-112's second bank using --bank=2
> 
> All the best,
> Zoë.
> 
> 


[Non-text portions of this message have been removed]

Sorry, I meant this one: http://bytenoise.co.uk/makedoepfer.py.txt

Same Url?

Lars Brondum

22 okt 2012 kl. 02:09 skrev Zoë Blade <zoe@bytenoise.co.uk>:

> If you grab a fresh copy of my script, you should now have the option to write to the A-112's second bank using --bank=2
> 
> All the best,
> Zoë.
> 
> 


[Non-text portions of this message have been removed]

> Sorry, I meant this one: http://bytenoise.co.uk/makedoepfer.py.txt
> 
> Same Url?

Yes, it's that one, same URL.  And I've just fixed the padding with silence issue now too, so you shouldn't get that click at the end anymore.

I believe I've now fixed a pitch related bug too.  I don't know if there are other pitch related bugs too or not.  Do samples now need less fine tuning with the tune knob?

Thanks,
Zoë.

Am 21.10.2012 17:09, schrieb Zoë Blade:
> On that note, is "nSek" German for milliseconds?  I could really do
> with a translation of this if anyone would be so kind: "sondern Wert
> für Rückwärtszähler mit 200 nSek. Zykluszeit."

nSek should be read as nanoseconds in German too.

 > "sondern Wert für Rückwärtszähler mit 200 nSek. Zykluszeit."
A translation of an incomplete phrase is difficult, because to 
understand some grammar aspects I would need the complete context.

The direct translation would be:
"...but [ the | a ] value for backward counter[s] with 200 nanoseconds 
cycle time."
Optional grammar variations in brackets. Can you send me the complete text?

Florian
-- 
http://fa.utfs.org/

>> "sondern Wert für Rückwärtszähler mit 200 nSek. Zykluszeit."

> A translation of an incomplete phrase is difficult, because to 
> understand some grammar aspects I would need the complete context.
> 
> The direct translation would be:
> "...but [ the | a ] value for backward counter[s] with 200 nanoseconds 
> cycle time."
> Optional grammar variations in brackets. Can you send me the complete text?

The full phrase is "Tune-Wert nicht direkt Samplingfrequenz, sondern Wert für Rückwärtszähler mit 200 nSek. Zykluszeit." ...but I managed to work out that the first bit is something along the lines of "The tuning value is not the direct sample frequency..."

I gather I have to take the original sample frequency and then perform a calculation on it, changing it from the number of samples per second to something else... maybe the number of 200 nanosecond CPU cycles to wait before moving on from each sample to the next?

Thanks,
Zoë.

If there's a clock cycle every 200 nanoseconds, that's 5000000 clock cycles a second (in other words, it's running at 5mHz)...  So I should probably divide that by the sample frequency, so it knows how many cycles to pause for in between updating the output value, instead of dividing the sample frequency by 5, which probably does nothing useful at all.

If someone could grab a fresh copy of my script and tell me if the tuning's spot on or even worse now, that'd be really useful! :D

Thanks,
Zoë.

Unfortunately no time at the moment! Tomorrow night!
Op 22 okt. 2012 19:03 schreef "Zo� Blade" <zoe@bytenoise.co.uk> het
volgende:

> **
>
>
> If there's a clock cycle every 200 nanoseconds, that's 5000000 clock
> cycles a second (in other words, it's running at 5mHz)... So I should
> probably divide that by the sample frequency, so it knows how many cycles
> to pause for in between updating the output value, instead of dividing the
> sample frequency by 5, which probably does nothing useful at all.
>
> If someone could grab a fresh copy of my script and tell me if the
> tuning's spot on or even worse now, that'd be really useful! :D
>
> Thanks,
> Zo�.
>  
>


[Non-text portions of this message have been removed]

Hello

I've been following this thread with interest and was looking forward to
getting more out of my a112. I've downloaded and installed Python3, put the
script into a folder with .wav files but when I use Windows command I get
the message - python3 is not recognized as an internal or external command,
operable program or batch file.

Any ideas with what I'm doing wrong?

Ed

On 22 October 2012 18:20, achtung_999 <heinrich.himmelwasser@gmail.com>wrote:

> Unfortunately no time at the moment! Tomorrow night!
> Op 22 okt. 2012 19:03 schreef "Zoė Blade" <zoe@bytenoise.co.uk> het
> volgende:
>
> > **
> >
> >
> > If there's a clock cycle every 200 nanoseconds, that's 5000000 clock
> > cycles a second (in other words, it's running at 5mHz)... So I should
> > probably divide that by the sample frequency, so it knows how many cycles
> > to pause for in between updating the output value, instead of dividing
> the
> > sample frequency by 5, which probably does nothing useful at all.
> >
> > If someone could grab a fresh copy of my script and tell me if the
> > tuning's spot on or even worse now, that'd be really useful! :D
> >
> > Thanks,
> > Zoė.
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]

> ...I get
> the message - python3 is not recognized as an internal or external command,
> operable program or batch file.
> 
> Any ideas with what I'm doing wrong?

Do you have any more luck with typing "python3.0"?  When you installed Python, was there an option you could select that said something about installing the command line tools, that was a bit too subtle to notice the first time?  Those are the main previous issues I'm aware of.

I tried "python3.0" with no luck but didn't change any options when
installing...I will try again. Thankyou.

On 22 October 2012 19:04, Zo� Blade <zoe@bytenoise.co.uk> wrote:

> **
>
>
> > ...I get
>
> > the message - python3 is not recognized as an internal or external
> command,
> > operable program or batch file.
> >
> > Any ideas with what I'm doing wrong?
>
> Do you have any more luck with typing "python3.0"? When you installed
> Python, was there an option you could select that said something about
> installing the command line tools, that was a bit too subtle to notice the
> first time? Those are the main previous issues I'm aware of.
>
>  
>


[Non-text portions of this message have been removed]

Sorry, I really should slow down these A-112 related posts...

I just got a reply back from tybamm of http://www.muffwiggler.com/forum/viewtopic.php?t=50154 fame.  Salient points:

> Of course, Diter can put it on his website, no matter, I'm happy to contribute ! 
> 
> And, another important new : I'm currently recoding the Super-miniwave Generator in Java, so it will be able to run on both windows, mac and linux ^^ I'm hardly working on this these days, it's coming soon...

Other than that, I don't know any more than anybody else, but it sounds promising!

It seemed to be a problem with Windows Vista. You need to do some extra
stuff to make Vista recognise Python after you install it. For anyone
interested look here:

http://www.neuralwiki.org/index.php?title=Guide_to_installing_Python_in_Windows_Vista

All working now.



On 22 October 2012 19:48, edward tomlin <edwardtomlin0@googlemail.com>wrote:

> I tried "python3.0" with no luck but didn't change any options when
> installing...I will try again. Thankyou.
>
>
> On 22 October 2012 19:04, Zo� Blade <zoe@bytenoise.co.uk> wrote:
>
>> **
>>
>>
>> > ...I get
>>
>> > the message - python3 is not recognized as an internal or external
>> command,
>> > operable program or batch file.
>> >
>> > Any ideas with what I'm doing wrong?
>>
>> Do you have any more luck with typing "python3.0"? When you installed
>> Python, was there an option you could select that said something about
>> installing the command line tools, that was a bit too subtle to notice the
>> first time? Those are the main previous issues I'm aware of.
>>
>>  
>>
>
>


[Non-text portions of this message have been removed]

Came home late and still had to check anyway...yup
Some short time with your script I downloaded this afternoon at 14.40 CET
(13.40 UK time).
Audio seems to be coming out around a tuning pot position between 5 and 8.
So it seems adaptive but I don't see too much difference from the one
before.
I used 8 bit samples with different sample frequencies first one coming out
at around 5.5, which was a 8 bit 16kHz sample.
Second one came out just under pot position 8. That was an 8 bit sample
with a 44.1kHz sample rate.
Mind you this was all done at a quick pace... after midnight.

greetings,

Ernst






On Mon, Oct 22, 2012 at 10:35 PM, edward tomlin <
edwardtomlin0@googlemail.com> wrote:

> It seemed to be a problem with Windows Vista. You need to do some extra
> stuff to make Vista recognise Python after you install it. For anyone
> interested look here:
>
>
> http://www.neuralwiki.org/index.php?title=Guide_to_installing_Python_in_Windows_Vista
>
> All working now.
>
>
>
> On 22 October 2012 19:48, edward tomlin <edwardtomlin0@googlemail.com
> >wrote:
>
> > I tried "python3.0" with no luck but didn't change any options when
> > installing...I will try again. Thankyou.
> >
> >
> > On 22 October 2012 19:04, Zoë Blade <zoe@bytenoise.co.uk> wrote:
> >
> >> **
> >>
> >>
> >> > ...I get
> >>
> >> > the message - python3 is not recognized as an internal or external
> >> command,
> >> > operable program or batch file.
> >> >
> >> > Any ideas with what I'm doing wrong?
> >>
> >> Do you have any more luck with typing "python3.0"? When you installed
> >> Python, was there an option you could select that said something about
> >> installing the command line tools, that was a bit too subtle to notice
> the
> >> first time? Those are the main previous issues I'm aware of.
> >>
> >>
> >>
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]

The "A-112 sample dump" application by Nico is really nice!   But I also like Zoe's script because it turns the sample into a sysex file - that way one can use it with other MIDI sequencers, librarians etc.  I also tried the .syx file on the ipad using the app "Midi Tool Box" - it works great.

Thanks again for the good work Zoe!

/Lars


On Oct 22, 2012, at 10:20 PM, Zo� Blade wrote:

> Sorry, I really should slow down these A-112 related posts...
> 
> I just got a reply back from tybamm of http://www.muffwiggler.com/forum/viewtopic.php?t=50154 fame. Salient points:
> 
> > Of course, Diter can put it on his website, no matter, I'm happy to contribute ! 
> > 
> > And, another important new : I'm currently recoding the Super-miniwave Generator in Java, so it will be able to run on both windows, mac and linux ^^ I'm hardly working on this these days, it's coming soon...
> 
> Other than that, I don't know any more than anybody else, but it sounds promising!
> 
> 



[Non-text portions of this message have been removed]

Zoë, the bank=2 option works excellent!



On Tue, Oct 23, 2012 at 11:06 PM, Lars Bröndum <lahebr2000@yahoo.se> wrote:

> The "A-112 sample dump" application by Nico is really nice!   But I also
> like Zoe's script because it turns the sample into a sysex file - that way
> one can use it with other MIDI sequencers, librarians etc.  I also tried
> the .syx file on the ipad using the app "Midi Tool Box" - it works great.
>
> Thanks again for the good work Zoe!
>
> /Lars
>
>
> On Oct 22, 2012, at 10:20 PM, Zoė Blade wrote:
>
> > Sorry, I really should slow down these A-112 related posts...
> >
> > I just got a reply back from tybamm of
> http://www.muffwiggler.com/forum/viewtopic.php?t=50154 fame. Salient
> points:
> >
> > > Of course, Diter can put it on his website, no matter, I'm happy to
> contribute !
> > >
> > > And, another important new : I'm currently recoding the Super-miniwave
> Generator in Java, so it will be able to run on both windows, mac and linux
> ^^ I'm hardly working on this these days, it's coming soon...
> >
> > Other than that, I don't know any more than anybody else, but it sounds
> promising!
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]