patchpool

Sampleconstruct · Post by **Sampleconstruct** » Fri May 29, 2015 7:09 pm

I was wondering today after spending quite a few entire days on writing the documentation for my new HALion library, wether this (not so amusing) work is actually worth the efforts. So, is anybody actually reading the patch lists/patch descriptions or could I just as well send out a recipe for broccoli pie?

Feel free to comment...and please add your vote to the poll.

kgdrum · Post by **kgdrum** » Fri May 29, 2015 7:23 pm

Of course I read them but please include the recipe for broccoli pie!

Sampleconstruct · Post by **Sampleconstruct** » Fri May 29, 2015 7:57 pm

kgdrum wrote:Of course I read them but please include the recipe for broccoli pie!

I absolutely hate broccoli, so that was only a bad example

kgdrum · Post by **kgdrum** » Fri May 29, 2015 8:54 pm

I'm a bit surprised as I thought broccoli might be responsible for some of your patch/sound inspirations!

Sampleconstruct · Post by **Sampleconstruct** » Fri May 29, 2015 8:58 pm

kgdrum wrote:I'm a bit surprised as I thought broccoli might be responsible for some of your patch/sound inspirations!

LOLZ, I think it' more the salad and red peppers, if it was the broccoli my sounds would sound rather mushy and slippery, and they would smell...

SJ_Digriz · Post by **SJ_Digriz** » Fri May 29, 2015 9:08 pm

I think there is a balance to be had here Simon. Your documentation is a bit over the top (in a good way). I think a simpler patch list by category + controls assigned would be enough. The page after page of detailed patch description is probably overkill, although much appreciated

aMUSEd · Post by **aMUSEd** » Fri May 29, 2015 9:20 pm

What I like best is when the patch notes are with the patch like in Alchemy, I find that very useful.

I like that about the MachFive info page, you can put a lot of info in there, although when a patch is scripted you don't see it and have to switch pages to access the info.

Sampleconstruct · Post by **Sampleconstruct** » Fri May 29, 2015 10:10 pm

SJ_Digriz wrote:I think there is a balance to be had here Simon. Your documentation is a bit over the top (in a good way). I think a simpler patch list by category + controls assigned would be enough. The page after page of detailed patch description is probably overkill, although much appreciated

Finding the balance is exactly the point, does the user need to "understand" a patch or does it suffice if he knows how to operate it. I'm sort of stuck in that routine of mentioning too much maybe, like it was an obligation which in fact doesn't exist...although I have alread cut down a bit, mentioning what a controller does if it's labelled "Reverb Mix" seems silly, even to me

kgdrum · Post by **kgdrum** » Sat May 30, 2015 6:12 am

Sampleconstruct wrote:
kgdrum wrote:I'm a bit surprised as I thought broccoli might be responsible for some of your patch/sound inspirations!
LOLZ, I think it' more the salad and red peppers, if it was the broccoli my sounds would sound rather mushy and slippery, and they would smell...

Simon do you think Splat-Pool is a marketable name for musicians who want their samples loaded with an occasional random surprise?

Sampleconstruct · Post by **Sampleconstruct** » Sat May 30, 2015 6:29 am

kgdrum wrote:
Sampleconstruct wrote:
kgdrum wrote:I'm a bit surprised as I thought broccoli might be responsible for some of your patch/sound inspirations!
LOLZ, I think it' more the salad and red peppers, if it was the broccoli my sounds would sound rather mushy and slippery, and they would smell...

Simon do you think Splat-Pool is a marketable name for musicians who want their samples loaded with an occasional random surprise?

Sounds good to me, and looks good too. SplatPool™

emasters · Post by **emasters** » Sat May 30, 2015 6:42 am

To get the product installed into HALion, I read the doc and found the link to your prior YouTube video - both helpful. Without this, I would have neglected selecting the "User" icon and the "Refresh" button. So both the doc and video avoided a support question.

Sampleconstruct · Post by **Sampleconstruct** » Sat May 30, 2015 7:08 am

emasters wrote:To get the product installed into HALion, I read the doc and found the link to your prior YouTube video - both helpful. Without this, I would have neglected selecting the "User" icon and the "Refresh" button. So both the doc and video avoided a support question.

Yeah, but reading the installation procedure is obligatory

, my question was more about the patch descriptions.

emasters · Post by **emasters** » Sat May 30, 2015 4:49 pm

Less so, on the patch descriptions. Perhaps more as an overview.

SJ_Digriz · Post by **SJ_Digriz** » Sat May 30, 2015 4:52 pm

Sampleconstruct wrote:
emasters wrote:To get the product installed into HALion, I read the doc and found the link to your prior YouTube video - both helpful. Without this, I would have neglected selecting the "User" icon and the "Refresh" button. So both the doc and video avoided a support question.
Yeah, but reading the installation procedure is obligatory , my question was more about the patch descriptions.

That was where I was going. The main point of the patches is what controls you mapped. I can hear what it sounds like

Again, those descriptions you put together are awesome. But truthfully, once I've been through the patch list once, I really only care about the mapping.

Sampleconstruct · Post by **Sampleconstruct** » Sat May 30, 2015 5:55 pm

Well, this is all very useful feedback, the poll is at 7:1 so I gather that descriptions are useful to most and it' s up to me to find a less elaborate method to get the info across. Those video demonstrations for the new HALion lib seem to get some positive attention, so that also is an alternative to those bibles full of technical language.

patchpool

KVR Audio

Poll: concerning documentation of my libraries, does anybody actually read the PDFs?

Do you read the documentation and patch descriptions published by patchpool?