Sometimes if I request to skip tracks this happens:
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
@toots is there a telnet/say command to view all available songs? I mean like
return all the ids of every song
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#issuecomment-419623409___
Savonet-users mailing list
You can add SSH access. It's actually a neat trick, it's described here:
http://www.liquidsoap.info/doc-1.3.3/server.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok thanks! Final question, is there anyway we can add a password for the telnet
protocol?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Glad to know! `request.all` should only show queued or currently playing
requests so that's to be expected.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots all seems fine, no falling of the stream (~2 days going) another
slightly unrelated thing over telnet what should request.all show?
Currently it shows this after about 12 hours running:
I have to use ./liquidsoap or it runs from command and not binary
--
You are receiving this because you are subscribed
@Niall7459 The installed liquidsoap through the opam is in the home directory.
For example: `/home/username/.opam/bin/liquidsoap` or
`/home/username/.opam/4.05.0/bin/liquidsoap`
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
@Yukioru I've installed 1.3.3-1 but when i run 'liquidsoap' its still running
version 1.1.1 that I installed using apt. Has opam installed it somewhere
different so I can make an alias to it. Thanks
--
You are receiving this because you are subscribed to this thread.
Reply to this email
https://github.com/savonet/liquidsoap/issues/572#issuecomment-413228714
@Niall7459
You need to use opam to install the latest version. Or manually collect from
the repository.
https://opam.ocaml.org/
https://opam.ocaml.org/packages/liquidsoap/
--
You are receiving this because you are
nope, I can attempt a build but it probably wont work for me
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Il check on my ubuntu system
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots
not yet on our lists :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Oh also, thanks for the kind words, much appreciated!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #572.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#event-1790109662--
Check out the
@Niall7459, I'm gonna close this one here for house keeping. I am focused on
issues on the recent code and this one hasn't been reported since `1.1.1`.
However, feel free to re-open or submit a new one if you experience it with the
latest code. Thks!
--
You are receiving this because you are
Just wanted to say, thanks for this amazing piece of software, I’ve used VLC,
WinAMP but nothing has come close to compatibility/features of liquidsoap. It’s
perfect for radio automation and extremely lightweight to run! Good luck!
--
You are receiving this because you are subscribed to this
Yep, in my case tracks are still prepared, the stream is still available,
sending metadata, just no audio.
I have my icecast server at http://listen.nagar.eu:8000/
And the stream url is http://listen.nagar.eu:8000/autodj.mp3
(working at the time of writing)
64-bit architecture. I used apt and
Ok, I think the two problems are different. In @Yukioru's case, the process is
frozen if I understand well, since there are no more logs. However in
@Niall7459's case the process keeps preparing tracks.
@Yukioru: let's continue the conversation in your new issue.
@Niall7459: Are you using 32 or
Anyway, it seems to me better to continue in the right topic? )
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I'm not sure that you were off-topic and, yeah, I'm not gonna let this one go
now that we're so close to fixing it :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots Let me create a new problem. I was wrong with the wording of the problem
in this topic.
I did not find any similar problems. As I understand, all the problems with the
silence in the stream.
Sorry for the comments off topic. And yet, can I hope that the problem will be
solved in 1.2.4?
Thanks for the clarification. @Niall7459 is that also what you are experiencing?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmmm. Maybe partly yes.
In the original description it is not clear whether the stream itself is still
available and there is just silence?
If so, then maybe I did not understand the problem correctly.
In my case, the liquidsoap process remains working, but the tracks stop playing
(the
Ok, thanks. I'm a bit confused now. The initial description of the issue was:
> After about half a day, my stream does not output music but continues to show
> loading songs in terminal. I need to restart the program to get the stream
> back
Is that what you are experiencing?
--
You are
@toots
[liquidsoap.log.txt](https://github.com/savonet/liquidsoap/files/2285672/liquidsoap.log.txt)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@Yukioru Any chance you could share a bit more of the logs? Something showing
the whole transition would be great.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Gotcha, thanks. On it!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#issuecomment-412517179--
@toots It still falls.
```
2018/08/12 23:29:50 [source:4] Source add_12534 gets up.
2018/08/12 23:29:50 [add_12534:4] Content kind is {audio=2;video=0;midi=0}.
2018/08/12 23:29:50 [source:4] Source smart_cross_5951_after gets up.
2018/08/12 23:29:50 [source:4] Source buffer_12492 gets up.
@toots OK. Replaced. Restarted the stream. Let's see how it will work.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks guys for these, this is extremely helpful. Let's try one last thing to
narrow it down: @Yukioru, could you try to change the `sequence([sa, sb])`
transition in the jingle case to `add(sa,sb)` like in the other case? I'm
trying to figure out if the problem comes from the `sequence`
Recent changes I have made:
- more songs have been added
- crossfade() added
This has made the stream fail every 8 or so hours. Before, I had crossfade()
but it was in the wrong place and not taking effect. I can hear the crossfade s
I think the problem is cross fading
Also I’m on Linux and I
Eventually.
>From my script I turned off the processing one at a time:
- ladspa;
- skip_blank;
- joshcross.
After the first two the stream also fell.
After disabling joshcross, the stream has been running for 2 days without
falling.
It's all with jingles on.
Yes, the processing could be another possible culprit, let us know if that
changes anything..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots The stream also falls.
I'm going to turn off the processing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
ok
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#issuecomment-45929--
Check out the vibrant
You can always try: `opam reinstall `
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots, I have updated the packages correctly?
Updated: fadd, dtools, liquidsoap
```
cd ./package
git pull
opam pin add.
opam upgrade package
```
I doubt it, because there was no reassembly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
No worries! I'm really hoping we can fix this one for the next release :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Today I will update to the current master branch. And I'll try again.
All this time the flow without jingles did not fall.
I'm sorry that it took such a long time to do this before.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Any update on this one?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#issuecomment-411073069--
Ok, thanks. I'm definitely investigating it as a stack corruption in the faad
decoder.
I've pushed another cleanup of the GC/callback code. There's a small chance
that it could fixe the issue, feel free to test when you get a chance. Thks!
--
You are receiving this because you are subscribed
@toots, with jingles also falls. I will test further - the result will be
reported.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Will this push changes to apt-get?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, I was compiling with the wrong version of OCaml. Fixed now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Heh. Now 128 line.
https://github.com/savonet/liquidsoap/blob/master/src/decoder/aac_decoder.ml#L128
```
# File "decoder/aac_decoder.ml", line 128, characters 41-47:
# Error: This expression has type string but an expression was expected of type
# bytes
```
--
You are receiving this
Ok, should be fixed now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/572#issuecomment-409289667--
I had to modify liquidsoap.opam, because ocaml-mm needs 0.4.0 versions from the
master branch. (I collected it manually, not through opam) and the problem with
the assembly is the same.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
https://github.com/savonet/liquidsoap/issues/572#issuecomment-409280286, Yep.
You fixed the line 168 in aac_decoder.ml, but the error writes on line 91.
https://github.com/savonet/liquidsoap/blob/master/src/decoder/aac_decoder.ml#L91
It was not in the changes.
Also make sure to update the pinned copy, just in case:
```
opam update liquidsoap
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmm. And you're using
https://github.com/savonet/ocaml-faad/commit/2e0593d4e49b90350d39af3a754f0ba589d23dba
?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
```
~/liquidsoap(master ✔) git checkout
Your branch is up-to-date with 'origin/master'.
```
I also took the last commit.
```
commit a6d381359d1ca19b62efd679e2ddd3baa9a64449
Author: Romain Beauxis
Date: Mon Jul 30 23:53:36 2018 -0500
Bump faad, adapt to new API, use Bytes.to_unsafe_string
I believe this was fixed in commit a6d3813
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots
Of course, I used the latest versions, but something went wrong.
```
=-=- Processing actions -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[ERROR] The compilation of liquidsoap failed at "make".
Processing 1/1: [liquidsoap: rm]
#=== ERROR while installing liquidsoap.dev
@Niall7459 lack of resources I don't think so. To me it looks like some kind of
stack corruption, which is why I'm tempted to investigate the C part of the
code, mostly the bindings. The OCaml part of the code has been well tested over
the years, it'll be a real surprise to find an issue of
@Yukioru you will need to also use the latest liquidsoap & dtools code:
```
git clone https://github.com/savonet/ocaml-dtools.git
cd ocaml-dtools
opam pin add .
git clone https://github.com/savonet/liquidsoap.git
cd liquidsoap
opam pin add .
```
--
You are receiving this because you are
For me I can find that this can vary in duration of how long the stream works
for.
Sometimes it can be 5 days, or 8 hours..
Although this _seems_ to closely match when another piece of software running
crashed, the stream stayed working, when I restarted this other software, the
stream went
When assembling liquidsoap, a type error occurred.
```
OCAMLOPT -c decoder/aac_decoder.ml
File "decoder/aac_decoder.ml", line 91, characters 49-55:
Error: This expression has type string but an expression was expected of type
bytes
../Makefile.rules:192: recipe for target
(and a locally pinned `liquidsoap` and `ocaml-dtools` with the latest code.
Same instructions)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, I've just pushed a cleanup of the `faad` decoder code. You might want to
try with this. If you have installed via `opam`, you can simply do:
```
git clone https://github.com/savonet/ocaml-faad.git
cd ocaml-faad
opam pin faad
```
You will need `autotools`/`automake`.
--
You are receiving
Sorry responding to myself: yes, it seems that they are in `m4a` format.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Very interesting, thanks! Any specific audio format for the jingles that aren't
used for the other tracks?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@toots
>From the past, the config has removed the jingles leaving only the tracks. So
>far, the config works 3 days without falling (_The last build of the master
>branch with ocaml 4.06.0 and opam 2.0.0 rc3_).
ladspa, skip_blank, crossfade has not deleted yet.
I'll write more as more
Hi,
Thank you very much for these details, this is super helpful.
Could you try to disable one by one the intermediate operators and see if the
bug keeps happening? Start with removing ladspa, then the crossfade, then
`skip_blank`. The idea would be to either narrow down a minimal script to
Hi @toots,
I have the same problem.
I tested it on different versions. The most stable is 1.3.1 with opam 1.2.0
from the Debian repository. OCaml version 4.01.0. (But this version loads CPU
very much #475 )
I also tried to install the release version of opam 1.2.2 and the version of
Hi @Niall7459,
Couple of additional questions:
- How did you install liquidsoap? If through opam or compiled yourself, what
version of the OCaml compiler are you using?
- Are you in a position to deploy a test script and try to remove some of the
operators? Half a day seems short enough to do
‘’’#!/usr/bin/liquidsoap
Thanks for this report. Do you have a script to share if possible as minimal as
can be?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
After about half a day, my stream does not output music but continues to show
loading songs in terminal. I need to restart the program to get the stream back
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
88 matches
Mail list logo
