Cannot compile on Fedora 12

[Ivan Arsenijević]

Hello,
I have 0404 PCI running on Fedora 12 x86_64. I'm trying to compile
emutrix, but cannot do so. Here's what I do:
1) wget ... ; tar xfz emutrix-1.0.tar.gz ; cd emutrix-0.1
2) qmake-qt4
3) make
Then I get are these lines:

/usr/lib64/qt4/bin/uic res/mainwindow.ui -o ui_mainwindow.h
Warning: name frame is already used
g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -
D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o main.o src/
main.cc
g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -
D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o mainwindow.o src/
mainwindow.cc

and it stops there; no further output, no messages, nothing.
In another console windows I can see there is a file "main.o" created
(218.552 bytes long).
If I try to run it anyway (chmod a+x ...) I get expected message
"cannot execute binary file".

Should I change anything in source code, Makefile or elsewhere to have
this interesting software compiled properly on Fedora?

Greetings,
Ivan

[Camilo Polymeris]

2010/9/18 Ivan Arsenijević <ivan.ars...@gmail.com>:

Hello,
A Makefile is included, just running make (without qmake-qt4) from a
fresh source directory works for me.
I also can confirm what you say happens with the source package (on
Ubuntu, also x86_64), but I have no idea why. It's the first time I
use Qt (and qmake) for a project, I'll try to figure it out.
Let me know if just running make helps, or if you have an idea what
could be causing this.
Greetings,
Camilo

[dimitri]

> Let me know if just running make helps, or if you have an idea what
> could be causing this.

It seems it is the -O2 compiler flag (which enables code
optimization), which is enabled when you run qmake-qt4. The Makefile I
included in the source package, OTH has debug flags enabled (no
optimization, more feedback, debugger symbols).
Try to stick to the provided Makefile, or use
qmake-qt4 "CONFIG+=debug"
I still have no idea why optimization messes with mainwindow.o, maybe
it just takes forever.
Greetings,
Camilo

[Ivan Arsenijević]

I have some success to report on.
I found on several other forums that it's mandatory on Fedora to run
"qmake-qt4" before running "make". I don't know why and there's no
explanation on those forums. That's why I run it in the first place,
otherwise I get the message about missing file /usr/share/qt4/mkspecs/
linux-g++/qmake.conf (which is probably some distribution-specific
difference between Fedora and Ubuntu).
But this time I've read the Makefile and the header gave me the idea.
Here's how it went:

[root@kanta64 emutrix0.1]# /usr/bin/qmake-qt4 -unix CONFIG+=debug -o
Makefile emutrix.pro
[root@kanta64 emutrix0.1]# make

/usr/lib64/qt4/bin/uic res/mainwindow.ui -o ui_mainwindow.h
Warning: name frame is already used

g++ -c -pipe -g -Wall -W -D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -
DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o
main.o src/main.cc

g++ -c -pipe -g -Wall -W -D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -
DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o

mainwindow.o src/mainwindow.cc
g++ -c -pipe -g -Wall -W -D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -
DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o

mainwindow_slots.o src/mainwindow_slots.cc
src/mainwindow_slots.cc:100: warning: unused parameter ‘checked’
/usr/lib64/qt4/bin/moc -DAPPLICATION_NAME=\"emutrix\" -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. src/mainwindow.h -o
moc_mainwindow.cpp
g++ -c -pipe -g -Wall -W -D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -
DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o

moc_mainwindow.o moc_mainwindow.cpp
/usr/lib64/qt4/bin/rcc -name emutrix res/emutrix.qrc -o
qrc_emutrix.cpp
g++ -c -pipe -g -Wall -W -D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -
DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o

qrc_emutrix.o qrc_emutrix.cpp
g++ -o emutrix main.o mainwindow.o mainwindow_slots.o
moc_mainwindow.o qrc_emutrix.o -lasound -lQtGui -lQtCore -
lpthread
[root@kanta64 emutrix0.1]#

