Main libvlc error interface dbus none initialization failed

Запуск VLC в докер-контейнере Пишу образ для Докера, в котором будет установлен VLC для стримов. Докерфайл По-моему странно то, что при запуске через cvlc (no-gui-режим) он просит х-server. Ну и ошибка с pulseaudio. UPD: на базовом образе Ubuntu 16.04 или 18.04 то же самое По-моему странно то, что при запуске через cvlc (no-gui-режим) он […]

Содержание

  1. Запуск VLC в докер-контейнере
  2. VLC addon socket error #1918
  3. Comments
  4. The problem
  5. Environment
  6. Problem-relevant configuration
  7. Traceback/Error logs
  8. Additional information
  9. Footer
  10. Main libvlc error interface dbus none initialization failed
  11. Re: VLC testing
  12. Re: VLC testing
  13. Re: VLC testing
  14. Re: VLC testing
  15. Re: VLC testing
  16. Re: VLC testing
  17. Re: VLC testing
  18. Re: VLC testing
  19. Re: VLC testing
  20. Re: VLC testing
  21. Re: VLC testing
  22. Re: VLC testing
  23. Re: VLC testing
  24. Re: VLC testing
  25. Re: VLC testing
  26. Re: VLC testing
  27. Re: VLC testing
  28. Re: VLC testing
  29. Re: VLC testing
  30. Re: VLC testing
  31. vlc-core on Home Assistant Operating System no longer playing audio and path seems invalid #2390
  32. Comments
  33. Describe the issue you are experiencing
  34. What type of installation are you running?
  35. Which operating system are you running on?
  36. Which add-on are you reporting an issue with?
  37. What is the version of the add-on?
  38. Steps to reproduce the issue
  39. Anything in the Supervisor logs that might be useful for us?
  40. Anything in the add-on logs that might be useful for us?
  41. Additional information

Запуск VLC в докер-контейнере

Пишу образ для Докера, в котором будет установлен VLC для стримов. Докерфайл

По-моему странно то, что при запуске через cvlc (no-gui-режим) он просит х-server. Ну и ошибка с pulseaudio.

UPD: на базовом образе Ubuntu 16.04 или 18.04 то же самое

По-моему странно то, что при запуске через cvlc (no-gui-режим) он просит х-server.

По-моему, в дебиане vlc по умолчании открывается с окном под видео. То что, ты желаешь проигрывать звук из консоли vlc «не колышет» — у него в настройках «Автоматический показ интерфейса ВИДЕО» и всё* остальное для него не существенно.

pulseaudio нет,а ему нужно. Или ошибка какая-то иная?

Ну вот у VLC есть несколько UI (web, qt, консолька). cvlc по идее должен открывать вариант без графического интерфейса (что, собственно, происходит под десктопным дебианом или убунту). Пробовал ставить пакет с Pulseaudio, это погоды не делает. Он видимо к нему не может подрубиться. Там в первой строчке лога

Еще забыл сказать, что если ставить на базовый образ Ubuntu 16.04 или 18.04, то происходит ровно то же

Он видимо к нему не может подрубиться. Там в первой строчке лога

. которую я до конца не дочитал 🙁

cvlc по идее должен открывать вариант без графического интерфейса (что, собственно, происходит под десктопным дебианом или убунту).

я прежде чем, «порадовать» тебя своим комментарием запускал cvlc в консоли с аналогичным твоему результатом

вот в эмуляторе терминала — да играет без интерфейса. Но эмулятор терминала вне X-в не работает. В контейнере же только консоль.

Я знаю только, что VLC очень хитрая прога и иногда игнорирует настройки, перебирая варианты, чтобы был рабочий результат.

Я как-то файл проблемного фильтра пытался удалить, так VLC все новые и новые режимы задействовал, чтобы картинку показать. И без pulse он вполне работает, даже если задана пульса.

Источник

VLC addon socket error #1918

The problem

Install VLC addon but unable to start. Throw error

Environment

  • Add-on with the issue: vlc_code
  • Add-on release with the issue:
  • Last working add-on release (if known): none
  • Operating environment (OS/Supervised): Raspbian Supervisor Install

Problem-relevant configuration

Traceback/Error logs

Additional information

The text was updated successfully, but these errors were encountered:

more logs on restart

2021-03-20 10:07:20 ERROR (SyncWorker_4) [homeassistant.components.vlc_telnet.media_player] Connection error: Could not connect to VLC. Make sure the Telnet interface is enabled and accessible.
2021-03-20 10:07:31 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration vlc_telnet: No module named ‘homeassistant.components.vlc_telnet.config_flow’
2021-03-20 10:07:31 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Main libvlc error interface dbus none initialization failed

We have an updated version of VLC which improves performance for video decode, including HEVC 4K video playback on Pi4.
It is currently in the untested raspberry pi repo, and should be considered beta.

If you would like to try it, edit /etc/apt/sources.list.d/raspi.list and add ‘untested’ to the line ‘deb’ line so that it looks like this:

If you don’t have «ui» in there, that’s okay.

Then update and upgrade as usual:

Known issues / features:

If the decoder runs out of memory for any reason it reports an error and vlc, after receiving that error, stops using the decoder — this manifests as a black or frozen pici whilst audio continues. If you stop (not pause) the video then the decoder will be killed and we can try again.

Closing VLC by Alt-F4 or directly closing the window whilst video is playing doesn’t always shut life down correctly and you end up with a still active (deadlocked) VLC with no window. Stopping the video first or exiting with Ctrl-Q seems to die properly reliably.

If you want 4k on a Pi4 then I’d recommend 512M CMA (Add cma=512M to /boot/cmdline.txt).
If you are on a 1G Pi4 then 384M is probably your best bet but that can run out of memory under X for hardware 4K videos. You will probably get away with it without X.

GPU mem is best left at default (unset) on Pi4.
4k playback in a window is choppy. Switching to fullscreen should play much better (F key).
Launching from command line in fullscreen mode should also be fine (that can be run outside of X too).

For Pi 3, 128M GPU memory is recommended (set gpu_mem=128 in config.txt) for non-HEVC playback.
256M GPU if you want to play any HEVC. This is software decode with GPU acceleration. Most 1080p videos should play.

If you want a more omxplayer like interface to the command line vlc, then:

allows things like seeking with cursor keys. See VLC ncurses interface

[edit]
Pi2/Pi3 with fkms won’t work with hevc files. The acceleration uses the QPUs (part of 3D hardware) which the ARM is in control of in fkms mode.
Disable fkms if you need hevc decode.

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

Hmm. Can’t get it to work.

which is even less useful.

This is on 4.19.84-v7l+ and 4.19.84-v8+, no X (no X installed), sshed in on console, and with a seriously nasty permissions bodge — chmod -R a+rwX /dev — to get a normal user enough permissions to talk to at least bits of the hardware.

I don’t know where those two extra, spurious cma= parameters are coming from.

Re: VLC testing

Hmm. Can’t get it to work.

which is even less useful.

This is on 4.19.84-v7l+ and 4.19.84-v8+, no X (no X installed), sshed in on console, and with a seriously nasty permissions bodge — chmod -R a+rwX /dev — to get a normal user enough permissions to talk to at least bits of the hardware.

I don’t know where those two extra, spurious cma= parameters are coming from.

Re: VLC testing

Difficult when you have no UI.

Trying ‘f’ (for ‘fullscreen’) errors with

which also isn’t helpful. Changing video track has no effect.

And, TBH, I wouldn’t expect it to. I suspect the first ‘cma=64M’ parameter is being used, which is making the memory allocation fail. Unfortunately, I don’t know where that’s being set — certainly not in my cmdline.txt — and I don’t know which module or what parameter that corresponds to to overrule it in /etc/modules

Re: VLC testing

Re: VLC testing

Hmm. Can’t get it to work.

This is on 4.19.84-v7l+ and 4.19.84-v8+, no X (no X installed), sshed in on console, and with a seriously nasty permissions bodge — chmod -R a+rwX /dev — to get a normal user enough permissions to talk to at least bits of the hardware.

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

I just installed it after adding the source and doing the update/dist-upgrade.
Tried https://www.youtube.com/watch?v=d6a3uRVE7gE on a 100mbps network that delivers 85-95mbps, but used Pi 4 WiFi on 5GHz, so only getting around 60mbps.

After choosing 2160 in YouTube settings, the video either in a window or full screen turned blocky, then alternated moving a few frames in great res, and freezing. My guess is YouTube Streaming and buffering. as it plays great at 1080p
So I downloaded the file in 3840×2160 2160p (508MB for about 4 minutes of video).

VLC won;t play that either, possibly because it is in webm format. It alternats between dark screen, single frames of really sharp images, and brief moments of moving ‘blocks’.

I’m heading out for a while, but will see if I can find another way to get a 4k video in another format. Or if I can find a long enough network cable and try streaming it at 90mbps..

Re: VLC testing

Re: VLC testing

Re: VLC testing

Re: VLC testing

This thread is about VLC — playing youtube videos through chromium won’t use VLC.
Using youtube-dl on that URL produces a VP9 file — so won’t benefit from the hevc hardware decode.

If you just want a sample 4k hevc file for testing, then:
http://downloads.4ksamples.com/videos/s . .2160p.mkv

Re: VLC testing

Interesting. I don’t understand the reply? Playing youyube videos through chromium definitely IS using VLC. I’ve posted a screen shot of it doing just that below.

I open chromium using the youtube-dl server. chromium opens VLC and plays the video in VLC. so the ‘chromium won;t use VLC part of the reply is wrong.

Does VLC just avoid using the Pi 4 hardware when playing in chromium

Excuse the furry image, I could not remember size limits for images. This is Chromium, open at a youtube page, the video paused, and redirected via chromium to VLC, where it is playing.
So, chromium as I understand it is using youtube-dl to extract and stream the file from youtube to VLC in a similarway you can play a video stream in VLC by cutting and pasting it, but vastly reduces the buffering.

Which is why I thought playing a video using VLC would be part of ‘VLC testing. The first post said ‘including 4k playback’. it didn;t say excluding other resolutions.

It seems you are saying that while VLC uses hardware to watch an mp4 that is on a drive, it cannot use hardware to watch a video online.

Which means if I copy the url of a video and paste it into VLC (using CTRL-n) to stream it — VLC cannot play it using the Pi hardware.
That is a pity.
But I guess it is just a limitation of VLC and the Pi hardware.

I should add though, that since the most recent updates to my Pi 4, and I don;t know if there were updates to VLC, because I automate them, the youtube ‘4k Demo’ video in the image above https://www.youtube.com/watch?v=sUd4PTIzm6s, playing inChromium using VLC, is ‘spectacular’ on a 55 inch UHD TV, even allowing for VLC not being able to use hardware decoding, and it plays just as well at full screen.
That is with the Youtube ‘Settings’ adjusted to use 2160p.

Where previously it was blocky and jerky, at the moment it is incredibly sharp and smooooth.

Источник

vlc-core on Home Assistant Operating System no longer playing audio and path seems invalid #2390

Describe the issue you are experiencing

Back in December, I was using vlc-core with the vlc-telnet successfully. I am currently trying to use vlc 0.1.3 on core 2022.2.5. I have uninstalled and reinstalled vlc and the telnet integration multiple times lately trying to fix the issue.

What happens? No audio come out. More importantly, it appears that vlc is looking in the wrong path.

Notice in the logs:

NOTE: When I go in through the terminal, the path /run/s6/services/vlc does not exist on the device!!

my configuration.yaml contains the following that might be relevant:

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Other (e.g., Raspbian/Raspberry Pi OS/Fedora)

Which add-on are you reporting an issue with?

What is the version of the add-on?

Steps to reproduce the issue

  1. install vlc-core
  2. restart
  3. add vlc-telnet integration
  4. attempt to play audio

Anything in the Supervisor logs that might be useful for us?

Anything in the add-on logs that might be useful for us?

Additional information

The text was updated successfully, but these errors were encountered:

To play media from a local media source you need to use the correct media_content_id .

I’ve tested this on my HA OS install and this works for me:

Note that I have the default media_dir configured which is called local .

Let’s start with a vanilla config. I revised so that I do not specify the media_dir directory. Revised configuration.yaml and restarted:

Documentation indicates:
By default, the integration looks for media in a specified folder. If other media_dirs are not declared you need to use /media/local path for example in companion app notification.

«/media-browser/browser» URL shows the file in the «root» folder.

Calling the service from the Developer tool indicates
Failed to call service media_player.play_media. Unknown source directory

Log indicates no activity.

Call to service:

yields
Failure to call service media_player.play_media
No log activity.

The file becomes listed within the vlc UI. Clicking on the file yields the no path log entry cited above

I tested this again with core-2022.2.5 on HA OS. It works fine for me.

If you want to continue troubleshooting I suggest setting the log level to debug for core and the vlc_telnet integration:

This will show the service calls in the core and also the updates in the vlc_telnet integration.

Thank you for your patience. Again, the frustration is that this WAS working for quite some time without issue. I modified logging as requested.

The following, a link to an external site, plays without issue.

I created a new directory, and placed one file in it.

I call the following:

It is unsuccessful.

You need to use the correct media_content_id. Just the path won’t work, at least not on all systems. Please follow the instructions in the docs link I posted.

Instructions are followed.

Result: no audio output

How are you accessing Home Assistant? The resolved media source address suggests that you’re using https. Have you tried to use a local address? Have you configured an External or Internal URL in your configuration?

Home Assistant is being accessed via SSL using a real CA for an existing domain. The cert/key from that domain is copied onto this device. The internal network has a DNS entry to route to the device. This effectively means that the external world believes the subdomain (ha.mydomain.com) is at different location than the internal network. HA is effectively all local and only accessed locally.

The configuration for Internal and External URLs are https://ha.mydomain.com:8123.

The internal network has a DNS entry to route to the device.

@hw-monkey There is unfortunately a long-standing open issue related to local DNS servers not being used consistently within the docker network that HA and its addons run in — home-assistant/plugin-dns#20 . I’ve been doing some work related to it but it’s currently still an issue. Although interestingly it sounds like you’ve had no problems since December which is definitely different then what other users on that issue have been seeing.

Still I have a test if you wouldn’t mind confirming that HA and its addons are correctly resolving your domain. If you have the SSH addon set up just run the following from it:

And confirm that you see the IP address you’re expecting. If you don’t have the SSH addon set up then you can add this to your HA config instead and see the result as a sensor to confirm it is being resolved correctly:

I did forget that I changed from self signed SSL to the new configuration around the end of the year. That must be what triggered the issue, but I failed to connect the dots.

Dig works as expected

I believe I have the same issue.
I can play media from media browser and from VLC WEB GUI. No problem.
But when my automation:

is trying to use it then mp3 file (ringbell.mp3) is getting some weird extra name:
ringbell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJlMjQwZjYxOTFjODI0N2VkYjVhMzZhMTc4MDg4NTcwMyIsInBhdGgiOiIvbG9jYWwvRHp3b25la2RvbW93eTJyYXp5Lm1wMyIsImlhdCI6MTY0NTcwNjEwNSwiZXhwIjoxNjQ1NzkyNTA1fQ.mFu4i29xTWYPnyrTjtFVz_55v2qhRkbNPgzd22S73j0

This file appears in vlc web gui and cannot be played.
I suspect this to be related to updates I did few days ago (OS from 7.2 to 7.4 and Core from 2021.12.10 to 2022.2.9)

Update on my issue.
When I have moved the media file to local folder (configwww) then the player was able to play them (even if the files in the VLC WEB GIU are still having this strange name.
Now with this automation now it works fine:

So now my issue is related to the fact that vlc cannot play hte media files in media folder.

The Home Assistant update with the new media player did not improve anything. In fact, the text to speech option available through the interface does not work. The vlc-telnet flashes a file name but never outputs any audio.

@Maco65 so you are right that this broke because of 2022.2 . In 2022.2 a number of media integrations (including vlc_telnet ) we’re updated to support playing media from any media source. Prior to this release vlc_telnet was one of several media integrations that could only play local media in your /media folder or if you gave them a full URL directly to a file. Now it can play any audio file you can find in media browser.

More specifically, it now supports any of the following for media_content_id :

  1. A complete URL to an audio file hosted somewhere (ex. https://example.com/audio/ringbell.mp3 )
  2. A relative URL to an audio file hosted somewhere in HA (ex. /local/ringbell.mp3 )
  3. A media source URI which looks like this (ex. media-source://media_source/local/ringbell.mp3 ). Note that if you use the play media action in the script editor UI you always get this one now since it leaves no ambiguity for HA.

The problem though in your case is 2 above. A relative URL is indistinguishable from file path and so it is treated like a relative URL. This is a problem because its an incorrect relative URL. If you used media-source://media_source/local/ringbell.mp3 then the URL that HA would hand to the VLC addon is /media/local/ringbell.mp3?authSig= . But your config causes it to hand it /media/ringbell.mp3?authSig= which is invalid and thus breaks.

What I would suggest is use the play media action in the UI to configure this action. And then you can show the YAML and copy and paste it anywhere else you need it. Or create the media-source URIs by hand if you want, they aren’t particularly complicated for local media ( media-source://media_source/local/ ).

As for the authSig , that part is fine. Anything you see in the media browser in HA is protected by authentication. So when you pick a media file to play from there HA generates a token which grants access to that file and puts it on the URL so that the external player can get to it without needing to know authentication was required.

If it still doesn’t work I’d recommend opening an issue in core. There’s not really anything the addon can do about this, it just gets handed a URL and told to play it.

Источник

We have an updated version of VLC which improves performance for video decode, including HEVC 4K video playback on Pi4.
It is currently in the untested raspberry pi repo, and should be considered beta.

If you would like to try it, edit /etc/apt/sources.list.d/raspi.list and add ‘untested’ to the line ‘deb’ line so that it looks like this:

Code: Select all

deb http://archive.raspberrypi.org/debian/ buster main ui untested

If you don’t have «ui» in there, that’s okay.

Then update and upgrade as usual:

Code: Select all

sudo apt update
sudo apt dist-upgrade

Known issues / features:

If the decoder runs out of memory for any reason it reports an error and vlc, after receiving that error, stops using the decoder — this manifests as a black or frozen pici whilst audio continues. If you stop (not pause) the video then the decoder will be killed and we can try again.

Closing VLC by Alt-F4 or directly closing the window whilst video is playing doesn’t always shut life down correctly and you end up with a still active (deadlocked) VLC with no window. Stopping the video first or exiting with Ctrl-Q seems to die properly reliably.

If you want 4k on a Pi4 then I’d recommend 512M CMA (Add cma=512M to /boot/cmdline.txt).
If you are on a 1G Pi4 then 384M is probably your best bet but that can run out of memory under X for hardware 4K videos. You will probably get away with it without X.

GPU mem is best left at default (unset) on Pi4.
4k playback in a window is choppy. Switching to fullscreen should play much better (F key).
Launching from command line in fullscreen mode should also be fine (that can be run outside of X too).

For Pi 3, 128M GPU memory is recommended (set gpu_mem=128 in config.txt) for non-HEVC playback.
256M GPU if you want to play any HEVC. This is software decode with GPU acceleration. Most 1080p videos should play.

If you want a more omxplayer like interface to the command line vlc, then:

allows things like seeking with cursor keys. See VLC ncurses interface

[edit]
Pi2/Pi3 with fkms won’t work with hevc files. The acceleration uses the QPUs (part of 3D hardware) which the ARM is in control of in fkms mode.
Disable fkms if you need hevc decode.

Following some of the answers in this question, I tried setting up an RTSP stream by running:

raspivid -o - -t 0 -hf -w 640 -h 360 -fps 25 | cvlc -vvv stream:///dev/stdin --sout '#rtp{sdp=rtsp://:8554}' :demux=h264

but this seems to fail with the output:

VLC media player 2.1.6 Rincewind (revision 2.1.6-0-gea01d28)
[0x1e320d0] main libvlc debug: VLC media player - 2.1.6 Rincewind
[0x1e320d0] main libvlc debug: Copyright �� 1996-2015 the VideoLAN team 
[0x1e320d0] main libvlc debug: revision 2.1.6-0-gea01d28
[0x1e320d0] main libvlc debug: configured with ./configure  '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--localstatedir=/var' '--libdir=${prefix}/lib/arm-lin
ux-gnueabihf' '--libexecdir=${prefix}/lib/arm-linux-gnueabihf' '--disable-dependency-tracking' '--build=arm-linux-gnueabihf' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' '--conf
ig-cache' '--disable-maintainer-mode' '--disable-silent-rules' '--disable-update-check' '--enable-fast-install' '--prefix=/usr' '--docdir=/usr/share/doc/vlc-nox' '--libdir=/usr/lib' '--sysconfdir=/etc' '--with-b
inary-version=0ubuntu14.04.1' '--enable-a52' '--enable-aa' '--enable-bluray' '--enable-bonjour' '--enable-caca' '--enable-chromaprint' '--enable-dbus' '--enable-dca' '--enable-dirac' '--enable-directfb' '--enabl
e-dvbpsi' '--enable-dvdnav' '--enable-faad' '--enable-flac' '--enable-fluidsynth' '--enable-freetype' '--enable-fribidi' '--enable-gnutls' '--enable-jack' '--enable-kate' '--enable-libass' '--enable-libfreerdp' 
'--enable-libmpeg2' '--enable-libxml2' '--enable-lirc' '--enable-live555' '--enable-mad' '--enable-mkv' '--enable-mod' '--enable-mpc' '--enable-mtp' '--enable-mux_ogg' '--enable-ncurses' '--enable-notify' '--ena
ble-ogg' '--enable-opus' '--enable-oss' '--enable-pulse' '--enable-qt' '--enable-realrtsp' '--enable-samplerate' '--enable-schroedinger' '--enable-sdl' '--enable-sftp' '--enable-shout' '--enable-skins2' '--enabl
e-smbclient' '--enable-speex' '--enable-svg' '--enable-taglib' '--enable-theora' '--enable-twolame' '--enable-upnp' '--enable-vcd' '--enable-vcdx' '--enable-vorbis' '--enable-x264' '--enable-zvbi' '--with-kde-so
lid=/usr/share/kde4/apps/solid/actions/' '--disable-decklink' '--disable-dxva2' '--disable-fdkaac' '--disable-gnomevfs' '--disable-goom' '--disable-libvnc' '--disable-opencv' '--disable-projectm' '--disable-quic
ksync' '--disable-sndio' '--disable-telx' '--disable-vsxu' '--disable-wasapi' '--enable-alsa' '--enable-atmo' '--enable-dc1394' '--enable-dv1394' '--enable-linsys' '--enable-omxil' '--enable-udev' '--enable-libv
a' '--enable-v4l2' '--disable-crystalhd' '--disable-mmx' '--disable-sse' '--disable-neon' '--disable-altivec' 'CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security' 'CXXFLAG
S=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security' 'build_alias=arm-linux-gnueabihf'
[0x1e320d0] main libvlc debug: searching plug-in modules
[0x1e320d0] main libvlc debug: loading plugins cache file /usr/lib/vlc/plugins/plugins.dat
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: camera component couldn't be enabled
mmal: main: Failed to create camera component
mmal: Failed to run camera app. Please check for firmware updates

[0x1e320d0] main libvlc debug: recursively browsing `/usr/lib/vlc/plugins'
[0x1e320d0] main libvlc debug: saving plugins cache /usr/lib/vlc/plugins/plugins.dat
[0x1e320d0] main libvlc debug: plug-ins loaded: 392 modules
[0x1e320d0] main libvlc debug: opening config file (/home/ubuntu/.config/vlc/vlcrc)
[0x1e320d0] main libvlc debug: translation test: code is "C"
[0x1e320d0] main libvlc debug: CPU has capabilities ARM_NEON FPU
[0x1eca128] main input debug: Creating an input for 'Media Library'
[0x1eca128] main input debug: Input is a meta file: disabling unneeded options
[0x1eca128] main input debug: using timeshift granularity of 50 MiB, in path '/tmp'
[0x1eca128] main input debug: `file/xspf-open:///home/ubuntu/.local/share/vlc/ml.xspf' gives access `file' demux `xspf-open' path `/home/ubuntu/.local/share/vlc/ml.xspf'
[0x1eca128] main input debug: creating demux: access='file' demux='xspf-open' location='/home/ubuntu/.local/share/vlc/ml.xspf' file='/home/ubuntu/.local/share/vlc/ml.xspf'
[0x1e45d18] main demux debug: looking for access_demux module matching "file": 18 candidates
[0x1e45d18] main demux debug: no access_demux modules matched
[0x1eca128] main input debug: creating access 'file' location='/home/ubuntu/.local/share/vlc/ml.xspf', path='/home/ubuntu/.local/share/vlc/ml.xspf'
[0x1eca958] main access debug: looking for access module matching "file": 25 candidates
[0x1eca958] filesystem access debug: opening file `/home/ubuntu/.local/share/vlc/ml.xspf'
[0x1eca958] main access debug: using access module "filesystem"
[0x1e45d18] main stream debug: Using stream method for AStream*
[0x1e45d18] main stream debug: starting pre-buffering
[0x1e45d18] main stream debug: received first data after 0 ms
[0x1e45d18] main stream debug: pre-buffering done 296 bytes in 0s - 1927 KiB/s
[0x1ecaf80] main stream debug: looking for stream_filter module matching "any": 9 candidates
[0x1ecaf80] main stream debug: no stream_filter modules matched
[0x1ecaf80] main stream debug: looking for stream_filter module matching "record": 9 candidates
[0x1ecaf80] main stream debug: using stream_filter module "record"
[0x1eca128] main input debug: creating demux: access='file' demux='xspf-open' location='/home/ubuntu/.local/share/vlc/ml.xspf' file='/home/ubuntu/.local/share/vlc/ml.xspf'
[0x1ecc9a8] main demux debug: looking for demux module matching "xspf-open": 63 candidates
[0x1ecc9a8] playlist demux debug: using XSPF playlist reader
[0x1ecc9a8] main demux debug: using demux module "playlist"
[0x1ece128] main demux meta debug: looking for meta reader module matching "any": 2 candidates
[0x1ece128] lua demux meta debug: Trying Lua scripts in /home/ubuntu/.local/share/vlc/lua/meta/reader
[0x1ece128] lua demux meta debug: Trying Lua scripts in /usr/lib/vlc/lua/meta/reader
[0x1ece128] lua demux meta debug: Trying Lua playlist script /usr/lib/vlc/lua/meta/reader/filename.luac
[0x1ece128] lua demux meta debug: Trying Lua scripts in /usr/share/vlc/lua/meta/reader
[0x1ece128] main demux meta debug: no meta reader modules matched
[0x1eca128] main input debug: `file/xspf-open:///home/ubuntu/.local/share/vlc/ml.xspf' successfully opened
[0x1ebf340] main xml reader debug: looking for xml reader module matching "any": 1 candidates
[0x1ebf340] main xml reader debug: using xml reader module "xml"
[0x1ecc9a8] playlist demux debug: parsed 0 tracks successfully
[0x1eca128] main input debug: EOF reached
[0x1ecc9a8] main demux debug: removing module "playlist"
[0x1ecaf80] main stream debug: removing module "record"
[0x1eca958] main access debug: removing module "filesystem"
[0x1e44718] main playlist debug: creating audio output
[0x1ebe998] main audio output debug: looking for audio output module matching "any": 5 candidates
[0x1ebe998] alsa audio output debug: Available ALSA PCM devices:
[0x1ebe998] alsa audio output debug: Discard all samples (playback) or generate zero samples (capture) (null)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Default Audio Device (default:CARD=ALSA)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Default Audio Device (sysdefault:CARD=ALSA)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Direct sample mixing device (dmix:CARD=ALSA,DEV=0)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 IEC958/HDMI Direct sample mixing device (dmix:CARD=ALSA,DEV=1)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Direct sample snooping device (dsnoop:CARD=ALSA,DEV=0)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 IEC958/HDMI Direct sample snooping device (dsnoop:CARD=ALSA,DEV=1)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Direct hardware device without any conversions (hw:CARD=ALSA,DEV=0)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 IEC958/HDMI Direct hardware device without any conversions (hw:CARD=ALSA,DEV=1)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 ALSA Hardware device with all software conversions (plughw:CARD=ALSA,DEV=0)
[0x1ebe998] alsa audio output debug: bcm2835 ALSA, bcm2835 IEC958/HDMI Hardware device with all software conversions (plughw:CARD=ALSA,DEV=1)
[0x1ebe998] main audio output debug: using audio output module "alsa"   
[0x1e44718] main playlist debug: keeping audio output
[0x1e44718] main playlist debug: adding item `stdin' ( stream:///dev/stdin )
[0x765004d8] main input debug: Creating an input for 'stdin'
[0x1eca958] main interface debug: looking for interface module matching "hotkeys,none": 15 candidates
[0x1e44718] main playlist debug: no fetch required for (null) (art currently (null))
[0x1eca958] main interface debug: using interface module "hotkeys"
[0x1e45498] main interface debug: looking for interface module matching "globalhotkeys,none": 15 candidates
[0x1e45498] main interface debug: no interface modules matched
[0x1e45498] main interface error: no suitable interface module
[0x1e320d0] main libvlc error: interface "globalhotkeys,none" initialization failed
[0x1e45498] main interface debug: looking for interface module matching "dbus,none": 15 candidates
[0x1e45498] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[0x1e45498] main interface debug: no interface modules matched
[0x1e45498] main interface error: no suitable interface module
[0x1e320d0] main libvlc error: interface "dbus,none" initialization failed
[0x1e45498] main interface debug: looking for interface module matching "dummy": 15 candidates
[0x1e45498] dummy interface: using the dummy interface module...
[0x1e45498] main interface debug: using interface module "dummy"
[0x1e44718] main playlist debug: processing request item: null, node: Playlist, skip: 0
[0x1e44718] main playlist debug: rebuilding array of current - root Playlist
[0x1e44718] main playlist debug: rebuild done - 1 items, index -1
[0x1e44718] main playlist debug: starting playback of the new playlist item
[0x1e44718] main playlist debug: resyncing on stdin
[0x1e44718] main playlist debug: stdin is at 0
[0x1e44718] main playlist debug: creating new input thread
[0x76502ad8] main input debug: Creating an input for 'stdin'
[0x763006d8] main stream output debug: using sout chain=`rtp{sdp=rtsp://:8554}'
[0x763006d8] main stream output debug: stream=`rtp'
[0x763008c8] main stream out debug: looking for sout stream module matching "rtp": 21 candidates
[0x763008c8] main stream out debug: set config option: sout-rtp-sdp to rtsp://:8554
[0x763008c8] stream_out_rtp stream out debug: RTSP stream at /
[0x763008c8] main stream out debug: net: listening to * port 8554
[0x763008c8] main stream out debug: using sout stream module "stream_out_rtp"
[0x76502ad8] main input debug: using timeshift granularity of 50 MiB, in path '/tmp'
[0x76502ad8] main input debug: `stream:///dev/stdin' gives access `stream' demux `' path `/dev/stdin'
[0x76502ad8] main input debug: enforced demux ` h264'
[0x76502ad8] main input debug: creating demux: access='stream' demux='h264' location='/dev/stdin' file='/dev/stdin'
[0x76302658] main demux debug: looking for access_demux module matching "stream": 18 candidates
[0x76302658] main demux debug: no access_demux modules matched
[0x76502ad8] main input debug: creating access 'stream' location='/dev/stdin', path='/dev/stdin'
[0x76302980] main access debug: looking for access module matching "stream": 25 candidates
[0x76302980] filesystem access debug: opening file `/dev/stdin'
[0x76302980] main access debug: using access module "filesystem"
[0x76302a68] main stream debug: Using stream method for AStream*
[0x76302a68] main stream debug: starting pre-buffering
[0x76302a68] main stream error: cannot pre fill buffer
[0x76302980] main access debug: removing module "filesystem"
[0x76502ad8] main input warning: cannot create a stream_t from access
[0x1e44718] main playlist debug: dead input
[0x763006d8] main stream output debug: destroying useless sout
[0x763008c8] main stream out debug: destroying chain... (name=rtp)
[0x763008c8] main stream out debug: removing module "stream_out_rtp"
[0x763024a0] main http host debug: HTTP host removed
[0x763008c8] main stream out debug: destroying chain done
[0x1e44718] main playlist debug: changing item without a request (current 0/1)
[0x1e44718] main playlist debug: nothing to play

This does create stream, but when I access it via VLC on a separate host, VLC just gives me an endless list of errors about not being able to read any data.

I’m assuming this is related to the error in the ouput:

mmal: Failed to run camera app. Please check for firmware updates

However, I’m able to use the picamera Python module to capture still images from the camera. Why is VLC unable to access the camera?

I’m having an issue using cvlc to stream. I’m currently using Ubuntu 17.10 and VLC 2.2.6 as seen below. I start the stream through a python sub-process command. Afterwards, the following is printed to the terminal. Any help is appreciated.

VLC media player 2.2.6 Umbrella (revision 2.2.6-0-g1aae78981c)
[000055e7514d3d28] dbus interface error: Failed to connect to the D-Bus session daemon: Failed to connect to socket /tmp/dbus-1msq9as6ke: Connection refused
[000055e7514d3d28] core interface error: no suitable interface module
[000055e7513c5a88] core libvlc error: interface "dbus,none" initialization failed
[000055e7514d3d28] dummy interface: using the dummy interface module...
[00007fc8c0006c18] x264 encoder: using cpu capabilities: MMX2 SSE2Fast LZCNT

[00007fc8c0006c18] x264 encoder: profile High, level 3.0

[00007fc8c0006c18] x264 encoder: final ratefactor: 38.84

[00007fc8cc4ffbd8] stream_out_transcode stream out: input interval 33333 (base 1)
[00007fc8cc4ffbd8] stream_out_transcode stream out: output interval 66666 (base 1)
[00007fc8c0006c18] x264 encoder: using SAR=715/714

[00007fc8c0006c18] x264 encoder: using cpu capabilities: MMX2 SSE2Fast LZCNT

[00007fc8c0006c18] x264 encoder: profile High, level 3.0

[00007fc8c8000e08] core input error: ES_OUT_SET_(GROUP_)PCR  is called too late (pts_delay increased to 312 ms)
[00007fc8c8000e08] core input error: ES_OUT_RESET_PCR called
[00007fc8c8000e08] core input error: ES_OUT_SET_(GROUP_)PCR  is called too late (pts_delay increased to 323 ms)
[00007fc8c8000e08] core input error: ES_OUT_RESET_PCR called
...

This is the code i use to start the sub-process. Opencv is piped into the sub-process’s stdin.

pipe_out = subprocess.Popen([ 'cvlc', "--demux=rawvideo", "--rawvid-fps=30",
                "--rawvid-width=715",
                "--rawvid-height=576",
                "--rawvid-chroma=RV24",
                "-",
                "--sout",
                "#transcode{vcodec=h264,vb=200,fps=15,width=715,height=576}:std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=:5052/stream.flv}"],
                stdin = subprocess.PIPE, stdout = subprocess.PIPE) 

Освоил трансляцию видео при помощи VLC на сайт в WinXP (в Linux я «начинающий», для начала попробовал под Win):
1. Устанавливаем VLC
2. На web-сервере создаем страничку…
3. Запускаем трансляцию vlc.exe -vvv 01.avi —sout=#transcode{vcodec=h264,vb=128,fps=5,scale=0,acodec=none}:http{dst=:8080/1.flv}
4. Открываем страничку и смотрим кино…

Потом «осваиваем» со звуком vlc.exe -vvv 01.avi —sout=#transcode{vcodec=h264,vb=128,fps=5,scale=0,acodec=mp4a,ab=32,channels=1,samplerate=8000}:http{dst=:8080/1.flv}

Пробуем повторить в Ubuntu-Server:
1. Устанавливаем VLC (apt-get install vlc)
2. На web-сервере создаем страничку…
3. Запускаем трансляцию vlc -I «dummy» /home/kldf/01.avi —sout=#transcode{vcodec=h264,vb=128,fps=5,scale=0.25,acodec=mp4a,ab=32,channels=1,samplerate=8000}:http{dst=:8080/1.flv}

и получаем:
VLC media player 1.1.3 The Luggage (revision exported)
Blocked: call to unsetenv(«DBUS_ACTIVATION_ADDRESS»)
Blocked: call to unsetenv(«DBUS_ACTIVATION_BUS_TYPE»)
[0x84295dc] inhibit interface error: Failed to connect to the D-Bus session daemon: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

[0x84295dc] main interface error: no suitable interface module
[0x842bb2c] main interface error: no suitable interface module
[0x838215c] main libvlc error: interface «globalhotkeys,none» initialization failed
[0x842bb2c] dummy interface: using the dummy interface module…
[0x843091c] main access out: creating httpd
[0x842f07c] main stream output error: stream chain failed for `transcodesamplerate=8000:http{dst=:8080/1.flv}’
[0x84268d4] main input error: cannot start stream output instance, aborting
жмем Ctrl+C
[0x84114bc] signals interface error: Caught Прерывание signal, exiting…
kldf@ubuntu:~$

Что ему надо?  D-Bus… X11… Графику ему подавай? Или можно на это не обращать внимания? 
«main stream output error: stream chain failed for» = «не работает»?

Постепенно сокращаем строку (в несколько этапов) до vlc -I «dummy» /home/kldf/01.avi —sout=#transcode{vcodec=h264}:http{dst=:8080/1.flv}
И получаем:
VLC media player 1.1.3 The Luggage (revision exported)
Blocked: call to unsetenv(«DBUS_ACTIVATION_ADDRESS»)
Blocked: call to unsetenv(«DBUS_ACTIVATION_BUS_TYPE»)
[0x94b25cc] inhibit interface error: Failed to connect to the D-Bus session daemon: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

[0x94b25cc] main interface error: no suitable interface module
[0x94a57fc] main interface error: no suitable interface module
[0x940b15c] main libvlc error: interface «globalhotkeys,none» initialization failed
[0x94a57fc] dummy interface: using the dummy interface module…
[0x94b99e4] main access out: creating httpd
broken ffmpeg default settings detected
use an encoding preset (vpre)
[0x94e0ee4] avcodec encoder error: cannot open encoder
[0x94e0ee4] main encoder error: Ошибка вещания/перекодирования
[0x94e0ee4] main encoder error: VLC не может открыть этот кодировщик.
[0x94d0ae4] stream_out_transcode stream out error: cannot find video encoder (module:any fourcc:h264)
[0x94d0ae4] stream_out_transcode stream out error: cannot create video chain
[0x94b0214] main decoder error: cannot create packetizer output (mp4v)
flv does not support that sample rate, choose from (44100, 22050, 11025).
[0x94bab44] avformat mux error: could not write header
Что ему еще? Какие кодеки ему нужно?

P.S. Чего только не делал… чего только не читал… (переустанови ffmpeg, потом это… и еще это…) уже запутался…


Пользователь решил продолжить мысль 19 Октября 2010, 06:57:23:


установил ubuntu c нуля (на другой винт)
vlc -I «dummy» /home/kldf/01.avi
показывает кино в псевдографике (иксов ведь нет), хотя сначала выдает «…Failed to connect to the D-Bus…»
значит «Failed to connect to the D-Bus» не страшно — нет иксов и не надо…
а вещать не хочет все равно
kldf@ubuntu:~$ vlc -I «dummy» /home/kldf/01.avi —sout=#http{dst=:8080/1.flv}
VLC media player 1.0.6 Goldeneye
[0x9e2cd68] inhibit interface error: Failed to connect to the D-Bus session daemon: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
[0x9e2cd68] main interface error: no suitable interface module
[0x9d4f148] main libvlc error: interface «inhibit,none» initialization failed
[0x9e30e80] main interface error: no suitable interface module
[0x9d4f148] main libvlc error: interface «globalhotkeys,none» initialization failed
[0x9e30e80] dummy interface: using the dummy interface module…
[0x9d4f2e0] main stream out error: no sout stream module matched «http»
[0x9e22780] main stream output error: stream chain failed for `http{dst=:8080/1.flv}’
[0x9e1feb8] main input error: cannot start stream output instance, aborting

kldf@ubuntu:~$ vlc -I «dummy» /home/kldf/01.avi —sout=#transcode{vcodec=h264}:http{dst=:8080/1.flv}
VLC media player 1.0.6 Goldeneye
[0x9edb108] inhibit interface error: Failed to connect to the D-Bus session daemon: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.
[0x9edb108] main interface error: no suitable interface module
[0x9e0e148] main libvlc error: interface «inhibit,none» initialization failed
[0x9e0e6f0] main interface error: no suitable interface module
[0x9e0e148] main libvlc error: interface «globalhotkeys,none» initialization failed
[0x9e0e6f0] dummy interface: using the dummy interface module…
[0x9ef3508] main stream out error: no sout stream module matched «http»
[0x9ede9f0] stream_out_transcode stream out error: cannot create chain
[0x9edd988] main stream output error: stream chain failed for `transcode{vcodec=h264}:http{dst=:8080/1.flv}’
[0x9edf098] main input error: cannot start stream output instance, aborting

I’m trying to run a script that launches a vlc process from a systemd service. The script works fine if I launch it manually, but fails if I call it from systemd. The error I see in the logs is:

Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edc51430] vlcpulse audio output error: PulseAudio server connection failure: Connection refused
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edc628e0] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edc628e0] main interface error: no suitable interface module
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edb822a0] main libvlc error: interface "dbus,none" initialization failed
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edc728f0] main interface error: no suitable interface module
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edb822a0] main libvlc error: interface "globalhotkeys,none" initialization failed
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [000055f6edc728f0] dummy interface: using the dummy interface module...
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [00007ff32c9933a0] mux_ogg mux: Open
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [00007ff32c9973d0] main tls client error: cannot resolve www.example.com port 443: System error
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [00007ff32c9964d0] access stream error: HTTP connection failure
Oct 18 15:24:40 ip-172-31-13-123 python3[23937]: [00007ff32c9933a0] mux_ogg mux: Close

This is the systemd service:

[Unit]
Description=vlc service
After=kurento-media-server.service
StartLimitIntervalSec=0

[Service]
Type=simple
User=ubuntu
ExecStart=/usr/bin/python3 /usr/local/bin/start-vlc.py

[Install]
WantedBy=multi-user.target

This is my script:

#!/usr/bin/python3

import subprocess
subprocess.run("vlc -I rc -I dummy 'https://www.example.com/stream/5f7c91b21584ad57e798678c/interpreter0.sdp' ':sout=#transcode{vcodec=none,acodec=mp3,channels=1}:duplicate{dst=http{mux=ts,mime=,dst=:50001},dst=http{mux=ogg,mime=audio/ogg,dst=:50051/live.ogg}}' ':sout-keep' &", shell=True)

I’m running VLC version 3.0.8, systemd 237, Ubuntu 18.04.5

Anyone have a clue of what could be wrong?

Thanks

Понравилась статья? Поделить с друзьями:
  • Main init error перевод
  • Main init error system exception inventory manager standoff 2
  • Make stop error code 1
  • Make oldconfig error 127
  • Make no targets specified and no makefile found stop ошибка