Skip to content

how do setJack, setJackConnect work with pipewire? #66

@jwaldmann

Description

@jwaldmann

On Fedora 35, with pipewire for audio routing:
I wanted to apply #61 (comment) but is does no longer work.

Standard operation is fine: When I just run dac $ osc 300, output ports csound:output_FL csound:output_FR do appear (visible with jack_lsp, and in qjackctl). I can connect them manually from the command line jack_connect 'csound:output_FL' 'Firefox:input_FL'.

But when I try this connection from within c-s-e, I get

Prelude Csound.Base> dacBy (setJackConnect [("csound:output_FL","Firefox:input_FL")]) $ osc 300
ERROR csound:output_FL not a valid port
^C

same with extra single quotes, and your suggested at (delaySig 1).

When I try to just re-name the output,

Prelude Csound.Base> dacBy (setJack "cse") $ osc 300

I expect it to produce sound as in the standard case, just with renamed csound ports. But I hear no sound at all, and there are no ports visible.


Hi Anton, I am again using csound-expression in my lecture. Because COVID, we switch to remote teaching, right this week, and all sorts of technical problems re-appear ... This thing here is not a blocker, as I can connect the ports manually, but that's quite inconvenient. What can I do to debug the above behaviour?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions