Cassio299

Forum Replies Created

Viewing 30 posts - 31 through 60 (of 71 total)
  • 19. Februar 2019 at 8:40 #44519

    Hi Josh

    Okay lets take a different aproche before those PI’s will be unwillingly flying out of the window!!.

    I think, there must be something odd going on in the settings department…

    Let us recap, there might be something we have overlooked.

    1. On the ‚Mainroom‘ Raspberry Pi 3+ you have Squeezelite, Bluetooth and Multi-squeeze running. You are streaming sound from your USB soundcard and a device connected to the 3.5mm audio jack.You own a 3a 5v power supply wich you are using with your ‚Mainroom‘ Raspberry Pi+

    Your ‚Mainroom‘ Pi 3+, was working fine until suddenly the audio jack stoped working.It started working again After a software reinstall. The audio jack worked for aprox. 5 days before it stoped working again.

    At the end of January the audio jack still doesn’t work, and you have almost given up on bluetooth to work also. However you do not uninstall the plugin.

    2. February: Your installation has changed you are no longer streaming/playing from one Raspberry pi 3+ ‚Mainroom‘ with a USB card and a 3,5mm audio device. The second device is called ‚desk‘ player. The second player also have a defect audio jack. You tried with the same SD card and sound cards with the same result and therefore think that the problem is the software.

    3. On the 18th you send me your Pi’s boot report (Demsg) from a Raspberry Pi called ‚Soundsystem‘ properly with new installed software and clearly not the same as the Pi called ‚Mainroom‘. Maybe a third PI??.

    A finally one of the first thing I asked you to do was telling me the status of the settings of Squeezelite and Shairport in the Audioplayer tab. On the 15th. you told me that the status was: Active: inactive (dead). also not running.

    On the 18th you wrote: I disabled the autostart of Squeezelite and Shairport in the AudioPlayer tab, however they still seem to start and run and the 19th you wrote: I cannot stop squeezelite and shairport (Trying to stop … could NOT stop process – try kill instead) and sometimes kill does not work. When I do manage to kill the processes, once I reload the page they have started again. The checkboxes are unticked.

    I now know that there are only one person who can solve the mystery of the sudden death of the auxiliary output!!!

    And that person needs to find out who, how and what in the chase of the unstoppable process!! first.

    Until then I wish you a happy reinstalling!!

    Peter

    18. Februar 2019 at 13:59 #44508

    Ups sorry didn’t know that !!

    18. Februar 2019 at 13:47 #44505

    Hi Josh

    Thats weird … in AudioPlayer tab try this: Squeezeligt: stop Squeezeligt then unmarked auto startup then click save next to it
    do it the same way for Shairport.

    reboot

    and go back and check.

    Have you checked bluetooth settings that you have picked the 2nd from top ALSA HDMI ?

    Peter

    18. Februar 2019 at 9:39 #44489

    Hi Poul

    Install the multisqueeze plugin

    Do the following settings:

    Audioplayer tab
    turn off Squeezelite
    turn off Shairport
    (remove the autostart mark and hit save)

    Multisqueeze tab

    Set the Instance as follow:

    Instance 0 : (Edit advanced options) sound card: default bcm2835 ALSA……..card = ALSA (your 3,5mmm jack)
    Instance 1 : (Edit advanced options) sound card: plughw – snd_rpi_hifiberry

    Set Audio Output on Raspberry PI: Force Headphone Jack

    Your audio jack out is called Max2Play_0 in squeezeligt
    Your audiophonics card is called Max2Play in squeezeligt

    Reboot

    that’s it

    Peter

    18. Februar 2019 at 9:09 #44487

    Hi Josh

    Your boot up file (Dmesg file looks ok) you do however have a hang on boot (just a delay):
    [ 4.297395] random: crng init done
    [ 4.297411] random: 7 urandom warning(s) missed due to ratelimiting

    this can be avoided by installing:

    sudo apt update
    sudo apt install haveged
    sudo systemctl enable haveged

    If you want!!!

    You should also expand your SD card if you haven’t already done so (to avoid future hang ups)

    You do so in the settings/reboot tab click on „expand filesystem“ then Reboot

    The following settings are important for your device to work as intented:

    Audioplayer tab
    turn off Squeezelite
    turn off Shairport

    Bluetooth tab
    Sound Device: Alsa – hw:0.1 HDMI (because you are using the 3,5mm jack wich needs the Alsa – hw:0.0 driver to run)
    (if you have set it to hw:0.0 unload bluetooth speaker change the setting and click save)

    Multisqueeze tab
    Your cards readout said that card 0 was the Alsa driver and card 1 was the USB DAC (this is the normal standard so nothing was changed here)

    Set the instances according to that

    Instance 0 : sound card: default bcm2835 ALSA……..card = ALSA (your 3,5mmm jack)
    Instance 1 : sound card: default – USB AUDIO DAC, or front – USB Audio DAC
    Instance 2 : sound card: Your Bluetooth Device (if you have a bluetooth audio speaker)

    Set Audio Output on Raspberry PI: Force Headphone Jack

    Let me know if this did anything !!

    Peter

    • This reply was modified 5 years, 10 months ago by Cassio299.
    17. Februar 2019 at 0:12 #44476

    chose the sound output through the card in the Alsa(). —- Do you mean selected the IQAudIO driver in the IQAudIO plugin ??

    Sometimes things in the PI get a lille mixed up therefore: check sound card plugin and Raspberry Settings and Squeeze light if you use that!! for your sound card selections. If everything look OK do this:

    shout down your pi

    unplug only your HDMI cable

    start your pi without your HDMI cable pluged in

    shut down your pi again

    and boot it up again

    16. Februar 2019 at 10:44 #44470

    Hi Alex

    Stop the bridge

    save the settings by clicking Use down bottom right on the page then you se a generate button !!

    16. Februar 2019 at 4:08 #44468

    Okay

    There is nothing wrong with the basic settings

    We can take a look at the log for hardware to see if there is any error message:

    Open Remote Control plugin and type:

    dmesg

    The last thing I know of that we can do… making the audio jack output the default output and/or secure that it stays that way

    I need the readout of those two commands:

    cat /proc/asound/cards

    and

    aplay -l

    This will show us in which ordre the sound cards are loaded there after we can set up a new file to make sure we that always get the same order!!

    • This reply was modified 5 years, 10 months ago by Cassio299.
    16. Februar 2019 at 1:14 #44467

    Hi chrimoe

    user: pi

    password: max2play

    for root login you need to change password in the Password Protection plugin (I needed to do that)

    15. Februar 2019 at 8:25 #44460

    Hi Josh

    There is no overlap in your settings and boot config is also ok, I can’t see if you have marked jack instead of HDMI but you have told Heiner that you did.

    Normally when we talk about software errors its more black or white (either it works or it doesn’t) It is more likely some outer interference ….. like your power supply (we are all hav’ing that problem sooner or later) I wood suggest that the next thing to try is the minimalistic approach. uninstall bluetooth and unplug your usb sound card. If you have other usb / GPIO devices pluged in remove them too.

    maybe if load all on one PI and nothing on the other … does that make a difference ???

    Most 5v plugs are more likely 4.6-4.75v wich is too low for the PI.

    Let me know the result of your test, I will try to think of any other possible solution.

    Peter

    14. Februar 2019 at 4:22 #44457

    Hi Josh

    I might be able to help if we work together!!

    I have looked at your enclosed debug files and I can see that you haven’t done a update lately

    If you go into the raspberry settings tap and scroll down to „Kernel and Package Updates and Upgrades“

    next: Reboot your PI

    If you haven’t installed the plugin: Remote Control do it and set it up

    I need to know the status of two programs

    After you have locked in with your user/password type:

    sudo systemctl status shairport

    look for the line „Active:“ and let me know what it says here after.

    Do the same thing with:

    sudo systemctl status Squeezelite

    looking forward to your answer

    Peter

    14. Februar 2019 at 1:48 #44456

    It sounds like a very good idea, good luck !!

    Peter

    13. Februar 2019 at 19:11 #44451

    Hi Fernando3728

    Setting up a display is not something done very easy….. it needs some programing and a lot of time. Therefore I usually find a preprogramed install.

    I use pydPiper for my display, it works with Logitech media server and squeeze light. you can find it here: Click here!!

    You will need the plugin: Remote Control to install it if your display is supported.

    Peter

    13. Februar 2019 at 18:57 #44450

    Hi Raymond

    Did the IR receiver work with the hardware plugin ??

    11. Februar 2019 at 21:21 #44434

    Edit:

    Du kannst dieser zurrücksetzung uhmgehen indem du einen force komando im aufstart eingeben:

    öffnet XTerm programm:

    sudo nano /boot/config.txt (eingeben)

    Mit dem Pfeiltaste nach unten bis die Zeile: „# uncommet if hdmi display is not detected and composite is being output“

    Entfernt das # von der nästen Zeile:
    „#hdmi_force_hotplug=1“

    add: hdmi_drive=2 (unter hdmi_force_hotplug=1)

    So solt es aussehen:

    # uncommet if hdmi display is not detected and composite is being output
    hdmi_force_hotplug=1
    hdmi_drive=2

    Danach:
    [Ctrl] + o (das buchstabe)

    [Ctrl] + x

    sudo reboot

    —–
    nach dem reboot check ob de hdmi modus stat gefunden hat:

    im XTerm:

    tvservice -s [enter]

    es soll jetz so aussehen: state 0x120006 [HDMI CEA (5) RGB lim 16:9], 1920×1080 @ 60.00Hz interlaced

    10. Februar 2019 at 15:46 #44426

    Hi Gregor

    Have you installed the correct drivers for your display ???

    10. Februar 2019 at 15:24 #44425

    Hi Peter

    Make sure that Build-In-Audio is disabled in Raspberry settings, if not disable it and make a reboot.

    Go into the audio player tab under Squeezelight settings click advanced and check if your soundcard is available.

    let me know the answer

    Peter

    10. Februar 2019 at 10:23 #44423

    Das originale Netzteil von Raspberry PI hat 2.5A und was wichtiger ist 5.1 Volt. Die meisten von der günstigen leifert oft zu weig Volt.

    Im meiner Einstellungen auf der PI gibt es keinen HDMI modus wahl.

    Um die einstellungen näher anzushauen brauche ich den status von tvservice:

    Im menü geht zur System Tools klick auf XTerm programm

    schreibt: tvservice -s [enter]

    schreibt mir bitte den antwort

    9. Februar 2019 at 2:36 #44419

    Hallo Peter

    Dein Problem klingt für mich, wie zu wenig strom. Benutz du der orginale Raspbery PI netzteil??? sonst versuch es mit einem anderen netzteil der mit 2,5 order 3 amp die Pi verzorgen kann.

    (auch hir:) Peter

    5. Februar 2019 at 1:18 #44348

    Well, I will try a bit more specific

    login to your Logitech media server (LMS) in your web-browser. On the front page to the left you see the same menus as you see on your lcd (with Jivelight) on the right side you find LMSs web-player.

    On the bottom right click were it says settings!

    A new webpage open with a lot of settings.

    On the top just below the „Logitech Media Server“ you will find 8 taps… the first is already open.

    Slik on the second tap it should be called something like player/players

    Just below the name of the second tap, you will find scroll down buttons
    The first scroll button should show the name of your player (check with your lcd touchscreen on top on the first page)

    On the second scroll button click on it and find were it says Menus!!

    See if you can find a line with Kodi or XMBC in there and unmark the mark in front of it.

    ——————————-

    If you can’t find anything with the name Kodi in there stay on the web side!!

    Click on tab number 6 (should be called something like extensions)
    The first extensions / plug-ins are all marked see if you can find something there called Kodi or XMBC and unmark it.

    Ps you can unmark all extensions and still have a functional player

    Let me know if that worked !

    Peter

    3. Februar 2019 at 16:38 #44327

    Hi geert56

    First of!! that’s easy!! next leave the first 4mb alone do as following:

    1 click on the ext4 /29GB partition (just mark it)
    2 click on the white arrow shaped icon (3ed from the left in the top bar)
    3 in the pop up you can either move the slider in the pictogram or set „new Sitze to max hight
    4 click „ok“ (verlichten)
    5 click on the green marker in the top bar
    that’s it!! your 195,31mb is now part of the the ext4 partition

    Peter

    3. Februar 2019 at 16:13 #44326

    Hi dicker007

    Triode / RichieZed’s Spotify Family app hasn’t been updated since 2017, and will most like not be updated anymore.

    Michael Herger created therefore a plugin called spotty which also supports Spotify’s families account. I would suggest that you ditch the Spotify Family plugin and use the „Spotify/still spotty“ plug-in in LMS. I run 7.9.2 here on my PI server and it runs just fine !!! -:)

    3. Februar 2019 at 15:28 #44325

    Hi Notroot

    Max2play uses the rasbian version of Kodi, which according to Kodi them selves, is stil version 17.3. Take a look: here

    I think you will more likely get an answer on the Kodi forum before max2play will know it!!

    3. Februar 2019 at 15:06 #44324

    Hi Frank

    It is possible to customize Jivelite via Logitech Media Server. in /settings(bottom right)/player tab (2nd top left)

    In the player tab (top left: scroll down) pick the name of the player where your Jivelite is installed on + pick menus in the next scroll down.

    You can also completely new menus with a plug-in called Custom Browse take a look: Here

    Peter

    24. Januar 2019 at 1:02 #44109

    Hi Markus

    why are you marked as a moderator ??

    10. Januar 2019 at 7:24 #43362

    Great….. you have already learnt a lot…

    Setting a share
    check if it is mounted
    and a fix if it isn’t

    have fun with you media player and server

    10. Januar 2019 at 6:18 #43357

    Exact !! we have to do some cleaning Heres what it should look like:

    //192.168.1.254/share <tab x1> mnt/share <tab x1> cifs <tab x1> user=samba,password=12345678,sec=ntlm,iocharset=utf8,vers=1.0 <tab x1> 0 <tab x> 0

    Check that the above filenames share + user and password are correct !!

    <tab x1> = the tab button

    You navigate the cursor inside fstab with the arrow keys!!

    Its one long line. Don’t mind when some of the text disappear while you are tapping. The spaces with tab and the non space between the commas are very important.

    Hit control + x
    write:yes
    Hit enter

    Reboot !!

    check if your share is mounted with:

    cd /mnt/share
    ls

    edit: I allmost forgot: I do not recommend that you copy/paste the above code …

    • This reply was modified 5 years, 11 months ago by Cassio299.
    10. Januar 2019 at 4:44 #43352

    You can only see the gui if you connect a tv/monitor

    ohh…. Im forgetting that Max2play dos’nt have the full raspbian version you might not be able to mount disks on the disk top!!
    Better stick to the ssh method!!

    10. Januar 2019 at 4:37 #43350

    If the Pi can’t login to your shared disk, it will not mount it!!

    It is quit easy to see if your disk is mounted:

    option 1: connect you pi to a monitor/TV

    – click the raspberry icon in the menu bar on the desktop
    – click settings
    – click Appearance Settings
    – mark Mounted Disks at the bottom of the page
    – click ok

    option 2

    ssh to pi from another Mac or PC

    cd /mnt/share
    ls

    You should now see folders and/or files from your disk connected to your router

    If your shared disk is not mounted…… you will have to dobb or tribble check your settings especially:

    sodu nano /etc/fstab

    remember: there is no space between your code every space is a tab.

    (to close fstab after you have edited: Control+X type:yes hit:enter)

    6. Januar 2019 at 9:52 #43176

    Sorry I just look up some standard internal ip addresses and yours were among it.

    If you still gets trouble after that the remove the password settings in your samba settings and just use your routers login and password

Viewing 30 posts - 31 through 60 (of 71 total)