Closed leicray closed 5 years ago
Thanks for the post. Please be assured that there is no intent to make Shairport Sync not work with Tuneblade. Can you tell me what version of Shairport Sync you are using please?
You could use:
$ shairport-sync -V
$ shairport-sync -V reports:
2.8.4-OpenSSL-Avahi-ALSA-stdout-soxr-metadata
Hello again. A very quick check with Windows 10, Tuneblade 1.5 and a few AirPlay devices – a real AirPort Express and a couple of Shairport Sync devices – shows the latest Shairport Sync development version to be working fine. It'll take me a little while to get back to the 2.8.4 release, but I can't remember anything in the interval that would have changed anything.
One little thing is to keep the latency at three seconds or less – two seconds is standard. Shairport Sync doesn't allocate enough memory for a buffer of longer than that. BTW, the "Real-time Streaming" feature does work with Shairport Sync.
Hello. This is what Tuneblade support recommended me in August. Perhaps here are some hints to isolate the problem:
Please reach out to the ShairPort-Sync team and suggest them to : Remove the am field in Zeroconf text records , or change the am value to something like ShairPort-Sync which TuneBlade can use to identify it. In latest versions, they have changed the value to 'AirPort ... ' which is an identifier for AirPort express devices and so TuneBlade will stop streaming after 10 minutes as it finds it to be an AirPort device.
Thanks for this @Klausi69 – I was completely unaware of it as a recommendation. I'd have a preference for setting the am
value to Shairport Sync
, but we'll have to see how compatible that is in general.
Okay, so I've just pushed a new pre-release – 2.8.6 – with that suggested change. It identifies itself with the am
string ShairportSync
. If you'd care to try it out, that would be great. Maybe @moodeaudio might be interested in checking it out too...
Hi Mike,
Sure. I’ll compile and get the binary to the user for testing.
Thanks!
-Tim
On Oct 10, 2016, at 2:13 PM, Mike Brady notifications@github.com wrote:
Okay, so I've just pushed a new pre-release – 2.8.6 – with that suggested change. It identifies itself with the am string ShairportSync. If you'd care to try it out, that would be great. Maybe @moodeaudio https://github.com/moodeaudio might be interested in checking it out too...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mikebrady/shairport-sync/issues/391#issuecomment-252698148, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDTT_rek1LubQpLoIw2Ru7jYEczybaSks5qyoBdgaJpZM4KSDf3.
Hi Mike,
Tim at @moodeaudio compiled a new binary and sent it to me for testing. Unfortunately, Tuneblade still times out after 10 minutes. I have performed all of the tests that Tim requested to ensure that the new version of shairport-sync is installed correctly.
Tim has asked me to report this back to you and to say that he's happy to compile a further version to send to me for testing if you can make further tweaks to the code
Thank you for your efforts thus far.
Hi leicray,
since yesterday, there is a new evaluating version of TuneBlade (1.5.3.0). The support says, this piece will not interrupt streams to Shairport Sync now in version 2.8.6. I have no permission to publish the download link in public. I suggest to contact Tuneblade support directly.
Thanks.
Thanks @leicray and @Klausi69 for these updates. Perhaps it would be worth contacting Tuneblade directly – @leicray, do you want to do that, or shall I? Meantime, when I get a chance, I'll try to see what the older Tuneblade is sensitive to. @Klausi69, if there was a name at Tuneblade, I'd gladly contact them. Thanks again.
Hi Mike,
I will contact Tuneblade and request version 1.5.3.0 for testing but it would do no harm for you to raise the issue too.
Thanks
The friendly sender is "The TuneBlade Team" on support@tuneblade.com ;-) I don't know any personal staff address. Half an hour ago, I asked them for revealing the download link because of public interest.
Thanks. I just sent them a mail...
Here is the download link: http://files.breakfreeaudio.com/downloads/TuneBlade_Installer_1_5_3_0.exe The support team added: "We're just testing this build with some other features internally so will publish in a day or so."
Super, and I also got a friendly reply from them. I'll be testing it over the next few days, through the weekend. It would be great if you'd test it too.
I too have had a nice friendly reply from Tuneblade with the same link to the installer. I'll do some testing at the weekend and report back.
Tuneblade version 1.5.3.0 cures the timeout problem with Shairport Sync. Many thanks to all who have helped in any way.
Hi, I'm running TuneBLade 1.6.3.0 and have installed shairport-sync (version 2.8.4) from the Jessie backports repository.
I am runnining into this issue - should I be?
Sorry, reading this thread properly indicates that I need to upgrade to shairport-sync 2.8.6. Will this version be added to the Jessie backports repo any time soon, or do I need to compile it on my system to get upgraded?
Hi there. I'm afraid I can't tell when or if it'll be added to Jessie backports, so I guess the best thing is to compile it yourself.
I figured that might be the case, so I compiled 2.8.6 myself and all is now working - thanks.
Once I finished all of the build and install steps, the systemd service wouldn't start because it was masked (presumably during the uninstall of the old version). Once I figured out what this meant I unmasked the service it and it started fine.
I may have inadvertently reversed this change in V3.0. I'll be checking over the weekend.
On 2017-03-10 12:39, Mike Brady wrote:
I may have inadvertently reversed this change in V3.0. I'll be checking over the weekend.
-- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [1], or mute the thread [2].
*
Links:
[1] https://github.com/mikebrady/shairport-sync/issues/391#issuecomment-285734367 [2] https://github.com/notifications/unsubscribe-auth/ANDTT-1T6Dh0E-xdR20AQrdC0fdSRn4Bks5rkYrJgaJpZM4KSDf3
Hi Mike,
Thanks.
-Tim
I think this have been dealt with successfully, thanks to all involved. Please open a new issue if necessary.
MoOde audio player (http://moodeaudio.org/) is a high quality audio player for the Raspberry Pi. MoOde uses shairport-sync as an Airplay receiver and I have found it useful to play audio from my PC using Tuneblade (http://tuneblade.com/). Although Tuneblade is a commercial product normally costing $9.99 it has a free mode which is advertised as working with Shairport. This free mode did work until recently but no longer does. This is probably because shairport-sync no longer identifies itself as a non-propriety system. I can understand that the way in which shairport-sync identifies itself was changed for greater compatibility with other applications, but it has now broken free use of Tuneblade.
Can some sort of compromise solution be achieved?