Hi Tim, I have attached a few PLS files which you may wish to consider adding to the included Moode radio stations.
They contain a variety of music types. I was initially looking for a radio station with nature sounds, but the others are okay as well.
They contain a variety of music types. I was initially looking for a radio station with nature sounds, but the others are okay as well.
Thank you Jonners for your answer, but when I write that I need a step to step guide to install Moode Audio 4, it's because I don't even know which program to use to copy the files in rel-stretch-r40.zip or the image builder on the micro card from my windows 10 laptop.
Before I asked the question I did try to look into the 13961replies and could not find a way to do it
@PIERRICK
I don't use a PC so others may be of more help. However I believe people recommend Etcher for copying the Raspbian .img file onto the sd card, and then Putty for ssh into the Pi for the build.
I don't use a PC so others may be of more help. However I believe people recommend Etcher for copying the Raspbian .img file onto the sd card, and then Putty for ssh into the Pi for the build.
@PIERRICK
This post may be of help:
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-1271.html#post5313812
This post may be of help:
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-1271.html#post5313812
Kent,
thank you for taking time to respond
"Keep in mind ....." I will continue to do so
"I gather....." correctly
"Can't say what's....." tell me about it
"I am perplexed....." me too, a complete rebuild resulted in the same behaviour, BUT,
I have now demonstrated that this is a local browser issue, in that using the web UI on a smartphone allowed the button to respond as expected.
Odd since all other controls give the expected response and corner pop-up but this one merely reloads the page.
"Did you check with "mosbrief" that the build finished successfully, e.g., the "// END" message appeared?" check
After yet another fresh build, I am getting the impression that there is something about or in my larger network share that is breaking the library function. Just about over it with playing crash test dummy with this though.
thank you for taking time to respond
"Keep in mind ....." I will continue to do so
"I gather....." correctly
"Can't say what's....." tell me about it
"I am perplexed....." me too, a complete rebuild resulted in the same behaviour, BUT,
I have now demonstrated that this is a local browser issue, in that using the web UI on a smartphone allowed the button to respond as expected.
Odd since all other controls give the expected response and corner pop-up but this one merely reloads the page.
"Did you check with "mosbrief" that the build finished successfully, e.g., the "// END" message appeared?" check
After yet another fresh build, I am getting the impression that there is something about or in my larger network share that is breaking the library function. Just about over it with playing crash test dummy with this though.
Yep.
I've attached a snap of the core team of moOde crash testers contemplating what to do next.
Regards,
Kent
Attachments
here it is :
for reminder i can't acces config pages (browser keeps loading...) and i also cannot connect to airplay and dlna renderer ?
(fresh moode 4.0 install)
Code:
20180224 165819 worker: Successfully daemonized
20180224 165819 worker: - Init
20180224 165819 worker: Session loaded
20180224 165819 worker: Debug logging (on)
20180224 165824 worker: Host (moode)
20180224 165824 worker: Hdwr (Pi-2B 1GB v1.1)
20180224 165824 worker: Arch (armv7l)
20180224 165824 worker: Kver (4.9.79-v7+)
20180224 165824 worker: Ktyp (Standard)
20180224 165824 worker: Gov (ondemand)
20180224 165824 worker: Rel (Moode 4.0 2018-01-26)
20180224 165824 worker: Upd (None)
20180224 165824 worker: MPD (0.20.12)
20180224 165824 worker: USB boot not enabled yet
20180224 165824 worker: File system expanded
20180224 165824 worker: HDMI port off
20180224 165825 worker: File check ok
20180224 165825 worker: - Network
20180224 165825 worker: eth0 exists
20180224 165825 worker: eth0 (192.168.1.83)
20180224 165825 worker: wlan0 does not exist
20180224 165825 worker: - Audio
20180224 165826 worker: ALSA outputs unmuted
20180224 165826 worker: Audio out (I2S audio device)
20180224 165826 worker: Audio dev (HiFiBerry DAC+ Pro)
20180224 165827 worker: ALSA mixer name (Digital)
20180224 165827 worker: MPD volume control (hardware)
20180224 165828 worker: Hdwr volume controller exists
20180224 165828 worker: Chip options (Burr Brown PCM5122)
20180224 165828 worker: - Services
20180224 165830 worker: MPD started
20180224 165830 worker: MPD scheduler policy (time-share)
20180224 165830 readMpdResponse(): reading response
20180224 165830 readMpdResponse(): success $str=(OK MPD 0.20.0)
20180224 165830 readMpdResponse(): success $resp[0]=(OK MPD 0.20.0)
20180224 165830 readMpdResponse(): reading response
20180224 165830 readMpdResponse(): success $str=(OK)
20180224 165830 readMpdResponse(): success $resp[0]=(outputid: 0)
20180224 165830 worker: MPD output 1 ALSA default (on)
20180224 165830 worker: MPD output 2 ALSA crossfeed (off)
20180224 165830 worker: MPD output 3 ALSA parametric eq (off)
20180224 165830 worker: MPD output 4 ALSA graphic eq (off)
20180224 165830 worker: MPD crossfade (off)
20180224 165830 worker: Airplay metadata off
20180224 165830 worker: (/usr/local/bin/shairport-sync -a "Moode Airplay" -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh -- -d hw:0 -c "Digital" > /dev/null 2>&1 &)
20180224 165830 worker: Airplay receiver started
20180224 165830 worker: Airplay volume mgt (auto)
20180224 165830 worker: UPnP renderer started
20180224 165831 worker: DLNA server started
20180224 165831 worker: Bluetooth controller started
20180224 170017 worker: Bluetooth controller initialized
20180224 170017 worker: - Last
20180224 170017 worker: USB sources (none attached)
20180224 170017 worker: NAS sources (mountall initiated)
20180224 170019 wrk_sourcemount(): mountstr=(mount -t cifs "//192.168.1.43/donnees/musique" -o username=XXX,password='XXXXX',rsize=61440,wsize=65536,iocharset=utf8,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/disquedur")
20180224 170019 wrk_sourcemount(): sysoutput=()
20180224 170020 worker: Volume level (81) restored
20180224 170020 readMpdResponse(): reading response
20180224 170020 worker: Maintenance interval (21600)
20180224 170020 worker: Watchdog started
20180224 170020 worker: Ready
Its been awhile since my last post here, I've been busy with a host of projects but I have finally built the small dedicated Audio streamer custom designed with MoOde in mind. The Streamer is targeted at USB Async DAC's* 🙂
* Tested with my USB DAC designs for AudioLab and ProJect.
We are still working on the APi so the PCB pictured below has a host of extra debug connections...
Dropbox - MoOde streamer.jpg
The hardware is working - we are currently creating the APi to control the board over a UART channel.
We added current and voltage monitoring on the USB ports which can be read back via the APi / UART channel and a "Detoxed" USB output for DAC connection with De-Jittered, RF filtered USB port and a clean 5.2V to power "self powered" USB DAC's.
The DAC's 5.2V power can also be disabled via the APi.
Does the current standard MoOde build include the dtblob for the RPI CM3 module?
* Tested with my USB DAC designs for AudioLab and ProJect.
We are still working on the APi so the PCB pictured below has a host of extra debug connections...
Dropbox - MoOde streamer.jpg
The hardware is working - we are currently creating the APi to control the board over a UART channel.
We added current and voltage monitoring on the USB ports which can be read back via the APi / UART channel and a "Detoxed" USB output for DAC connection with De-Jittered, RF filtered USB port and a clean 5.2V to power "self powered" USB DAC's.
The DAC's 5.2V power can also be disabled via the APi.
Does the current standard MoOde build include the dtblob for the RPI CM3 module?
Last edited:
I may be a grandfather but I still suffer from what my grandmother called "if you give a child a hammer" syndrome.
Today Bluetooth is the hammer.
Here's my Bluetooth-ready moOde player connected to my Decent Audio System (DAS). There's my significant other's Amazon Echo with its, umm, adequate speakers.
I have no trouble setting moOde into Bluetooth Speaker mode, pairing, and connecting it to, say, my phone, and hearing music from one phone app or another spill out of the DAS.
I also have no trouble pairing and connecting the Echo to an, umm, adequate JBL Bluetooth speaker, telling Alexa to play something, and hearing the music spill out of the JBL.
What I can't seem to do is couple the Echo to moOde so that audio flows from all those Alexa Skills to my DAS.
Available indicators in both moOde and Alexa settings suggest that discovery, pairing, and connecting has occurred but all I get is dead air.
It occurs to me that, somewhat akin to hermaphroditic earthworms (you can look it up), they're having trouble sorting out who is the source and who is the sink.
Before I start one of my usual ready-fire-aim exercises, I thought I'd ask if anyone else has succeeded connecting their Echo. If so, what was the secret sauce?
Regards,
Kent
Today Bluetooth is the hammer.
Here's my Bluetooth-ready moOde player connected to my Decent Audio System (DAS). There's my significant other's Amazon Echo with its, umm, adequate speakers.
I have no trouble setting moOde into Bluetooth Speaker mode, pairing, and connecting it to, say, my phone, and hearing music from one phone app or another spill out of the DAS.
I also have no trouble pairing and connecting the Echo to an, umm, adequate JBL Bluetooth speaker, telling Alexa to play something, and hearing the music spill out of the JBL.
What I can't seem to do is couple the Echo to moOde so that audio flows from all those Alexa Skills to my DAS.
Available indicators in both moOde and Alexa settings suggest that discovery, pairing, and connecting has occurred but all I get is dead air.
It occurs to me that, somewhat akin to hermaphroditic earthworms (you can look it up), they're having trouble sorting out who is the source and who is the sink.
Before I start one of my usual ready-fire-aim exercises, I thought I'd ask if anyone else has succeeded connecting their Echo. If so, what was the secret sauce?
Regards,
Kent
The attached file (unzip to Word .docx) is how I built v4 using my Win10 computer. YMMV.
Hope that helps.
Librespot status
Hi everyone,
One of the librespot devs here, just came across this project, and first impressions are that it's impressive 🙂 With regards to the passt few mentions of librespot on here, we're working on maturing it a bit, since it was still a somewhat immature project when we started working on it again about a month ago. We have, for the most part, ironed out the major bugs, with one of the few exceptions being the one that you encountered above. The issue isn't actually the switching (at least to the best of our knowledge), but rather due to the networking session disconnecting, and reconnection logic not yet having been implemented. This was identified in librespot crashes - main thread panic * Issue #103 * librespot-org/librespot * GitHub and is actively being tracked in Rewrite the session handling logic * Issue #134 * librespot-org/librespot * GitHub. We should get around to implementing a fix in the not too distant future.
With regards to providing binaries and making it easier to use, we're currently cleaning up the codebase in preparation for publishing the code to crates.io (the rust package manager). Once this is done, we'll be looking to start treating librespot more as an internal library, for integration into other codebases, with the aim of fewer (breaking) changes and a more reliable versioning system. At the same time, we will be focusing on librespotd, a standalone daemon that other programs can communicate with to add Spotify Connect functionality to their applications, or to run as a standalone program. librespotd will be available at Initial volume works good, see screenshot. hw:1,0 doesn't work for me.
I have a RP3 running Moode 4.0 -> usb out -> Aune S6Switching back to plughw
[Edit] Got another panick when switching tracks in a playlist to fast.
Looks like still early days [/QUOTE] Hi everyone,One of the librespot devs here, just came across this project, and first impressions are that it's impressive 🙂 With regards to the passt few mentions of librespot on here, we're working on maturing it a bit, since it was still a somewhat immature project when we started working on it again about a month ago. We have, for the most part, ironed out the major bugs, with one of the few exceptions being the one that you encountered above. The issue isn't actually the switching (at least to the best of our knowledge), but rather due to the networking session disconnecting, and reconnection logic not yet having been implemented. This was identified in [url]https://github.com/librespot-org/librespot/issues/103 and is actively being tracked in Rewrite the session handling logic * Issue #134 * librespot-org/librespot * GitHub. We should get around to implementing a fix in the not too distant future.With regards to providing binaries and making it easier to use, we're currently cleaning up the codebase in preparation for publishing the code to crates.io (the rust package manager). Once this is done, we'll be looking to start treating librespot more as an internal library, for integration into other codebases, with the aim of fewer (breaking) changes and a more reliable versioning system. At the same time, we will be focusing on librespotd, a standalone daemon that other programs can communicate with to add Spotify Connect functionality to their applications, or to run as a standalone program. librespotd will be available at https://github.com/librespot-org/librespotd"]https://github.com/librespot-org/librespotd[/URL] (it's just a placeholder atm), and will provide functionality to make it easier to interface with, such as a proper interface for retrieving metadata, controlling playback, and listening for change events. Librespotd will be the program that gets the precompiled binaries, and will be distributed through the standard means (PPA, Github Releases, etc.) that should make it easier to integrate with on an ongoing basis.
This is likely a few months off, but in the meantime, if there is a more pressing question/feature/bug you can either file an issue here Issues * librespot-org/librespot * GitHub or jump into Gitter to chat directly, found here: https://gitter.im/librespot-org/spotify-connect-resources. Drop us a line there if you have any questions 🙂
Hi everyone,
One of the librespot devs here, just came across this project, and first impressions are that it's impressive 🙂 With regards to the passt few mentions of librespot on here, we're working on maturing it a bit, since it was still a somewhat immature project when we started working on it again about a month ago. We have, for the most part, ironed out the major bugs, with one of the few exceptions being the one that you encountered above. The issue isn't actually the switching (at least to the best of our knowledge), but rather due to the networking session disconnecting, and reconnection logic not yet having been implemented. This was identified in librespot crashes - main thread panic * Issue #103 * librespot-org/librespot * GitHub and is actively being tracked in Rewrite the session handling logic * Issue #134 * librespot-org/librespot * GitHub. We should get around to implementing a fix in the not too distant future.
With regards to providing binaries and making it easier to use, we're currently cleaning up the codebase in preparation for publishing the code to crates.io (the rust package manager). Once this is done, we'll be looking to start treating librespot more as an internal library, for integration into other codebases, with the aim of fewer (breaking) changes and a more reliable versioning system. At the same time, we will be focusing on librespotd, a standalone daemon that other programs can communicate with to add Spotify Connect functionality to their applications, or to run as a standalone program. librespotd will be available at Initial volume works good, see screenshot. hw:1,0 doesn't work for me.
Code:
target/release/librespot --name testing3 --device hw:1,0 --initial-volume 20 INFO:librespot: librespot 4f3a594 (2018-02-17). Built on 2018-02-21. Build ID: ajbm2XrO INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-jkm8.ap.spotify.com:4070" INFO:librespot_core::session: Authenticated as "******" ! INFO:librespot_playback::audio_backend::alsa: Using alsa sink INFO:librespot_core::session: Country: "NL" INFO:librespot_playback::player: Loading track "Karma Police (Remastered)" INFO:librespot_playback::player: Track "Karma Police (Remastered)" loaded ALSA lib pcm.c:8382:(snd_pcm_set_params) Sample format not available for PLAYBACK: Invalid argument ERROR:librespot_playback::audio_backend::alsa: Alsa error PCM open -22 ERROR:librespot_playback::player: Could not start audio: Alsa error: PCM open failed ALSA lib pcm.c:8382:(snd_pcm_set_params) Sample format not available for PLAYBACK: Invalid argument ERROR:librespot_playback::audio_backend::alsa: Alsa error PCM open -22
Code:
target/release/librespot --name testing3 --device plughw:1,0 --initial-volume 20 INFO:librespot: librespot 4f3a594 (2018-02-17). Built on 2018-02-21. Build ID: ajbm2XrO INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-v1bc.ap.spotify.com:4070" INFO:librespot_core::session: Authenticated as "kopstukken" ! INFO:librespot_playback::audio_backend::alsa: Using alsa sink INFO:librespot_core::session: Country: "NL" INFO:librespot_playback::player: Loading track "Karma Police (Remastered)" INFO:librespot_playback::player: Track "Karma Police (Remastered)" loaded
Code:
INFO:librespot_playback::player: Loading track "Karma Police (Remastered)" INFO:librespot_playback::player: Track "Karma Police (Remastered)" loaded INFO:librespot_playback::player: Loading track "Fitter Happier (Remastered)" INFO:librespot_playback::player: Track "Fitter Happier (Remastered)" loaded INFO:librespot_playback::player: Loading track "Electioneering (Remastered)" INFO:librespot_playback::player: Track "Electioneering (Remastered)" loaded INFO:librespot_playback::player: Loading track "Climbing Up the Walls (Remastered)" INFO:librespot_playback::player: Track "Climbing Up the Walls (Remastered)" loaded thread 'main' panicked at 'Box<Any>', core/src/session.rs:87:43 thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: SendError("...")', /checkout/src/libcore/result.rs:916:5 stack backtrace:0: 0x82c2b3 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::hb6166e15fda1e065at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:491: 0x8362e7 - std::sys_common::backtrace::print::hbb547a48d4d45c54at /checkout/src/libstd/sys_common/backtrace.rs:68at /checkout/src/libstd/sys_common/backtrace.rs:572: 0x824b67 - std::panicking::default_hook::{{closure}}::hb3351df37d61d489at /checkout/src/libstd/panicking.rs:3813: 0x824673 - std::panicking::default_hook::ha118e44019160a5bat /checkout/src/libstd/panicking.rs:3974: 0x825013 - std::panicking::rust_panic_with_hook::h9cedc3dcc869a838at /checkout/src/libstd/panicking.rs:5775: 0x561d03 - std::panicking::begin_panic::h6c297eb57182bef06: 0x5c548f - <futures::future::map_err::MapErr<A, F> as futures::future::Future>::poll::h54b0d8855e9393787: 0x7f16b7 - futures::task_impl::std::set::h28789caeb07e58438: 0x7f02a3 - <futures::task_impl::Spawn<T>>::poll_future_notify::hac4b590ae1f22cb29: 0x7f4ba7 - tokio_core::reactor::Core::poll::h7ae65b652a8d113f 10: 0x44efc7 - tokio_core::reactor::Core::run::hc3eec5c43c664b0f 11: 0x462bdf - librespot::main::h4d986fdbca3cee68 12: 0x44c43b - std::rt::lang_start::{{closure}}::he99eb8df53d4ae63 13: 0x824cbb - std::panicking::try::do_call::h42f53f2dc816c41bat /checkout/src/libstd/rt.rs:59at /checkout/src/libstd/panicking.rs:480 14: 0x847eb7 - __rust_maybe_catch_panicat /checkout/src/libpanic_unwind/lib.rs:101 15: 0x82bf43 - std::rt::lang_start_internal::hea8910ac69028645at /checkout/src/libstd/panicking.rs:459at /checkout/src/libstd/panic.rs:365at /checkout/src/libstd/rt.rs:58 16: 0x4636f7 - main 17: 0x76c3c677 - __libc_start_main stack backtrace:0: 0x82c2b3 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::hb6166e15fda1e065at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:491: 0x8362e7 - std::sys_common::backtrace::print::hbb547a48d4d45c54at /checkout/src/libstd/sys_common/backtrace.rs:68at /checkout/src/libstd/sys_common/backtrace.rs:572: 0x824b67 - std::panicking::default_hook::{{closure}}::hb3351df37d61d489at /checkout/src/libstd/panicking.rs:3813: 0x824673 - std::panicking::default_hook::ha118e44019160a5bat /checkout/src/libstd/panicking.rs:3974: 0x825013 - std::panicking::rust_panic_with_hook::h9cedc3dcc869a838at /checkout/src/libstd/panicking.rs:5775: 0x824e5b - std::panicking::begin_panic::h8259fca926742a49at /checkout/src/libstd/panicking.rs:5386: 0x824de3 - std::panicking::begin_panic_fmt::hb044a1e2dca6dd17at /checkout/src/libstd/panicking.rs:5227: 0x824d8b - rust_begin_unwindat /checkout/src/libstd/panicking.rs:4988: 0x87b0cb - core::panicking::panic_fmt::hd4212c5d5ed3b640at /checkout/src/libcore/panicking.rs:719: 0x5ae8df - core::result::unwrap_failed::h851276061752a9cc 10: 0x5859d7 - librespot_core::session::Session::send_packet::h13b3c90d36997378 11: 0x5b04ef - librespot_core::mercury::MercuryManager::request::h107e783a6abeb202 12: 0x51fae7 - librespot_metadata::Metadata::get::h9e23e928175b5417 13: 0x4fb37b - librespot_playback::player::PlayerInternal::run::h83fe9ec43a7a6671 14: 0x45beb3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2f514b0eb570dad9 15: 0x4524d7 - std::panicking::try::do_call::hbcd3322838af5842 16: 0x847eb7 - __rust_maybe_catch_panicat /checkout/src/libpanic_unwind/lib.rs:101 17: 0x45fecb - <F as alloc::boxed::FnBox<A>>::call_box::h5bdec24e0e01658f 18: 0x832a4b - std::sys_common::thread::start_thread::h5c8ded4a8e2b80a7at /checkout/src/liballoc/boxed.rs:825at /checkout/src/libstd/sys_common/thread.rs:24 19: 0x825667 - std::sys::unix::thread::Thread::new::thread_start::h38f4e2017be83d0fat /checkout/src/libstd/sys/unix/thread.rs:90 ERROR:librespot_playback::player: Player thread panicked! pi@moode:~/librespot $ Message from syslogd@moode at Feb 21 14:40:57 ...kernel:[ 3100.622499] skbuff: skb_over_panic: text:8054f268 len:294 put:294 head:96c35e40 data:96c35e82 tail:0x70126 end:0x222 dev:eth0Message from syslogd@moode at Feb 21 14:40:57 ...kernel:[ 3100.648200] Internal error: Oops - BUG: 0 [#1] SMP ARMMessage from syslogd@moode at Feb 21 14:40:57 ...kernel:[ 3100.771854] Process swapper/0 (pid: 0, stack limit = 0x80c00210)Message from syslogd@moode at Feb 21 14:40:57 ...kernel:[ 3100.779437] Stack: (0x80c01d48 to 0x80c02000)Message from syslogd@moode at Feb 21 14:40:57 ...kernel:[ 3100.785371] 1d40: 00000126 96c35e40 96c35e82 00070126 00000222 b9558800This is likely a few months off, but in the meantime, if there is a more pressing question/feature/bug you can either file an issue here Issues * librespot-org/librespot * GitHub or jump into Gitter to chat directly, found here: https://gitter.im/librespot-org/spotify-connect-resources. Drop us a line there if you have any questions 🙂
sashahilton00,
Welcome 🙂 and thank you for the BRILLIANT news 🙂 IMO MoOde's only real weakness was lack of Spotify Connect - this would be game changer for MoOde 🙂
I has been mentioned that one of the issues with Librespot was some issue with the volume control jumping to 100% or some such.
If I can support you with any hardware - please just message me.
Welcome 🙂 and thank you for the BRILLIANT news 🙂 IMO MoOde's only real weakness was lack of Spotify Connect - this would be game changer for MoOde 🙂
I has been mentioned that one of the issues with Librespot was some issue with the volume control jumping to 100% or some such.
If I can support you with any hardware - please just message me.
Tim,
I few post back I explained I've JUST built the first PCB's after a long delay and we are just completing the APi (and system firmware). Obviously, with every intention to get a board to you once they are ready - the board does after all have compatible with "MoOde" on the PCB silkscreen 🙂 - so surely my hearts in the right place?
For sure its taken longer then expected (but there have been delays with installing the in house SMD production line (we lost over a month while we waited for equipment to arrive that the distributor had not ordered)) but we are moving past these now and the first PCB's are finally coming together.
In all fairness - during our phone conversions I did mentioned to you that you will be receiving hardware as SOON as its ready 🙂 I guess you might have not understood its been delayed my end due to my bad communications... rest assured first units are only now popping off the end of the production line 🙂
Ps. I hope that offering hardware support to Librespot is seen with the intent to benefit the MoOde community 🙂 as Spotify connect for MoOde would IMO fill in its largest missing piece 🙂 - here in Europe Spotify is REALLY important.
Last edited:
Some phone call from a far distant time in 2017...? I don't even remember it.
So very strange.
-Tim
Tim,
I checked with my notes when we discussed the hardware and it was around 28th November 2017* 🙂 so its only around 3 months ago... not so shabby considering how far we have progressed since then 🙂
*Actually you can confirm this date for yourself in our Skype history 🙂
I cannot comment about software development, but 3 months or so is not bad WRT building and testing hardware... or maybe I'm just slower then others 🙂
Its true, normally I'd be faster but as I mentioned in an above post we lost over a month due to a misunderstanding with an equipment order combined with the Christmas holiday period...
Once we have the firmware development completed (hopefully this weekend), I'll get a Beta unit over to you.
Last edited:
Guys can we have a support for SI4705, its terrestrial FM receiver which has digital audio output ie on i2s bus, and the FM chip is controlled via I2C. At present the amplifier board or the dac board we are using have the same interface.
what I am proposing is to make a board such that it has a TAS5756M + SI4705 + a multiplexer so we can switch between Raspberry Pi I2S and SI4705 I2S and the multiplexer can be controlled by one i/o pin to toggle beteween the 2 I2S bus going to TAS5756M
what I am proposing is to make a board such that it has a TAS5756M + SI4705 + a multiplexer so we can switch between Raspberry Pi I2S and SI4705 I2S and the multiplexer can be controlled by one i/o pin to toggle beteween the 2 I2S bus going to TAS5756M