|
|
| Hello |
|
Posted by: lehuyv - 04-23-2024, 09:00 PM - Forum: Introduce Yourself
- Replies (1)
|
 |
Hi Everyone,
Here is my current setup
AUDIO DEVICE
Device: IQaudIO Pi-DigiAMP+
Mixer name: Digital
Chip: Burr Brown TAS5756
Interface: I2S
Formats: S16_LE, S24_LE, S32_LE
Platform: Pi-Zero W 1.1 512MB
So far so good, Like the simplicity of the software.
Cheers,
Huy
|
|
|
| Hello from Titonka, Iowa USA |
|
Posted by: ZZRuss - 04-22-2024, 12:44 AM - Forum: Introduce Yourself
- Replies (2)
|
 |
Hello MoOdeites and Pi people. The email said an introduction was in order.
My name is Russ, a retired radio/electronics technician now living in the big city of 500 in Titonka, Iowa. I’m an (almost) 40 year Amateur Extra holding the call KB8DPN. I’m a tech freak, and love things like Pi projects, computers, audio, etc. I’m here to learn. Ran across an old Pi 2 today that needed a function. A quick image burned to SD wit MoOde, and now have a new little server running on my network. Wonderful program, so much to learn and discover. I’m limited in sight, but still trying, although this stuff isn’t getting any bigger.
Anyway, hoping to make some new and interesting tech acquaintances, learn some new stuff and enjoy. It’s a pleasure to be here amongst all of you.
—Russ
|
|
|
|
| New user, trouble to create library to connect to a synology nas |
|
Posted by: sdess - 04-21-2024, 04:35 PM - Forum: Support
- Replies (4)
|
|
Hi,
I'm a new user of moOde. I just installed the last version on a raspberry pi 3 Type B.
I'm able to listen some music when I select a radio link, it's a good start.
I have a synology Nas. I created a new user and gave it access to a folder "music"
I'm able to connect to this folder with my windows 11, \\192.168.1.151\music + synology user et password.
There is a folder with 12 music files I'm able to listen on windows.
I tried to create a library like that on moode/configure/library :
Type : Samba
path : 192.168.1.151/music
userid : the ne synology user
Password : his password
name : musicnas.
When I hit scan, moode seems to find nothing.
So I addited the path mannually.
When I navigate to the folder musicnas, it's always empty.
I connected in ssh, I tried to mount the path, but this action has to by done un superuser. I don't have the root password. I assume that it's not necessary.
I don't know what to test next ...
Any help would be great.
Other question : I'm use to access my Nas music library thru Upnp. Does moode have this kind of access ?
Thank you.
Steeve
|
|
|
|
| Waveshare 7.9" HDMI Capacitive Touch Screen on Moode 9 |
|
Posted by: popeye65 - 04-21-2024, 01:20 PM - Forum: FAQ and Guides
- Replies (2)
|
|
I have built a Stealth V3 player, comprising a Raspberry 4b, a set of DC power supply, and a Waveshare 7.9" HDMI screen. This is a small how-to for Moode 9, currently tested on ~pre4 version. I will try to keep this updated after V9 is released. Basically it works for me and maybe it's not optimal, I'm not a guru in RPI hardware detection and firmware options.
Steps:
- setup the PI image, get ssh working
- adapt /boot/firmware/cmdline.txt /home/pi/.xinitrc as shown below
- reboot
- your console will scroll boot messages
- and start the GUI after a while (I still have to check if the 2 min I observe until the GUI is available is due to some timeout or the result of loading X11 and Chromium)
sudo vi /boot/firmware/cmdline.txt
Quote:#add this to the end of the line:
video=HDMI-A-1:400x1280M@60,rotate=90
# the full line should look similar to this, but might vary slightly
console=serial0,115200 console=tty1 root=PARTUUID=92517673-02 rootfstype=ext4 fsck.repair=yes rootwait video=HDMI-A-1:400x1280M@60,rotate=90
sudo vi /home/pi/.xinitrc
Quote:# before the "xset" commands, add this:
DISPLAY=:0 xrandr --output HDMI-1 --rotate left
# in the "SCREENSIZE="$(fbset ...." line, swap $2 and $3, so the lines become :
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $3","$2 }')"
The touch screen worked out of the box. However, you may need to press the "Rotate Touch" button a few times until it works correctly. The display modules saves the rotation setting internally.
|
|
|
|
| GPIO button only works after setting it to pull down manually |
|
Posted by: m4th31st - 04-20-2024, 07:46 AM - Forum: Support
- Replies (1)
|
|
I have an issue where a button (connected to GPIO 26) only works after I manually set pin 26 to be used as pull down, by running the following Python code:
Code: import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(26, GPIO.IN, pull_up_down=GPIO.PUD_DOWN)
So I thought a workaround would be to run the above script in /etc/rc.local, but this doesn´t solve the problem. I checked that the script is run at startup by adding other lines of code to it.
I connected the button between 3V3 and GPIO 26 (which should be pulled down, so I connected it to the right pins... right?). I also tried other GPIO pins between 9 and 27, but the same problem persists.
Is there a file where I can check (and change) the default mode (pulled up / pulled down) all the pins have after startup? I think I need to change it there.
|
|
|
|
| Change Moode volume with bluetooth headphone buttons |
|
Posted by: jenzd - 04-19-2024, 11:19 PM - Forum: Support
- No Replies
|
|
Hi all,
I am trying to find a way to use the volume buttons of my bluetooth headphones to set the volume shown in Moode's GUI (i.e. actvate "absolute volume" for the bluetooth output) .
I already got to the point where I can use the headphone volume buttons to set the volume level shown by alsamixer -D bluealsa. Yet this does not have any effect on the volume shown by the Moode GUI. How do the alsa and Moode (MPD?) volume settings actually relate to each other? Is there a way to keep them synchronised as well?
What I did so far (starting from a fresh Moode 8.3.9 installation):
1) Enable the native A2DP volume control of bluealsa by adding the switch --a2dp-volume in the config file /etc/systemd/system/bluealsa.service:
Code: [Service]
Type=simple
ExecStart=/usr/bin/bluealsa -p a2dp-source -p a2dp-sink -c aptx -c aptx-hd -c ldac --a2dp-volume --sbc-quality=xq+
2) Connect to the bluetooth headphone and deactivate bluealsa's internal scaling by issuing the following command (using the device name shown by bluealsa-cli list-pcms):
Code: bluealsa-cli soft-volume /org/bluealsa/hci0/dev_XX_XX_XX_XX_XX_XX/a2dpsrc/sink false
3) Verify that bluealsa-cli --verbose list-pcms shows "Softvolume: false" and that I can now use the volume buttons on the headphone to change the volume shown by alsamixer -D bluealsa
Any ideas what is missing to take the final step and synchronise with the Moode volume level (if this is possible at all)?
Thanks & best regards
Jens
|
|
|
|
| Switch renderer from cmdline or url |
|
Posted by: rawdlite - 04-19-2024, 10:48 AM - Forum: Support
- No Replies
|
 |
Hello,
I would like to switch between renderers via cmdline or by opening a URL.
Usecase is gpio buttons to activate squeezelite or airplay etc.
I checked moodeutl, but there are only options to restart a renderer not to activate one.
What is the best way to switch between renderers from a remote script?
TIA
|
|
|
|
|