Than I happily wanted to see how it goes, but it cut me away:

[root@kanta64 emutrix0.1]# ./emutrix
Starting emutrix ...
Setting up UI...
Checking soundcards...
Found soundcard # 0 : E-mu 0404b PCI [MAEM8852]
Error: "Sorry! No EMU 1010 based cards found."

Too bad :-(

Anyway, just to let you know: if I try to use the slider in the left
bottom part of the emutrix's window, as soon as I start moving it
upwards, the application crashes, and the appropriate message is:

Going to write stereo faders "Master Playback Volume" to 1
Writing to "Master Playback Volume" ALSA element.
emutrix: src/mainwindow.cc:146: void MainWindow::writeValue(const
QString&): Assertion `elements.contains(el)' failed.
Aborted (core dumped)
[root@kanta64 emutrix0.1]#

The same thing happens if I click on any of the fields in the matrix,
which is probably expected in my case.

By the way, is there any brief explanation about all those values that
are making the matrix? I only want to use capturing from the Optical
IN connector, but I don't know what and how to set. There are lot of
complaints about the information on this is being too sparse...

If you wish me to compile emutrix differently, or to try anything else
on Fedora, I'm willing to help. Hopefully, 0404 PCI can become
supported some day...

And I wish to thank you for this application, I think it will be
beneficial to many other users :-)

[dimitri]

On Sep 18, 7:56 pm, Ivan Arsenijević <ivan.arsenije...@gmail.com>
wrote:

> I have some success to report on.

Nice :-)

> I found on several other forums that it's mandatory on Fedora to run
> "qmake-qt4" before running "make". I don't know why and there's no
> explanation on those forums. That's why I run it in the first place,
> otherwise I get the message about missing file /usr/share/qt4/mkspecs/
> linux-g++/qmake.conf (which is probably some distribution-specific
> difference between Fedora and Ubuntu).

Ok. Interesting. I will add a comment about that to the docs.
BTW, "CONFIG+=debug" wasn't really necessary on my computer, only it
took 10 minutes to compile without it, that is with -O2.

> Than I happily wanted to see how it goes, but it cut me away:
>
> [root@kanta64 emutrix0.1]# ./emutrix
> Starting  emutrix ...
> Setting up UI...
> Checking soundcards...
> Found soundcard # 0 :  E-mu 0404b PCI [MAEM8852]
> Error:  "Sorry! No EMU 1010 based cards found."
>
> Too bad :-(
>

I really don't know how 0404 cards work. Would it make sense to
support them?
The thing with 1010 based cards, like the 1212M, 1820, 1616, etc is
that they have lots of inputs and outputs which can all be routed to
each other in complicated ways. That's why I wrote this app. The 0404
on the other hand has less connectors so maybe you don't really need
an app like this.

If the mixer controls for the 0404 are similar to 1212's maybe it can
be supported. Could you send the output of 'amixer controls'?

> Anyway, just to let you know: if I try to use the slider in the left
> bottom part of the emutrix's window, as soon as I start moving it
> upwards, the application crashes, and the appropriate message is:
>
> Going to write stereo faders  "Master Playback Volume"  to  1
> Writing to  "Master Playback Volume"  ALSA element.
> emutrix: src/mainwindow.cc:146: void MainWindow::writeValue(const
> QString&): Assertion `elements.contains(el)' failed.
> Aborted (core dumped)
> [root@kanta64 emutrix0.1]#
>
> The same thing happens if I click on any of the fields in the matrix,
> which is probably expected in my case.
>
> By the way, is there any brief explanation about all those values that
> are making the matrix?

What do you mean by values? The labels? "1010 ADAT 0", and the like
refer to physical connectors on the cards, in this case the 1010 card.
"ALSA Playback/Capture" refer to alsa inputs and outputs (devices hw:X,
2 and hw:X,3, resp.), available to applications or JACK or whatever...

> I only want to use capturing from the Optical
> IN connector, but I don't know what and how to set. There are lot of
> complaints about the information on this is being too sparse...
>
> If you wish me to compile emutrix differently, or to try anything else
> on Fedora, I'm willing to help. Hopefully, 0404 PCI can become
> supported some day...
>
> And I wish to thank you for this application, I think it will be
> beneficial to many other users :-)

Sorry it doesn't work for you. Moving the 0404 to "non supported
cards" column... :-(
From the above it seems the 0404 mixer doesn't even have a "Master
Playback Volume" element, leading to think that it works quite
differently from 1010 cards. Send me the output of the 'amixer
controls' command, and maybe I can help you figure out how to enable
capturing from optical in, and see how feasible it is to support the
0404 PCI someday.
Greetings,
Camilo.

[Camilo Polymeris]

> From the above it seems the 0404 mixer doesn't even have a "Master
> Playback Volume" element, leading to think that it works quite
> differently from 1010 cards.

On second thought, it may also be just a bug detecting the card I
fixed after releasing v0.1.
Could you try replacing line 43 in mainwindow.cc:

if (QString(name).startsWith(QLatin1String("E-mu 1010"))) // Simple
check, may not be enough to see if card is compatible

with this:

if (QString(name).startsWith(QLatin1String("E-mu 1010")) ||
QString(name).startsWith(QLatin1String("E-mu 0404")))

and recompile?
Thanks,
Camilo

[Ivan Arsenijević]

Hello,
Thank you for your support. I've tried few things today. I've run
compilation like this:

[root@kanta64 emutrix0.1]# qmake-qt4 -unix -o Makefile emutrix.pro
[root@kanta64 emutrix0.1]# time

make
/usr/lib64/qt4/bin/uic res/mainwindow.ui -o
ui_mainwindow.h
Warning: name frame is already
used

g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -

D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/

QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o main.o src/
main.cc
g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -

D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o mainwindow.o src/
mainwindow.cc
In file included from src/mainwindow.cc:19:
./ui_mainwindow.h: In member function ‘void
Ui_MainWindow::retranslateUi(QMainWindow*)’:
./ui_mainwindow.h:19954: note: variable tracking size limit exceeded
with -fvar-tracking-assignments, retrying without
In file included from src/mainwindow.cc:19:
./ui_mainwindow.h: In member function ‘void
Ui_MainWindow::setupUi(QMainWindow*)’:
./ui_mainwindow.h:1301: note: variable tracking size limit exceeded
with -fvar-tracking-assignments, retrying without

g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -

D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -

DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o
mainwindow_slots.o src/mainwindow_slots.cc
src/mainwindow_slots.cc:100: warning: unused parameter ‘checked’

/usr/lib64/qt4/bin/moc -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -

DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/

usr/include/QtCore -I/usr/include/QtGui -I/usr/include -I. -I. src/
mainwindow.h -o moc_mainwindow.cpp

g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -

D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/

QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o moc_mainwindow.o
moc_mainwindow.cpp
/usr/lib64/qt4/bin/rcc -name emutrix res/emutrix.qrc -o
qrc_emutrix.cpp

g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-
protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -

D_REENTRANT -DAPPLICATION_NAME=\"emutrix\" -DQT_NO_DEBUG -DQT_GUI_LIB -
DQT_CORE_LIB -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/
QtCore -I/usr/include/QtGui -I/usr/include -I. -I. -o qrc_emutrix.o
qrc_emutrix.cpp
g++ -Wl,-O1 -o emutrix main.o mainwindow.o mainwindow_slots.o

moc_mainwindow.o qrc_emutrix.o -lasound -lQtGui -lQtCore -
lpthread

real 9m41.062s
user 9m25.137s
sys 0m11.873s
[root@kanta64 emutrix0.1]#

So, I got the similar time needed for compilation like you've
mentioned (around 10 minutes).

