
Recherche avancée
Autres articles (59)
-
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...)
Sur d’autres sites (4156)
-
Revision 3331 : On ajoute un accès à la configuration dans les menus
25 avril 2010, par kent1 — LogOn ajoute un accès à la configuration dans les menus
-
Using ffmpeg to livestream webcam video over UDP from Pocketbeagle running linux, what is missing ?
26 août 2021, par bherman330I've been reading up on a lot of questions pertaining to ffmpeg and streaming a live feed from a webcam, and have gotten pretty close but I am just missing something small. I have a Pocketbeagle (pocket-size linux computer) running Debian, with a webcam attached via USB. The pocketbeagle is connected to my Windows computer via ethernet over USB. The pocketbeagle has the IP 192.168.7.2, and my computer 192.168.7.1. I am attempting to stream via UDP to VLC, but I cannot see the video feed on VLC no matter what I try


The command I am running is this :


ffmpeg -f v4l2 -input_format mjpeg -i /dev/video0 -framerate 10 -video_size 1280x720 -f mpegts udp:192.168.7.1:15151



This results in this output, which appears to actually be streaming something as the Lsize and time increase while it runs until I kill it :


ffmpeg version 4.1.6-1~deb10u1 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 8 (Debian 8.3.0-6)
configuration: --prefix=/usr --extra-version='1~deb10u1' --toolchain=hardened --libdir=/usr/lib/arm- 
linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping 
--enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa -- 
enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio - 
-enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi - 
-enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable- 
libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable- 
librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh 
 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx -- 
enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq 
 --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable- 
libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 
 --enable-shared
 libavutil 56. 22.100 / 56. 22.100
 libavcodec 58. 35.100 / 58. 35.100
 libavformat 58. 20.100 / 58. 20.100
 libavdevice 58. 5.100 / 58. 5.100
 libavfilter 7. 40.101 / 7. 40.101
 libavresample 4. 0. 0 / 4. 0. 0
 libswscale 5. 3.100 / 5. 3.100
 libswresample 3. 3.100 / 3. 3.100
 libpostproc 55. 3.100 / 55. 3.100
 Input #0, video4linux2,v4l2, from '/dev/video0':
 Duration: N/A, start: 2998.098197, bitrate: N/A
 Stream #0:0: Video: mjpeg, yuvj422p(pc, bt470bg/unknown/unknown), 1280x720, 30 fps, 30 tbr, 
 1000k tbn, 1000k tbc
 Stream mapping:
 Stream #0:0 -> #0:0 (mjpeg (native) -> mpeg2video (native))
 Press [q] to stop, [?] for help
 [swscaler @ 0x1bb2d40] deprecated pixel format used, make sure you did set range correctly
 Output #0, mpegts, to 'udp:192.168.7.1:15151':
 Metadata:
 encoder : Lavf58.20.100
 Stream #0:0: Video: mpeg2video (4:2:2), yuv422p, 1280x720, q=2-31, 200 kb/s, 30 fps, 90k tbn, 30 
 tbc
 Metadata:
 encoder : Lavc58.35.100 mpeg2video
 Side data:
 cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: -1
 frame= 17 fps=2.8 q=31.0 Lsize= 654kB time=00:00:02.10 bitrate=2552.5kbits/s speed=0.343x x
 video:605kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 8.214545%
 Exiting normally, received signal 2.



On top of that, VLC recognizes a stream of some sort has started, and very slowly increments the time (like 1 second every 30s-1m). However, I do not see any video coming through.


Any help in getting this running would be much appreciated !


-
lavc/flacdsp : optimise RVV vector type for lpc16
14 mai 2024, par Rémi Denis-Courmontlavc/flacdsp : optimise RVV vector type for lpc16
This calculates the optimal vector type value at run-time based on the
hardware vector length and the FLAC LPC prediction order. In this
particular case, the additional computation is easily amortised over
the loop iterations :T-Head C908 :
C V before V after
1 48.0 214.7 95.2
2 64.7 214.2 94.7
3 79.7 213.5 94.5
4 96.2 196.5 94.2 #
5 111.0 195.7 118.5
6 127.0 211.2 102.0
7 143.7 194.2 101.5
8 175.7 193.2 101.2 #
9 176.2 224.2 126.0
10 191.5 192.0 125.5
11 224.5 191.2 124.7
12 223.0 190.2 124.2
13 239.2 189.5 123.7
14 253.7 188.7 139.5
15 286.2 188.0 122.7
16 284.0 187.0 122.5 #
17 300.2 186.5 186.5
18 314.0 185.5 185.7
19 329.7 184.7 185.0
20 343.0 184.2 184.2
21 358.7 199.2 183.7
22 371.7 182.7 182.7
23 387.5 181.7 182.0
24 400.7 181.0 181.2
25 431.5 180.2 196.5
26 443.7 195.5 196.0
27 459.0 178.7 196.2
28 470.7 177.7 194.2
29 470.0 177.0 193.5
30 481.2 176.2 176.5
31 496.2 175.5 175.7
32 507.2 174.7 191.0 ## Power of two boundary.
With 128-bit vectors, improvements are expected for the first two
test cases only. For the other two, there is overhead but below noise.
Improvements should be better observable with prediction order of 8
and less, or on hardware with larger vector sizes.