[Jack-Devel] Remaining problems

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[Jack-Devel] Remaining problems

liebrecht
To consolidate remaining problems



CONFIRMED: Jack routes output to 1818vsl properly. So outputs work.
I verified that sound can be sent to 1818vsl, therefore since I cannot
create any signal in mixbus, I asume that mixbus will be able to send
sound to the 1818vsl successfully as it is connected to the same working
port on jack that setbfree sent sound to the 1818vsl. So that test of
mine confirmed that jack does route correctly to 1818vsl
So in my case we do not have to discuss the output routing to the
interface. Jack seems to do that well.

1) I have to figure out why with jack started and inputs and outputs of
1818vsl connected to mixbus, no sound is received.
Any suggestion how I can test the routing of inputs on the 181vsl to
what jack routed ?

Here is my patchage setup as already reported
"http://grossmann-venter.com/issues/jack/patchage_status-01.png"

The 18 inputs of the 1818vsl is clearly made available and connedcted to
mixbus.
I want to connect some of them to something else I can monitor
independent from mixbus.

Anyone has a suggestion?
Ardour is not a good option, as mixbus is basically ardour with a skin.
I need to add something else to one of the 18 routes and send signal
from the 1818vsl and capture it with something.
Please suggest what you are using to attach to ports to test for data.
Thanks.

2) After (1) is solved etc, I need to get pulseaudio to work through
jack, but I will discuss that later. Without pulseaudio I will not have
any control of desktop sound as there is no volume control. E.g.
audacity blasts at full volume through jack as it by error starts with
full volume at startup..annoying and not pleasant.. So I will have to
route all those through pulseaudio at a later date once I have mixbus
working
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

John Rigg
On Tue, Mar 26, 2019 at 11:07:38AM -0400, [hidden email] wrote:
> Here is my patchage setup as already reported
> "http://grossmann-venter.com/issues/jack/patchage_status-01.png"
>
> The 18 inputs of the 1818vsl is clearly made available and connedcted to  
> mixbus.
> I want to connect some of them to something else I can monitor  
> independent from mixbus.

It looks from the patchage screenshot like jack is routing your
inputs properly. It may be that alsa has set the input gain to
minimum (or muted the inputs).

Do you have a /var/lib/alsa/asound.state file?
If so look at the input levels listed in that file.

You should be able to set the levels with alsamixer,
if it works with your interface.

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

liebrecht



On 2019-03-26 16:44, John Rigg wrote:
> On Tue, Mar 26, 2019 at 11:07:38AM -0400,
> [hidden email] wrote:

>
> Do you have a /var/lib/alsa/asound.state file?
> If so look at the input levels listed in that file.
>

I was just about to look at it, figured out I should look at it when you
posted it.

I understand Mixer is the 1818VSL, why there is only 16 inputs, I dont
know there should be 18.
Anycase if this is the volume settings then it is indeed zero.

control.11 {
                iface MIXER
                name 'Mic Capture Volume'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                value.8 0
                value.9 0
                value.10 0
                value.11 0
                value.12 0
                value.13 0
                value.14 0
                value.15 0






--------------------Content of /var/lib/alsa/asound.state
----------------






state.HDMI {
        control.1 {
                iface CARD
                name 'HDMI/DP,pcm=3 Jack'
                value false
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.2 {
                iface MIXER
                name 'IEC958 Playback Con Mask'
                value
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.3 {
                iface MIXER
                name 'IEC958 Playback Pro Mask'
                value
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.4 {
                iface MIXER
                name 'IEC958 Playback Default'
                value
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access 'read write'
                        type IEC958
                        count 1
                }
        }
        control.5 {
                iface MIXER
                name 'IEC958 Playback Switch'
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.6 {
                iface PCM
                device 3
                name ELD
                value ''
                comment {
                        access 'read volatile'
                        type BYTES
                        count 0
                }
        }
        control.7 {
                iface CARD
                name 'HDMI/DP,pcm=7 Jack'
                value false
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.8 {
                iface MIXER
                name 'IEC958 Playback Con Mask'
                index 1
                value
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.9 {
                iface MIXER
                name 'IEC958 Playback Pro Mask'
                index 1
                value
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.10 {
                iface MIXER
                name 'IEC958 Playback Default'
                index 1
                value
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access 'read write'
                        type IEC958
                        count 1
                }
        }
        control.11 {
                iface MIXER
                name 'IEC958 Playback Switch'
                index 1
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.12 {
                iface PCM
                device 7
                name ELD
                value ''
                comment {
                        access 'read volatile'
                        type BYTES
                        count 0
                }
        }
        control.13 {
                iface CARD
                name 'HDMI/DP,pcm=8 Jack'
                value false
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.14 {
                iface MIXER
                name 'IEC958 Playback Con Mask'
                index 2
                value
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.15 {
                iface MIXER
                name 'IEC958 Playback Pro Mask'
                index 2
                value
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.16 {
                iface MIXER
                name 'IEC958 Playback Default'
                index 2
                value
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access 'read write'
                        type IEC958
                        count 1
                }
        }
        control.17 {
                iface MIXER
                name 'IEC958 Playback Switch'
                index 2
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.18 {
                iface PCM
                device 8
                name ELD
                value ''
                comment {
                        access 'read volatile'
                        type BYTES
                        count 0
                }
        }
        control.19 {
                iface CARD
                name 'HDMI/DP,pcm=9 Jack'
                value false
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.20 {
                iface MIXER
                name 'IEC958 Playback Con Mask'
                index 3
                value
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.21 {
                iface MIXER
                name 'IEC958 Playback Pro Mask'
                index 3
                value
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.22 {
                iface MIXER
                name 'IEC958 Playback Default'
                index 3
                value
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access 'read write'
                        type IEC958
                        count 1
                }
        }
        control.23 {
                iface MIXER
                name 'IEC958 Playback Switch'
                index 3
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.24 {
                iface PCM
                device 9
                name ELD
                value ''
                comment {
                        access 'read volatile'
                        type BYTES
                        count 0
                }
        }
        control.25 {
                iface CARD
                name 'HDMI/DP,pcm=10 Jack'
                value false
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.26 {
                iface MIXER
                name 'IEC958 Playback Con Mask'
                index 4
                value
'0fff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.27 {
                iface MIXER
                name 'IEC958 Playback Pro Mask'
                index 4
                value
'0f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access read
                        type IEC958
                        count 1
                }
        }
        control.28 {
                iface MIXER
                name 'IEC958 Playback Default'
                index 4
                value
'0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
                comment {
                        access 'read write'
                        type IEC958
                        count 1
                }
        }
        control.29 {
                iface MIXER
                name 'IEC958 Playback Switch'
                index 4
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.30 {
                iface PCM
                device 10
                name ELD
                value ''
                comment {
                        access 'read volatile'
                        type BYTES
                        count 0
                }
        }
        control.31 {
                iface PCM
                device 3
                name 'Playback Channel Map'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 8
                        range '0 - 36'
                }
        }
        control.32 {
                iface PCM
                device 7
                name 'Playback Channel Map'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 8
                        range '0 - 36'
                }
        }
        control.33 {
                iface PCM
                device 8
                name 'Playback Channel Map'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 8
                        range '0 - 36'
                }
        }
        control.34 {
                iface PCM
                device 9
                name 'Playback Channel Map'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 8
                        range '0 - 36'
                }
        }
        control.35 {
                iface PCM
                device 10
                name 'Playback Channel Map'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 8
                        range '0 - 36'
                }
        }
}
state.VSL {
        control.1 {
                iface MIXER
                name 'AudioBox 1818 VSL Audio 2.0 Output Playback'
                value.0 true
                value.1 true
                value.2 true
                value.3 true
                value.4 true
                value.5 true
                value.6 true
                value.7 true
                value.8 true
                value.9 true
                value.10 true
                value.11 true
                value.12 true
                value.13 true
                value.14 true
                value.15 true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 16
                }
        }
        control.2 {
                iface MIXER
                name 'AudioBox 1818 VSL Audio 2.0 Output Playback'
                index 1
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.3 {
                iface MIXER
                name 'AudioBox 1818 VSL Audio 2.0 Output Playback'
                index 2
                value.0 255
                value.1 255
                value.2 255
                value.3 255
                value.4 255
                value.5 255
                value.6 255
                value.7 255
                value.8 255
                value.9 255
                value.10 255
                value.11 255
                value.12 255
                value.13 255
                value.14 255
                value.15 255
                comment {
                        access 'read write'
                        type INTEGER
                        count 16
                        range '0 - 255'
                        dbmin -12750
                        dbmax 0
                        dbvalue.0 0
                        dbvalue.1 0
                        dbvalue.2 0
                        dbvalue.3 0
                        dbvalue.4 0
                        dbvalue.5 0
                        dbvalue.6 0
                        dbvalue.7 0


> You should be able to set the levels with alsamixer,
> if it works with your interface.
>
> John
> _______________________________________________
> Jack-Devel mailing list
> [hidden email]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
                        dbvalue.8 0
                        dbvalue.9 0
                        dbvalue.10 0
                        dbvalue.11 0
                        dbvalue.12 0
                        dbvalue.13 0
                        dbvalue.14 0
                        dbvalue.15 0
                }
        }
        control.4 {
                iface MIXER
                name 'AudioBox 1818 VSL Audio 2.0 Output Playback'
                index 3
                value 255
                comment {
                        access 'read write'
                        type INTEGER
                        count 1
                        range '0 - 255'
                        dbmin -12750
                        dbmax 0
                        dbvalue.0 0
                }
        }
        control.5 {
                iface CARD
                name 'AudioBox 1818 VSL Internal Clock Validity'
                value true
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.6 {
                iface CARD
                name 'AudioBox 1818 VSL S/PDIF Clock Validity'
                value true
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.7 {
                iface CARD
                name 'AudioBox 1818 VSL ADAT Clock Validity'
                value true
                comment {
                        access read
                        type BOOLEAN
                        count 1
                }
        }
        control.8 {
                iface MIXER
                name 'AudioBox 1818 VSL Clock Selector Clock Sour'
                value 'AudioBox 1818 VSL Internal Clock'
                comment {
                        access 'read write'
                        type ENUMERATED
                        count 1
                        item.0 'AudioBox 1818 VSL Internal Clock'
                        item.1 'AudioBox 1818 VSL S/PDIF Clock'
                        item.2 'AudioBox 1818 VSL ADAT Clock'
                }
        }
        control.9 {
                iface MIXER
                name 'Mic Capture Switch'
                value.0 true
                value.1 true
                value.2 true
                value.3 true
                value.4 true
                value.5 true
                value.6 true
                value.7 true
                value.8 true
                value.9 true
                value.10 true
                value.11 true
                value.12 true
                value.13 true
                value.14 true
                value.15 true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 16
                }
        }
        control.10 {
                iface MIXER
                name 'Mic Capture Switch'
                index 1
                value true
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
        control.11 {
                iface MIXER
                name 'Mic Capture Volume'
                value.0 0
                value.1 0
                value.2 0
                value.3 0
                value.4 0
                value.5 0
                value.6 0
                value.7 0
                value.8 0
                value.9 0
                value.10 0
                value.11 0
                value.12 0
                value.13 0
                value.14 0
                value.15 0
                comment {
                        access 'read write'
                        type INTEGER
                        count 16
                        range '0 - 255'
                        dbmin -12750
                        dbmax 0
                        dbvalue.0 -12750
                        dbvalue.1 -12750
                        dbvalue.2 -12750
                        dbvalue.3 -12750
                        dbvalue.4 -12750
                        dbvalue.5 -12750
                        dbvalue.6 -12750
                        dbvalue.7 -12750
                        dbvalue.8 -12750
                        dbvalue.9 -12750
                        dbvalue.10 -12750
                        dbvalue.11 -12750
                        dbvalue.12 -12750
                        dbvalue.13 -12750
                        dbvalue.14 -12750
                        dbvalue.15 -12750
                }
        }
        control.12 {
                iface MIXER
                name 'Mic Capture Volume'
                index 1
                value 255
                comment {
                        access 'read write'
                        type INTEGER
                        count 1
                        range '0 - 255'
                        dbmin -12750
                        dbmax 0
                        dbvalue.0 0
                }
        }
        control.13 {
                iface CARD
                name 'Keep Interface'
                value false
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
}
state.usbtv {
        control {
        }
}
state.CH345 {
        control {
        }
}
state.XS8 {
        control {
        }
}
state.Interface {
        control.1 {
                iface CARD
                name 'Keep Interface'
                value false
                comment {
                        access 'read write'
                        type BOOLEAN
                        count 1
                }
        }
}
state.M1x1 {
        control {
        }
}
state.UB99 {
        control {
        }
}


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

John Rigg
In reply to this post by John Rigg
On Tue, Mar 26, 2019 at 08:44:39PM +0000, John Rigg wrote:
> It may be that alsa has set the input gain to
> minimum (or muted the inputs).

It looks like this is probably the problem:

https://linuxmusicians.com/viewtopic.php/?f=6&t=7543

According to that forum thread the 1818VSL turns its
input levels down to zero by default. You need to set
it in alsamixer.

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

John Rigg
In reply to this post by liebrecht
On Tue, Mar 26, 2019 at 04:16:03PM -0400, [hidden email] wrote:

>
>
>
> On 2019-03-26 16:44, John Rigg wrote:
>> On Tue, Mar 26, 2019 at 11:07:38AM -0400,  
>> [hidden email] wrote:
>
>>
>> Do you have a /var/lib/alsa/asound.state file?
>> If so look at the input levels listed in that file.
>>
>
> I was just about to look at it, figured out I should look at it when you  
> posted it.
>
> I understand Mixer is the 1818VSL, why there is only 16 inputs, I dont  
> know there should be 18.
> Anycase if this is the volume settings then it is indeed zero.

So you found the problem. You should be able to use alsamixer to
turn them up. Let us know if it works.

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

liebrecht
On 2019-03-26 17:14, John Rigg wrote:
>
> So you found the problem. You should be able to use alsamixer to
> turn them up. Let us know if it works.

Not really I was searching for it because the shortcuts to the alsa gui
mixer didnt work and nothing could be changed, so I was searching where
settings were kept when you posted.

Setting all values in capture to 255 didnt solve the problem. I also
restarted alsa, still doesnt have any sound from the 1818vsl. Sound to
the 1818vsl still works.
Is there maybe another global alsa input volume setting I am not aware
off ?


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

liebrecht
In reply to this post by John Rigg
On 2019-03-26 17:14, John Rigg wrote:
>
> So you found the problem. You should be able to use alsamixer to
> turn them up. Let us know if it works.

Hi John, I managed to get pulseaudio to route to jack. It was nothing
involving
load-module module-jack-source
load-module module-jack-sink channels=2
as was recommended to add to pulseaudio config file.
That really didnt work.
In the process I had to completely uninstall qjackctl and mixbus still
sent sound great so did pulse through jack. Good riddance in my case as
qjackctl never did anything useful for me.

So now pulse plays very nice and I have everything from my myriad of
bluetooth devices and all my desktop audio and what not routed through
jack to the 1818vsl. All works flawless.


The only current remaining problem is therefore:
Why no signal from 1818vsl is routed from alsa to mixbus although it is
clearly routed with jack.
As already mentioned All sound routes successfully to the 1818vsl.

What is really necessary is an application that can tap into any in or
output and output raw data, so a user can debug these interfaces. Since
you dont bother about latency etc, it would be dead easy to write
something like that. It should really be a built in patch tap tester for
patchage.

You and a few other on the group- helped me a boatload, and it is almost
finished.
All I now have to try and solve is why alsa or jack do not route the
sound coming from the 1818vsl.

Thanks
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

Ralf Mardorf
On Tue, 26 Mar 2019 20:55:00 -0400, [hidden email]
wrote:
>All I now have to try and solve is why alsa or jack do not route the
>sound coming from the 1818vsl.

Hi,

it's not easy to help with that, since there not only is much talk
about idiotic features jack should provide, more confusing is that
already provided information is not easy to find again, because you
didn't stay with a clean thread, you opened one subject after the other.

Subject: [Jack-Devel] Jack Problems
Subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled  still wont start.
Subject: [Jack-Devel] Pulseaudio Replacement
Subject: [Jack-Devel] Remaining problems
Subject: Re: [Jack-Devel] JACK is a great deterministic audio server

That's no well-structured troubleshooting.

I don't know which issue in what way is really already solved.

Randomly patching something together, so that half of a problem is
solved, has nothing to do with troubleshooting. Maybe half of the issue
isn't solved, because what is working now, is just a cheap fix for half
of the issue, but the cause that the issue can't be solved completely.

Thank heaven, that you don't need to care about volume controls
provided by jack, too ;).

I recommend to do one step after the other.

1. Try to solve all input and output issues, excepted of bluetooth, IOW
without pulseaudio first. IOW even if you don't want to use Qjackctl,
get jack and qjackctl running first.

2. Once it's possible to get all IOs working with jack and qjackctl you
could drop qjackctl and get pulseaudio working together with jack.

It was already pointed out earlier that uninstalling and reinstalling
is no well-structured troubleshooting.

Regards,
Ralf
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

liebrecht
On 2019-03-27 00:57, Ralf Mardorf wrote:

> Hi,
>
> it's not easy to help with that, since there not only is much talk
> about idiotic features jack should provide,

Hi Ralf. No problem I solved the Mixbus input problem a boatload of
others.

The big problem was qjackctl for me that has been putting me on a wild
goose chase for quite some time as almost everyone made it seem
indispensable which really did not work for me.

I have
1) pulseaudio routing to jack without qjackctl. Completely uninstalled
and never used.
1) Bluetooth with all my bluetooth devices working perfect.
2) all desktop audio
3) Mixbus working great now and I can route to both pulse if I want to
but default to Jack with no xruns at very low latency.
3) all applications now routed through either pulseaudio where it makes
sense (such as bluetooth) and other directly to jack.
4) I have 6 other midi devices audio routing perfectly.
5) I have my audio keyboard shortcuts running flawlessly using pulse.
6) and more.., such as adding a mixer to my jack outputs to the Main
181VSL output.

I dont understand the "idiotic" accusation. I just wanted to haver a
failsafe between the Main output and jack. It works great. I never
suggested to have all ports with volume controls, please read my posts.


I have a few outstanding problems, but they will be easily solved.

It all works brilliantly and my method is solid.

In order to document it in a repeatable deterministic way, I will
uninstall everything and then reinstall using my notes until everything
works after complete uninstalation and reinstallation  which makes sure
that the documentation is correct and accurate and repeatable. Just
documenting it makes no sense and results in an essay open for
interpretation. Essays are basically mostly what you get on the
internet. That is fine but they are generally not executable.

I hope it satisfies your concern about my uninstallation/reinstallation.
It has scientific merrit if you think of it. So I really dont understand
the concern.
This way I get a rugged document for at least Debian Stretch based on a
few complete install/reinstalls. I already did one, and will do the last
one after I fixed the few remaining problems.

I think you misinterpret what I try to do by your criticsm of me working
from a known reference by reinstallation. Document and reinstall
actually helped me to solve the problem easily in the end.

I must thank a lot of people helping me warts and all scraps and
scruffs, jabs, insults included.

But I specially want to thank John Rigg for very helpful suggestions in
a gentlemanly fashion.

Thanks John.



> Hi,
>
> it's not easy to help with that, since there not only is much talk
> about idiotic features jack should provide, more confusing is that
> already provided information is not easy to find again, because you
> didn't stay with a clean thread, you opened one subject after the
> other.
>
> Subject: [Jack-Devel] Jack Problems
> Subject: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack
> Reinstalled  still wont start.
> Subject: [Jack-Devel] Pulseaudio Replacement
> Subject: [Jack-Devel] Remaining problems
> Subject: Re: [Jack-Devel] JACK is a great deterministic audio server
>
> That's no well-structured troubleshooting.
>
> I don't know which issue in what way is really already solved.
>
> Randomly patching something together, so that half of a problem is
> solved, has nothing to do with troubleshooting. Maybe half of the issue
> isn't solved, because what is working now, is just a cheap fix for half
> of the issue, but the cause that the issue can't be solved completely.
>
> Thank heaven, that you don't need to care about volume controls
> provided by jack, too ;).
>
> I recommend to do one step after the other.
>
> 1. Try to solve all input and output issues, excepted of bluetooth, IOW
> without pulseaudio first. IOW even if you don't want to use Qjackctl,
> get jack and qjackctl running first.
>
> 2. Once it's possible to get all IOs working with jack and qjackctl you
> could drop qjackctl and get pulseaudio working together with jack.
>
> It was already pointed out earlier that uninstalling and reinstalling
> is no well-structured troubleshooting.
>
> Regards,
> Ralf
> _______________________________________________
> Jack-Devel mailing list
> [hidden email]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

Ralf Mardorf
On Wed, 27 Mar 2019 03:02:17 -0400, [hidden email]
wrote:
>I hope it satisfies your concern about my
>uninstallation/reinstallation.

Yesno, most important is, that it now works and that you know what steps
to do, to get it working, if you would install it again. It's doesn't
really matter that we don't know what caused the issue in the first
place, but it wouldn't harm to know the reason for the failure ;).
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Remaining problems

John Rigg
In reply to this post by liebrecht
On Tue, Mar 26, 2019 at 08:27:02PM -0400, [hidden email] wrote:
> On 2019-03-26 17:14, John Rigg wrote:
>>
>> So you found the problem. You should be able to use alsamixer to
>> turn them up. Let us know if it works.
>
> Not really I was searching for it because the shortcuts to the alsa gui  
> mixer didnt work and nothing could be changed, so I was searching where  
> settings were kept when you posted.

You shouldn't need a GUI shortcut to start alsamixer. It starts from
the command line and has an ncurses interface. Check you have it
installed - it's in the alsa-utils package in Debian.

> Setting all values in capture to 255 didnt solve the problem.

Wrong setting. The dbvalues are set to -12750 in the asound.state
file you posted. They need to be set to 0 for full volume. Look at
the playback values and mirror those.

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

[Jack-Devel] Jack/USB cycle of USB output Sound device.

liebrecht
In reply to this post by Ralf Mardorf
So Jack routes from Alsa and Alsa handles the USB 1818VSl directly.

Problem:
If I plug out the 1818vsl (my main sound card) usb plug, then jack
disconnects although it is not directly handling the usb device but alsa
is.
If I reconnect jack does not reconnect, so I have to go then through my
startup script and restart jack after which it all works again.

Question
Is there a daemon available that monitors the usb device 1818vsl in my
case and then reconnects if the device is unplugged and replugged ?

If not, I will have to write such daemon for my own purposes and it is
no sweat doing it, but just wondered if I am maybe missing  that someone
already done it as it is a blatantly obvious missing piece. I ask as I
dont want to reinvent the wheel if it already exists.




_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Anders Genell


30 mars 2019 kl. 04:45 skrev [hidden email]:

So Jack routes from Alsa and Alsa handles the USB 1818VSl directly.

Problem:
If I plug out the 1818vsl (my main sound card) usb plug, then jack disconnects although it is not directly handling the usb device but alsa is.

Well, if the sound card disappears, Jack has nothing to keep connections to, so that is not unexpected. 


If I reconnect jack does not reconnect, so I have to go then through my startup script and restart jack after which it all works again.

Question
Is there a daemon available that monitors the usb device 1818vsl in my case and then reconnects if the device is unplugged and replugged ?


There is the udev daemon that could be useful, perhaps?
Some inspiration could be found here, maybe: https://alsa.opensrc.org/Udev

If not, I will have to write such daemon for my own purposes and it is no sweat doing it, but just wondered if I am maybe missing  that someone already done it as it is a blatantly obvious missing piece. I ask as I dont want to reinvent the wheel if it already exists.

I understand you avoid qjackctl, otherwise you could perhaps use it to save your patching and recall it when the card is reconnected. Maybe using udev and jack_plumbing you could achieve something similar?

I am by no means a jack expert so please don’t take my word for this being a good solution. Just some ideas off the top of my head. 

Regards,
Anders





_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Thomas Brand
In reply to this post by liebrecht
On Sat, March 30, 2019 04:45, [hidden email] wrote:
> Question
> Is there a daemon available that monitors the usb device 1818vsl in my
> case and then reconnects if the device is unplugged and replugged ?
>

I think it's not that simple. If jack looses its backend, there's nothing
to connect to, no clock etc. Even if jack can take care of the time where
no backend is available, if a new backend is attached, it might have a
different SR or different buffersize. Clients aren't usually prepared for
that. The best a client can do is listen to server shutdown messages, wait
for the server to come back and eventually re-initialize according to new
jack SR/buffer size.

> If not, I will have to write such daemon for my own purposes and it is
> no sweat doing it, but just wondered if I am maybe missing  that someone
> already done it as it is a blatantly obvious missing piece. I ask as I
> dont want to reinvent the wheel if it already exists.

There is another missing bit, AFAIK the alsa devices don't have a unique
id, it makes it almost impossible to create fixed relationships between
devices and other logic. I don't want to say that its impossible but if it
would be easy it would possibly already exist. That said .. i saw people
ripping of the audio interface / swapping on Apple computers and the
system somehow managed to not go into strange state.

Greetings
Thomas



_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Jeremy Jongepier
In reply to this post by liebrecht
On 3/30/19 4:45 AM, [hidden email] wrote:

> So Jack routes from Alsa and Alsa handles the USB 1818VSl directly.
>
> Problem:
> If I plug out the 1818vsl (my main sound card) usb plug, then jack
> disconnects although it is not directly handling the usb device but alsa
> is.
> If I reconnect jack does not reconnect, so I have to go then through my
> startup script and restart jack after which it all works again.
>
> Question
> Is there a daemon available that monitors the usb device 1818vsl in my
> case and then reconnects if the device is unplugged and replugged ?
Maybe you can find some pointers here: http://gareus.org/blog/jack2dbus

Jeremy


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Fons Adriaensen-3
In reply to this post by Thomas Brand
On Sat, Mar 30, 2019 at 11:26:24AM +0100, Thomas Brand wrote:

> I think it's not that simple. If jack looses its backend, there's nothing
> to connect to, no clock etc. Even if jack can take care of the time where
> no backend is available, if a new backend is attached, it might have a
> different SR or different buffersize.

Actually I think something could be done without too much complexity.

* When Jack detects that a backend goes away, it switches to a 'dummy'
  one with the same sample rate, buffer size, and number of channels.
  Basically this is the same as freewheeling, except that waiting for
  a timer would be inserted in between cycles.

* When the backend is available again, there is a single API call
  that re-initiliases it with the existing parameters. Once this is
  done, Jack switches back.

Apart from signalling the events (again similar to freewheeling) this
could be transparent to clients.


--
FA


 


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Thomas Brand
On Sat, March 30, 2019 13:25, Fons Adriaensen wrote:

> On Sat, Mar 30, 2019 at 11:26:24AM +0100, Thomas Brand wrote:
>
>
>> I think it's not that simple. If jack looses its backend, there's
>> nothing to connect to, no clock etc. Even if jack can take care of the
>> time where no backend is available, if a new backend is attached, it
>> might have a different SR or different buffersize.
>
> Actually I think something could be done without too much complexity.
>
>
> * When Jack detects that a backend goes away, it switches to a 'dummy'
> one with the same sample rate, buffer size, and number of channels.
> Basically this is the same as freewheeling, except that waiting for
> a timer would be inserted in between cycles.
>
> * When the backend is available again, there is a single API call
> that re-initiliases it with the existing parameters. Once this is done,
> Jack switches back.
>
>
> Apart from signalling the events (again similar to freewheeling) this
> could be transparent to clients.
>
>
Good idea, instead of shutting down, the server would just go into
freewheeling (which clients should be able to handle transparently) until
a new backend is attached.
If server operation would be separated from backend (freely attach /
dettach), this would open up new possibilities.
On a related note, I thought about jack to fall back to dummy interface
every time a normal start isn't possible. We could guarantee that jack can
always be started, and if backends can be freely swapped, this wouldn't be
a problem (just attach one later). Just thinking out loud.

Greetings
Thomas


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Robin Gareus
In reply to this post by liebrecht
On 3/30/19 4:45 AM, [hidden email] wrote:

> So Jack routes from Alsa and Alsa handles the USB 1818VSl directly.
>
> Problem:
> If I plug out the 1818vsl (my main sound card) usb plug, then jack
> disconnects although it is not directly handling the usb device but alsa
> is.
> If I reconnect jack does not reconnect, so I have to go then through my
> startup script and restart jack after which it all works again.
>
> Question
> Is there a daemon available that monitors the usb device 1818vsl in my
> case and then reconnects if the device is unplugged and replugged ?

Yes, dbus-deamon and udevd. For the case at hand dbus is more practical,
because since it can trigger events as the user running jack and you can
also use jack2's dbus interface to change backends. Furthermore jack2
already signals a device errors via dbus.

It is also possible to re-configure jack2 backends and devices on the
fly, and call 'switch-master' to apply the new settings. Have a look at
`jack_control`.

Alas, there is no canned solution to tie this all together in a generic
way. It is however relatively easy to roll your own for a specific system.

The main issue is retaining and mapping connections to physical I/O. The
ports are owned by the jack-driver, and when switching backends or
drivers, the ports are re-created and connections are lost.

That being said, a demo of a prototype from 2010/11:
http://robin.linuxaudio.org/tmp/jackdbus.ogv

I wrote a few scripts and patches back then, but most of that is
meanwhile upstream in jackd2 and direct dbus calls have been superseded
by jack_control. -- I expect it'll be easier to start afresh.

HTH,
robin
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Fernando Lopez-Lezcano
In reply to this post by Fons Adriaensen-3
On 3/30/19 5:25 AM, Fons Adriaensen wrote:

> On Sat, Mar 30, 2019 at 11:26:24AM +0100, Thomas Brand wrote:
>
>> I think it's not that simple. If jack looses its backend, there's nothing
>> to connect to, no clock etc. Even if jack can take care of the time where
>> no backend is available, if a new backend is attached, it might have a
>> different SR or different buffersize.
>
> Actually I think something could be done without too much complexity.
>
> * When Jack detects that a backend goes away, it switches to a 'dummy'
>    one with the same sample rate, buffer size, and number of channels.
>    Basically this is the same as freewheeling, except that waiting for
>    a timer would be inserted in between cycles.
>
> * When the backend is available again, there is a single API call
>    that re-initiliases it with the existing parameters. Once this is
>    done, Jack switches back.
>
> Apart from signalling the events (again similar to freewheeling) this
> could be transparent to clients.

Sounds great to me. I have occasionally made that mistake - unplug
something while forgetting jack is running and that, worst case, can
screw the machine up (recoverable but still a pain - jackd2 uses 100% of
a cpu and everything is very very slow).

Switching back and forth to the dummy driver sounds like a good solution
to a real problem.

Probably not so easy if/when you switch cards, but well, to recover from
plug/unplug of the same card it would be worth it.

-- Fernando

_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Jack/USB cycle of USB output Sound device.

Fons Adriaensen-3
On Sat, Mar 30, 2019 at 02:12:14PM -0700, Fernando Lopez-Lezcano wrote:
 
> Switching back and forth to the dummy driver sounds like a good solution to
> a real problem.

Just a detail: I do no propose switching to the standard dummy driver.
It should be sufficient to implement a variation of the freewheeling mode.

> Probably not so easy if/when you switch cards, but well, to recover from
> plug/unplug of the same card it would be worth it.

The use case I had in mind is to recover quickly from an accidental
disconnect. I remember at least two times in a 'live' situation someone
pulling the power lead to an external sound card. It's kind of silly
that even 'pro' gear which has XLRs for the audio uses a $0.50 plastic
connector and a flimsy cable for the wall wart...

Ciao,

--
FA





_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
12