2 Aug
2014
2 Aug
'14
11:47 p.m.
Hi,
I mainly work on the laws of sound, not much on how to code,
but tux know coding and look at here
http://chezlefab.net/share/8e3b1648a0a683334186/lmmodeljo-fab.tar.gz
it-is the future, I just have to correct the wav converter
there are many drums
Try the code
A drum is simply a strong decrease in amplitude accompanied by a change in
length by 5 forehead (30 fronts enough)
"Segmentation faults , "that is if you try out linux
Best regard
2014-08-02 23:16 GMT+02:00 James Morris <james(a)jwm-art.net>et>:
On Sat, 2 Aug 2014 14:13:58 +0200
pierre jocelyn andre <temps.jo(a)gmail.com> wrote:
Hello there,
again sorry for my poor English
my synthesizer creates sounds of drums
each sound weighs 16 bytes
we must forget audacity is too heavy, so much many bytes per sound
sounds produced by my synthesizer can not be encoded as encoding
deforms, as streaming deforms,
here you have some synthesizer sounds in wikimedia
http://commons.wikimedia.org/wiki/Special:Contributions/9temps
here you have video
https://www.youtube.com/watch?v=XwCeR5S8kHI
I hear no drums in that video. I watched one of the others and found
the sounds interesting (as I commented there) but didn't hear any
drums, and it's not obvious what's going on, how can you change the
synthesis parameters for instance? Must the code be edited and
recompiled?
here you have some piano code
http://www.letime.net/vocale/lmmodel1jo.tar.gz
Segmentation faults as soon as I hit any button.
piano with drum
must be
I am currently working with the debian facile community to improve
codes
I've just looked at MaFenetre.cpp and it's over 9000 lines!
You need to stop the lazy coding habit of copying and pasting the same
code over and over again with minor modifications. I see 1438 lines
beginning at line 6580 with the same code copied and pasted over and
over again, and then again another piece of code copied and pasted for
the last 1116 lines of the file.
You need to turn much of MaFenetre.cpp into functions to reduce the
redundancy.
Learn how to use structured programming.
Start setting minimal standards for your code and adhere to them.
But I'm only self taught too, and not a pro either, so what do I know.
james.
best regards
2014-08-02 11:20 GMT+02:00 Fede <federicogalland(a)gmail.com>om>:
> I was looking for the best way to synthesize drums a few months
> ago, and while I tried various samplers and synths, I decided that
> my ultimate drum machine would be a tracker. The tracker interface
> cannot be beaten for the rhythmic purposes. Plus it has perfect
> timing since you don't depend on MIDI.
>
> I'm currently using the hydrogen drumkit samples for that. Mainly
> the 909s which sound good enough.
>
> Also, for the arrangements of my band I'm starting to use rosegarden
> +linuxsampler, which I load GMaq's 4pc drumkit sf2.
>
> Since the drum timbres don't usually change a lot during
> performance, this options plus some effects should be good enough
> (chibitracker comes with reverb and cheesetracker has built in
> ladspa).
>
> If you want to make your own drum piece timbres, I'd recommend you
> to use audacity to draw your samples. You have access to all the
> LADSPA and nyquist plugins, and it's a really comfortable tool to
> work with short samples (I'm thinking of the envelope editor
> function which I love).
>
> Good luck, and tell us the option you've taken.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>