gapmedia

Forum Replies Created

Viewing 30 posts - 1 through 30 (of 39 total)
  • 6. Oktober 2021 at 0:56 #51714

    Hello MarioM,

    Just checked:
    #### LINUX-VERSION ####
    Distributor ID: Raspbian
    Description: Raspbian G
    NU/Linux 8.0 (jessie)
    Release: 8.0
    Codename: jessie

    I will try a new image and see if it works, thanks for your help.

    4. Oktober 2021 at 3:00 #51699

    Hello MarioM,

    Thank you for your reply.

    I have tried what you said and turned off any fixed IP assignment, but the behaviour is the same. If I re-enter the password and save, internet connection is restored/made.

    All I can tell you about the setup is that it is Max2Play Vers 2.47 on an RPi3 with Cirrus Logic/Wolfson card. Jessie and Wheezy ring a bell with me from when I downloaded the image 2+ years (?) ago. Sorry, not much into the programming side of Rpi’s. It does say on the settings page that I am using „Wolfson Cirrus Logic New (for Kernel 4.4.+)“.

    When I enquired on the forum a little while ago about later versions of Max2Play, I was told that the latest versions are written for the Rpi4 and will (possibly?) break the Wolfson Cirrus card in my setup. It was suggested not to upgrade. I may have that wrong, but the response will be written in a previous thread here.

    Edit: I have just remembered, my enquiry/discussion on upgrading to a later version of Max2Play was via email, not on the forum, sorry.

    Thank you again,
    Simon

    • This reply was modified 2 years, 7 months ago by gapmedia.
    20. August 2021 at 3:27 #51580

    Thanks Carousel and Jan,

    It’s working again. I logged into my router, and found that it was connected via LAN on a new address that didn’t appear to be showing on ‚Net Analyzer‘. I could be wrong here, in regards to ‚Net Analyzer‘ not showing the new address, as I was only really looking at the old addresses that were still showing, but not connecting to the Max2Play web interface. It has now gone back to connecting via wifi at its old wifi address, and/or the new address as well? One of the old addresses has dropped off.

    Is it usual for the device to have 2 accessible wifi addresses?

    Thanks,
    Simon

    • This reply was modified 2 years, 9 months ago by gapmedia.
    29. November 2016 at 13:22 #24325

    Hi,

    Thanks for the feedback. I will try your suggestions.

    29. November 2016 at 12:41 #24300

    Hi Christoph,

    Thanks for the suggestions.

    I have no data to backup my thoughts, but I am beginning to wonder if there is a difference between Raspberry Pi’s throughout the world. My Pi’s (Australia) are all made in China, I assume most Pi’s sold in Europe are made in UK (Wales?). Could this be a reason why WIFI (Access Point) and Bluetooth seem to perform better for some than others? Different chips? I would think that a RPi3 with on board WIFI and Bluetooth running Max2play should perform the same anywhere in the world, but I can’t seem to get somethings working as they should? Just a (stupid) thought.

    Simon

    29. November 2016 at 12:26 #24298

    Hi Stefan,

    I have watched the video-walkthrough, and believe I have followed the instructions correctly.

    I am running 2.38 which has been upgraded from an install of 2.31. I have not upgraded to the latest kernel under ‚Raspberry Settings‘.

    Here is the Bluetooth Debug output:

    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####

    #### PACMD LIST | grep active ####
    active port: <analog-output>
    active profile: <output:analog-stereo>

    #### PACMD LIST | grep sink ####
    Default sink name: null
    name: <module-null-sink>
    module.description = „Clocked NULL sink“
    module.description = „When a bluetooth sink or source is added, load module-loopback“
    module.description = „Automatically restore the default sink and source“
    name: <module-always-sink>
    module.description = „Always keeps at least one sink loaded even if it’s a null one“
    module.description = „When a sink/source is idle for too long, suspend it“
    module.description = „Load filter sinks automatically when needed“
    name: <module-null-sink>
    module.description = „Clocked NULL sink“
    3 sink(s) available.
    driver: <module-null-sink.c>
    driver: <module-null-sink.c>
    driver: <module-null-sink.c>
    driver: <module-null-sink.c>
    sinks:
    0 sink input(s) available.

    #### X-SERVER RUNNING ####
    1

    #### PULSEAUDIO RUNNING ####
    0 S 1000 1104 1 0 80 0 – 18635 poll_s ? 00:00:00 pulsebluetooth
    1 S 1000 1133 1 0 80 0 – 27737 poll_s ? 00:00:00 pulseaudio

    #### BLUETOOTH SQUEEZEBOX SERVER AUTOSTART ####

    28. November 2016 at 13:28 #24287

    I have installed Bluetooth hoping to stream from my mobile-phone to Squeezeserver, but neither my RPi3 can see my phone or my phone the RPi3? I have tried with both Sony Xperia (Android) and iPhone 5. The phones do see each other through Bluetooth though. I have tried uninstalling and reinstalling the Bluetooth plugin in max2play with no success.

    Simon

    28. November 2016 at 13:12 #24286

    Hi Chrischi,

    I seem to have the same problem.

    After access point is setup I can see max2play as a network, but only for a very short time immediately after re-booting. Sometimes I can login, but the connection only lasts briefly, and after that max2play will no longer shows up as an available network. On one occasion, and I have tried many, many times, my mobile-phone was able to stay connected to the max2play access point, login via the web interface, and control LMS via Squeezebox control for Android, so access point will work with my hardware (RPi3 and Wolfson/Cirrus card) but only ever that once.

    The same problem occurs with the Apple devices we have at home. I have tried turning of our home network to see if it interferes with the max2play access point, but it makes no difference. Does anyone have any suggestions I could try?

    Simon

    19. November 2016 at 4:09 #24018

    Thank you nonchalant. I will attempt your instructions, and see how I go.

    Regards,Simon

    17. November 2016 at 16:47 #23949

    Thank you Christoph.

    17. November 2016 at 16:42 #23947

    Nonchalant, this is fantastic news, thank you!

    Although at first read I do not fully understand how to implement the feature 🙁 Do I have to use Ragnar’s .asoundrc file as well as your script? Sorry, but I am a complete noob when it comes to programming. I think I can follow what I have to do with your script and the editing of the audioplayer.config, but I am not sure what to do with Ragnar’s file.

    Thanks for any further help you may be prepared to give me with this.

    Regards,
    Simon

    • This reply was modified 7 years, 6 months ago by gapmedia.
    17. November 2016 at 16:06 #23946

    I am also interested in mono output from Squeezebox Server, although I use the Wolfson / Cirrus card on RPi3.

    There is a setting for ‚Output Channel Mode‘ in LMS under Player/Basic Settings/Audio that allows you to choose Stereo, Left. or Right Channels for output in LMS, but unlike other settings in LMS this one doesn’t work for me. Does this setting work for anyone else?

    Thanks,
    Simon

    11. Oktober 2016 at 1:30 #23363

    Hi mike and Stefan,

    Mike, thanks for your reply. Seems 2.37 fixes things.

    Stefan, that is great news. Unfortunately, „the current version of Max2Play (version 2.37) uses a newer Kernel that fits the latest Max2Play-Image and uses a renamed Device Tree Overlay for the card.“ is all a bit above me technically, and that is why I love your M2P, it works and lets me do things with a RPi that I wouldn’t be able to without it. Maybe it is time or me to try and learn about DTO’s and Kernels.

    I have updated to 2.37 and all is still working, but I noticed under debug on the Settings/Reboot page that I am on Kernel 4.1.13, is this okay or should I update to Kernel 4.4.y that you mention below? How would I do this? Re-select the Wolfson/Cirrus card under Raspberry Settings and reboot?

    Debug info: Linux xxxx 4.1.13-v7+ #1 SMP PREEMPT Sat Nov 21 12:39:03 CET 2015 armv7l GNU/Linux

    I still see at the bottom of the Raspberry Settings page, ‚Upgrade to latest Kernel (breaks Wolfson Audio cards!):‘ Does this still apply, or this how to get to Kernel 4.4.y?

    Thanks.
    Simon

    4. Oktober 2016 at 1:09 #23273

    Hi Stefan,

    Thank you for the update. I am very happy to hear that the Cirrus/Wolfson card is still part of M2P’s future.

    Keep up the great work.

    Cheers,
    Simon

    18. September 2016 at 13:29 #23086

    UPDATE.

    Stefan,

    If I install from M2P 2.31 I am able to get the RPi3 and Wolfson/Cirrus card working and updated to 2.36. Is this because I do not change the Kernel installing this way?

    Maybe this was the way I originally setup my RPi3 systems, M2P 2.31, and why were working on 2.35. I certainly cannot setup the RPi3 and Wolfson/Cirrus card using M2P 2.34.

    I have noticed that the RED light on the Wolfson/Cirrus card no longer remains on permanently, which I think it used to. I believe the RED light has something to do with indicating whether the WM8804 digital interface chip is working in software or hardware mode? Not sure what it means under M2P.

    Simon

    • This reply was modified 7 years, 8 months ago by gapmedia.
    • This reply was modified 7 years, 8 months ago by gapmedia.
    • This reply was modified 7 years, 8 months ago by gapmedia.
    17. September 2016 at 5:03 #23074

    Hello Stefan,

    Thanks for your reply.

    If I understand correctly, you are saying that the Wolfson/Cirrus card no longer works on RPi3 and M2P? I can still see the Wolfson/Cirrus option under Raspberry Settings on 2.36.

    I have had 2x RPi3’s with M2P 2.34/2.35 and the Wolfson/Cirrus card running successfully for months.

    My issue started when I replaced my older NETGEAR N300 WNR2000 wireless router with a Linksys EA6300 AC1200 wireless router, due to Airplay stuttering streaming problems. My Rpi2 setup continues to work, and now streams perfectly from an IOS device using Airplayer, but I can no longer get my RPi3 setup to connect to the network. I thought something may have corrupted on my RPi3 setup, so I reinstalled trying 2.34, 2.35 and even 2.36 yesterday, but everytime I select the Wolfson/cirrus card, save the setting and reboot the networking functions of the RPi3 appear to be switched off. From then on I cannot connect to the RPi3 wirelessly or using LAN. Everything works perfectly wireless and LAN wise during installation until the Wolfson/Cirrus card is selected.

    I will try replacing my new router with the old one to see if the issue goes away.

    Stefan, I am not pointing my finger at M2P as the RPi3 worked beautifully up until I replaced my router. It seems to be an incompatibility issue that occurs between router and RPi3 after the Wolfson/Cirrus card’s software is introduced. I am not having this issue with any other device in my network and my new router though.

    Simon

    • This reply was modified 7 years, 8 months ago by gapmedia.
    • This reply was modified 7 years, 8 months ago by gapmedia.
    16. September 2016 at 2:39 #23062

    Hello Jac,

    Am I correct in reading that you are never able to get an IP address for your RPi3?

    If so, your problem is a little different to mine. I can setup my RPi3 wirelessly using WPS from the start up until the stage when I ‚install‘ my audio card (Wolfson/Cirrus card). It doesn’t matter what order I attempt to setup Max2Play as all goes well until I ‚install‘ the audio card. The next time I reboot the RPi3 no IP address is assigned to it, and it no longer joins the network. I cannot even reconnect using LAN. It appears that all wireless and LAN devices on the RPi3 have been disabled.

    Simon

    15. September 2016 at 15:44 #23045

    I am having a very similar problem.

    All has been working very well with Max2Play, Wolfson/Cirrus, and Rpi 2 and RPi 3.

    After I upgraded my router from a NETGEAR WNR2000 to Linksys EA6300 AC1200, due to Airplay streaming problems, I now cannot get an IP address for the RPi 3 setup, the RPi2 setup still work okay! Even an RPi3 that was already setup and working okay with the Netgear router will not work when tried with the Linksys.

    Setup goes okay with with all steps and reboots up until after the Wolfson/Cirrus card is installed. After rebooting at this stage neither LAN nor Wireless works again until a full reinstall. I noticed that the router is assigning the RPi3 a IPv6 address, but not an IP address. I switched off IPv6 in Max2Play, but the router still assigns the RPi3 a IPv6 but no IP. I also switched off IPv6 in the router setup, but an IP address is still not assigned after the Wolfson/Cirrus card is installed. Have tried setup 5 times now on RPi3 with same result each time straight after the Wolfson card is installed.

    I am installing 2.34, then upgrading to 2.35 in setup. The already setup RPi 3 that would not work with the Linksys was at 2.35 already.

    Simon

    • This reply was modified 7 years, 8 months ago by gapmedia.
    30. Mai 2016 at 4:20 #20399

    Hello,

    If the analogue input to the Cirrus/Wolfson audio card could be activated in Max2play and ‚passed‘ through to the outputs, I think that would provide a great feature for the system. I often use the built in power amplifier of the Cirrus/Wolfson card, and a line input would enable a phono-preamplifier, CD player, TV etc to be used as a source for the audio system.

    Regards,
    Simon

    30. Mai 2016 at 4:05 #20398

    Hello,

    I too have been ‚playing‘ with Inguz in LMS and would really like to have it available in Max2play if possible.

    Regards,
    Simon

    5. Mai 2016 at 0:15 #20049

    Hi Heiner,

    Thanks for your reply.

    I have just downloaded the new ‚m2p_rpi3_default_231.img.zip‘ and all is working with the RPi 3 and the Cirrus/Wolfson card again, many thanks for your great work!

    Best regards,
    Simon

    • This reply was modified 8 years ago by gapmedia.
    • This reply was modified 8 years ago by gapmedia.
    • This reply was modified 8 years ago by gapmedia.
    • This reply was modified 8 years ago by gapmedia.
    • This reply was modified 8 years ago by gapmedia. Reason: Problem solved by new M2P download
    7. April 2016 at 2:43 #19687

    Hi Heiner,

    Thanks for the link to the test files. I had a quick read about MQA encoding/decoding. Do you think that is something that can be included (licensed?) within Max2play in the future? It sounds very interesting.

    By following the instructions in the topic thread below, all seems to working correctly now with my DSD/DSF files.

    https://www.max2play.com/en/forums/topic/hifiberry-dac-pro-squeezelite-lms-7-9-nightly-dsd-fail/

    Do you know if there are any 12S DAC’s that play DSD over PCM through the Pi with Max2play? I assume my Cirrus/Wolfson card will only play DSD/DSF files converted to FLAC(?), as it will not play them unless I set the ‚DSD‘ setting to ‚Disabled‘, and the ‚FLAC‘ setting to ‚dsdplay‘ in the ‚DSF‘ setting under ‚File Types‘ in the LMS ‚Advanced‘ settings menu.

    Both 5.6 and 2.8 DSF files are playing successfully for me.

    Do you know if there is any quality loss of DSD files played-back ‚converted‘ to FLAC?

    Regards,
    Simon

    • This reply was modified 8 years, 1 month ago by gapmedia. Reason: Read about MQA encoding and decoding after looking at the test files link supplied by Heiner
    29. März 2016 at 16:18 #19506

    Hello Heiner,

    Thanks for the speedy reply, and solution.

    Simon

    29. März 2016 at 16:16 #19504

    Hello,

    Should I be able to play DSD (DSF) files using my Raspberry Pi2 B with Cirrus Logic/Wolfson card, and Max2play? I am not sure if my player supports DOP, but I have followed the above and still cannot see DSD (DSF) files in Squeezebox Server. I am using Nightly 7.9. The DSDPlayer Plugin shows as active, and all the settings and options mentioned above exist in the Squeezebox Server Web-administration settings menus.

    Thanks,
    Simon

    29. März 2016 at 16:00 #19499

    I have similar problem.

    After update to 2.29 USB memory stick will no longer mount. I get this message, „STORE N GO in not mounted (Device /dev/sda1 with UUID E772-4721)“ under „External Drives on Max2Play – mountpoints for USB-Storage“. I cannot access the device.

    Simon

    29. März 2016 at 15:53 #19498

    Hello,

    I have the same problem after updating from 2.28 to 2.29. When attaching a USB stick I get „STORE N GO in not mounted (Device /dev/sda1 with UUID E772-4721)“ under the „External Drives on Max2Play – mountpoints for USB-Storage“ heading. I am unable to access the device.

    Simon

    19. März 2016 at 4:10 #19364

    I have now tried setting up Accesspoint under Max2play 2.28. It shows Accesspoint as setup/installed under the web interface. but it appears that a ‚max2play‘ network is not created using the 2 different wifi dongles I have. Under 2.27 a ‚max2play‘ network was created using Accesspoint and one of the wifi dongles, but I couldn’t login to it.

    I was wondering if anyone using the Raspberry Pi 3 with onboard wifi has had success with Accesspoint under 2.28?

    Simon

    22. Februar 2016 at 23:49 #18636

    Hi Maximilian,

    Can I ask which wifi dongle you are using? The two different brand dongles I have both support accesspoint, but they don’t appear to be fully compatible with the Max2play Accesspoint. Also, one dongle appears to be ’slightly more‘ compatible than the other. Maybe if I can try the same wifi dongle as you Accesspoint will work as expected.

    As you have noted, Noop’s code allows me to create an Accesspoint using either dongle, and then successfully login with smartphone or PC. The only problem for me is that once Noob’s code is installed I cannot go back to wifi mode, even after uninstalling Accesspoint. Obviously, and as expected Noob’s code is still installed. The only way for me to reconnect the Pi to other wifi networks from then on is via LAN, or a fresh Max2play install. I could I suppose swap between installs on different SD cards. Not my preferred option.

    Thanks for Max2play, and your ongoing support.

    Regards,
    Simon

    17. Februar 2016 at 13:16 #18534

    Hi Alex,

    I have a similar issue. I own a Logitech Touch, which was my inspiration for trying the Pi with Max2play. I have to say that I think the Pi and Cirrus/Wolfson surpasses the Touch. Stupidly, I often forget that I have LMS running on my PC, and it takes ‚control‘ of the Pi before I remember what’s going on, and I have to switch the Pi from one LMS to the other. No big problem really.

    I think Noob has solved the Accesspoint problem, but unfortunately Max2play doesn’t ‚know‘ about the new ‚files‘ it has to remove to go back to wifi. I hope Noob and Maximilian can get together and combine their codes to fix the Accesspoint issue.

    With Noobs 6 lines of code ‚installed‘ in Max2play all works brilliantly with Accesspoint and both of the USB wifi dongles I own , in my case anyway. Without Noobs code installed in Max2play, one dongle shows me a ‚max2play‘ network but does not allow me to login, and the other (Edimax) dongle creates no SSID for ‚max2play‘ at all.

    The only problem is that after Noobs code is installed in Max2play I cannot go back to wifi, even after connecting with LAN and removing Accesspoint. On bootup the dongles show activity , but then stop flashing and never create a wifi connection. The only way back to wifi access is a fresh install of Max2play.

    Regards,
    Smon

    16. Februar 2016 at 15:50 #18522

    Hi Alex,

    Just saw your post above after I posted the bit below. I am off to bed now, hope you have a successful meeting. As you will see, I have had some success thanks to you, just have to work out the ’switching‘ between wifi and accesspoint operation.

    I worked out the Putty bit. Didn’t realise when I paste the script it will just run.

    Hooray!!! The script worked. I was able to log onto ‚max2play‘ network, and find the max2play Gui on my devices. Then, as I had not installed the Squeezebox Server, I decided to remove the Accesspoint so I could setup the Server from the Net. Unfortunately, this seemed to remove USB wifi dongle support and the wifi did not load on reboot. It is not responding to WPS at startup either. I will reconnect to the LAN in the morning to see if I can set up the wifi again, and if this is a reoccurring issue when switching between Accesspoint and wifi. I would like to be able to switch between wifi access and Accesspoint at times if possible, without having to connect to LAN. Have you tried ’switching‘ between wifi and Accesspoint? Did it work for you?

    Anyway, thank you and Noob for your help and instructions. At least I have seen Accesspoint work now. Just hope I can figure out the last little bit.

    Regards,
    Simon

    • This reply was modified 8 years, 3 months ago by gapmedia.
Viewing 30 posts - 1 through 30 (of 39 total)