Cannot get the system to work about studiodisplay

[KyleRickards]

Actually how do I completely remove this and all the installation files, I cannot get it working and would like to go back to a clean install?

[Moonbase59]

Sorry for the late response. I agree that StudioDisplay can be a bit overwhelming until you get around the concept of having a central MQTT server and possibly many machines interacting with it, each having their own ~/studiodisplay folder and own config file (named after their hostname).

Nevertheless, except for Weather Underground revoking their free keys (see #4), StudioDisplay still works fine on many installations. I also plan for another weather module.
If I can be of further help, let me know.

Now if you really want to remove it from the system(s) you have installed it own, that’s pretty easy: If you installed according to the README, you should have a folder called "studiodisplay" in the home directory of any system you installed it on (~/studiodisplay). Just completely remove that, using a file manager or the command rm -rf ~/studiodisplay.

On all machines where you have modified the crontab:
Remove the crontab lines added during the installation process (they usually have a command like /home/pi/studiodisplay/… in them) using

crontab -e

On the IDJC machine, only if you have made an autostart for the IDJC Monitor:
Remove the autostart, either the crontab entry or the Autostart you defined in your desktop environment.

Optional (remove only if you are really sure you don’t need it for anything else!): If you have prepared a machine especially to act as the central MQTT and web server (like a Raspberry using FullPageOS), you can (on that machine) …

Completely remove the MQTT server:

sudo service mosquitto stop
sudo apt-get purge mosquitto mosquitto-clients

Remove the web page link created in /var/www/html on your web server:

sudo rm /var/www/html/studiodisplay

Remove (or comment out) the redirection line in your web server’s config file:

sudo nano /etc/lighttpd/lighttpd.conf

# redirect to StudioDisplay
url.redirect = ("^/$" => "/studiodisplay/" )

Then restart the web server:

sudo service lighttpd restart

Everything should be "clean" again.
Sorry if it didn’t work out for you!

[KyleRickards]

Hi Thanks for getting back to me, I wish I could get it working as it should but oh well! It does look very good though. Kyle

…

Sent from my iPad On 29 Jun 2019, at 09:37, Matthias C. Hormann <[email protected]> wrote: Sorry for the late response. I agree that StudioDisplay can be a bit overwhelming until you get around the concept of having a central MQTT server and possibly many machines interacting with it, each having their own config file (named after their hostname). Nevertheless, except for Weather Underground revoking their free keys (see #4), StudioDisplay still works fine on many installations. I also plan for another weather module. If I can be of further help, let me know. Now if you really want to remove it from the system(s) you have installed it own, that’s pretty easy: If you installed according to the README, you should have a folder called "studiodisplay" in the home directory of any system you installed it on (~/studiodisplay). Just completely remove that, using a file manager or the command rm -rf ~/studiodisplay. On all machines where you have modified the crontab: Remove the crontab lines added during the installation process (they usually have a command like /home/pi/studiodisplay/… in them) using crontab -e On the IDJC machine, only if you have made an autostart for the IDJC Monitor: Remove the autostart, either the crontab entry or the Autostart you defined in your desktop environment. Optional (remove only if you are really sure you don’t need it for anything else!): If you have prepared a machine especially to act as the central MQTT and web server (like a Raspberry using FullPageOS), you can (on that machine) … Completely remove the MQTT server: sudo service mosquitto stop sudo apt-get purge mosquitto mosquitto-clients Remove the web page link created in /var/www/html on your web server: sudo rm /var/www/html/studiodisplay Remove (or comment out) the redirection line in your web server’s config file: # redirect to StudioDisplay url.redirect = ("^/$" => "/studiodisplay/" ) Then restart the web server: sudo service lighttpd restart Everything should be "clean" again. Sorry if it didn’t work out for you! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Moonbase59]

Thanks for the kind words. Unfortunately, with the multitude of possible configurations, I can’t foresee every possible issue. Were you installing (parts of it) on a Pi or just trying the first steps on your IDJC machine? If yes, what Linux did you use and which version of IDJC?

Did you study the files in the docs folder? Maybe the architectural overview in https://github.com/Moonbase59/studiodisplay/blob/master/docs/architecture.md helps to get the idea?

[KyleRickards]

Hi I’m on Linux Mint 19 and latest version of IDJC, just using my intel machine? I did try and work through the instructions but one bit totally threw me

…

Sent from my iPad On 29 Jun 2019, at 19:58, Matthias C. Hormann <[email protected]> wrote: Thanks for the kind words. Unfortunately, with the multitude of possible configurations, I can’t foresee every possible issue. Were you installing (parts of it) on a Pi or just trying the first steps on your IDJC machine? If yes, what Linux did you use and which version of IDJC? Did you study the files in the docs folder? Maybe the architectural overview in https://github.com/Moonbase59/studiodisplay/blob/master/docs/architecture.md helps to get the idea? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Moonbase59]

What was the bit that threw you?
By saying "latest version of IDJC" do you mean the version from the repos or did you compile IDJC yourself? What version does IDJC show on the "Help → About → Help" page?

Traditionally, StudioDisplay is meant to run on its own Raspberry Pi, driving a big wall-mount studio display (a replacement of the old studio clock) and possibly some signal towers, but it CAN be run on the IDJC machine for testing purposes, of course. What do you plan to use it for? Mainly driving a fancy display, driving a professional studio signal tower, or both? Or maybe even integrating your studio signalling into your home automation system?

I do have a Linux Mint 19.1 (Cinnamon DE) Intel machine here on which I added all the "Ubuntu Studio" stuff (to get JACK2 + PulseAudio running), and currently run a self-compiled IDJC 0.8.18_development on that machine. So we might be able to compare one thing or the other.

If you are not too far apart (timezone-wise), we might even have a voice chat on my Mumble server, or maybe even a short AnyDesk session for a little installation help.