Hi,
My hosting provider offers forums, wikis, etc via cPanel. I could install any of these into moodeaudio.org but I'd need others to volunteer to do the admin.
Would any of the below work?
-Tim
Why not use the one available in github? It’s a tried-and-true method for software projects and all you need to do is turn it on.
How to:Documenting your projects on GitHub * GitHub Guides
Attachments
Last edited:
Why not use the one available in github? It’s a tried-and-true method for software projects and all you need to do is turn it on.
How to:Documenting your projects on GitHub * GitHub Guides
Hi Mike,
There have been some recent proposals for setting up a dedicated moOde support forum and documentation wiki. I can do this with cPanel on moodeaudio.org but I would need someone(s) to admin them.
Github is not a forum or a wiki.
-Tim
Hi,
This is a redundant post but does anyone use miniDLNA ?
-Tim
Sorry for my ignorance, but is that the same or different than the DLNA server option on the Configure Audio page?
Bryce.
Hi Mike,
There have been some recent proposals for setting up a dedicated moOde support forum and documentation wiki. I can do this with cPanel on moodeaudio.org but I would need someone(s) to admin them.
Github is not a forum or a wiki.
-Tim
It can work well if you appoint a few trusted guys/gals as forum admins. Then it can be a collective effort.
This also worked for me. Thank you very much.For those suffering with the Tidal playlists issue with upmpdcli there is a fix.
if you want to be a bit more secure and you are more comfortable with git then from /home/pi
Code:git clone [url]https://@opensourceprojects.eu/git/p/upmpdcli/code[/url] upmpdcli-code
there is no need to compile just copy __init__.py
from
~/upmpdcli-code/src/mediaserver/cdplugins/tidal/tidalapi/
to
/usr/share/upmpdcli/cdplugins/tidal/tidalapi
May be my ignorance but I have had too many funnies downloading downloading code outside of git to publish the url to the file for a simple wget or curl.
NB The developer made the same change for Tidal as well which I have not yet tested.
Hi Mike,
There have been some recent proposals for setting up a dedicated moOde support forum and documentation wiki. I can do this with cPanel on moodeaudio.org but I would need someone(s) to admin them.
Github is not a forum or a wiki.
-Tim
A wiki is wherever you put one 🙂 But I get what you’re saying.
I’m happy to admin a wiki for you - it’s not like I’m not on the net 18 hours a day and have time to spare...
Let me do a quick bit of research on those packages you posted earlier and I’ll post the pros and cons.
I have used phpBB which is good, not great (I really liked vBulletin -this forum runs from it-, but that has a cost and installation overhead). PhpBB has all you would ever need for a forum, albeit not the greatest look.Hi,
My hosting provider offers forums, wikis, etc via cPanel. I could install any of these into moodeaudio.org but I'd need others to volunteer to do the admin.
Would any of the below work?
-Tim
GitHub has a great Wiki!, and it works great for tracking issues (be them bug reports or development of features). Not really great for forum-like interaction.
I'd be happy with either solution, but still think a simple set of instructions in the webpage (just like the ones provided a few posts back for the B+) would overcome the need for any of the above solutions.
In any case, I'd be happy to help moderate and help in a dedicated forum. I wouldn't venture to admin it, too time consuming for the time being. I did it once and it was a lot of effort. That is why I am pushing for a simpler starting point and see what turns out from that.
Best regards,
Rafa.
Hi,
My hosting provider offers forums, wikis, etc via cPanel. I could install any of these into moodeaudio.org but I'd need others to volunteer to do the admin.
Would any of the below work?
-Tim
Hi Tim
IMHO we should start with a wiki first because that's the most needed. I can volunteer to administer a wiki (together with other volunteers). I have never done it before. Need some one to tell me what it involves or to point me to some ressources that explains how to administer a wiki. I can learn fast.
Remy
I was doing the same thing. Take a look here: WikiMatrix - Compare them allA wiki is wherever you put one 🙂 But I get what you’re saying.
I’m happy to admin a wiki for you - it’s not like I’m not on the net 18 hours a day and have time to spare...
Let me do a quick bit of research on those packages you posted earlier and I’ll post the pros and cons.
As far as I'm concerned, I think it's down to DokuWiki vs MediaWiki. MediaWiki is more complex, being the platform used by wikipedia. But DokuWiki looks more modern and a little bit simpler. I like the fact that you don't need a database, there are only text files. And also, I like the syntax more because it's close to MarkDown and is simpler than that of MediaWiki.
So, DokuWiki has my vote.
Last edited:
For those suffering with the Tidal playlists issue with upmpdcli there is a fix.
There will be a new release coming out but in the meantime I have attached the diff file that JF sent me.
Remove the .txt from the end and scp to /home/pi.
Then from a terminal session try.
Code:cd /usr/share/upmpdcli sudo patch -p3 < ~/upmpdcli-tidal-and-qobuz-playlists.diff
This seemed to work for me, however had already git cloned the source tree.
if you want to be a bit more secure and you are more comfortable with git then from /home/pi
Code:git clone [url]https://@opensourceprojects.eu/git/p/upmpdcli/code[/url] upmpdcli-code
there is no need to compile just copy __init__.py
from
~/upmpdcli-code/src/mediaserver/cdplugins/tidal/tidalapi/
to
/usr/share/upmpdcli/cdplugins/tidal/tidalapi
May be my ignorance but I have had too many funnies downloading downloading code outside of git to publish the url to the file for a simple wget or curl.
NB The developer made the same change for Tidal as well which I have not yet tested.
Worked for me as well, only reason I am chiming is because I am a total noob, and I managed to do this with a combo of cyberduck and google to fill in the blanks for the terminal part. I would post my method, but the guru's would probably vom a little in their mouths. Hey, at least I'm trying!
I think it's just about the wireless country
Everything seems to working fine
This post was in reference to the raspberry-sys-mods package and @Man in a van is on the right track. I checked the github repo. The new version of this package includes the code which checks for country code being set and disabling WiFi if it isn't. We don't need this functionality in the upgrade of moOde 4.0 because the country code is already set in the build process.
Thanks for the tip.
Regards,
Kent
Hi Kent,
Thanks for the great instructions. Although I have an RPi3, I wanted to try this to see if I could get through it. No issues at all, although I do have a couple of comments.
I have always used a Window 10 PC to create my SD cards for steps 1 through 3, but I have never had to remove and reinsert the SD card. Perhaps is it because I am using Win32DiskImager. The "boot" partition is always there after writing the image has completed.
If you follow these instructions the hostname in step 5 will always be "raspberrypi.local" will it not? Just might be a bit easier for new users.
The whole process only took between 60 and 90 minutes. I forgot to note my start time.
Thanks again. Bryce.
Hi, Bryce.
Interesting about the Windows 10 behavior. I have it on dual-boot with Linux on my laptop but out of old habits I never use it for programming activity, just for Win-only apps (yes, Linux lovers, I know how to use WINE and PlayOnLinux).
As for the hostname, be careful to note that .local is not a real domain in the meaning of the Internet Domain Name System. The details are complicated, see this zeroconf explanation Zero-configuration networking - Wikipedia or this article by Apple Domain Naming Conventions
I'm being pedantic because how some device on your LAN finds your moOde player depends on such factors as the protocols running on that device (dns, dns-sd or bonjour, etc) and any services (dhcp, dns) running on, say, your router and how they are configured. Using the .local convention may or may not work. For example, my Android devices cannot locate any hosts by the .local convention. They support dns-sd but don't hook it into their web browser. (I'm teaching myself Android programming so I can try to create a Moode-Finder app. Keeps me out of bars!)
To address your specific question, yes the zeroconf hostname will be raspberrypi.local at Step 5 but it will change to moode.local when the hostname changes from raspberrypi to moode.
Regards,
Kent
Last edited:
I just tried again tonight and can't seem to make this happen for whatever reason, a fully functioning instance of Moode 4.0 built on the 11/29/17 Stretch-Lite will not boot up on a 3B+ board after doing the update/upgrade.
I've paid attention to the LEDs on the 3B+ and during the failed boot the yellow LED will flash 4 times slowly followed by 4 times quickly in succession, repeating itself continuously.
@MikeyFresh
That light pattern means your system didn't upgrade. Still haven't figured out why some get this result.
Regards,
Kent
Hi, Bryce.
As for the hostname, be careful to note that .local is not a real domain in the meaning of the Internet Domain Name System.
Regards,
Kent
Right you are Kent, and I didn't realize I had make that mistake until after it was too late to edit. I was just thinking about what you need to type at that point.
Cheers, Bryce.
On the matter of wikis and forums and github, oh my
Gentle persons:
I think I weighed in on this subject a year ago or more, but here's the short version based on my experience running various of this services for other projects in the past.
I agree with others that moodeaudio.org itself should receive minor modifications on the basics of getting and building moOde. Indeed, I PM'ed some thoughts to Tim a while ago. His highest priority is to get 4.1 out the door ASAP so we haven't gone any farther with them yet.
My personal preference would be to keep this forum alive for ephemeral discussions and to create Github Pages for more permanent HowTos. As has been pointed out, moOde already has a GitHub presence and adding Github Pages is pretty straightforward. I particularly like that the GitHub Issue, Pull Request, and Merge mechanisms are baked in. They make it easier to keep things tidy and current. As in all things GitHub, more than one person can be assigned privileges in the repository.
Candidly, I don't care for Wikis. My experience with them on other projects is that no matter how organized they are at the start, they become byzantine over time as people add, modify, and delete material.
Just my 2-cents worth. I will do my part to contribute no matter what the technology choices turn out to be.
Regards,
Kent
Gentle persons:
I think I weighed in on this subject a year ago or more, but here's the short version based on my experience running various of this services for other projects in the past.
I agree with others that moodeaudio.org itself should receive minor modifications on the basics of getting and building moOde. Indeed, I PM'ed some thoughts to Tim a while ago. His highest priority is to get 4.1 out the door ASAP so we haven't gone any farther with them yet.
My personal preference would be to keep this forum alive for ephemeral discussions and to create Github Pages for more permanent HowTos. As has been pointed out, moOde already has a GitHub presence and adding Github Pages is pretty straightforward. I particularly like that the GitHub Issue, Pull Request, and Merge mechanisms are baked in. They make it easier to keep things tidy and current. As in all things GitHub, more than one person can be assigned privileges in the repository.
Candidly, I don't care for Wikis. My experience with them on other projects is that no matter how organized they are at the start, they become byzantine over time as people add, modify, and delete material.
Just my 2-cents worth. I will do my part to contribute no matter what the technology choices turn out to be.
Regards,
Kent
Right you are Kent, and I didn't realize I had make that mistake until after it was too late to edit. I was just thinking about what you need to type at that point.
Cheers, Bryce.
No worries. We're all in this together. Everything I know was learned the hard way😉
Tidal track search
I am getting the same issue as I did with the Tidal playlists when I am searching for tracks or artists using both Linn Kazoo and Lumin. It appears to find the track but then gives me the login or communication failure error. I have no idea where to start finding the issue. Probably also a upmpdcli issue? Any ideas please? Rpi 2B, Allo Piano + Kali, Moode 4.0
I am getting the same issue as I did with the Tidal playlists when I am searching for tracks or artists using both Linn Kazoo and Lumin. It appears to find the track but then gives me the login or communication failure error. I have no idea where to start finding the issue. Probably also a upmpdcli issue? Any ideas please? Rpi 2B, Allo Piano + Kali, Moode 4.0
Last edited:
I am getting the same issue as I did with the Tidal playlists when I am searching for tracks or artists using both Linn Kazoo and Lumin. It appears to find the track but then gives me the login or communication failure error. I have no idea where to start finding the issue. Probably also a upmpdcli issue? Any ideas please? Rpi 2B, Allo Piano + Kali, Moode 4.0
Ah, just tried and I see that as well, Linn Kazoo. Only when I search and click on "Tracks" and "Albums", but not on "Artist" it's fine.
Rpi3B Allo Boss
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi