SqueezePlay OS (Version 2) for OpenFrame

[offbeatdave]

How would I go about making this available to anyone who might want it (free)? Would you want it for SqueezePlayOS?

It's a +1 from me! It looks great, just like the wordclock which a forum user made for the Openpeak/o2/PnP III OS! Love the look of it from the photo! It would be the clock of choice for my bedside sqpOS2 Joggler.

[johnnygal]

First off roobabrb, thanks for the release. I am trying it out now on one of my jogglers.

Has anyone seen the time on the jogglers jump to 27 Feb 2023? I have had it twice now on the SQ OS v2 joggler in the few days I have been running with it. I have never got this on my other 2 jogglers running SQ OS v1.

Any ideas? Is this release using different time servers? Anything I could try?

Thanks.

[roobarb!]

Has anyone seen the time on the jogglers jump to 27 Feb 2023? I have had it twice now on the SQ OS v2 joggler in the few days I have been running with it. I have never got this on my other 2 jogglers running SQ OS v1.

How weird! The software queries an NTP server whenever the network connection comes up, so it should at least begin correctly. I've just checked a unit I've had running for a few hours here and the date and time are still correct. Most bizarre!

Just so everyone knows, I'll not be able to get on the forums for a week or so. I know there are a few outstanding issues with v2 at the moment (most notably the lack of AirPlay support and a bit of a bug with auto-configuring of DNS servers) which I have actually fixed, but don't have time to package up and release today. The next version should have all of this working and an update to SqueezePlay to take off the remaining rough edges.

If you're really desperate, v1 is still on the server if you need it.

[pete]

Yup; here I utilize my PFSense firewall internal NTP server connecting to a GPS with PPS today.

Then again I have always utilized an internal NTP server.

[johnnygal]

Has anyone seen the time on the jogglers jump to 27 Feb 2023? I have had it twice now on the SQ OS v2 joggler in the few days I have been running with it. I have never got this on my other 2 jogglers running SQ OS v1.

How weird! The software queries an NTP server whenever the network connection comes up, so it should at least begin correctly. I've just checked a unit I've had running for a few hours here and the date and time are still correct. Most bizarre!

Yep, very strange. When it does happen a reboot sorts it out, as it resyncs at startup.

Will keep an eye on it anyway.

[mikeywilliams]

Just got one of the ex-betting shop jogglers without stands and SqueezeplayOS is working wonderfully on it.
The removed stand may cause some overheating - opinions differ as to how much cooling the stands actually achieve. My question is as to under what conditions SqueezeplayOS is likely to stress the processor - and what the noticeable effects of overheating would be - sound stuttering or what?

[dan1502]

I'd greatly appreciate some help.

My Joggler was working fine running Squeezeplay OS and EDO along with an Audioquest Dragonfly. It worked without issue as it also did with the Benchmark DAC1 HDR. I had to do the relaunch work around when using it with an M2Tech Hiface 2.

So I recently picked up a TEAC A-H01 which is a combined DAC and integrated amp. It is listed as working with kernel 12 on the EDO compatibility spreadsheet.

Although the it could be seen listed in Squeezeplay I had all sorts of issues such as it not booting with the DAC switched on then when relaunching after switching the DAC on it wouldn'd connect to the server.

So first I updated the Vortexbox LMS to V7.8. This didn't help.

I then updated to Squeezeplay OS v2.4. It then would boot up fine with the DAC switched on but it wouldn't connect with the server.

I used a brand new USB2.0 lead. I tried switching it with another and I got music.

So I tried a hi-res file and got lots of clicking and gaps.

So I thought I try it back with the Auidioquest Dragonfly.

It sees the Dragonfly but show no streaming information.

It plays but the volume is unbelievably quiet.

I've tried reinstalling both the OS and EDO and removing asound.conf and also checking a few other things as far as I could understand from the thread.

So the plan was to check the Teac A-H01 with the Joggler that has been working fine for months then if all ok, buy another. Now I feel I've screwed everything!

So this is a bit of a beg for help as I've now spent about 12 hours or more trying to sort it.

[dan1502]

I thought I'd give it another go this morning. I reflashed Squeezeplay OS v2.6 and then added EDO as per page 4 (I think) of the hi-res thread on here.

I then tested it with the Dragonfly again. The colour of the dragonfly changes to recognise standard and high res files and both play but with very low volume. There is no info where you would normally see asynchronous and speed info etc in audio settings.

I then tried it again with the TEAC A-H01. With this it plays standard resolution files fine but clips with high res. Again no information is provided when going into the DAC in audio settings during playback. However 99% of our music is standard CD quality so at least it works and the system can be used as intended. I have ordered another Joggler so shall load the old Squeezeplay OS (and EDO) onto that and hopefully that will then work with the Dragonfly in that system.

It would still be good to get this working properly with EDO and the new OS. I also have a Benchmark DAC1 HDR so I shall probably try it with that later in case knowing whether that works helps.

I just wish I could understand programming and have a go at resolving it myself.

[Man in a van]

Did you read from here, there is also info on this page about the patch for hi res files,


http://www.jogglerwiki.com/forum/viewto ... 0&start=80

also, maybe you can adjust the volume in the settings?, cancel the internal speakers and increase the volume setting?.

Sometimes when doing a re-install I start with a new Openpeak and then the new SPOS

http://birdslikewires.co.uk/articles/openpeak-firmware .


atb.

Ronnie.

[dan1502]

I did read that Ronnie but it was a bit over my head if I'm honest and I wasn't sure exactly what to do to try it. Also, the TEAC A-H01 uses the Burr-Brown PCM5102 DAC which I think is different to the UD-501. Would using this solution with the new OS (v2.6) be ok?

I haven't tried reinstalling Openpeak before flashing with SPOS. Is that really worth trying? (I'll read the link)

Thanks, Dan

Just to add that I tried it with the Benchmark DAC1 and it plays standard and hi-res fine but bear in mind this is not asynchronous (again no info).

[Man in a van]

Dan,

I don't think that the DAC is the problem, more the USB chip which is the Tenor that has caused previous software problems:

http://www.teac-audio.eu/en/products/a-h01-83773.html

What sometimes helps is to install the OS via a passive USB hub and also to connect the Joggler via the same Hub ( this method is documented somewhere over on the original EDO thread on the squeezebox forum.

Again with regard to the low volume, maybe you can adjust the level in the Alsa mixer via SSH once you can resolve the connection problem.

atb.

Ronnie

[dan1502]

Ah, ok, that makes sense then. So I guess it brings me back to my question as to whether the solution you kindly linked to above should work ok with SPOS v2.4 (if not I could reflash with v1.9) and either way whether you or someone else would mind expanding on what is suggested in that link so as I know exactly what to type via putty.

Presumably to check the alsa mixer I just type alsa at the command line? If I recall correctly it tells you how to change and save values.

[JimbobVFR400]

Use alsamixer as all one word and you get a GUI to alter levels.

[dan1502]

Thanks, I shall try that.

I just read through the TEAC UD-H01 and the specs Ronnie linked to and the Tenor USB chip is the same.

Hopefully Wilberforce will come to my rescue and and explain how I go about implementing the fix including confirming whether or not I should first reflash with SPOS v1.9. I note some of the lines in the patch refer to TEAX UD-H01.

[Man in a van]

Dan, after loading the Internal OS v1.9 I SSH'd into the Joggler and pasted this,

Code: Select all

    cd ~
    wget http://www.jogglerwiki.com/forum/download/file.php?id=329 -O EnhancedDigitalOutput.tar.gz
    sudo tar -xvf EnhancedDigitalOutput.tar.gz -C /opt/squeezeplay/share/jive/applets/ --overwrite

then I pasted these two commands for the hi-res files,

Code: Select all

    sudo apt-get update
    sudo apt-get install patch

and,

Code: Select all

    cd /usr/share/perl5/Slim/Player
    sudo wget https://raw.github.com/terual/slimpy/master/192kHz.patch
    sudo patch < 192kHz.patch

Wilberforce did provide a new kernel and instructions for the Tenor if you look here

http://www.jogglerwiki.com/forum/viewto ... 0&start=80

but as the new OS has an updated kernel perhaps this is not required.

I can't help with Linux as I only just lernt to spel it

keep trying.

atb.

Ronnie

[dan1502]

I'm fine with loading the OS and EDO. I've even written out instructions to help others without having to trawl through the threads and in very simple steps.

I think the commands for hi-res files are to adapt LMS (but correct me if I'm wrong) which I don't need to do as I use a Vortexbox, the software in respect of which is already adapted for hi-res.

I have read Wilberforce's instructions and kernel you link to. It's following that which I struggle with. I don't really understand them enough to even try i.e. what to type where, whether I perform the instructions after installing the OS and EDO etc etc. I would also like to know whether I need to reflash back to 1.09 first (which is not a problem).

[Man in a van]

I would guess that if you follow Wilberforce then to be safe you will need v1.09.

why not try a PM to the gent?

atb

Ronnie

[dan1502]

Sounds like a plan. Why didn't I think of that?

[JimbobVFR400]

AFAIK LMS already has support for high res files, the EDO applet adds the extra capability to Squeezeplay.

I'm not 100% convinced LMS needs the patch

[dan1502]

I think it might be to raise the capability beyond 96 but I know this was definitely incorporated into the LMS version packaged with Vortexbox software and therefore not necessary.