Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meters don't work at all #6

Closed
GoogleCodeExporter opened this issue Feb 17, 2016 · 10 comments
Closed

Meters don't work at all #6

GoogleCodeExporter opened this issue Feb 17, 2016 · 10 comments

Comments

@GoogleCodeExporter
Copy link

Hi,

I'm the maintainer of mudita24 for Debian and this is to inform you that a 
Debian user has notified us that mudita24's meters don't work at all for him; 
he's also reported that envy24control wasn't affected by this issue.

When launched from the terminal, mudita24 outputs the following:

cassiel@jimi:~$ mudita24
using    --- input_channels: 6
         --- output_channels: 6
         --- pcm_output_channels: 6
         --- spdif in/out channels: 2

His setup relies on ALSA+JACK, more information follows:

cassiel@jimi:~$ cat /proc/cpuinfo
processor       :
0

vendor_id       :
AuthenticAMD

cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 5200+


cassiel@jimi:~$ lspci -v|grep -A 8 -B 2 -i dmx

03:07.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24]
PCI Multi-Channel I/O Controller (rev 02)
        Subsystem: TERRATEC Electronic GmbH DMX 6fire 24/96
        Flags: bus master, medium devsel, latency 32, IRQ 22
        I/O ports at e800 [size=32]
        I/O ports at e400 [size=16]
        I/O ports at e000 [size=16]
        I/O ports at d800 [size=64]
        Capabilities: <access denied>
        Kernel driver in use: ICE1712


If you need more information about the original report, please find the Debian 
bug at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655708


Thanks in advance for any reply.

Original issue reported on code.google.com by quadris...@gmail.com on 13 Jan 2012 at 2:08

@GoogleCodeExporter
Copy link
Author

I have a DMX 6fire card which has worked in the past, but I can't test it now 
because the computer it was in is broken and I don't have time to resurrect it 
right now.

First, last I checked, I believe the Ubuntu version of mudita24 is woefully out 
of date (1.03). Current subversion sources are at 1.10. In particular, recent 
updates to various mainstream linuxen seems to have broken things at the Gtk 
level and 1.10 fixes these issues: 
........................
r11 Added attic branch containing legacy GTK+ 2.4/2.6 support. Trunk will 
remove this support so it can move forward into future.

r7 (September 23 2011) Tim E. Real: 1) Moved to cmake build system. 2) Fixed 
wrong alsactl location. Now cmake looks for alsactl. Override with environment 
variable ALSACTL_PROG. 3) Added usage info. 4) Fixed serious fatal X error: 
height too big. Was far too many markings, brought down the system, due to 
lowest alsa db value now returing -9999999. Installed some limits
..............................

Second, I'm seeing "access denied" in the above messages so this may not be a 
mudita24 issue at all.

The hardware meter values can be read at the ALSA level. If the following 
command
(corrected for card name, etc) doesn't work then that's where you should start 
looking for errors:

$ amixer -c M66 cget iface=PCM,name='Multi Track 
Peak',numid=45,iface=PCM,name='Multi Track Peak'
>   ; type=INTEGER,access=r-------,values=22,min=0,max=255,step=0
>   : values=63,62,51,49,56,60,63,62,59,54,0,0,0,0,0,0,0,0,0,0,113,112



Original comment by NielsMa...@gmail.com on 15 Jan 2012 at 4:53

@GoogleCodeExporter
Copy link
Author

numid 45 is the wrong control here, correct one on my system seems to be 57 and 
then your command line produces the expected output, ie:

tvrtko@deuteros:~$ amixer cget iface=PCM,name='Multi Track 
Peak',numid=57,iface=PCM,name='Multi Track Peak'
numid=57,iface=PCM,name='Multi Track Peak'
  ; type=INTEGER,access=r-------,values=22,min=0,max=255,step=0
  : values=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,53,53,53,53

While numid=45 gives:

