I made another commit yesterday, with higher values. (Range from -127
to 127 had only a max value of 127 while scale is 255). I had the idea
to change from ByteArray to QList (for greater range), or better
the whole audioframe, so the we could make an abstract audio class,
which can then have, this
maybe we need a db scale on the meter, as long as the meter can show the
correct values.
> On Mon, Sep 27, 2010 at 4:36 PM, jb wrote:
> > On Tuesday 28 September 2010 00:13:40 Dan Dennedy wrote:
> >> On Mon, Sep 27, 2010 at 2:17 PM, Simon Eugster
wrote:
> >> > Sorry I cannot comment on your U
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2010 12:40 PM, amir wrote:
> hello all,
> this looks great, I have two suggestions:
> 1. I think the Vu is better vertically on the side of the monitor, the
> current
agreed
> position "pull" the eyes from the monitor to the meter, maybe ev
hello all,
this looks great, I have two suggestions:
1. I think the Vu is better vertically on the side of the monitor, the current
position "pull" the eyes from the monitor to the meter, maybe even let the
user decide were he wants to position the meter.
2 add the ability to toggle on/off the di
On Mon, Sep 27, 2010 at 4:36 PM, jb wrote:
> On Tuesday 28 September 2010 00:13:40 Dan Dennedy wrote:
>> On Mon, Sep 27, 2010 at 2:17 PM, Simon Eugster wrote:
>> > Sorry I cannot comment on your UV yet, but I really cannot run
>> > anything atm :( (and I wanted to show kdenlive in a lecture on
>>