Here is the requested information:

[root@kanta64 emutrix0.1]# amixer controls
numid=4,iface=MIXER,name='Master Playback Switch'
numid=3,iface=MIXER,name='Master Playback Volume'
numid=2,iface=MIXER,name='Capture Switch'
numid=1,iface=MIXER,name='Capture Volume'
[root@kanta64 emutrix0.1]#

If it's of more interest, you can find much more details in the result
of the command alsa-info.sh. I have uploaded it here:
http://arsa.in.rs/alsa-info.txt.OaC1gmGiv6.bz2

Yes, by "values in matrix" I actually meant "the labels", sorry for
imprecision. There's a comment in the specific thread "Official Alsa
Wiki for Developers : emu" (https://bugtrack.alsa-project.org/wiki/
wikka.php?wakka=emu&show_comments=1#comments) which states that
routing "DSP 0" to "0202 ADC Left" and "DSP 1" to "0202 ADC Right"
will link the DSPs to the Analogue input. I just wanted to achieve the
same with the Optical IN, but I don't get it how.

If you need a beta tester for emutrix on 0404 PCI, Im here to help.

Thank you,
Ivan

[Ivan Arsenijević]

Sorry, I've seen your suggestion only after writing the previous post.
Well, yes, this small change in line src/mainwindow.cc makes a huge
difference :-)
After compiling, I get a rather long text and the window opens. I had
no time to check anything yet in the window as I'm late for work :-)
But I will definitely experiment more tonight.
The message I receive when starting emutrix is until the rest of this
post. What do you suggest to try first for Optical IN? :-)

[root@kanta64 emutrix0.1]# ./emutrix
Starting emutrix ...
Setting up UI...
Checking soundcards...
Found soundcard # 0 : E-mu 0404b PCI [MAEM8852]

Selecting card # 0
Opening card...
Loading card elements...
97 elements loaded. Setting start defaults...;
Going to write stereo faders "Master Playback Volume" to 0

Writing to "Master Playback Volume" ALSA element.

Going to write stereo faders "PCM Capture Volume" to 0
Writing to "PCM Capture Volume" ALSA element.
Going to write stereo faders "Synth Playback Volume" to 0
Writing to "Synth Playback Volume" ALSA element.
Going to write stereo faders "Synth Capture Volume" to 0
Writing to "Synth Capture Volume" ALSA element.
Going to write stereo faders "Line Playback Volume" to 0
Writing to "Line Playback Volume" ALSA element.
Going to write stereo faders "Line Capture Volume" to 0
Writing to "Line Capture Volume" ALSA element.
Going to write stereo faders "CD Playback Volume" to 0
Writing to "CD Playback Volume" ALSA element.
Going to write stereo faders "CD Capture Volume" to 0
Writing to "CD Capture Volume" ALSA element.
Going to write stereo faders "Mic Playback Volume" to 0
Writing to "Mic Playback Volume" ALSA element.
Going to write stereo faders "Mic Capture Volume" to 0
Writing to "Mic Capture Volume" ALSA element.
Going to write stereo faders "Aux Playback Volume" to 0
Writing to "Aux Playback Volume" ALSA element.
Going to write stereo faders "Aux Capture Volume" to 0
Writing to "Aux Capture Volume" ALSA element.
Going to write stereo faders "IEC958 Optical Capture Volume" to 0
Writing to "IEC958 Optical Capture Volume" ALSA element.
Going to write stereo faders "IEC958 Optical Playback Volume" to 0
Writing to "IEC958 Optical Playback Volume" ALSA element.
Going to write stereo faders "Analog Mix Capture Volume" to 0
Writing to "Analog Mix Capture Volume" ALSA element.
Going to write stereo faders "Analog Mix Playback Volume" to 0
Writing to "Analog Mix Playback Volume" ALSA element.
Going to write stereo faders "PCM Center Playback Volume" to 100
Writing to "PCM Center Playback Volume" ALSA element.
Going to write stereo faders "PCM Front Playback Volume" to 100
Writing to "PCM Front Playback Volume" ALSA element.
Going to write stereo faders "PCM LFE Playback Volume" to 100
Writing to "PCM LFE Playback Volume" ALSA element.
Going to write stereo faders "PCM Side Playback Volume" to 100
Writing to "PCM Side Playback Volume" ALSA element.
Going to write stereo faders "PCM Surround Playback Volume" to 100
Writing to "PCM Surround Playback Volume" ALSA element.
Going to write stereo faders "PCM Playback Volume" to 100
Writing to "PCM Playback Volume" ALSA element.
Going to write stereo faders "Front Playback Volume" to 100
Writing to "Front Playback Volume" ALSA element.
Going to write stereo faders "Surround Playback Volume" to 100
Writing to "Surround Playback Volume" ALSA element.
Going to write stereo faders "Center Playback Volume" to 100
Writing to "Center Playback Volume" ALSA element.
Going to write stereo faders "LFE Playback Volume" to 100
Writing to "LFE Playback Volume" ALSA element.
Writing to "Tone Control - Switch" ALSA element.
Writing to "IEC958 Optical Raw Playback Switch" ALSA element.
Registering callbacks with ALSA
Setting up Master Playback Volume callback...
Reading initial status
Master volume changed to 0
Setting up Clock Internal Rate callback...
Reading initial status
Clock rate changed.
Setting up 0202 DAC Left Playback Enum callback...
Reading initial status
"0202 DAC Left Playback Enum" routing changed to -23
Setting up 0202 DAC Right Playback Enum callback...
Reading initial status
"0202 DAC Right Playback Enum" routing changed to -2
Setting up 1010 ADAT 0 Playback Enum callback...
Reading initial status
"1010 ADAT 0 Playback Enum" routing changed to -2
Setting up 1010 ADAT 1 Playback Enum callback...
Reading initial status
"1010 ADAT 1 Playback Enum" routing changed to -2
Setting up 1010 ADAT 2 Playback Enum callback...
Reading initial status
"1010 ADAT 2 Playback Enum" routing changed to -2
Setting up 1010 ADAT 3 Playback Enum callback...
Reading initial status
"1010 ADAT 3 Playback Enum" routing changed to -2
Setting up 1010 ADAT 4 Playback Enum callback...
Reading initial status
"1010 ADAT 4 Playback Enum" routing changed to -27
Setting up 1010 ADAT 5 Playback Enum callback...
Reading initial status
"1010 ADAT 5 Playback Enum" routing changed to -28
Setting up 1010 ADAT 6 Playback Enum callback...
Reading initial status
"1010 ADAT 6 Playback Enum" routing changed to -29
Setting up 1010 ADAT 7 Playback Enum callback...
Reading initial status
"1010 ADAT 7 Playback Enum" routing changed to -2
Setting up 1010 SPDIF Left Playback Enum callback...
Reading initial status
"1010 SPDIF Left Playback Enum" routing changed to -23
Setting up 1010 SPDIF Right Playback Enum callback...
Reading initial status
"1010 SPDIF Right Playback Enum" routing changed to -24
Setting up ADC1 14dB PAD 0202 Capture Switch callback...
Reading initial status
"ADC1 14dB PAD 0202 Capture Switch" changed to false
Setting up ADC1 14dB PAD Audio Dock Capture Switch callback...
Reading initial status
"ADC1 14dB PAD Audio Dock Capture Switch" changed to false
Setting up ADC2 14dB PAD Audio Dock Capture Switch callback...
Reading initial status
"ADC2 14dB PAD Audio Dock Capture Switch" changed to false
Setting up ADC3 14dB PAD Audio Dock Capture Switch callback...
Reading initial status
"ADC3 14dB PAD Audio Dock Capture Switch" changed to false
Setting up DAC1 0202 14dB PAD Playback Switch callback...
Reading initial status
"DAC1 0202 14dB PAD Playback Switch" changed to false
Setting up DAC1 Audio Dock 14dB PAD Playback Switch callback...
Reading initial status
"DAC1 Audio Dock 14dB PAD Playback Switch" changed to true
Writing to "DAC1 Audio Dock 14dB PAD Playback Switch" ALSA element.
Setting up DAC2 Audio Dock 14dB PAD Playback Switch callback...
Reading initial status
"DAC2 Audio Dock 14dB PAD Playback Switch" changed to true
Writing to "DAC2 Audio Dock 14dB PAD Playback Switch" ALSA element.
Setting up DAC3 Audio Dock 14dB PAD Playback Switch callback...
Reading initial status
"DAC3 Audio Dock 14dB PAD Playback Switch" changed to true
Writing to "DAC3 Audio Dock 14dB PAD Playback Switch" ALSA element.
Setting up DAC4 Audio Dock 14dB PAD Playback Switch callback...
Reading initial status
"DAC4 Audio Dock 14dB PAD Playback Switch" changed to true
Writing to "DAC4 Audio Dock 14dB PAD Playback Switch" ALSA element.
Setting up DSP 0 Capture Enum callback...
Reading initial status
"DSP 0 Capture Enum" routing changed to -2
No routing callback for element "DSP 0 Capture Enum"
Setting up DSP 1 Capture Enum callback...
Reading initial status
"DSP 1 Capture Enum" routing changed to -2
No routing callback for element "DSP 1 Capture Enum"
Setting up DSP 10 Capture Enum callback...
Reading initial status
"DSP 10 Capture Enum" routing changed to -2
No routing callback for element "DSP 10 Capture Enum"
Setting up DSP 11 Capture Enum callback...
Reading initial status
"DSP 11 Capture Enum" routing changed to -2
No routing callback for element "DSP 11 Capture Enum"
Setting up DSP 12 Capture Enum callback...
Reading initial status
"DSP 12 Capture Enum" routing changed to -2
No routing callback for element "DSP 12 Capture Enum"
Setting up DSP 13 Capture Enum callback...
Reading initial status
"DSP 13 Capture Enum" routing changed to -2
No routing callback for element "DSP 13 Capture Enum"
Setting up DSP 14 Capture Enum callback...
Reading initial status
"DSP 14 Capture Enum" routing changed to -2
No routing callback for element "DSP 14 Capture Enum"
Setting up DSP 15 Capture Enum callback...
Reading initial status
"DSP 15 Capture Enum" routing changed to -2
No routing callback for element "DSP 15 Capture Enum"
Setting up DSP 2 Capture Enum callback...
Reading initial status
"DSP 2 Capture Enum" routing changed to -2
No routing callback for element "DSP 2 Capture Enum"
Setting up DSP 3 Capture Enum callback...
Reading initial status
"DSP 3 Capture Enum" routing changed to -2
No routing callback for element "DSP 3 Capture Enum"
Setting up DSP 4 Capture Enum callback...
Reading initial status
"DSP 4 Capture Enum" routing changed to -2
No routing callback for element "DSP 4 Capture Enum"
Setting up DSP 5 Capture Enum callback...
Reading initial status
"DSP 5 Capture Enum" routing changed to -2
No routing callback for element "DSP 5 Capture Enum"
Setting up DSP 6 Capture Enum callback...
Reading initial status
"DSP 6 Capture Enum" routing changed to -2
No routing callback for element "DSP 6 Capture Enum"
Setting up DSP 7 Capture Enum callback...
Reading initial status
"DSP 7 Capture Enum" routing changed to -2
No routing callback for element "DSP 7 Capture Enum"
Setting up DSP 8 Capture Enum callback...
Reading initial status
"DSP 8 Capture Enum" routing changed to -2
No routing callback for element "DSP 8 Capture Enum"
Setting up DSP 9 Capture Enum callback...
Reading initial status
"DSP 9 Capture Enum" routing changed to -2
No routing callback for element "DSP 9 Capture Enum"
Setting up DSP A Capture Enum callback...
Reading initial status
"DSP A Capture Enum" routing changed to -2
Setting up DSP B Capture Enum callback...
Reading initial status
"DSP B Capture Enum" routing changed to -2
Setting up DSP C Capture Enum callback...
Reading initial status
"DSP C Capture Enum" routing changed to -2
Setting up DSP D Capture Enum callback...
Reading initial status
"DSP D Capture Enum" routing changed to -2
Setting up DSP E Capture Enum callback...
Reading initial status
"DSP E Capture Enum" routing changed to -2
Setting up DSP F Capture Enum callback...
Reading initial status
"DSP F Capture Enum" routing changed to -2
Setting up Dock DAC1 Left Playback Enum callback...
Reading initial status
"Dock DAC1 Left Playback Enum" routing changed to -2
Setting up Dock DAC1 Right Playback Enum callback...
Reading initial status
"Dock DAC1 Right Playback Enum" routing changed to -2
Setting up Dock DAC2 Left Playback Enum callback...
Reading initial status
"Dock DAC2 Left Playback Enum" routing changed to -2
Setting up Dock DAC2 Right Playback Enum callback...
Reading initial status
"Dock DAC2 Right Playback Enum" routing changed to -2
Setting up Dock DAC3 Left Playback Enum callback...
Reading initial status
"Dock DAC3 Left Playback Enum" routing changed to -27
Setting up Dock DAC3 Right Playback Enum callback...
Reading initial status
"Dock DAC3 Right Playback Enum" routing changed to -28
Setting up Dock DAC4 Left Playback Enum callback...
Reading initial status
"Dock DAC4 Left Playback Enum" routing changed to -29
Setting up Dock DAC4 Right Playback Enum callback...
Reading initial status
"Dock DAC4 Right Playback Enum" routing changed to -2
Setting up Dock Phones Left Playback Enum callback...
Reading initial status
"Dock Phones Left Playback Enum" routing changed to -2
Setting up Dock Phones Right Playback Enum callback...
Reading initial status
"Dock Phones Right Playback Enum" routing changed to -2
Setting up Dock SPDIF Left Playback Enum callback...
Reading initial status
"Dock SPDIF Left Playback Enum" routing changed to -2
Setting up Dock SPDIF Right Playback Enum callback...
Reading initial status
"Dock SPDIF Right Playback Enum" routing changed to -2
Master volume changed to 0