tvrtko@deuteros:~$ amixer cget iface=PCM,name='Multi Track 
Peak',numid=45,iface=PCM,name='Multi Track Peak'
numid=45,iface=MIXER,name='Multi Track Internal Clock Default'
  ; type=ENUMERATED,access=rw------,values=1,items=13
  ; Item #0 '8000'
  ; Item #1 '9600'
  ; Item #2 '11025'
  ; Item #3 '12000'
  ; Item #4 '16000'
  ; Item #5 '22050'
  ; Item #6 '24000'
  ; Item #7 '32000'
  ; Item #8 '44100'
  ; Item #9 '48000'
  ; Item #10 '64000'
  ; Item #11 '88200'
  ; Item #12 '96000'
  : values=9

So I guess controls should be parsed at mudita24 startup instead of being 
hardcoded, if I read what you are saying correctly.

Tvrtko

Original comment by tvr...@ursulin.net on 15 Jan 2012 at 5:10

@GoogleCodeExporter
Copy link
Author

Interesting.... of course I'm testing this on a system that needs updating....

gnulem-199-.../trunk/mudita24> amixer -c M66 cget iface=PCM,name='Multi Track 
Peak',numid=45
numid=45,iface=PCM,name='Multi Track Peak'
  ; type=INTEGER,access=r-------,values=22,min=0,max=255,step=0
  : values=255,255,0,0,0,0,0,0,0,0,166,164,0,0,0,0,0,0,0,0,174,168
gnulem-200-.../trunk/mudita24> amixer -c M66 cget iface=PCM,name='Multi Track 
Peak',numid=57
numid=57,iface=MIXER,name='ADC Volume',index=2
  ; type=INTEGER,access=rw---R--,values=1,min=0,max=163,step=0
  : values=0
  | dBscale-min=-63.50dB,step=0.50dB,mute=1

Original comment by NielsMa...@gmail.com on 15 Jan 2012 at 5:16

@GoogleCodeExporter
Copy link
Author

gnulem-203-.../trunk/mudita24> amixer -c M66 controls
numid=33,iface=CARD,name='ICE1712 EEPROM'
numid=55,iface=MIXER,name='ADC Volume'
numid=56,iface=MIXER,name='ADC Volume',index=1
numid=57,iface=MIXER,name='ADC Volume',index=2
numid=58,iface=MIXER,name='ADC Volume',index=3
numid=25,iface=MIXER,name='IEC958 Multi Capture Switch'
numid=26,iface=MIXER,name='IEC958 Multi Capture Switch',index=1
numid=31,iface=MIXER,name='IEC958 Multi Capture Volume'
numid=32,iface=MIXER,name='IEC958 Multi Capture Volume',index=1
numid=42,iface=MIXER,name='IEC958 Playback Route'
numid=43,iface=MIXER,name='IEC958 Playback Route',index=1
numid=51,iface=MIXER,name='DAC Volume'
numid=52,iface=MIXER,name='DAC Volume',index=1
numid=53,iface=MIXER,name='DAC Volume',index=2
numid=54,iface=MIXER,name='DAC Volume',index=3
numid=59,iface=MIXER,name='Deemphasis'
numid=60,iface=MIXER,name='Deemphasis',index=1
numid=50,iface=MIXER,name='Delta IEC958 Input Status'
numid=21,iface=MIXER,name='H/W Multi Capture Switch'
numid=22,iface=MIXER,name='H/W Multi Capture Switch',index=1
numid=23,iface=MIXER,name='H/W Multi Capture Switch',index=2
numid=24,iface=MIXER,name='H/W Multi Capture Switch',index=3
numid=27,iface=MIXER,name='H/W Multi Capture Volume'
numid=28,iface=MIXER,name='H/W Multi Capture Volume',index=1
numid=29,iface=MIXER,name='H/W Multi Capture Volume',index=2
numid=30,iface=MIXER,name='H/W Multi Capture Volume',index=3
numid=38,iface=MIXER,name='H/W Playback Route'
numid=39,iface=MIXER,name='H/W Playback Route',index=1
numid=40,iface=MIXER,name='H/W Playback Route',index=2
numid=41,iface=MIXER,name='H/W Playback Route',index=3
numid=1,iface=MIXER,name='Multi Playback Switch'
numid=2,iface=MIXER,name='Multi Playback Switch',index=1
numid=3,iface=MIXER,name='Multi Playback Switch',index=2
numid=4,iface=MIXER,name='Multi Playback Switch',index=3
numid=5,iface=MIXER,name='Multi Playback Switch',index=4
numid=6,iface=MIXER,name='Multi Playback Switch',index=5
numid=7,iface=MIXER,name='Multi Playback Switch',index=6
numid=8,iface=MIXER,name='Multi Playback Switch',index=7
numid=9,iface=MIXER,name='Multi Playback Switch',index=8
numid=10,iface=MIXER,name='Multi Playback Switch',index=9
numid=11,iface=MIXER,name='Multi Playback Volume'
numid=12,iface=MIXER,name='Multi Playback Volume',index=1
numid=13,iface=MIXER,name='Multi Playback Volume',index=2
numid=14,iface=MIXER,name='Multi Playback Volume',index=3
numid=15,iface=MIXER,name='Multi Playback Volume',index=4
numid=16,iface=MIXER,name='Multi Playback Volume',index=5
numid=17,iface=MIXER,name='Multi Playback Volume',index=6
numid=18,iface=MIXER,name='Multi Playback Volume',index=7
numid=19,iface=MIXER,name='Multi Playback Volume',index=8
numid=20,iface=MIXER,name='Multi Playback Volume',index=9
numid=34,iface=MIXER,name='Multi Track Internal Clock'
numid=35,iface=MIXER,name='Multi Track Internal Clock Default'
numid=36,iface=MIXER,name='Multi Track Rate Locking'
numid=37,iface=MIXER,name='Multi Track Rate Reset'
numid=44,iface=MIXER,name='Multi Track Volume Rate'
numid=47,iface=PCM,name='IEC958 Playback Con Mask'
numid=46,iface=PCM,name='IEC958 Playback Default'
numid=48,iface=PCM,name='IEC958 Playback Pro Mask'
numid=45,iface=PCM,name='Multi Track Peak'

