Hello Devin!<br><br>Your ideas all sound good, and I think a combination of video-tutorials and writing documentation is the way to go. I would gladly volounteer to do a basic tutorial if you teach me how to sample a synth through synthclone. For example, I have a synth inside LMMS (TripleOscillator) that I would love to sample and use in other apps. How would I go about doing that inside synthclone? (I guess the explanation would suffice for any synth connectable via a jack-midi port, right?). That could probably generate a simple tutorial of basic synth-cloning from me. I do however have to say that I within the next maybe two weeks have a pretty packed schedual, so I cannot promise anything timewise.<br>
<br>Another idea would be a forum, or a thread in an existing forum well populated by LAU's, making it easy to post instructions and/or tutorials for synthclone. Make it a community effort!<br><br>I will not be around LAC unfortunately.<br>
<br>Cheers!<br><br><div class="gmail_quote">On Sun, Apr 8, 2012 at 8:15 PM, Devin Anderson <span dir="ltr"><<a href="mailto:surfacepatterns@gmail.com">surfacepatterns@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Apr 8, 2012 at 8:44 AM, Gabbe Nord <<a href="mailto:gabbe.nord@gmail.com">gabbe.nord@gmail.com</a>> wrote:<br>
> This sounds like a very interesting software for me, but I have no<br>
> experience with similar software, so I have no clue how I would go about to<br>
> use this one, and I can't seem to find any tutorial on how to do it?<br>
<br>
</div>You're not the only person to bring up this problem. There is very<br>
little documentation on how to use synthclone, and synthclone could<br>
benefit from input from user-experience experts to make the software<br>
more intuitive. Unfortunately, synthclone has been a one-person<br>
operation up until now, and I'm not a user experience expert or<br>
particularly good at writing documentation.<br>
<br>
I would like to take some steps to rectify this problem. Here are<br>
some ideas I have:<br>
<br>
1.) Make a video tutorial on how to use synthclone.<br>
<br>
I'm considering submitting a drum kit to the Hydrogen Spring Drum Kit<br>
Contest by sampling kits I've made on my external drum synth using<br>
synthclone. If and when I do, I'll create a video tutorial on how I<br>
use synthclone to create the Hydrogen drum kit.<br>
<br>
2.) Find some time to write documentation.<br>
<br>
It might not be the greatest documentation ever, but it would be<br>
something. The problem is that I wrote the software, and probably<br>
make some bad assumptions about what the user does and doesn't know<br>
that someone with a fresh perspective might not make.<br>
<br>
3.) Get other people involved.<br>
<br>
I would love to have other people join me in helping to make<br>
synthclone better for everyone! So, if you are (or anyone out there<br>
is) interested in contributing to synthclone, please let me know!<br>
<br>
What do you think about these ideas? Do you have additional ideas<br>
that might help?<br>
<br>
I'll be at the Linux Audio Conference this week, so if you're going to<br>
be at LAC and have some ideas you'd like to discuss, please let me<br>
know.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Devin Anderson<br>
surfacepatterns (at) gmail (dot) com<br>
<br>
blog - <a href="http://surfacepatterns.blogspot.com/" target="_blank">http://surfacepatterns.blogspot.com/</a><br>
synthclone - <a href="http://synthclone.googlecode.com/" target="_blank">http://synthclone.googlecode.com/</a><br>
</div></div></blockquote></div><br>