Yes I did. I have tried already everything. I checked usb ports using"lsusb" command and device is visible in the system:
Bus 001 Device 004: ID 20b1:000a XMOS Ltd
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Matt
Thank you for your help, however I cannot find the cause of this, will try again when 4.1 is out.
See post #14416 where there is a link to set up instructions.
Remember to use a good quality uSD card and preferably an ethernet connection rather than WiFi for setup.
Ian
cheap microSD cards
With my previous install of Moode 4.0 I found that I was getting drop outs in music replay, and I noted that I wasn't seeing similar reports.
Knowing that somewhere in this gargantuan thread I'd read a caution about cheap microSD cards, I did a fresh install on a Sandisk.
Problem solved !
With my previous install of Moode 4.0 I found that I was getting drop outs in music replay, and I noted that I wasn't seeing similar reports.
Knowing that somewhere in this gargantuan thread I'd read a caution about cheap microSD cards, I did a fresh install on a Sandisk.
Problem solved !
Problem probably sorted out. Have been wipe SD card and reinstall Moode again. Now "USB Audio device appears on the list.
Matt
Which specific file are you referring to?
I have several dsd64 and 128 files in my test collection and no issues with playback.
Hardware issues...
Have a few questions in regards to hardware issues I've been having.
1. Is there anything needed to be done, besides have the BT config switch on, to enable Bluetooth? I have had a Pi 3 for a while now, and have never been able to find the BT with my phone. Wondering if I have broken hardware on this Pi...
2. Recently, after finding out my fancy new case couldn't be fully assembled with a SD card in the socket, and then putting the SD card in when fully assembled would require tweezers... I removed a side panel to make it easier. This involved my laziness and some moderate force on said SD card in it's socket. Now, I have a flakey system that freezes, or is unresponsive. Have I damaged the SD card or socket? Got out the microscope and small soldering iron tip and reflowed the socket pins, but no joy. Will try other things, boards etc, later. Question here, is it possible to partially boot the system up, i.e. have the card lose its connection during boot, and have a mostly functioning player? Till you need to hit some part of the system that never got loaded? Trying to explain some of the behavior I'm seeing...
Have a few questions in regards to hardware issues I've been having.
1. Is there anything needed to be done, besides have the BT config switch on, to enable Bluetooth? I have had a Pi 3 for a while now, and have never been able to find the BT with my phone. Wondering if I have broken hardware on this Pi...
2. Recently, after finding out my fancy new case couldn't be fully assembled with a SD card in the socket, and then putting the SD card in when fully assembled would require tweezers... I removed a side panel to make it easier. This involved my laziness and some moderate force on said SD card in it's socket. Now, I have a flakey system that freezes, or is unresponsive. Have I damaged the SD card or socket? Got out the microscope and small soldering iron tip and reflowed the socket pins, but no joy. Will try other things, boards etc, later. Question here, is it possible to partially boot the system up, i.e. have the card lose its connection during boot, and have a mostly functioning player? Till you need to hit some part of the system that never got loaded? Trying to explain some of the behavior I'm seeing...
Software issues...
Have a few questions regarding behavior in the interface, to let know and to ask if they are expected in current Moode 4.0
1. I see a difference in the file player and volume control interfaces when my Android phone is in portrait or sideways positions. This I understand. I see behavioral differences between my desktop browser and the phone. Hmmm, Chrome on the phone, Firefox on the desktop. Maybe that's it? Big thing is, unlike discussions mentioned here earlier with the bar that does not update a number, or the sideways round knob bar that only changes with buttons, the desktop version will still slide the knob manually, volume adjusts continuously and the number adjusts smoothly as well. I thought that was gone in 4.0! Just browser dependant? Is the lack of these features a Chrome issue?
2. I have seen some kind of hidden bar or something in the lower half of the sideways/landscape orientation on the Android running Chrome. If I am in a config menu, and drop a drop menu, and the drop portion is in the lower third of the screen, the menu items are not visible. If you slide the screen up, so the drop menu is farther up the screen you will see the menu items appear as they get above the invisible border. Portrait mode does not have this problem, possibly because you don't have a display that's much longer than the screen. The invisible whatever seems to slide up and down a bit as you slide the screen up and down, but not by a large amount. The threshold where things appear or dissapear will move as you drag things up or down. I first noticed this with the Chip Selection menu since I got the Allo Boss, and was viewing the filter settings menu.
Will try to observe these things tomorrow, on Firefox for Android. Wondering if this might have to do with the earlier Chrome issues.
3. There are minor display scaling issues, like the Audio Info panel coming out just a bit larger than fitting on the screen, so you have to scroll a few lines, and similar. Will look to see if it's phone display size, think I'm on mid not full resolution, not sure if this changes the aspect ratio on my Galaxy 8... will experiment.
Have a few questions regarding behavior in the interface, to let know and to ask if they are expected in current Moode 4.0
1. I see a difference in the file player and volume control interfaces when my Android phone is in portrait or sideways positions. This I understand. I see behavioral differences between my desktop browser and the phone. Hmmm, Chrome on the phone, Firefox on the desktop. Maybe that's it? Big thing is, unlike discussions mentioned here earlier with the bar that does not update a number, or the sideways round knob bar that only changes with buttons, the desktop version will still slide the knob manually, volume adjusts continuously and the number adjusts smoothly as well. I thought that was gone in 4.0! Just browser dependant? Is the lack of these features a Chrome issue?
2. I have seen some kind of hidden bar or something in the lower half of the sideways/landscape orientation on the Android running Chrome. If I am in a config menu, and drop a drop menu, and the drop portion is in the lower third of the screen, the menu items are not visible. If you slide the screen up, so the drop menu is farther up the screen you will see the menu items appear as they get above the invisible border. Portrait mode does not have this problem, possibly because you don't have a display that's much longer than the screen. The invisible whatever seems to slide up and down a bit as you slide the screen up and down, but not by a large amount. The threshold where things appear or dissapear will move as you drag things up or down. I first noticed this with the Chip Selection menu since I got the Allo Boss, and was viewing the filter settings menu.
Will try to observe these things tomorrow, on Firefox for Android. Wondering if this might have to do with the earlier Chrome issues.
3. There are minor display scaling issues, like the Audio Info panel coming out just a bit larger than fitting on the screen, so you have to scroll a few lines, and similar. Will look to see if it's phone display size, think I'm on mid not full resolution, not sure if this changes the aspect ratio on my Galaxy 8... will experiment.
Last edited:
No that's a Borneo special.....left over from your last browser visit...
Like Rafa says....a caching issue ... clear your browsers cache and reboot for good measure then find all the goodness your enforced absence has deprived you of all these lost weeks...
Welcome back Mike...!
Thanks guys, that’s exactly what it was. I wasn’t sure if I had a broken build, but a bunch of reloads later and it’s all as it should be - the sweet, sweet UI I’ve grown to know and love
First a some obvious things for the Bluetooth
Integrated BT turned on in System Config?
Have you opened the Bluetooth config page and initialised BT, then scanned for devices?
Bluetooth enabled in Audio config - Renderers page?
Regarding the uSD card socket, if you have a usable image that allows you to get to System config you can enable USB boot, then an image on a USB stick or uSD card/USB adaptor can be used instead.
Hi @Headburger,
Yes, I've implemented this for moOde 4.1
-Tim
Thanks! good to know.
I just did sudo apt update then upgrade and it is working fine on the Rpi3 B+. However system info says it is an unknown Rpi so there are a few tweaks that can be done to make it more polished and complete.
Hi Kent, Tim,
the scrollbar starts oscillating when the songtext below the station logo is too long to fit in one line.
Michael
@Morias
Good to know.
Mine is supposed to arrive tomorrow afternoon and I know Tim ordered his before I did, so soon!
For your RPi3B+, what value does /proc/cpuinfo contain in the "Revision:" field? (elinux says it will be a020d3). The function getHdwrRev() in playerlib.php uses the last four digits of that value to determine the model descriptor string. Tim just needs to add one more value to the mapping array. You could do it yourself if you can't wait
Regards,
Kent