Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

fatg3erman / RompR

Web client for Mopidy and MPD

WebUI doesn't update #90

BuckyTheElder ·
#1

I've updated to RompR2.x and everything looks and works fine, except the auto-updating elements such as the progress bar and the time display when playing music. Also, the marker in the playlist doesn't go to the next song when one song is finished and it starts playing the next.

My RompR runs on an embedded board (NanoPi M4v2) under Gentoo Linux and Apache, no Systemd, so not quite the standard setup. But maybe you could point me to the things responsible for updating the UI elements so I can find what keeps them from working.

I already enabled debugging but since it all happens (or doesn't happen) in the browser the logs don't show anything unusual.

Thanks in advance

Bucky

  • replies 4
  • views 291
  • likes 0
Mark Greenwood fatg3erman · Team
#2

You'll be wanting to look in the browser console with debug enabled. It's all run on timers from there. Which browser are you using? Older browsers, or ones that don't implement certain javascript features, won't work.

BuckyTheElder · Author
#3

I'm getting the same behaviour in different browsers (Firefox, Chrome, Opera, all current versions). I've kept the RompR 1.61 instance on my web server, as backup. This version displays time, progress bar etc. correctly.

If I set debug.setLevel(7); in the browser's console, it replies "Debugging set to debug. Aren't you clever?" and nothing else happens, while on 1.61 it frequently prints lines like these:

15:45:46.124 15:45:46 : PLAYER Command List
Array []
debug.js:53:34
15:45:46.264 15:45:46 : PLAYER Got response for
Array []

Object { volume: "73", repeat: "0", random: "0", single: "0", consume: "0", playlist: "39", playlistlength: "3", mixrampdb: "0.000000", state: "play", song: "0", … }

BuckyTheElder · Author
#4

OK, found it. RompR2 loaded the mopidy player (I'm using mpd) and decided to do so because the websocket port was set. After going through the setup page again and clearing the websocket field it switched to mpd and now updates everything correctly.

Cheers

Mark Greenwood fatg3erman · Team
#5

OK that makes sense. It will load the mopidy player if you configure the websocket. The fact it wasn't responding means the mpd websocket server isn't running for some reason. It's not essential but it will work better with it.

Using RompЯ with MPD

A beautiful, feature-rich music player.

fatg3erman.github.io