Original comment by NielsMa...@gmail.com on 15 Jan 2012 at 5:18

@GoogleCodeExporter
Copy link
Author

I had a small peak in your code and it looks you reference this control by 
name, not numid, so the bug is probably somewhere else. I'll grab the current 
version and give it a spin...

Original comment by tvr...@ursulin.net on 15 Jan 2012 at 5:29

@GoogleCodeExporter
Copy link
Author

Right, have 1.1.0 14 runnig now. A more detailed description of the bug is that 
meters seem to be sampled once on startup but then they are otherwise 
stuck/static. Pressing "Reset Peaks" clears them and puts in to "(Off)" state.

Original comment by tvr...@ursulin.net on 15 Jan 2012 at 5:45

@GoogleCodeExporter
Copy link
Author

The function updating the meters are only called once and is then destroyed 
because it does not return TRUE as required by g_timeout_add().
https://developer.gnome.org/glib/2.35/glib-The-Main-Event-Loop.html#g-timeout-ad
d

The attached patch solves the problem for me.

Original comment by soren.we...@gmail.com on 19 Mar 2013 at 12:39

Attachments:

@GoogleCodeExporter
Copy link
Author

#7 patch fixes this issue - still in svn 29 June 15. please add to svn version

Original comment by djch-goo...@hutchhome.co.uk on 29 Jun 2015 at 10:18

@GoogleCodeExporter
Copy link
Author

Done: svn commit --username NielsMayer@gmail.com -m 'applied patch by 
soren.wedel.nielsen https://code.google.com/p/mudita24/issues/detail?id=6#c7 
and verified by djch-google@hutchhome.co.uk 
https://code.google.com/p/mudita24/issues/detail?id=6#c8 ... thanks!'
...
Sending        mudita24/envy24control.c
Transmitting file data .
Committed revision 16.

Can previous commenters contact debian upstream?

Original comment by NielsMa...@gmail.com on 30 Jun 2015 at 7:37

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Patch verified as working.

Original comment by NielsMa...@gmail.com on 30 Jun 2015 at 7:40

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant