Q skrev 2010-12-17 22:57:
> I assume this occurs with anything you compile from source, that it
> defaults to /usr/local/lib unless you tell it otherwise, causing
> problems if older versions have been installed elsewhere by other means.
> (I make this assumption on the fact that all the libraries
Andreas Persson wrote:
> OK. This is exactly the behavior you would get if you run libgig without
> the fix. So, I'm sure that you somehow failed to build or install or
> link with the fixed version. Maybe you have an old libgig file in
> /usr/lib, and your "make install" installed the new one
Q skrev 2010-12-17 21:49:
> The "Velocity dynamic range" value is at 0. Using slider, entry of
> number into the box or the up arrow, increase "Velocity dynamic range" to 4.
>
> Use Ctrl+S or "Save" from the File menu to save the file. Close gigedit
> using either Ctrl+Q or Quit from the File menu.
Andreas Persson wrote:
> Q skrev 2010-12-17 20:47:
>> As mentioned earlier, sadly the updated libgig isn't working right for
>> me. I hope the bug isn't too much of a headache to fix.
>
> I've know tested the fix a bit more thoroughly, and it seems to work for
> me. I created a gig with regions w
Q skrev 2010-12-17 20:47:
> As mentioned earlier, sadly the updated libgig isn't working right for
> me. I hope the bug isn't too much of a headache to fix.
I've know tested the fix a bit more thoroughly, and it seems to work for
me. I created a gig with regions with all 15 combinations of filter
Andreas Persson wrote:
>
> Maybe it was too fast then. I saw a rather obvious calculation error in
> gig.cpp, fixed it and did one quick test that worked.
>
>> I did "cvs update -d -P" in the libgig directory. I then re-built libgig
>> ("./configure"; "make"; "sudo make install"),
>
> Should ha
Q skrev 2010-12-17 20:11:
> Woah, thanks for the fast response! Unfortunately, though, it's still
> not working for me.
Maybe it was too fast then. I saw a rather obvious calculation error in
gig.cpp, fixed it and did one quick test that worked.
> I did "cvs update -d -P" in the libgig directory
Andreas Persson wrote:
> Q skrev 2010-12-17 13:36:
>> The velocity curve settings are very confusing and counterintuitive.
>
> Agreed. But they are also very compatible to GigaStudio. See
> http://hem.spray.se/andreas56/curves/.
Okay, I understand. I've seen the curves before, but didn't know ho
Q skrev 2010-12-17 13:36:
> The velocity curve settings are very confusing and counterintuitive.
Agreed. But they are also very compatible to GigaStudio. See
http://hem.spray.se/andreas56/curves/.
> However, whenever I open the duly saved gigfile, either in Gigedit once
> more or in JSampler, th
Hello
I'm trying to build some instruments in Gigedit. What I'm trying to
achieve is that the instruments will be completely insensitive to
velocity, yet have a lowpass filter controlled by the modwheel (but
inverted, so full mod is filter fully closed).
The velocity curve settings are very co
Guten Tag
I am trying to make a gig file from some wav samples that I made. There
is no problem when creating regions but when I try to "drag and drop" my
first sample The "Sample" field still shows "NULL" even though the
console output says that the sample has been added:
> $ gigedit
> Initializ
11 matches
Mail list logo
