!IlMdvXrwPGkeeOuMDw:matrix.org

Shortwave

166 Members
Find and listen to internet radio stations - Homepage: https://gitlab.gnome.org/World/Shortwave19 Servers

Load older messages


SenderMessageTime
5 Feb 2025
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix pushed 2 commits to shortwave5 (new branch): 10:44:52
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix opened merge request !503: Release Shortwave 5.0.0 10:45:32
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] guidog opened issue #763: Please offer station icon via mpris API

The station icon is currently a http URL. Since shortwave already fetched it, it would be nice if it'd export the artUrl as data:<base64> thus freeing e.g. desktop shells from making another https request to refetch the data (thus opening another attack window by spoofing the data on a http connection when the player widget is e.g. used on a lock screen).

12:12:24
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] guidog changed the title of issue #763 to Please offer station icon via mpris API as `data:` 12:12:35
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix merged merge request !503: Release Shortwave 5.0.0 12:37:53
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix pushed 2 commits to main: 12:37:53
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix created tag 5.0.0 12:38:48
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix deleted tag 5.0.0 12:39:01
@gitlab:t2bot.ioGitlab Notifications * [World/Shortwave] haecker-felix created tag 5.0.0 :

Release 5.0.0

12:39:20
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] daPhipz opened merge request !504: Reword string for less ambiguity

I hope that I matched your type of commit messages correctly ;)

Now that the 5.0.0 release is out of the way (happy release day, btw! :tada: ), the string from #762 can be fixed.

12:56:27
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix commented on merge request !504: Reword string for less ambiguity

Thanks!

12:57:00
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix pushed 2 commits to main:
  • dc728209 Reword string for less ambiguity by Philipp Kiemle
  • a9ea58c7 Merge branch 'daPhipz-main-patch-41840' into 'main' […]
12:57:10
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix merged merge request !504: Reword string for less ambiguity 12:57:10
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] tonekaboni commented on issue #547: shortwave does direct output to different audio device

Hi,

I could reproduce it with Shortwave from Nightly (5) on Bluefin (F41) and with Shortwave stable (4). But I could only reproduce it, when a Bluetooth Headphone was connected.

I never discovered this problem in other apps. I tried Amberol and Decibel and couldn't reproduce the problem. Could it be a python related problem?

Setup:

  • USB Headset (Logitech PC 8)
  • Audio out of external Display via DisplayPort (HDMI/DisplayPort) (no USB-C)
  • Optional: Bluetooth headphones (Sennheiser HD 4.50R)
  1. Start Shortwave (or another audio app)
  2. Play a station (or audio file)
  3. Open Gnome Settings, Audio
  4. Switch Output Device

Shortwave only follow the change, when the previous used output (the one to which Shortwave sticks) was chosen again. After that it follows the output change as expected. (Like if it would unset the individual setting and follow the desktop preset again)

Without the BT headphone Shortwave 4 and 5 acted as expected.

13:54:52
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] tonekaboni commented on issue #547: shortwave does direct output to different audio device

Hi,

I could reproduce it with Shortwave from Nightly (5) on Bluefin (F41) and with Shortwave stable (4). But I could only reproduce it, when a Bluetooth Headphone was connected.

I never discovered this problem in other apps. I tried Amberol and Decibel and couldn't reproduce the problem. Could it be a python related problem?

Setup:

  • USB Headset (Logitech PC 8)
  • Audio out of external Display via DisplayPort (HDMI/DisplayPort) (no USB-C)
  • Optional: Bluetooth headphones (Sennheiser HD 4.50R)
  1. Start Shortwave (or another audio app)
  2. Play a station (or audio file)
  3. Open Gnome Settings, Audio
  4. Switch Output Device

Shortwave only follow the change, when the previous used output (the one to which Shortwave sticks) was chosen again. After that it follows the output change as expected. (Like if it would unset the individual setting and follow the desktop preset again)

Without the BT headphone Shortwave 4 and 5 acted as expected.

(with another computer, FW Laptop and USB-C connected Display, I couldn't reproduce the behaviour)

13:56:15
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] jfft replied to a thread on issue #547: shortwave does direct output to different audio device

@haecker-felix today I asked around, and Philippe kindly pointed to a recent addition in GStreamer that would make this easier: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/08057e0

