|
Date: 2004-03-25 |
Author: mute |
Viewed 5481 times |
This isn't for the technically challenged, but with that said...
this is not as difficult as it may sound, specially when following the instructions to the T and using the demo bmx to get started.
you must have pybuzz installed. you can download pybuzz from
buzzmachines, http://www.buzzmachines.com
BIG FAT RULE: Never close the pybuzz shell window (python interpreter/debug window), it will close automatically when you close Buzz. If you try to close that window using it's X it will hang on u.
Instructions:
1) copy mute_wavcopy.py to buzz\gear\generators\pybuzz
2) run buzz
3) open the demo bmx, mute_batch.bmx
4) right click Quence Pybuzz, click import and open mute_wavcopy.py
5) right click Freq Out and specify the filename.wav and path to use
6) use buzz\gear\generators\pybuzz\pybuzz.wav
7) look at the sequence/patterns, dont change anything (yet)
8) open the buzz\gear\generators\pybuzz folder in Windows Explorer
9) press play on buzz, make sure looping is turned off
10) when buzz stops, look at the recorded wav results in the pybuzz folder
you should have:
pybuzz.wav
001_pybuzz.wav
002_pybuzz.wav
11) you should now understand how it works. your default wav always
has to be in this folder, and unless you edit my script following the tips
below, the .wav name and path you select with the Frequency Unknown's Freq Out or Morex WordOut's wave recorders has to be buzz\gear\generators\pybuzz\pybuzz.wav
12) EDITING TIPS
open mute_wavcopy.py in notepad
edit the values:
original=open("pybuzz.wav", 'rb')
new=open("%03i_pybuzz.wav" %avalue,'wb')
to filenames of your choice.
the 'original' name must be the name you specified
in your waverecorder.
In the future, I may update this with an editable path or something
in which case i'll post an update @ buzzmachines.com
Feel free to edit and learn from this script. If you make anything interesting
let me know
|
| Attached File: mute_batchrec.rar |
|
| Readers Comments: |
add comment |
|
in case you didnt look at the last review and my conversations w/ th0ke.. the whole point of this is to create a batch recording system within buzz so you can quickly create samples using buzz instruments and effects.. dumping samples out to a directory like
001_sample.wav
002_sample.wav
003_sample.wav
etc..
you can do this using this setup. 2004-03-25 by mute (Voted 10 for this review!) |
|
| so umn yah, this is for creating sample libraries quickly with no post editing in cooledit or whatever else nessicary 2004-03-25 by mute (Voted 10 for this review!) |
|
I must admit i know nothing about pybuzz ... but your template seems to work here.
How does pybuzz make different output samples instead of the one i specified in freqout ?
Cool! (the samples don't have a file extension, but after adding '.wav' they are playing fine)
So now i can play several samples in a row and this template will record them to different wave files ?! That's useful. :) 2004-03-26 by thOke (Voted 9 for this review!) |
|
here's an updated version th0ke, should fix that problem. http://www.plosive.net/buzz/pybuzz/mute_wavcopy.py
all the pybuzz script does is copy the file.. and everytime it does the file copying action (that pattern 'filecopy') it more or less tells the python script to increase the # it's using.. so you get the 001, 002, 003, etc..
the script itself isnt really hard to alter if you want to use different filename.wav's .. i personally have the script open in notepad and re-edit the output filename everytime i start working on a different kind of sample. if you wanna edit that check out #12 on the readme txt..
pybuzz itself is a python interpreter / peer machine. its not unlike what you can do with apps like pure-data and max/msp. if you have a full python install and not just python32.dll, you can do almost anything with it from file copying, generate sound, controlling other apps from buzz, etc..
glad its working for you ;] get the new version, i had to fix a couple things in the one i included in the rar.
thought this was kinda cool...imagine setting up a bmx template like this using all kinds of gens, etc.. then sequencing out all the recording/file copying. you could send someone a 40kb file that creates a ton of samples.. that would otherwise take forever to upload as individual wavs
2004-03-26 by mute (Voted 10 for this review!) |
|
thanks ... i will try it tonight. i am sure one can do wonderful things with this pybuzz (i even installed python some time ago, but i was too lazy to learn more about it yet)
some more example files would increase the motivation to bother with the long python manual. 2004-03-26 by thOke (Voted 10 for this review!) |
|
| So if I get this right, what your script does is look for the pybuzz.wav file in the pybuzz directory and increment it by one every time you send a word parameter to the pybuzz gen? How are you "triggering" pybuzz by sending the same data to it all the time? At any rate, it's very cool that you can do this, what with the external manipulation of files and all. 2004-03-27 by wizenwet (Voted 10 for this review!) |
|
wizen: yah , the trigger with just the same value happens because the way i set it up in OnParameter within the pybuzz script is so that the file copy happens whenever that param recieves any value. Initially my idea was to have one pattern for recording & file copying, but i couldn't delay the filecopy long enough. if i did it that way you would bind word1 to the record switch on a machine and control on/off... so you'd only need the pybuzz patterns in the seq editor.
th0ke, etc: dont be afraid to look at the script or the python manual ;] the only module available in python32.dll is the sys module,. which is kinda limited. i didn't know a lick of python when i started coding this script.
im alrady off to better things. did a full install of python lastnight and've been working on some more elaborate stuff. once i have a bunch of scripts i plan to make a repository or something so people can dl them and upload their own.
2004-03-27 by mute (Voted 10 for this review!) |
|
