-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting and stopping playback takes very long time to start #79
Comments
Hi @tariktokic Thanks for filling out the issue template. I could replicate your problem with your given information with latest airconnect version playing any song from Apple Music to my Sonos Play:1. This could be related to a problem with the latency config for airupnp. This could be tested using the command line arguments or the config file: https://github.com/eizedev/AirConnect-Synology#configuration I will also check this in the next days, i am currently not able to access my NAS. If you have time to test, could you please play a track from Apple Music on your Play:1, let it run a few seconds and then pause again and then upload the part from the airconnect.log here? If in doubt, clear the log shortly before. Thanks. Also, it could be related to an old problem using default flac codec. Sonos has changed something in newer firmware versions. Before 15.3 it could help to change codec from flac to wav in den config file (see readme for info how to do this). |
Hi @tariktokic I have release the latest version of AirConnect in the Release. On my synology models, the problem still exists in the latest version. I still have 2-3 ideas that I want to test (f.e. Change from flac to mp3), otherwise I'll open an issue with the AirConnect developer about it. |
Hi @eizedev |
Hi @eizedev I've got the same (or related) issue for years actually. Playback delay is ~10 sec, but stopping and volume control are immediate! DS218+ with DSM 7.1.1-42962 Update 6 I already touched the
was one month ago. Perhaps as a consequence of editing the In any case, the symptoms (~10 sec playback delay) are the same for years. Log text since airconnect starts:
Thank you!! |
Thank you for your feedback. Next weekend I'll find some time to take a closer look, at the moment I'm quite busy in my spare time. |
same issue |
We are expecting our child in the next 2-3 weeks, so unfortunately I don't have the time at the moment, even if I had planned to :-). Sorry it's taking so long. I'm pretty sure it's not the Synology package, we'll have to ask philippe44 if he has any ideas. |
Congratulations and our best wishes! |
Our child was born last weekend. Personally, it will be a while before I have time to look at it again :) |
Congratulations René!
…________________________________
De : René ***@***.***>
Envoyé : Thursday, November 30, 2023 9:37:27 PM
À : eizedev/AirConnect-Synology ***@***.***>
Cc : Gandulf78 ***@***.***>; Manual ***@***.***>
Objet : Re: [eizedev/AirConnect-Synology] Starting and stopping playback takes very long time to start (Issue #79)
Our child was born last weekend. Personally, it will be a while before I have time to look at it again :)
If there is anyone here in the community who would like to help, you are welcome to submit a pull request (or open an issue in the AirConnect repository with philipp44 with reference to this issue). I'll definitely take a look at it when I get the chance.
—
Reply to this email directly, view it on GitHub<#79 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKQTQ7TJKNHK2Q4CJV3F4JLYHDVAPAVCNFSM6AAAAAA4IQWVT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGUZDKNJQGQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
i have released a new version (PRE-release) with latest AirConnect binaries and a lot of fixes for airupnp. The pre-release version should basically work, but is not yet finalized as I would like it to be. However, the content of the package and the logic should not have changed. Thanks! @5trobl I will also look into the problem with the config file not being recognized correctly. If you have time, please check whether uninstalling the package and then reinstalling it might solve the problem. All directories and files should be deleted and overwritten with the latest ones from the newest package that you install. The file Example for creating airupnp config file, change ip to your needs (will be fixed in README, found a typo): After running this command the config file will be generated and linked to the correct location (it will take a few seconds/minutes to complete until airupnp recognizes all speakers etc.) root@box:~# ls -l /volume1/@appstore/AirConnect/config.xml
lrwxrwxrwx+ 1 airconnect airconnect 30 Jan 15 00:04 /volume1/@appstore/AirConnect/config.xml -> /volume1/airconnect/config.xml
root@box:~# ls -l /volume1/airconnect/config.xml
----------+ 1 root root 1094 Jan 14 23:58 /volume1/airconnect/config.xml You could change the log level from Log Levels:
Example Config file with adjusted log level on one of my own devices (change ip!):
AIRCAST_ENABLED=1
AIRCAST_LATENCY="1000:2000"
AIRCAST_LOGLEVEL="all=error"
AIRUPNP_ENABLED=1
AIRUPNP_LATENCY="1000:2000"
AIRUPNP_LOGLEVEL="all=error"
AIRUPNP_PORT=49154
FILTER_AIRPLAY2_DEVICES="<NULL>,S1,S3,S5,S9,S12,ZP80,ZP90,S15,ZP100,ZP120,1.0,LibreWireless"
SYNO_IP="192.168.1.249" |
Hi! |
Thanks! I wish you a happy new year too! I cannot test it at the moment (Since I have "broken" my network by rebuilding my local network ;)), could you please upload the log during playback if it is still not working? Thanks! Edit: Issue opened: philippe44/AirConnect#517 |
Hello René. |
Hi all, Hi @Gandulf78 We are a few steps further and the developer has released a new version for testing (not yet official) which I have packaged for you here. Can you please test it and give me some feedback? Or even better, post it directly in this issue (with logs if you can). It should work better, but I can't reproduce it on my end. Thanks! (Not all packages can be found in this zip, get back to me if you miss the right version) |
Hi~ |
ok, thanks! that is exactly the same behavior than on my NAS -I will pass it on |
I've done some verification with my own system
It seems to me that the issue is your version of Sonos buffering much more than mine. The other difference you can see is the 1st sync packet arriving later. But that has no impact on playback. The exact role of that sync packet is unclear in AirPlay because I've seen it used differently across iOS and macOS versions. |
ok, @philippe44 I think, after doing some troubleshooting, I was able to narrow down the problem and have found a workaround. I have a few devices, all with latest apple software/firmware (iPad Pro, iPhone, macOS) and all old speakers (mostly Play:1) are on latest SONOS firmware. Any idea what Sonos (again) did to break it? We had a similar problem a few month back with older Sonos releases. Should I switch the default settings of airupnp for the Synology package to these settings or do you have any idea what could be changed to leave the default settings? I think I will integrate a config setting to make it changeable for the Synology users.
Click to expand - From MacBook Pro using Spotify App - 1.8.1 Log (Loglevel DEBUG):
Edit: I have uploaded a zip file containing some versions (no static packages, file size limit of GitHub) of the Synology package with added changes from above as hard coded values. could someone @Gandulf78 @huleiEthan f.e. please test it and give feedback how it works on your devices? Thanks |
I just tested it on my DS220+ with my iPhone XR. It is much better on start-up : 1-2 s to start! |
is "-g 0" or is "-c wav" what is making the difference? |
will test it tomorrow |
yes! It's work in my case, starting takes about 2s. |
Had Not much the last two days. Will test it in the next days |
BTW, I don't recommend much using wav as they have a hard limit in term of playback duration which is not really compatible with AirPlay. It's 4GB (that I might have limited to 2GB, I'll have to verify that), so about 3 hours (or 6) of playback. |
@philippe44 i've tested it today with all different parameters and settings.
So i will build a new package for testing tomorrow. |
What do you mean by flac did not work? Did it work before? And this is the default codec if you don't specify any option |
Hmmm, than i missed something. I only added |
I will check but flac is the default for sure c, now I might have not allowed flc or flac on the command line |
I corrected my README regarding flc vs flac as it was incorrect ("flac" should be used, not "flc"). But it does not change much in a sense that flac is the default codec and if the -c is not recognized, the default value is used. The only difference is that the name of the file sent to the player still still be ".flc" if you set "-c flc". So none of this seems to make sense (not what you are saying, of course I trust you see what you see, it's just I cannot make sense of it) |
During the test, I briefly appended -c mp3 and -c flac to determine the differences. With -c mp3 I could not detect any difference compared to not specifying the parameter at all. With -c flac, it didn't play any sound for the next 30 seconds, but i also did not checked the log, and then didn't follow it any further. I'll have another look tomorrow. Maybe I mistyped -c flac towards the end when testing and that's why it didn't work. Finally, I omitted the parameter again as usual and only added -g 0, which makes a significant difference. With -l 50:100 it got even better (in my environment) Basically, the behavior now with the command line call from above is great and I'll build another package tomorrow for the others here to test. |
Would you mind trying again with just -c flac to be sure? The 2nd latency parameter reduce lag for sure but at the expense of potential buffering issue in case of network hiccup |
ok
i have increased the http latency to 500 and playback now takes about 1 second, maximum 2 seconds to start. I think this is okay. @philippe44 Do you think |
@5trobl In new testing version (below) the log file should be deleted if it exceeds a size of 50MB (a one shot backup until the next start will created All others: if you get any errors during upgrade process (not uninstall and reinstall) please let me know. That is related to my change in the upgrade process. It works on my devices, at least ;-). Readme and code will be updated, if anything is working. |
There is no perfect solutio, it's just one to deal with network issues from the AirPlay to the bridge and the other is from the bridge to the UPnP device. So UPnP device do their own buffering and wait a lot to play, in which case :HTTP can be zero, some like Sonos don't so you have to add some because otherwise they'll miss data very frequently. Now the need for -g 0 baffles me. |
Hi. |
Hi |
I have uploaded a new release for For me if i change the config in "AIRUPNP_CONTENTLENGTH_MODE=0"
"AIRUPNP_LATENCY=50:500" (results in it is nearly instant, max. 2 seconds delay on playback. No playback problems if i play from apple music, spotify or directly from macOS/ipad/iOS in the last weeks (for hours) |
Unfortunately the new package won’t start on my DS224+. Installation works flawless, but after running airconnect it immediately stops… 1.8.1 did work without any issues. Thanks for your help! |
Thanks for the reply. i already got the info from @Gandulf78 in another issue. I have changed |
Should now be fixed in the latest release: https://github.com/eizedev/AirConnect-Synology/releases/tag/1.8.3-20240403. thanks to @seiryIsNotABlock @seiry for your help to find the problem and creating the pull request!! |
Hi - So happy reading this. I'm using Sonos speakers and was having the 10-15 second delay when starting and resuming. airupnp.exe -l :50:500 -g 0 |
Describe the bug
After selecting the SONOS Play 1 box in Apple Music and starting the playback it takes between 15-20 seconds until the music starts or stops.
To Reproduce
Expected behavior
The playback should start or stop at least 2-5 seconds later
Hardware
Device on which you are running AirConnect-Synology):
Package
Which package from the releases page have you downloaded):
Thank you for the good work!
The text was updated successfully, but these errors were encountered: