Moode Forum
moOde release 4.1 - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: moOde release 4.1 (/showthread.php?tid=24)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12


RE: moOde release 4.1 - Tim Curtis - 04-08-2018

Hi,

Yes, I'm able to repro this on my 24" ASUS monitor which suggests maybe an issue with the local Chrome Browser and the CSS used for the buttons however the buttons render correctly on the PI Touch using same local Chrome Browser. Very odd.

Also when I set my monitors resolution 1920x1200 in my viewport simulator and use Safari the buttons render correctly.

We will have to wait until @swizzle can get a change to noodle this one.

-Tim


RE: moOde release 4.1 - patrik96 - 04-08-2018

(04-08-2018, 08:13 PM)Tim Curtis Wrote: Hi,

After a succecful 4.1 upgrade my NAS not accesibile anymore, It has CIFS, NFS share what is working before upgrade
I try to set the vers=1.0,sec=ntlm,ro,dir_mode=0777,file_mode=0777 to vers 2 and 3 without succes.  have a same problem before the New Volumio, and that is the case why I swiched to Moode, what is far better sonically! I like to use Moode again!
The error is: 20180408 222803 wrk_sourcemount(): Mount error: (mount error: could not resolve address for 01A500: Unknown error)

Thanks BR



RE: moOde release 4.1 - Tim Curtis - 04-08-2018

When the NAS config fails and u reopen it, what is the error that appears at the bottom of moode log?


RE: moOde release 4.1 - JST1963 - 04-08-2018

Hi moOde fans,


RE: moOde release 4.1 - patrik96 - 04-08-2018

(04-08-2018, 08:28 PM)Tim Curtis Wrote: When the NAS config fails and u reopen it, what is the error that appears at the bottom of moode log?
Here it is:
20180408 224818 worker: Job sourcecfg
20180408 224818 wrk_sourcemount(): Mount error: (mount error: could not resolve address for 01A500: Unknown error)
20180408 224824 wrk_sourcemount(): Mount error: (mount.nfs: Failed to resolve server 01A500: Name or service not known)
20180408 224824 wrk_sourcemount(): Mount error: (mount error: could not resolve address for 01A500: Unknown error)
20180408 224824 src-config: remount: (unmountall initiated, mountall initiated)


RE: moOde release 4.1 - Tim Curtis - 04-08-2018

The error suggests DNS resolve issue. What are the entries on the Network config screen?


RE: moOde release 4.1 - swizzle - 04-08-2018

(04-08-2018, 08:13 PM)Tim Curtis Wrote: We will have to wait until @swizzle can get a change to noodle this one.

If you remove the “width:110px” part of the volbtns rule set in panels.css (/var/local/www/cssw) around line 182 it should behave as expected.

The +/- staying fixed on the screen while everything else scrolls is to work around a bug in Chrome, the next version will hopefully fit the playback screen onto a landscape phone screen so the unlikely event of scrolling that page should be even less common.

The timeline thumb should work, but the screen shot posted looks weird, e.g. the thumb is too small compared to how it should look, try clearing cache maybe? It should be more like the size in the following pic but grey instead of white and without the two color line (that’ll come in 4.2) - edit it also won’t work on a radio stream for obvious reasons:

[Image: za9lv.png]


RE: Update 4.0 -> 4.1 - rikardo1979 - 04-09-2018

(04-08-2018, 06:03 PM)TomWoB Wrote: Hi all,

my update from 4.0 -> 4.1 worked fine on a "Pi-2B 1GB v1.2" (duration 28 minutes) !

I wanted to attach the complete log-file of the installation for reference but "*.txt* or "*.log" files are not allowed to attach (?) ... why ?

Regards
Tom

If you like to share log files please post it to https://pastebin.com/ and attach URL link here. 
Thanks


RE: moOde release 4.1 - jmarcusg - 04-09-2018

1) Ran SSH update on a RPi Model 3 B and received the following below:
2) Ran sudo apt-get update (rebooted) and sudo apt-get update --fix-missing (rebooted)
3) S Y S T E M    P A R A M E T E R S  

Date and time = 2018-04-08 21:04:40
System uptime = up 5 minutes
Timezone = America/New_York
moOde = Release 4.0 2018-01-26

Any ideas?


Code:
E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/ffmpeg/libavcodec57_3.2.10-1~deb9u1+rpt1_armhf.deb  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:522cac06e1585ac41c6d76375b77c925eb5c220ec6a5c28ba51d6e86273bd713
   - SHA1:9f790e57c0b7fd9916ec0199745a8de4beca9b44 [weak]
   - MD5Sum:ac94aae02ac0d8b8b69d4ffb5b863c8a [weak]
   - Filesize:4150504 [weak]
  Hashes of received file:
   - SHA256:312ced8614029178772ba1026bd1f00c40f70868d3941a8e2075bf1d8ab55039
   - SHA1:d1ab8567d5e16e2992c4d74c1ac00a1aeb3c2045 [weak]
   - MD5Sum:d4a44a6bae297fafaa1b1a61d4903270 [weak]
   - Filesize:450560 [weak]
  Last modification reported: Fri, 02 Feb 2018 09:47:54 +0000
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
** Package upgrade failed
** Exiting update
Update installed, REBOOT required
pi@moode:~ $



RE: moOde release 4.1 - jmarcusg - 04-09-2018

(04-09-2018, 01:07 AM)jmarcusg Wrote: 1) Ran SSH update on a RPi Model 3 B and received the following below:
2) Ran sudo apt-get update (rebooted) and sudo apt-get update --fix-missing (rebooted)
3) S Y S T E M    P A R A M E T E R S  

Date and time = 2018-04-08 21:04:40
System uptime = up 5 minutes
Timezone = America/New_York
moOde = Release 4.0 2018-01-26

Never mind. I re-ran the script and it appears the install was successful this time.

Date and time = 2018-04-08 21:55:33
System uptime = up 2 minutes
Timezone = America/New_York
moOde = Release 4.1 2018-04-02

Marc