RaySession icon indicating copy to clipboard operation
RaySession copied to clipboard

Buffer cannot be changed anymore from ray session

Open rgbeitor opened this issue 10 months ago • 4 comments

Hi:

First, thank you for your work and the nice software. I've been using RaySession for several years already.

The issue: As the title says. I cannot change anymore the buffer in the RaySession GUI. It seems that it is trying it but reverts back to the original.

It was possible before (same sound card/mixer).

It is still possible if I use:

pw-metadata -n settings 0 clock.force-quantum 512

as regular user. This one changes buffer size to 512 specifically, but other values work as well.

Just for reference:

OS: Ubuntu 24.04.2 LTS (Ubuntu Studio). RaySession version: 0.14.3

Thanks in advance

rgbeitor avatar Mar 10 '25 09:03 rgbeitor

Hi ! I did not changed anything about buffersize change for a long. So, I really don't know what it could be. What happens if you launch raysession from the command line and try to change buffersize ?

Houston4444 avatar Mar 10 '25 20:03 Houston4444

Hi.

Thank you for the quick answer.

Well, I was checking minutes ago and... it happens almost nothing!

See: this is the output without debug:

rgb@merak:~$ raysession 
[ray-daemon]GUI connected at osc.udp://merak:16332/
[ray-daemon]URL : osc.udp://192.168.100.9:16187/
[ray-daemon]      osc.udp://merak:16187/
[ray-daemon]ROOT: /home/rgb/Ray Sessions
^C[ray-daemon]Bye Bye...

(before ^C, I was changing the buffer in the GUI)

And this is the output with debug mode.

rgb@merak:~$ raysession --debug
OSC::daemon sends ('/ray/gui/server/announce', '0.14.3', 0, 236, '/home/rgb/Ray Sessions', 1)
OSC::daemon sends ('/ray/gui/server/status', 0)
OSC::daemon sends ('/ray/gui/session/name', '', '')
OSC::daemon sends ('/ray/gui/session/notes', '')
OSC::daemon sends ('/ray/gui/server/terminal_command', 'konsole --hide-tabbar --hide-menubar --hold -p tabtitle=RAY_TERMINAL_TITLE -e')
OSC::gui_receives /ray/gui/server/announce, siisi, ['0.14.3', 0, 236, '/home/rgb/Ray Sessions', 1], osc.udp://127.0.0.1:16187/
OSC::gui sends ('/ray/server/ask_for_patchbay',)
OSC::gui_receives /ray/gui/server/status, i, [0], osc.udp://127.0.0.1:16187/
OSC::daemon_receives /ray/server/ask_for_patchbay, , [], osc.udp://127.0.0.1:16384/
OSC::gui_receives (/ray/gui/session/name, ['', ''], ss)
OSC::daemon_receives /ray/server/ask_for_patchbay, , [], osc.udp://127.0.0.1:16384/
OSC::daemon sends ('/minor_error', '/ray/server/ask_for_patchbay', -18, 'unknown osc message: /ray/server/ask_for_patchbay ')
OSC::gui_receives (/ray/gui/session/notes, [''], s)
OSC::gui_receives (/ray/gui/server/terminal_command, ['konsole --hide-tabbar --hide-menubar --hold -p tabtitle=RAY_TERMINAL_TITLE -e'], s)
OSC::gui_receives (/minor_error, ['/ray/server/ask_for_patchbay', -18, 'unknown osc message: /ray/server/ask_for_patchbay '], sis)
OSC::daemon sends ('/ray/gui/patchbay/fast_temp_file_memory', '/tmp/tmpens9cxo8')
OSC::gui_receives (/ray/gui/patchbay/fast_temp_file_memory, ['/tmp/tmpens9cxo8'], s)
OSC::daemon sends ('/ray/gui/server/recent_sessions', 'finger_drumming_A', 'virus_microq_microwave', 'bristol_arp2600', 'test_XR18_sends_returns', 'cardinal_iannix_generative_modular', 'zynthian_ports_7-8')
OSC::daemon sends ('/ray/gui/server/message', 'daemon runs at osc.udp://merak:16187/')
[ray-daemon]GUI connected at osc.udp://merak:16384/
OSC::gui_receives /ray/gui/server/recent_sessions, ssssss, ['finger_drumming_A', 'virus_microq_microwave', 'bristol_arp2600', 'test_XR18_sends_returns', 'cardinal_iannix_generative_modular', 'zynthian_ports_7-8'], osc.udp://127.0.0.1:16187/
OSC::gui_receives (/ray/gui/server/message, ['daemon runs at osc.udp://merak:16187/'], s)
[ray-daemon]URL : osc.udp://192.168.100.9:16187/
[ray-daemon]      osc.udp://merak:16187/
[ray-daemon]ROOT: /home/rgb/Ray Sessions
OSC::gui_receives /ray/gui/patchbay/announce, iii, [1, 48000, 1024], osc.udp://127.0.0.1:17887/
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [0], i)
OSC::gui_receives (/ray/gui/patchbay/transport_position, [0, 0, 0, 0, 0, 0, 0.0], iiiiiif)
OSC::gui_receives (/ray/gui/patchbay/fast_temp_file_running, ['/tmp/tmprmzvui7j'], s)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [2], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)
    

OSC::gui sends ('/ray/patchbay/set_buffer_size', 256)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [2], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)
OSC::gui sends ('/ray/patchbay/set_buffer_size', 128)

It seems to get the order to change to 256 or 128, but it doesn't work. You can change it, but in a couple of seconds, the buffer box fades to grey and after this, back to the original resolution (1024) in my case.

If I change the buffer from other terminal with:

rgb@merak:~$ pw-metadata -n settings 0 clock.force-quantum 512
Found "settings" metadata 31
set property: id:0 key:clock.force-quantum value:512 type:(null)

the result is very similar but not exactly the same.

OSC::gui_receives (/ray/gui/patchbay/dsp_load, [2], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [2], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)
OSC::gui_receives (/ray/gui/patchbay/buffer_size, [512], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [2], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [3], i)
OSC::gui_receives (/ray/gui/patchbay/dsp_load, [1], i)

And this is actually changing the buffer size.

It looks like the OSC is not communicating well with the pipewire daemon...

Is there a way to change the level of "verbosity" of the debug mode?

Is there any other test that I can try?

BR

rgbeitor avatar Mar 10 '25 23:03 rgbeitor

Mmmh, something is very strange. Daemon receives twice /ray/server/ask_for_patchbay, although GUi sends this only one time.

OSC::daemon_receives /ray/server/ask_for_patchbay, , [], osc.udp://127.0.0.1:16384/

and the second time it says it does not know this message.

OSC::daemon sends ('/minor_error', '/ray/server/ask_for_patchbay', -18, 'unknown osc message: /ray/server/ask_for_patchbay ')

I don't understand how it is possible, but it may be totally unlinked to your problem.

Here, you uses the last release (v0.14.3), it would be interesting to try what happens if you build the master branch from source. You can try it without installing, launching ./src/bin/raysession from source code directory. If you do that, I suggest to not open your working sessions, otherwise you may have problems re-opening them with last release version.

Houston4444 avatar Mar 11 '25 10:03 Houston4444

Hi again, sorry for the delay answering.

I'll try to build it from source. It is important for me to not lose the previous sessions.

I'll come back here with the results.

Thanks for your support so far.

rgbeitor avatar Mar 13 '25 14:03 rgbeitor