posted 15 November 2008 13:06            

Do I need another program to do that?

posted 15 November 2008 18:04            

quote:

---

Here is some code that you could use in a text file or a tool to set the header information of already existing sample files. (It cannot be used in a Script that generates the recordings because the sample files will not exist already.)

"Create a SamplesFile object."
sf := 'aString' asSampleFile.

"Set various bits of header information. aPitch is interpreted as MIDI note number if given as a number without units; could use a value with units (100 hz). aVel is 0-127, always unitless. aTime is interpreted as in units of samples; could use a value with units (1.5 s)."
sf uiBasePitch: aPitch.
sf uiLowPitch: aPitch.
sf uiHighPitch: aPitch.

sf uiLowVelocity: aVel.
sf uiHighVelocity: aVel.

sf uiLoopStart: aTime.
sf uiLoopEnd: aTime.

"Write the updated header back to the disk."
sf updateHeader.

---

These are used by the autosampling tool I posted on the wiki btw.

hth,

posted 17 November 2008 09:13            

I;m gonna try and use your tool today - I have made a massive sample insutrument from drum hits with multiple mics, keeping the mic mix live during sample playback... but the load times are huge, so I want to use your tool to re-sample the mic mixed hits... will keep you posted

[This message has been edited by cristian_vogel (edited 17 November 2008).]

posted 18 March 2009 11:56            

quote:

---

How can I set the velocity range, base pitch etc in the header of a sample file?

---

1. Open the file in the Kyma Sample File Editor.
2. Click the "..." button.
3. Select Edit Info

posted 18 March 2009 12:18            

quote:

---

I have to ask how are we supposed to know about the Smalltalk command 'updateHeader' if its not detailed in the manual?

---

I think Luddy was just trying to help you out by sharing a piece of code; I don't think he intended you to think that it is part of the official Kyma release or something officially documented in the manual.

Sometimes we'll write a snippet of code to help someone with a specific task and send it to them via a private email. That does not necessarily mean that we intend to support that little piece of code, guarantee that it will continue to work in the future, document it in the manual, or make it part of the Kyma release.

Sometimes a cigar is just a cigar. (and sometimes a hastily hacked together piece of code is just something useful to help someone out).

posted 25 March 2009 06:26            

I have to say I find the last SSC comment quite arrogant.
~~~
I think Luddy was just trying to help you out by sharing a piece of code; I don't think he intended you to think that it is part of the official Kyma release or something officially documented in the manual.

Sometimes we'll write a snippet of code to help someone with a specific task and send it to them via a private email. That does not necessarily mean that we intend to support that little piece of code, guarantee that it will continue to work in the future, document it in the manual, or make it part of the Kyma release.

Sometimes a cigar is just a cigar. (and sometimes a hastily hacked together piece of code is just something useful to help someone out).
~~~

let me paraphrase this how i read it...

"we will share with some users an undocumented capy/Smalltalk work-around that we may or may not have any intention of supporting in future. Dont ask us for the complete reference on capy/smalltalk as implemented in Kyma coz it's a moving target."

I politely suggest that dedicated Kyma users who have spent good money and time on their investment deserve better quality support than the pithy response offered above. This reflects badly apon the company.

respectfully
Sean