![]() just connect the phone via USB to the computer, start the Speedify client, done. Personally, I find the solution easier: no problems with different IP addresses, DHCP servers in the same network, etc. Additional hardware is not required, five devices can use the Speedify connection in parallel (only that one will not necessarily have a corresponding number of LTE devices for bundling). The own VPS for the complete self-build solution is more expensive per month. ![]() Regarding the costs, you can currently () get Speedify for a good 1.50 EURO per month (when paying for 3 years in advance). In terms of speed, both variants are similarly fast. I have not tried this yet, the setup would then rather correspond to the variant with OpenMPTCPRouter. The audio through that HDMI interface is a somewhat grey matter, but hey - nothing stops you from using a simple USB sound card.What should also work according to the Speedify website: run the client on a Raspberry Pi and then share it on the network. If you don't need USB3.0 you can safely go with a less expensive and power consuming RPi - there are inexpensive HDMI-CSI2 modules available that you connect to the camera port. There are rumors that you can get 50 fps with overclocking.Īnd basically there's no difference if you use Pi4 or Pi0 - they share the same codec block. Have a look at v4l2m2m - my tests show it's able to do p with no overclocking (omx_h264 maxes out at 30 fps at the same resolution). However there's a pretty decent hardware encoder available (apart from really good hardware decoder) that they should have used, allowing to get up to 1080p30 H.264 streaming with hardly any hit on the CPU utilization. And that's why they struggle to get more than 24fps from a 720p stream. Since the Pi is a rather low CPU performance device encoding the stream on the CPU itself makes not much sense. Video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknownĭo have in mind that they missed out on the one of the most important factors. Failed to update header with correct filesize.Įrror writing trailer of pipe:: Broken pipeįrame= 0 fps=0.0 q=0.0 Lsize= 0kB time=00:00:00.00 bitrate=N/A speed= 0x Failed to update header with correct duration. 264 - core 158 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc_lookahead=0 rc=crf mbtree=0 crf=17.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=1000 vbv_bufsize=1000 crf_max=0.0 nal_hrd=none filler=0 ip_ratio=1.40 aq=0įinishing stream 0:1 without any data written to it. profile Constrained Baseline, level 3.2, 4:2:0, 8-bit Thread message queue blocking consider raising the thread_queue_size option (current value: 8)įrame= 0 fps=0.0 q=0.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/Aįinishing stream 0:0 without any data written to it. Guessed Channel Layout for Input Stream #1.0 : stereoĭuration: N/A, start: 1576099663.557438, bitrate: 1536 kb/s Dequeued v4l2 buffer contains 4147200 bytes, but 3110400 were expected. ![]() The driver changed the time per frame from 1/24 to 117/7013 The V4L2 driver changed the video from 1280x720 to 1920x1080 35.101Ĭopyright (c) 2000-2019 the FFmpeg developers libavdevice 58. Ffmpeg version N-95970-gd5274f8 Copyright (c) 2000-2019 the FFmpeg developersĬonfiguration: -prefix=/home/pi/ffmpeg_build -pkg-config-flags=-static -extra-cflags=-I/home/pi/ffmpeg_build/include -extra-ldflags=-L/home/pi/ffmpeg_build/lib -extra-libs='-lpthread -lm' -bindir=/home/pi/bin -enable-gpl -enable-libass -enable-libfdk-aac -enable-libfreetype -enable-libmp3lame -enable-libopus -enable-libvorbis -enable-libvpx -enable-libx264 -enable-libx265 -enable-nonfreeįfmpeg version N-95970-gd5274f8 libavformat 58.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |