.cc - week one.
This semester we are creating our own MSP (Max Signal Processing) libraries, with the aim of pooling them altogether for the final project later on. To begin with we were asked to make the following two objects:
i. Pop-less DAC (Digital to Analogue Converter)
ii. Volume fader
.thoughts.
For the most part the original dac~ object is better than the jam.dac~ object. While my object may not pop to begin with, it instead has a small volume ramp. Having said that, I have not really encountered a problem with the original dac~ popping. On top of this dac~ has other features like the 'stopwindow' message, as well as an endless addition of channels and messages which arrange those channels. If you double click on the dac~ object it opens the Max "DSP Status" window which has heaps of options/preferences for Digital Signal Processing in Max. So while I learned some stuff about MSP making jam.dac~, it's not going take over dsp~ just yet.
.issues.
The only way I know incorporating these objects into other patches is by using the 'bpatcher' object or by creating a 'patcher' and copying the whole objects patch into that window. Having said that, clicking on 'help' for each of my custom objects will only open the 'thispatcher.help' window. And also, I was unable to set the 'Ramp Time' for the jam.fadeamp~ object as a argument (it's only inputted through an inlet).
It is going to be a semester of number crunching. I can smell the blood, sweat and tears already.
.sources.
Haines, Christian 26.07.2007 "Music & Sound Processing." EMU, Adelaide University.
No comments:
Post a Comment