You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the tests I was having some trouble with "test_bt_sequence_ticks". That test creates a song with a simsyn, and a simple pattern that modifies its "wave" parameter. The test then attaches a signal to the element's "notify::wave" and plays the song to test whether the element's properties are updated properly by the playing song. The test fails currently because no updates happen.
I have not been able to get callbacks by manually attaching to "notify::wave", i.e. just in gstbt_sim_syn_init, and I noticed that the Machine Properties Dialog isn't updating when machine parameters change from song patterns. Has something changed/broken in GStreamer to do with notify::* callbacks recently that stops them firing?
I'll create a small GStreamer test program to find out more, but just putting this bug here in the meantime in case someone knows more.
This test is indeed not working for me either. I've should have disabled it with a comment. I worked at some point, but so far I was not able to figure out whats wrong.
verify that the automation is changing the simsyn:wave property and not the proxied osc:wave property (this would explain why it works, but we don't see the UI changing)
While working on the tests I was having some trouble with "test_bt_sequence_ticks". That test creates a song with a simsyn, and a simple pattern that modifies its "wave" parameter. The test then attaches a signal to the element's "notify::wave" and plays the song to test whether the element's properties are updated properly by the playing song. The test fails currently because no updates happen.
I have not been able to get callbacks by manually attaching to "notify::wave", i.e. just in gstbt_sim_syn_init, and I noticed that the Machine Properties Dialog isn't updating when machine parameters change from song patterns. Has something changed/broken in GStreamer to do with notify::* callbacks recently that stops them firing?
I'll create a small GStreamer test program to find out more, but just putting this bug here in the meantime in case someone knows more.
Here's the song I've been using to test: test_bt_sequence_ticks.txt
The text was updated successfully, but these errors were encountered: