Hi,
Now I've installed snd-firewire-ctl-services finally with kernel 5.4, though I have two problems with its running and I'd like to be given help about them.
First of all I must apologize to Sakamoto-san for the time he took in dealing with the 4.x kernel.
With 4.9 or 4.19 kernels, I got some warnings on MOTU/TASCAM in the build of libhinawa and failed the build of snd-firewire-ctl-services. Seemingly they were caused by the short of MOTU/TASCAM support in the source of these kernels. So I had to move to the 5.4 kernel. If it is helpful with the development of libhinawa or snd-firewire-ctl-services, I'll make another post about the failure.
I would like to move on to my problems.
Though there were some warnings, I could install snd-firewire-ctl-services:
root@darkstar:/tmp/snd-firewire-ctl-services-master# cargo build
warning: variant is never constructed: `DisplayClear`
--> libs/oxfw/src/apogee_proto.rs:26:5
|
26 | DisplayClear,
| ^^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 1 warning emitted
warning: field is never read: `firmware_version`
--> libs/motu/src/model.rs:17:5
|
17 | firmware_version: u32,
| ^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 1 warning emitted
Compiling snd-firewire-ctl-services v0.1.0 (/tmp/snd-firewire-ctl-services-master/services)
Finished dev [unoptimized + debuginfo] target(s) in 9.65s
So I started testing it, and got the first problem.
I mean that Only root user in login shell can start it with "cargo run" command in its build directory.
At first, I tried "snd-fireworks-ctl-service" and "cargo --run ..." command as a non-root user;
[~]$ snd-fireworks-ctl-service 2
bash: snd-fireworks-ctl-service: command not found
[~]$ cargo run --bin snd-fireworks-ctl-service 2
error: could not find `Cargo.toml` in `/home/of_mine` or any parent directory
next "cargo --run" again in its build directory;
[snd-firewire-ctl-services-master]$ cargo run --bin snd-fireworks-ctl-service 2
error: failed to open: /tmp/snd-firewire-ctl-services-master/target/debug/.cargo-lock
Caused by:
Permission denied (os error 13)
with sudo;
[snd-firewire-ctl-services-master]$ sudo cargo run --bin snd-fireworks-ctl-service 2
Compiling glib-sys v0.10.1
Compiling gobject-sys v0.10.0
Compiling alsatimer-sys v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
error: failed to run custom build command for `alsatimer-sys v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)`
Caused by:
process didn't exit successfully: `/tmp/snd-firewire-ctl-services-master/target/debug/build/alsatimer-sys-c801a364330bd9b0/build-script-build` (exit code: 1)
--- stdout
cargo:rerun-if-env-changed=ALSATIMER_NO_PKG_CONFIG
cargo:rerun-if-env-changed=PKG_CONFIG
cargo:rerun-if-env-changed=ALSATIMER_STATIC
cargo:rerun-if-env-changed=ALSATIMER_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_PATH
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
--- stderr
`"pkg-config" "--libs" "--cflags" "alsatimer" "alsatimer >= 0.0"` did not exit successfully: exit code: 1
--- stderr
Package alsatimer was not found in the pkg-config search path.
Perhaps you should add the directory containing `alsatimer.pc'
to the PKG_CONFIG_PATH environment variable
No package 'alsatimer' found
Package alsatimer was not found in the pkg-config search path.
Perhaps you should add the directory containing `alsatimer.pc'
to the PKG_CONFIG_PATH environment variable
No package 'alsatimer' found
warning: build failed, waiting for other jobs to finish...
error: build failed
and finally as root in login shell, I could start it:
[snd-firewire-ctl-services-master]$ sudo su -l
...
root@darkstar:/tmp/snd-firewire-ctl-services-master# cargo run --bin snd-fireworks-ctl-service 2
Compiling glib-sys v0.10.1
Compiling gobject-sys v0.10.0
Compiling alsatimer-sys v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling hinawa-sys v0.3.0 (https://github.com/alsa-project/hinawa-rs.git?tag=v0.3.0#f3acb958)
Compiling alsactl-sys v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling alsaseq-sys v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling glib v0.10.3
Compiling hinawa v0.3.0 (https://github.com/alsa-project/hinawa-rs.git?tag=v0.3.0#f3acb958)
Compiling alsatimer v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling alsactl v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling ta1394 v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/ta1394)
Compiling alsaseq v0.1.1 (https://github.com/alsa-project/alsa-gobject-rs.git?tag=v0.1.1#160b6d93)
Compiling core v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/core)
Compiling bebob v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/bebob)
Compiling tascam v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/tascam)
Compiling motu v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/motu)
warning: field is never read: `firmware_version`
--> libs/motu/src/model.rs:17:5
|
17 | firmware_version: u32,
| ^^^^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 1 warning emitted
Compiling oxfw v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/oxfw)
warning: variant is never constructed: `DisplayClear`
--> libs/oxfw/src/apogee_proto.rs:26:5
|
26 | DisplayClear,
| ^^^^^^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 1 warning emitted
Compiling dg00x v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/dg00x)
Compiling efw v0.1.0 (/tmp/snd-firewire-ctl-services-master/libs/efw)
Compiling snd-firewire-ctl-services v0.1.0 (/tmp/snd-firewire-ctl-services-master/services)
Finished dev [unoptimized + debuginfo] target(s) in 2m 38s
Running `target/debug/snd-fireworks-ctl-service 2`
But It is time-consuming for my poor cpu to execute the build process in every start.
I'd like to start the service with "snd-fireworks-ctl-service" command as a non-root user without runtime build at any other place than its build directory, if I can.
Anyway next I tried to operate my AudioFire4.
I could see its control sets:
[~]$ amixer -c 2 info
Card hw:2 'AudioFire4'/'Echo Digital Audio AudioFire4 v5.7, GUID 0014860c9d63a3f3 at fw1.0, S400'
Mixer name : 'AudioFire4'
Components : ''
Controls : 44
Simple ctrls : 37
[~]$ amixer -c 2 scontrols
Simple mixer control 'enable-mixer',0
Simple mixer control 'input-meter',0
Simple mixer control 'input-nominal',0
Simple mixer control 'metering',0
Simple mixer control 'monitor-gain',0
Simple mixer control 'monitor-gain',1
Simple mixer control 'monitor-gain',2
Simple mixer control 'monitor-gain',3
Simple mixer control 'monitor-gain',4
Simple mixer control 'monitor-gain',5
Simple mixer control 'monitor-mute',0
Simple mixer control 'monitor-mute',1
Simple mixer control 'monitor-mute',2
Simple mixer control 'monitor-mute',3
Simple mixer control 'monitor-mute',4
Simple mixer control 'monitor-mute',5
Simple mixer control 'monitor-pan',0
Simple mixer control 'monitor-pan',1
Simple mixer control 'monitor-pan',2
Simple mixer control 'monitor-pan',3
Simple mixer control 'monitor-pan',4
Simple mixer control 'monitor-pan',5
Simple mixer control 'monitor-solo',0
Simple mixer control 'monitor-solo',1
Simple mixer control 'monitor-solo',2
Simple mixer control 'monitor-solo',3
Simple mixer control 'monitor-solo',4
Simple mixer control 'monitor-solo',5
Simple mixer control 'output-meter',0
Simple mixer control 'output-mute',0
Simple mixer control 'output-nominal',0
Simple mixer control 'output-volume',0
Simple mixer control 'phantom-powering',0
Simple mixer control 'playback-mute',0
Simple mixer control 'playback-solo',0
Simple mixer control 'playback-volume',0
Simple mixer control 'stream-playback-routing',0
But I only could set 'phantom-powering'.
Additionaly with the QasMixer, a GUI mixer app, I could see the input/output meter indicated the signal level, but that was all. This is the second problem.
Have I made any mistakes in above steps? Or were there other things which I should have done?
I think my AF4's hardware is not the problem because it works well with ffado (,but which I wouldn't like to use for several reason. Of course I had uninstalled the libffado before the operation test.)
I'd appreciate any advice or information to solve these problems.
I'd like to post the install log of alsa-gobject and libhinawa ,if it is also needed.
(I didn't put them in this post because I afraid they make this post far too long.)
Regards,
Susie B.
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
