Read the build guide for protodac on GitHub. It says 5v either from gpio or external supply.
The build guide is excellent, it explains component choices and should make constructing a protodac pretty straightforward.
the tda1387 chip can take 3-5,5V ... i think the only problem is that i have to adjust the output stage resistor for 3.3V (and the output level might be different then) instead of 5V
For registration (@ayala and @Ghoostknight ), please send an email to tim@moodeaudio.org and he will create an account for you.
Regards,
Francesco
Regards,
Francesco
I have not tried a 3.3V supply. It would require a complete redesign of component values.
IMHO, 5V is a ubiquitous supply voltage, and should be supported.
https://github.com/atlantageek/moode-servo-volume
Now the Volume knob can be in-sync with the digital volume on the browser. This is something I've been playing with. Basically its a modified version of vol.sh converted to python that talks to an attached arduino. A S1123 servo is attached to the Arduino. This servo is special cause it has a fourth wire where the arduino can read its position (read the value of the built in POT)
So if you change the volume in the web interface the physical servo turns accordingly. If you turn the servo the volume in moode is adjusted. I tuned it to my servo and made an attempt at a calibration process on initial power up. Feel free to criticize or suggest changes.
Thanks.
Now the Volume knob can be in-sync with the digital volume on the browser. This is something I've been playing with. Basically its a modified version of vol.sh converted to python that talks to an attached arduino. A S1123 servo is attached to the Arduino. This servo is special cause it has a fourth wire where the arduino can read its position (read the value of the built in POT)
So if you change the volume in the web interface the physical servo turns accordingly. If you turn the servo the volume in moode is adjusted. I tuned it to my servo and made an attempt at a calibration process on initial power up. Feel free to criticize or suggest changes.
Thanks.
Thats cool.
Couple suggestions:
(1) Attach an Open Source license (GPLv3, MIT, etc) to the code in your Git repo if you want others to be able to freely use, modify, redistribute, etc., otherwise without a license, default copyright laws apply which means that no one can copy, redistribute or create derivatives.
(2) Maybe attach some pics and links to the parts
Couple suggestions:
(1) Attach an Open Source license (GPLv3, MIT, etc) to the code in your Git repo if you want others to be able to freely use, modify, redistribute, etc., otherwise without a license, default copyright laws apply which means that no one can copy, redistribute or create derivatives.
(2) Maybe attach some pics and links to the parts
thanks! if i go with a protodac i will go with a a addtional 5V then, my guess is even if i adjust the capacitor values for 3.3V the performance will be not the same
Nice 🙂
Its also good practice to include a mention of the license in your source file headers.
Copyright <YEAR> <COPYRIGHT_HOLDER>
Licensed under the MIT license:
http://www.opensource.org/licenses/mit-license.php
I would check /var/log and see if there is an xwindows error or something. I dont have access to my system right now to identify the exact log file.
Check the cables. Try the HDMI cable which came with the screen. I have the same problem when I used another cable.
Hi all,
Looking at the screenshot it looks like a software problem (it is a Chrome message) so logical and phisical connections are ok (did you see on the screen all the raspberry boot procedure messages before that white screen?)
Do you have created the microSD with the "raspberry imager", as per the security procedure?
It "YES" please go to the moode forum and open a thread with your issue, because a deeper analisys is needed.
Best regards,
Francesco
Looking at the screenshot it looks like a software problem (it is a Chrome message) so logical and phisical connections are ok (did you see on the screen all the raspberry boot procedure messages before that white screen?)
Do you have created the microSD with the "raspberry imager", as per the security procedure?
It "YES" please go to the moode forum and open a thread with your issue, because a deeper analisys is needed.
Best regards,
Francesco
Very likely there would be some error detail in the chrome/chromium log, accessed e.g. via ssh (does moode have ssh enabled?) Details for enabling e.g. https://www.makeuseof.com/find-erro...how-to-enable-chrome-39-s-error-logs-on-linux (again there may be so moode-specific issues like RO filesystem etc.)
@anounaki and @atlantageek,
since some release moOde has introduced the Raspberry security procedure(for improved security the OS image does not contain the userid pi, SSH service, WiFi SSID or Access Point password), for a correct setup of the system you have to use the raspberry imager to prepare the microSD: the instructions are reported at the following link:
set up procedure
Would you please be so kind to follow that (if you did not yet) and report the results?
Best regards and thanks,
Francesco
since some release moOde has introduced the Raspberry security procedure(for improved security the OS image does not contain the userid pi, SSH service, WiFi SSID or Access Point password), for a correct setup of the system you have to use the raspberry imager to prepare the microSD: the instructions are reported at the following link:
set up procedure
Would you please be so kind to follow that (if you did not yet) and report the results?
Best regards and thanks,
Francesco
I have a Pi Zero-W with a Justboom DAC HAT Zero on it that makes some clicking/crackling sounds. The music doesn't lag, skip, or anything, but there is this background noise whether the music is playing or not. Usually it's not an issue except on softer music like classical. I've been living with it for a while now, but wonder if there's a fix. I've been using bluetooth to stream from my PC (itunes) to the Pi which feeds into a headphone amp at work. I've read this is possibly and issue with the wifi and BT frequencies interfering with each other, but I need wifi to access the Moode GUI and BT to send the music from the PC. I'm Pi illiterate FWIW. Any suggestions?
I've attached an audio recording of the noise.
Moode Pi ZeroW JustBoom DACHAT
I've attached an audio recording of the noise.
Moode Pi ZeroW JustBoom DACHAT
I suppose it could be the power supply. I have a 30V/2A switchmode supply feeding a linear regulator for the 24V to the headphone amp and a XL4015 dc/dc converter to drop the voltage to 5V for the Pi.