Chord Electronics ☆ Poly ☆ (wireless & microSD module for Mojo) ☆★►USEFUL INFO on 1st PAGE!!◄★☆

Apr 10, 2019 at 10:55 AM Post #12,841 of 19,989
Peter, was your Poly a swapped out Poly from the first batch that were slow to power on? Or was it the original? I did not have to resort to inserting the SD card, but my Poly is a replaced unit. Maybe that is the difference?
Mine was a swapped out unit and needed the SD card trick.
 
Apr 10, 2019 at 11:09 AM Post #12,842 of 19,989
Trying out dsd songs using 8player Pro on my iPhone...impressive, no more dropouts and connection so far make me a happy user well done for this v2.00 firmware
 
Apr 10, 2019 at 11:12 AM Post #12,843 of 19,989
I had that exact same problem after updating to fw 2.0. It's worked perfectly today (we'll see about tomorrow :wink:). I deleted and re-installed Glider. Then it took a series of shutting down poly/mojo, restarting. Then force-quit/restart Glider. Repeat until a toothpick comes out clean. :smile:

Sorry to hear about Joe! He is one of the coolest nerds!! If anyone at Glider is listening, please let @joe28 that his absence is sorely missed.

My Iphone apps are flaky too I was primarily using Glider but now Mconnect seems to work better.

I too deleted and reinstalled Glider, and now it works great with 2.0 using hotspot mode (I haven't tried it yet using wifi). Glider always was inconsistent for me with the old firmware, but so far it appears to be smooth sailing. As for Joe- I haven't seen him here for a while and there is some talk on the Glider community board that he may have left the project. That is too bad as I agree Joe was a gem.

Back to 2.0 and Glider.
:)
 
Apr 10, 2019 at 11:51 AM Post #12,845 of 19,989
It's sad to see only Tidal and Qobuz integration with Poly. Qobuz isn't available in Canada yet and the last thing I want to do is give Jay-Z any of my money for a Tidal sub.

Would love to see Deezer HiFi included down the dev road? Hell, even Spotify Premium I'd take.
 
Apr 10, 2019 at 12:03 PM Post #12,847 of 19,989
My Glider observations - it all seems to be working well, but there are some changes, which is no doubt to be expected. Chiefly, I am now seeing three 'Network Sources' - one that's always been there, one that looks like just a (DLNA?) renderer, and one that describes itself as 'MPD Player @ [IP address]'. Anyone have this? If so, does it make any difference which one is selected as the output?

I'm no technician, so any comments welcome. I plan to stick with Glider if I can - does the job for me.
 
Apr 10, 2019 at 12:19 PM Post #12,848 of 19,989
It's all good, I'm on 2.0.0. Just need to figure out why M.A.L.P. isn't connecting though... :thinking:
Use GoFigure to check your IP address and that it matches M.A.L.P profiles
 
Apr 10, 2019 at 12:32 PM Post #12,849 of 19,989
Cheers for the info, I will check mine to see if it's the same, probably since it's 1.37, as mine were new a few weeks ago and the stock FW was 1.36 something, then it auto updated.

I was wondering, do you have guest mode turned off and full dynamic range turned on ? I'm using a mini toslink cable into TT2 and another CCA connected to H2, also via mini toslink.

Are you also using a mini toslink cable to connect your CCA to whatever device that you are plugging it into ?

It could be a problem with just using the toslink cable, maybe using the standard cable works ok ?

I would love to figure this out, as I'm stuck at 48khz on both.

Cheers


I am connected via 3.5mm line out. I have not checked the dynamic range or anything, just plugged in (I will check these setting)
Guest mode switched off.

OK checked full dynamic range was switched off, I have toggled this to on to see if any changes
 
Apr 10, 2019 at 12:40 PM Post #12,850 of 19,989
My Glider observations - it all seems to be working well, but there are some changes, which is no doubt to be expected. Chiefly, I am now seeing three 'Network Sources' - one that's always been there, one that looks like just a (DLNA?) renderer, and one that describes itself as 'MPD Player @ [IP address]'. Anyone have this? If so, does it make any difference which one is selected as the output?

I'm no technician, so any comments welcome. I plan to stick with Glider if I can - does the job for me.


Same here. (MPD)

I deleted and re-downloaded Glider.

It sounds terrific.
 
Apr 10, 2019 at 12:44 PM Post #12,851 of 19,989
Apr 10, 2019 at 12:51 PM Post #12,853 of 19,989
I am connected via 3.5mm line out. I have not checked the dynamic range or anything, just plugged in (I will check these setting)
Guest mode switched off.

OK checked full dynamic range was switched off, I have toggled this to on to see if any changes

Cool, so what I can see is that both of you are not using an optical cable, maybe thats the key to this bug, maybe it's limited to toslink users.

I'm gunna have to try a normal cable instead, but how am I going to connect it, as there is no line in on my chord gear, I will have to look at the manuals and then figure out how I can connect to them with a non optical cable.

Cheers
 
Apr 10, 2019 at 1:10 PM Post #12,854 of 19,989
I'm having a completely repeatable issue which is new to me with the firmware update. It happened as I was walking up and down the garden with a wheelbarrow listening to Poly via MALPD (though the same thing happens with playlists via GoFigure). I hear a click as Poly loses the connection to the house wifi as I go down the garden. Fine. As I come back I hear the click as it reconnects. Then the music stops instantly. Maybe I am just being dim, but it seems to me as though the new version of MPD on the Poly does not like disconnecting and then reconnecting to the same network while it is playing a playlist, and doing so makes it crash. As I say this is completely repeatable: it happens at exactly the same point in my walk up and down the garden (with horse manure, mind, so that may be to blame...) every time. I guess the work around is to put Poly in hotspot mode, but I also wonder if there is a simple fix. @MattBartlett any ideas?
 
Apr 10, 2019 at 1:12 PM Post #12,855 of 19,989
Cool, so what I can see is that both of you are not using an optical cable, maybe thats the key to this bug, maybe it's limited to toslink users.

I'm gunna have to try a normal cable instead, but how am I going to connect it, as there is no line in on my chord gear, I will have to look at the manuals and then figure out how I can connect to them with a non optical cable.

Cheers
Just for you I will test out 24/96 over optical tomorrow. Okeydoke? And I'll move further discussion over to DMs to avoid polluting this thread more.
 
Last edited:

Users who are viewing this thread

Back
Top