Thank you very much!

[Camilo Polymeris]

2010/9/20 Ivan Arsenijević <ivan.ars...@gmail.com>:

> Sorry, I've seen your suggestion only after writing the previous post.
> Well, yes, this small change in line src/mainwindow.cc makes a huge
> difference :-)
> After compiling, I get a rather long text and the window opens. I had
> no time to check anything yet in the window as I'm late for work :-)
> But I will definitely experiment more tonight.
> The message I receive when starting emutrix is until the rest of this
> post. What do you suggest to try first for Optical IN? :-)
>

By optical you mean S/PDIF, right? Try linking the input rows labeled
1010 S/PDIF to ALSA captures (probably 11 & 12), like this:
http://groups.google.com/group/emutrix/web/emutrix-optical.png

That works for me. But the S/PDIFs on the 1010 card are coaxial, while
ADAT is optical, so it may vary.
You could also try playing with the S/PDIF Optical Raw switch and
S/PDIF Optical fader in alsamixer, but only after starting emutrix.
Emutrix will reset that last element on start.

Let me know what works so I can incorporate it in future versions of
emutrix. BTW, it's your system, your call, but I recommend you not run
emutrix as root. I don't think it will break something in your system,
but you never know, the code is probably riddled with bugs.

Greetings,
Camilo