Hi Niels.
Something odd. Are you sure about those digital mixer ranges?
They now go down to only -48dB instead of -144dB.
Seems like 2/3 of the range is missing?
Verified against the original mixer, and amixer.
Also, the 'active' colour of the meters seems way too 'soft'?
Seems like just a
On Wed, Aug 4, 2010 at 12:00 PM, Tim E. Real termt...@rogers.com wrote:
Something odd. Are you sure about those digital mixer ranges?
Yep.
They now go down to only -48dB instead of -144dB.
Seems like 2/3 of the range is missing?
Truncated. At least for my purposes, the original faders w/
FYI, I added the following since
http://nielsmayer.com/envy24control/mudita24-1.0.1.tar.gz
... shall I release a 1.0.2 with the following additions (?):
* fixed --card and --device to allow valid ALSA names and numbers
( https://bugzilla.redhat.com/show_bug.cgi?id=602900 ).
* Add
On Sat, Jul 31, 2010 at 12:06 PM, Tim E. Real termt...@rogers.com wrote:
Niels do you have a new release or repo I can work with rather than
the original release, which may be too outdated to patch against by now?
http://nielsmayer.com/envy24control/mudita24-1.0.1.tar.gz
(source directory,
On Sat, Jul 31, 2010 at 11:24:31PM -0700, Niels Mayer wrote:
The main thing I haven't been able to resolve is Fons' complaint
regarding the DAC Volumes in Analog Volume panel not all being the
same height, due to a -10/+4 radiobox that only appears in first DAC
column for the Terratec
On Sun, Aug 1, 2010 at 3:54 PM, f...@kokkinizita.net wrote:
Is this a regression in mudita24 or a feature request for standard
envy24control? I didn't change this aspect of the code, as far as
I can tell.
The original has the same problem.
Well that's good to hear, in the sense that I
Hey gang. Took a break for a few days...
On July 28, 2010 09:10:32 pm Tim E. Real wrote:
Although slider thumb track size is known, extra unknown space
above and below the slider trough may make our custom marker
positions not precisely accurate.
Talk about whack-a-mole, gtk 2.20 has
On Mon, Jul 26, 2010 at 10:25 PM, Tim E. Real termt...@rogers.com wrote:
For now here's the code, throw it inside
dac_volume_to_db() and
adc_volume_to_db() but *replace* DAC_VOLUME_NAME with ADC_VOLUME_NAME,
and I believe mixer_volume_to_db() and wherever else required.
Do you need a
On July 27, 2010 09:09:51 pm Tim E. Real wrote:
So if that's the case, then we could simply try my first idea, just throw
up a vbox beside the slider with labels (and careful upper/lower item
expansion). I'm trying this in Glade.
Follow-up: Close but no cigar.
There are oh-so-subtle problems
On July 28, 2010 08:12:39 pm Tim E. Real wrote:
So I think the best solution now is let the application custom draw
the marks in a blank window beside the sliders.
The key is to pay attention to the half-way point of the
thumb track size,
Although slider thumb track size is known, extra
On July 26, 2010 04:50:04 am f...@kokkinizita.net wrote:
On Sun, Jul 25, 2010 at 04:55:10PM -0700, Niels Mayer wrote:
On Sun, Jul 25, 2010 at 3:23 PM, f...@kokkinizita.net wrote:
- The analog gain sliders behave strangly. They seem to 'detent'
on the scale marks, it's quite impossible to
On Tue, Jul 27, 2010 at 04:08:11PM -0400, Tim E. Real wrote:
Tested: Oh dear. I see what you guys mean now.
It's not hysteresis I was seeing, per se, but a desire for the
slider to snap to the marker detents.
Which is caused by adding the marks to the sliders in the first place.
Possible
On July 27, 2010 04:08:11 pm Tim E. Real wrote:
but we get to still keep the handy page up/down snaps,
as they are part of gtk_adjustment etc.
Sorry my mistake. Markers are required for page up/down snaps,
as Niels said before.
Too bad. That feature was quite handy, eh?
And the marks
On Tue, Jul 27, 2010 at 3:56 PM, Tim E. Real termt...@rogers.com wrote:
Sorry my mistake. Markers are required for page up/down snaps,
as Niels said before.
Too bad. That feature was quite handy, eh?
And the marks looked sooo nice.
And we need at least mark for one unity gain.
Tim -- thanks
On July 27, 2010 08:04:26 pm you wrote:
On Tue, Jul 27, 2010 at 3:56 PM, Tim E. Real termt...@rogers.com wrote:
Sorry my mistake. Markers are required for page up/down snaps,
as Niels said before.
Too bad. That feature was quite handy, eh?
And the marks looked sooo nice.
And we need at
On July 25, 2010 08:00:23 pm you wrote:
On Sun, Jul 25, 2010 at 3:57 PM, Tim E. Real termt...@rogers.com wrote:
CPU 20% on idle, and when adjusting sliders it's around 50%. All OK.
Is this more CPU load or less than the original envy24control? It
should be a lot less load.
Oops, don't know
On 26 July 2010 00:16, Niels Mayer nielsma...@gmail.com wrote:
On Sun, Jul 25, 2010 at 2:16 PM, James Morris ja...@jwm-art.net wrote:
CPU up to 99% here as soon as any audio plays and GUI very sluggish.
Delta 66 AMD64 Gentoo.
That looks like it might be an instance of the bug I thought I'd
On July 26, 2010 03:29:13 am Tim E. Real wrote:
I just noticed that the upper red part of all the meters are gone.
Any plans to re-instate that red coloured portion?
I fear a backlash on that.
Sorry was not paying full attention, I see the top is actually 0dBFS.
Hmm, I think I see your point
At Sun, 25 Jul 2010 12:10:44 -0700,
Niels Mayer wrote:
Summary of updates from envy24control 0.6.0 (GIT HEAD) to 1.0.0:
(0) After a decade, incremented version to 1.0.0 (**)
(1) Implemented missing Peak Hold functionality in meters and
reimplemented meters for increased efficiency and
On Sun, Jul 25, 2010 at 04:55:10PM -0700, Niels Mayer wrote:
On Sun, Jul 25, 2010 at 3:23 PM, f...@kokkinizita.net wrote:
- The meters just indicate level in a linear way. Half scale
is -6dB etc.
I figured there's enough changes in this first round that need
testingfeedback and decided
Suse 11.2 amd64
TERRATEC EWX 24/96
No issues to build it.
The faders with the +4dBu -10dBV switch here are shorter too.
CPU usage when playing and showing the meters around 5%, max around 22%,
for 0.6.0 and 1.0.0.
CPU usage when playing and moving the DAC faders for 0.6.0 it's around
30%, but
On Mon, 2010-07-26 at 12:13 +0200, I wrote:
Suse 11.2 amd64
TERRATEC EWX 24/96
CPU usage when playing and moving the DAC faders for 0.6.0 it's around
30%, but for 1.0.0 it's 60%.
Pardon.
CPU usage when playing and moving the DAC faders for 0.6.0 it's 20%
25%, but for 1.0.0 it's 30%
On 26 July 2010 11:13, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
After the 'normal' output for both versions I get:
'(envy24control:9266): Gtk-WARNING **: GtkSpinButton: setting an
adjustment with non-zero page size is deprecated
(envy24control:9266): Gtk-WARNING **: GtkSpinButton:
On Mon, 2010-07-26 at 11:52 +0100, James Morris wrote:
On 26 July 2010 11:13, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
After the 'normal' output for both versions I get:
'(envy24control:9266): Gtk-WARNING **: GtkSpinButton: setting an
adjustment with non-zero page size is
On Mon, Jul 26, 2010 at 1:47 AM, Takashi Iwai ti...@suse.de wrote:
Great. I'd love to merge it to the upstream tree after code review.
Could you simply post your patch(es) to alsa-devel ML (and Cc to
maintainers)? Then we can check your changes.
Takashi -- I am glad to hear of your interest
On Sun, Jul 25, 2010 at 4:10 PM, Tim E. Real termt...@rogers.com wrote:
So I say instead some descriptive tooltips would be very handy
for users, at least on the hardware settings tab, even if there
is a manual. But what about language translations? Is that
more or less automatic, or
On July 26, 2010 03:35:43 pm you wrote:
I'd have a better advantage if I had the motivation to add tooltips or
a language catalog, which sounds very tedious to try and do by myself.
Of course, if someone else wants to work on it, I'd be happy to
investigate and integrate any patches coming my
On Mon, Jul 26, 2010 at 1:50 AM, f...@kokkinizita.net wrote:
Adding a log2() and a multiplication doesn't seem like much of a
pain compared to the rest.
Yes, but orthogonal to getting what I'd already completed out... And
also, I figured there'd be discussion about the confusion in scales on
On Mon, Jul 26, 2010 at 12:29 AM, Tim E. Real termt...@rogers.com wrote:
trust me it will look great at the expense of only 28 extra pixels for
the minimum height over the original - it's all you can really do, man:
Remove the -72 and -108 dB marks on all the monitor sliders
in volume.c:
On Mon, Jul 26, 2010 at 3:52 AM, James Morris ja...@jwm-art.net wrote:
On 26 July 2010 11:13, Ralf Mardorf ralf.mard...@alice-dsl.net wrote:
'(envy24control:9266): Gtk-WARNING **: GtkSpinButton: setting an
adjustment with non-zero page size is deprecated
(envy24control:9266): Gtk-WARNING **:
On July 26, 2010 09:07:35 pm you wrote:
On Mon, Jul 26, 2010 at 12:29 AM, Tim E. Real termt...@rogers.com wrote:
trust me it will look great at the expense of only 28 extra pixels for
the minimum height over the original - it's all you can really do, man:
Remove the -72 and -108 dB
On Sun, Jul 25, 2010 at 3:10 PM, Niels Mayer nielsma...@gmail.com wrote:
(2) All volumes are represented as decibels, including the 0 to -48dB
i don't own one, so its not of much concern to me, but dBWHAT ?
___
Linux-audio-dev mailing list
On Sun, Jul 25, 2010 at 03:21:22PM -0400, Paul Davis wrote:
On Sun, Jul 25, 2010 at 3:10 PM, Niels Mayer nielsma...@gmail.com wrote:
(2) All volumes are represented as decibels, including the 0 to -48dB
i don't own one, so its not of much concern to me, but dBWHAT ?
For the meters I'd
On Sun, Jul 25, 2010 at 12:21 PM, Paul Davis p...@linuxaudiosystems.com wrote:
(2) All volumes are represented as decibels, including the 0 to -48dB
i don't own one, so its not of much concern to me, but dBWHAT ?
The http://en.wikipedia.org/wiki/Decibel is a unitless measurement. :-)
However,
On Sun, Jul 25, 2010 at 12:10:44PM -0700, Niels Mayer wrote:
Summary of updates from envy24control 0.6.0 (GIT HEAD) to 1.0.0:
Compiles OK here but:
- The meters just indicate level in a linear way. Half scale
is -6dB etc.
- The analog gain sliders behave strangly. They seem to 'detent'
on the
On Sun, Jul 25, 2010 at 2:16 PM, James Morris ja...@jwm-art.net wrote:
CPU up to 99% here as soon as any audio plays and GUI very sluggish.
Delta 66 AMD64 Gentoo.
That looks like it might be an instance of the bug I thought I'd
fixed. It's especially odd because I too have a Delta66 and AMD64
On July 25, 2010 06:57:42 pm Tim E. Real wrote:
I propose that the multi track rate locking be renamed to just
lock ( *not* locked because believe it or not I actually thought
that was an indicator, not a control - there is confusion with the
locked label underneath the word clock button,
On Sun, Jul 25, 2010 at 3:23 PM, f...@kokkinizita.net wrote:
- The meters just indicate level in a linear way. Half scale
is -6dB etc.
I originally talked about doing this in a previous thread, along with
various other things that ended up being impossible, like integrating
jkmeter :-).
I
38 matches
Mail list logo
