-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
crossfade duration not updated via API / Azuracast #1152
Comments
Hi! Thanks for reporting. Could you add a description of the script that is being executed? Are you trying to crossfade on a live source like |
Hi toots, I am just user but I mentioned in the other thread over at Azuracast (linked above) that you asked this. I am not sure what the most efficient way to solve this is for you and the azuaracast devs? Thanks again. |
In regard to what I am personally doing: I have a simple playlist with a few audiofiles, created within azuracast. For that playlist there is a setting of "crossfade duration" within azuracast. Entering a value (e.g. 20 seconds) there does nothing, but the azuracast devs say it should in theory. I am doing nothing else. I am afraid that is all I can tell you from a user perspective. |
@toots Here is the liquidsoap.liq that we generate when live streaming is enabled and with crossfading set to 20 seconds on our demo installation at https://demo.azuracast.com The crossfade is applied before adding the I've tested what it sounds like on the demo installation with the crossfade set to 20 seconds and it sounds like I expected it to sound. When a song is nearing its end you will start hearing the next song becoming louder and the current song becoming quieter. @davidkamp would you mind also posting the liquidsoap.liq that is generated for your installation?
|
Hi @Vaalyn @toots Set to 30s I hear a transition of 2secs max, where the songs overlap.
|
Yep, when I set the crossfade to 20s that's what happened in the demo installation. When looking at your liquidsoap.liq one difference that stands out to me is that you are using the |
Thanks, but no difference. I tried all possible combinations of crossfade modes before posting my initial report. |
Hi there. I'd like to get this fixed for
It is possible that the bug is already fixed there.. Next, I'll need some logs showing what's going on around the issue with at least level 4 or if possible 5: Finally, the most efficient way for me to deal with it is to be able to reproduce locally. A small script than can reproduce the issue and, if needed, the files that cause it, possibly sent via email (toots@rastageeks.org) Let me know & let's fix this! |
Hi @toots |
If you can. At the very least, some logs extracts would be great to start investigating.. |
Thanks @toots, when trying your commands in my console I get what you see in the attached screenshot. I installed opam since it was not installed on the digitalocean server using a commend suggested in digitalocean console. Maybe I need do something else before your opam command works? |
No, I'm not sure what's going on, I would need more background regarding your install. Could we start with some logs then? Run with |
Hi @toots Under administration / system maintenance / system logs it says: "Because you are running Docker, some system logs can only be accessed from a shell session on the host computer. You can run docker-compose logs -f (nginx|web|stations|...) to access container logs from the terminal. But if you fixed the issue (it existed on your end and no longer exists now) why not just update? I'll also need to check how I can actually update my install, not sure how that works with docker. |
@davidkamp You can add the You'll need to The log that @toots want's to see is the |
Unfortunately all I see under "liquidsoap log" is |
@davidkamp Regarding the updating you'll just have to run the update commands when we released a new version:
Could you check for the logs manually via SSH / console? Here are the commands you'll need: Go to the AzuraCast directory via When inside the bash shell of the container you go to the config directory of your station via Now check what files are available inside this directory via |
|
Thanks but unfortunately there are no log files in that folder. So the "error: log file not found!" in the gui is true. |
Perfect, So in a few days I can run: Right? |
@davidkamp that's rather strange, there should be logs from liquidsoap and icecast in that directory. Is it completely empty? Would you mind posting a screenshot of the output from the
Yes, as soon as we release the update on the AzuraCast side which might not be immediately when 1.4.2 is out. |
@Vaalyn Sure here you go: |
That's really weird... |
yes - Azuracast apllication logs are there.
no.
I only installed the docker container as available on digitalocean roughly one month ago. no updates. Currently: running as listed in the azuracast gui:
|
@davidkamp AzuraCast 0.10.2 has been released which includes Liquidsoap 1.4.2. You can update any installation type to take advantage of the latest updates. |
@SlvrEagle23 Perfect- thanks so much. |
Now liquidsoap does not work at all anymore. |
I updated, now no Broadcast works.... My stations do not work at all. My two live stations are now offline, embedded players show an error message. This is really frustrating. What should I do? I am attaching a few screenshots of the error messages I am getting when trying to start/restart Liquadsoap autoDJ. |
@Vaalyn @toots @SlvrEagle23 @dbeiner But if I look the droplet within digitalocean it says: What does this mean? I restarted the droplet and stations etc multiple times after the update completed. |
@davidkamp Please don't use the Liquidsoap GitHub repository for issues with AzuraCast. You already have an existing issue pending with us in our repository; please follow that for updates and do not disturb our upstream project maintainers. |
@SlvrEagle23 Sorry, did not mean to disturb. Here is what solved it for me: Also it seems the crossfade duration now works as expected which is great! |
Any update on this one? I'm gonna revisit it with the upcoming |
Hi! We just fixed #1074 that was a crossfade-related bug. Any chance you could try with the latest Thanks! |
AzuraCast has been updated to the latest 1.4.3 prerelease build; please update your AzuraCast installation and let us know if the issue is resolved. |
Thanks for that @SlvrEagle23 ! When you get a chance, would you mind updating the image one more time? I let some changes in the commit fixing the issue that shouldn't have been in, just reverted them.. Sorry about that! |
@toots Done, just rebuilt the image with the latest commit in the 1.4.3-prerelease branch. |
Any update on this one? |
Hi! I might close this issue if we don't hear back in a couple of days, presuming it closed through the recent work on crossfade. Let me know if that isn't the case! |
I'm marking this one as closed, please re-open if needed. |
Hi,
I posted an issue with incorrect crossfade durations (impossible to set any duration) on the Azuracast github. They confirmed the issue exists, but their code is apparently 100% following your API so it might be an upstream issue, something within the liquidsoap API causing this?
Here is the thread: AzuraCast/AzuraCast#2632
Could you look into this?
Thanks so much,
David Kamp.
The text was updated successfully, but these errors were encountered: