Plexamp nice until it stops working, which is often

Plex Labs
,
1

i use plexamp on a few different macs (1.1.0 on 10.14.[23]/mojave) and windows 10, both local playback. sometimes when i’m remote, sometimes when i’m local (on the same subnet as my server). i like the media controls on the keyboard, it’s a better experience for me than the browser. the full plex client isn’t installed, only plexamp. server is centos 6.9 running whatever is available to plexpass users, currently 1.14.1.5488

on macos:

  • many times, it will stop mid-song. restarting the app doesn’t fix it. sometimes logging out and logging back in fixes it. i usually just give up for a while, try another day and forget my previous troubles.
  • sometimes starting the app gives me an empty server list, which can only be resolved by logging out/in
  • discovery bar: main screen lets me browse all music. if i click on an a current song title, it takes me to the album and song list. if i click discovery bar it gives me an empty list. why not the same behavior as the main screen? :slight_smile:

both macos/windows:

  • when i’m on the same subnet as my server, why am i fed through the remote plex proxy service? I can netcat the server on port 32400 directly and get a response. (having to stream out and stream in content is a bit ridiculous, especially in the days of metered internet connections). i can get direct playback via browser.
  • when i’m remote from the server, and i can do direct playback from the browser, but i’m still forced through the plex proxy service. again, netcat to server:port works correctly.

what additional info do you need from me?

thanks!

2

We’d need to see logs to try to figure out what’s going on here. The upcoming v2.0 has a completely new player with better caching, which can help in some cases.

Unless it’s an auth issue (which is unlikely), this shouldn’t have any effect, so the fact that it “fixes” it is probably coincidental.

I’m sorry, I don’t understand what you mean here by “click discovery bar it gives me an empty list.”

You’re not. The “proxy” is running in a separate process but as part of Plexamp itself.

1 Like
3

thanks. what logs?

4

I am pretty sure he is talking about the log.log file which exists in the installation directory.

5

Came here specifically to state I am so excited to hear a v2.0 is on the way. I just found this application today and it has been super amazing to have at work. *Sorry offtopic.

1 Like
6

so I started tailing Application.log in ~/Library/Logs/Plexamp, discovered that plexamp didn’t trust my custom cert (even though it’s trusted by all the browsers)

the application is much more responsive now. direct play works now as well.

i’m looking forward to the new version.

thanks for the hints :slight_smile:

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.