14:18:19
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] jfft replied to a thread on issue #547: shortwave does direct output to different audio device

@haecker-felix today I asked around, and Philippe kindly pointed to a recent addition in PipeWire that would make this easier: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/08057e0

14:18:36
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] jfft replied to a thread on issue #547: shortwave does direct output to different audio device

@haecker-felix today I asked around, and Philippe kindly pointed to a recent addition in PipeWire+GStreamer that would make this easier: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/08057e0

14:19:33
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix replied to a thread on issue #547: shortwave does direct output to different audio device

That may help, but I wonder more why Shortwave sometimes doesn't follow the the default output device to begin with. I don't have any logic or similar implemented which influences the output device. Not sure if I want to "hardcode" that Shortwave always uses the default device, because there are legit cases when you want to change it, for example using pavucontrol.

And I'm not sure if I'm able to use this, as I'm using the gstreamer pulsesink element.

Apps that are not affected today just happen to already have implemented the required fix

But it would be good if you could name some example here, then I can have a look how they resolved it.

14:39:45
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix replied to a thread on issue #547: shortwave does direct output to different audio device

I don't think it's related to Bluetooth, as I was able to reproduce it with a dummy output. Often it's enough to start playback, change the output device, stop/start the playback - and then quite often Shortwave starts playing on the previous output device again instead of using the new selected one.

14:42:11
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] haecker-felix commented on merge request !502: Adds Previous/Next MPRIS commands

Please don't modify code which is not related to your MR. I know that there's a cargo-deny issue with smol-timeout, but that's not related to your MR - no need to fix that.

Beside that, I'm not sure if I like the idea. It has some problems:

  • It doesn't make sense semantically. For example, if I press the MPRIS previous button, I'd expect that it plays the previous played track - just like any other MPRIS music player, and not changing the currently played live stream.
  • What actually means "previous" / "next" here? For example in this case when "BBC Radio 4" gets played, I'd assume that the previous station is "BBC Radio 2" and the next one is "BBC World Service".

But that differs when you change the station sorting:

I'm not convinced by the idea of "misusing" MPRIS buttons, just because they provide some way to interact with the application.

14:59:59
@batwam:matrix.org@batwam:matrix.org I can confirm that the issues I had with the gnome extension are now solves with the update on Identity and CanPause. Thank you very much! 15:25:07
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] cxorg replied to a thread on merge request !502: Adds Previous/Next MPRIS commands

Hi,

I will leave the resolution of pipeline build/test issues for you to manage which are not directly related to this feature.

I get the impression you are testing an initial build I made which did not work with the selected sort order of saved favourites. It seemed to be the order the tracks/stations were added to the DB. Check the current commit 1c26b1c13b03829368c06cbe2eb977b5bb7d50d2

The last build submitted works with the selected sort order as seen in the interface. In addition, if a station is playing then next will move to the next station in favourites and play, otherwise the selection is simply shifted without playing.

The behaviour is in line with other media players I have to hand on both Linux and Android. In use I'm happy with this behaviour.

If you have other ideas, let me know?

16:00:02
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] pvagner commented on issue #595: Use opus as recording codec

Alternativelly would it be doable to avoid reencoding and save the recordings using the same codec parameters from the source stream?

23:52:34
6 Feb 2025
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] translations pushed 1 commit to main:
  • 0003ebc7 Update Italian translation by Davide Ferracin
19:33:56
7 Feb 2025
@batwam:matrix.org@batwam:matrix.org left the room.00:44:35
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] ilippert commented on issue #464: Network change/loss: Playback does not recover

Another obvious challenge is that Shortwave in the current state cannot recover from turning on/off a VPN connection.

10:30:01
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] ilippert replied to a thread on issue #464: Network change/loss: Playback does not recover

for me pressing the keyboard's play/pause key does manage to restart the sound, version 5.0.0

10:31:05
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] gitlabamrit opened issue #764: Increase Maximum Recording Duration

Some tracks that I want to record exceed the existing 30 min duration limit.

Can the maximum duration be extended to 60 min? Is there any particular reason 30 min was selected?

Thanks.

13:37:10
@gitlab:t2bot.ioGitlab Notifications [World/Shortwave] translations pushed 1 commit to main:
  • 6eed798a Update Finnish translation by Jiri Grönroos
14:27:21

There are no newer messages yet.


Back to Room ListRoom Version: