Are you trying to connect from the same machine or a different machine?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Try this:
```
set("server.telnet.bind_addr", "127.0.0.1")
set("server.telnet.port", 1234)
set("server.telnet", true)
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You mean it works with older gstreamer now too?
Imo it would be nice if we can get this working on debian stable.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok I made a playlist with videos my setup can play and I can confirm that 6 hrs
later it is still running, no memory issues whatsoever with ```1.14.2```.
Now I just need to fix webm support :P
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Hmm, I'm unable to get webm decoding to work .. will come back to you when I
have a working setup with 1.14.2 ..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I'll remove the debian packages and re-```make install``` my 1.14.2 build :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Btw that ```GST_STATE_CHANGE_PLAYING_TO_PAUSED``` in thread 13 is me messing on
the telnet interface. Which doesn't do anything except set these state changes
(stream still dead)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Hmm, I get ```ptrace: Operation not permitted.```
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Hmm, even though the on-screen logging is much more verbose, there is nothing
written to file ..
But also I don't see anything added to the log when this stale situation
occurs. (it just says 'finished with ..')
Also the LS process does still respond, I can connect over telnet! it then says
Ah yes sorry, will run again with this setting!
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
@toots same result btw. after some time LS just sits idle and unresponsive.
Some log:
```2018/08/20 01:50:41 [random(dot)pl:3] Finished with
"/media/video/random/somevid.mp4".
2018/08/20 01:50:41 [decoder:3] Method "GSTREAMER" accepted
"/media/video/random/anothervid.webm".
2018/08/20 01:50:41
It means that we're working on fixing a particular problem right now.
Hold your horses with your list of requests. There can be other reports on this.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
Ok it's running (updated all repos and submodules).
Lets see how long it lasts :D
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
ok not sure what happened but I'm no longer getting output from LS. process is
still running and using memory. no cpu usage whatsoever.
can't do a ```ctrl+c``` either (I updated ocaml-duppy so this did work again)
--
You are receiving this because you are subscribed to this thread.
Reply to
Can you try your test-script but with my videoconvert and audioconvert settings?
that's:
```
video_pipeline=
"videoconvert ! x264enc bitrate=2000 ! video/x-h264,profile=baseline !
queue ! mux.",
audio_pipeline=
"audioconvert ! voaacenc bitrate=44100 ! queue ! mux.",
```
Yes I have it running with my original playlists and queues. Will let in run
for a while to see what happens to the memory :)
What I can tell so far is that when running ```output(dot)gstreamer.skip```
that the memory only changes per video (higher or lower), but doesn't actually
keep
Ok, I'm not trying (debian stable gstreamer) with your output stage (except
with the rtmpsink) and it works!
So the only difference is the ```videoconvert``` and ```audioconvert``` parts.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view
This, which is like the minimum I want to be able to run (can of course make a
more minimal version)
```
set("server.telnet.bind_addr", "127.0.0.1")
set("server.telnet.port", 1234)
set("server.telnet", true)
set("log.file.path", "/media/log/playvideo.log")
set("frame.video.width", 888)
(with latest current sources same result btw)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Is that with gstreamer ```1.10.4``` or ```1.14.2``` ?
btw I was missing a bunch of plugins and dependencies on my manual compile of
```1.14.2``` but even when all those where resolved I got
```
...
2018/08/18 14:17:31 [output(dot)gstreamer:1] Got ill-balanced activations (from
Hmm, I just built and installed gstreamer ```1.14.2``` and LS crashes:
```
$ liquidsoap test.liq
2018/08/18 01:02:43 >>> LOG START
2018/08/18 01:02:43 [main:3] Liquidsoap
Ok, it 'seems' stable, but it's not actually playing any video.
Memory usage is super low (way lower than I would expect minimum to be).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
And then:
```
(gdb) continue
Continuing.
Thread 36 "liquidsoap" received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:242
242 in ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
```
--
You are
Full log with just a single test file:
```
$ liquidsoap test.liq
[0/1992]
2018/08/17 09:55:50 >>> LOG START
Ok, pulled latest ocaml-gstreamer and liquidsoap. Reinstalling both ..
segfault :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hahaha, that must be the very stable memory usage then .. (I thought it was a
bit low)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmm, that's really odd then ..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
(of course I'm on debian stable with this box .. I can try upgrading to
testing. don't feel like compiling all of gstreamer myself :P)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
1.10.4-1
--
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/511#issuecomment-413647749--
Check out the
Hah! I never would've figured this out!
Everything installed now in the fresh ocaml environment.
testing ...
And fails with a whole bunch of:
```
(Liquidsoap:20280): GStreamer-CRITICAL **: gst_mini_object_unref: assertion
'mini_object->refcount > 0' failed
(Liquidsoap:20280):
Nope. Made a fresh .opam switch with 4.07.0 and when pinning duppy I get:
```
dreamer@streamer:~/ocaml-duppy$ opam pin add . -y
duppy is now path-pinned to /home/dreamer/ocaml-duppy
[duppy] /home/dreamer/ocaml-duppy/ synchronized
[duppy] Installing new package description from
Yes, it also seems duppy doesn't want to build with opam 4.07.0
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok this is weird, I upgraded ocaml with ```opam switch 4.07.0``` and then
reinstall the packages but I just get:
```
Sorry, no solution found: there seems to be a problem with your request.
No solution found, exiting
```
--
You are receiving this because you are subscribed to this thread.
Ok, need all these sources with --recursive of course. and liquidsoap is
without the 'ocaml-' ;)
But, I need a newer ocaml now (have 4.02.3 and need >=4.03 ...)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok, I'll try all of these straight from source then :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My output stage:
```
output.gstreamer.audio_video(
video_pipeline=
"videoconvert ! gdkpixbufoverlay location=/media/logo.png offset-x=768
offset-y=20 ! x264enc bitrate=2000 ! video/x-h264,profile=baseline ! queue !
mux.",
audio_pipeline=
"audioconvert ! voaacenc
Yes, I recompiled both.
```
dreamer@streamer:~$ opam reinstall gstreamer
=-=- Synchronising
Hmm, segfaults after couple seconds.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Yes, left it running for a while and oomkiller came by to shoot it down :(
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok it runs now, but still eats memory as I skip tracks in the playlist.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ok I manually installed the package with ```opam pin add gstreamer
``` and reinstalled LS and everything.
Now LS uses 400MB memory and the threads are using almost no CPU. Seems your
changes killed gstreamer intirely :(
--
You are receiving this because you are subscribed to this thread.
So I tried an ```opam reinstall gstreamer``` (and also ```uninstall
gstreamer``` followed by ``install```), and how I can test is that on the
telnet interface I run ```output(dot)gstreamer.skip``` and I still see the
memory use increase steadily.
Maybe you have to up the version so opam picks
Ah, you didn't change the version number. Not sure if opam is installing the
new ocaml-gstreamer now ..
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
So was this at all useful @toots ?
Just let me know if I can do anything else.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I have the feeling I'm experiencing the same issue.
On startup my LS instance uses about ~1.3GB memory but this steadily climbs
until oomkiller comes by to shut it down. Will explore some profiling with
valgrind in a bit.
--
You are receiving this because you are subscribed to this thread.
45 matches
Mail list logo
