Activity

1. wmedrano commented on Mar 5, 2025

   

   wmedrano

   on Mar 5, 2025

   Last edited by wmedrano

   Member

   More actions

   New function! jack_port_rename

   jack_port_rename isn't the in the bindings for jack_sys, so its probably relatively new. I probably need to make a cookbook for updated the bindings in a way that supports both dynamic_loading true/false and doesn't break any users.

   If you want to load it dynamically at runtime:

   • This is what happens when dynamic_loading feature is enabled, which is by default.
   • https://docs.rs/jack-sys/latest/jack_sys/fn.library.html
     • The underlying jack_sys package is re-exported as jack::jack_sys.
     • The type here is unsafe extern "C" fn(*mut jack_port_t, *const ::libc::c_char) -> ::libc::c_int;

   Calling Requirements

   • I'm not sure if Rust has a way to guarantee this, will ask around, but best hacky ideas I have at the moment are either:
     • Add Port::rename as unsafe.
     • Create an object that marks the scope as being outside of callback handling.
       • Mark its creation as unsafe.
2. teodly commented on Mar 19, 2025

   

   teodly

   on Mar 19, 2025

   Author

   More actions

   I have locally changed Port::set_name implementation to use jack_port_rename and... the port was successfully renamed in pw-dump, but jack_lsp, qpwgraph and Carla were still showing the old name. So it looks like renaming ports in PipeWire doesn't work no matter which method is used.