I made some updates to the example and will make some more. I have some
"text" stuff I'm in the middle of working on, but for the sake of moving
things along, here's a sample of individual keys.

https://drive.google.com/file/d/0B6hxg-gC2Uz_WXlyeno2YUo4Z00/view

I did cheat a little by ignoring how the keys play along with each other,
so when you press 3+ keys in the app, the signals collide and clip due to
how i did the reverb. This was mostly due to time and contest submission,
so i didn't spend much additional time resolving it. It's just lingering on
my TODO.

I fired up tgui-harm but it seems that I need to get an actual midi device
connected before I can make it do anything. I moved recently and have a
desk+chair to put together before i unbox my midi keyboard, so maybe I'll
try it out then. Suggestions otherwise, I'd say go ahead and let a row on
the keyboard play in-place of an actual keyboard.

On Thu, Jun 23, 2016 at 7:44 AM Daniel Skinner <dan...@dasa.cc> wrote:

> Yes, the Android app is a toy app. Touchscreen or not, the hardware
> latency alone makes that a fact. But that's why it's an example, not the
> root project.
>
> I've been using the gui example as a playground to work out further
> improvements to a separate project and I realize this is in disarray. I
> need to fix that and will be shortly. But ive also added a standalone
> example that runs from command line and generates a tone. Once midi support
> is added, I wanted to bring in the piano sound and let a cli example play a
> piece with it.
>
> I'll try and fix it up this Sunday and let you know. But my interest in
> Android isn't as a target but rather a more general interest in low powered
> devices and hardware I'd like to build on TUIO protocol. The gui example
> itself will break out into its own project but is intended for desktop.
>
> As for how serious anyone takes it, doesn't matter since I record my own
> music and I'm writing these primarily for my own use. Package snd is really
> all about live inputs, for example, once I have FFT, I can create a vocoder
> for a mic based on the input from my guitar and I'll make a song based
> solely on that. This is just what I do, but I've used other libs before I
> wanted more control over the process.
>
> Things like the piano sound will always just be examples for package snd,
> it's just not the intent, only a possibility.
>
>
> On Thu, Jun 23, 2016, 3:46 AM <wbo...@gmail.com> wrote:
>
>> Hi Daniel,
>>
>> I already investigated your piano and snd projects at github, but could
>> not get them working: too much unknown libraries. Anyhow, it seemed to be
>> aiming at the Android platform, with an on-screen piano keyboard and no
>> MIDI interface. For Android this is a sensible project, but for a musician
>> it qualifies as a toy app, not fit to play real music, and competing with a
>> lot of similar apps. In the past I created several myself, and believe me:
>> you cannot use a touch screen as a real piano keyboard. It's unplayable.
>>
>> About the speed of Go: that depends on what you compare it to. In the
>> past I wrote similar programs in C++. There I used more complicated
>> algorithms, with more calculations at each signal frame, and still the
>> program could run at 48000Hz without problems. So apparently in this area
>> Go is 2x slower then C++. I tried all known trics to increase the speed,
>> like: no garbage creation, and also pre-calculate as much as possible.
>> Increasing the buffer size had little effect, because all needed
>> calculations still must be done.
>>
>> I would love to hear how your piano is sounding. Can't you update your
>> github projects and also augment the README's such that a simple user like
>> me can build something that works?
>>
>> Wouter Boeke
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to golang-nuts+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to