'프로그램 사용 > VNC' 카테고리의 다른 글
libvncserver 마우스 이벤트 (0) | 2022.02.25 |
---|---|
libvncserver 사용예 (0) | 2022.02.15 |
gconf-editor / ubuntu 14.04 LTS vino + VNC 접속불가 (0) | 2015.03.22 |
VNC web 버전? (0) | 2014.12.11 |
VNC 5.0.5 (0) | 2013.09.04 |
libvncserver 마우스 이벤트 (0) | 2022.02.25 |
---|---|
libvncserver 사용예 (0) | 2022.02.15 |
gconf-editor / ubuntu 14.04 LTS vino + VNC 접속불가 (0) | 2015.03.22 |
VNC web 버전? (0) | 2014.12.11 |
VNC 5.0.5 (0) | 2013.09.04 |
[binaries]
c = '/usr/lib/ccache/arm-linux-gnueabihf-gcc'
cpp = '/usr/lib/ccache/arm-linux-gnueabihf-g++'
ar = '/usr/bin/arm-linux-gnueabihf-ar'
strip = '/usr/bin/arm-linux-gnueabihf-strip'
pkgconfig = '/usr/bin/arm-linux-gnueabihf-pkg-config'
[host_machine]
system = 'linux'
cpu_family = 'arm'
cpu = 'armv8hl'
endian = 'little'
|
meson build/ \
--cross-file=$HOME/pi/mesa/cross_file
|
[링크 : https://makersweb.net/qt/17557]
ubuntu 에서 apt install meson 으로 설치시 구버전이라 발생하는 에러
meson_options.txt:1:0: ERROR: Unknown type feature. |
[링크 : https://github.com/swaywm/wlroots/issues/1258]
Ninja는 속도에 중점을 둔 소형 빌드 시스템으로, Make의 느린 증분 빌드의 대안으로 만들어졌습니다. |
cpp
[링크 : https://github.com/google-coral/tflite]
[링크 : https://coral.ai/docs/edgetpu/tflite-cpp/]
python
[링크 : https://coding-yoon.tistory.com/91]
+
auto* delegate = edgetpu_create_delegate(device.type, device.path, nullptr, 0); interpreter->ModifyGraphWithDelegate({delegate, edgetpu_free_delegate}); |
[링크 : https://github.com/google-coral/tflite/blob/master/cpp/examples/classification/classify.cc]
auto delegates = delegate_providers.CreateAllDelegates(); for (auto& delegate : delegates) { const auto delegate_name = delegate.provider->GetName(); if (interpreter->ModifyGraphWithDelegate(std::move(delegate.delegate)) != kTfLiteOk) { LOG(ERROR) << "Failed to apply " << delegate_name << " delegate."; exit(-1); } else { LOG(INFO) << "Applied " << delegate_name << " delegate."; } } |
edgetpu_c.h 파일 내용 분석 (0) | 2022.02.07 |
---|---|
tensorflow brace-enclosed initializer list (4) | 2022.02.07 |
google coral, tpu yolo (0) | 2022.01.27 |
google coral, ubuntu 18.04 (0) | 2020.10.20 |
google coral (0) | 2020.10.06 |
h.264 코덱으로 된 녀석이라 데이터 부분만 빼내서 ffmpeg 거치면 재생이 가능할줄 알았는데 무리인가?
[링크 : https://video.stackexchange.com/questions/29073]
[링크 : https://codecpack.co/download/recover-mp4.html]
[링크 : https://stackoverflow.com/questions/19300350]
+
2022.02.14
복구 성공!
동일 기기에서 촬영된 정상 동영상과 복구할 동영상이 필요함
1. 정상 동영상에서 부터 무언가를 추출
C:\> recover_mp4.exe good.mp4 --analyze /// 중략 Now run the following command to start recovering: recover_mp4.exe corrupted_file result.h264 --noaudio --ext Then use ffmpeg to mux the final file: ffmpeg.exe -r 12.097 -i result.h264 -c:v copy result.mp4 |
2. 비정상 동영상으로 부터 h264 만 추출
위에서 알려준 옵션대로 처리해야 복구가 진행된다.
C:\> recover_mp4.exe corrupted_file result.h264 --noaudio --ext // 중략 skip: 0x001C02C5 [0x 6] ??? {00 00 00 02 09 F0} H264: 0x001C02CB [0x 15CA] -> 0x 1BF903 {41 9B A0 14} P frame %100.000 Complete! H264 non-IDR NAL unit size: Min 0x4, Avg 0x1289, Max 0x366C Video=99.864 'result.h264' created, size 1838797 (99.864%) |
3. 복구 데이터를 이용해서(아마도 h.264 스트림?) mp4로 변환
-r 뒤의 숫자는 framerate 니까 굳이 안 넣어 주면 원본의 속도로 복구 된다. (안되면 넣어주는게 좋을 듯)
C:\> ffmpeg.exe -r 30 -i result.h264 -c:v copy recovered.mp4 Input #0, h264, from 'result.h264': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive), 800x480, 25 fps, 25 tbr, 1200k tbn Output #0, mp4, to 'recovered.mp4': Metadata: encoder : Lavf59.16.100 Stream #0:0: Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(progressive), 800x480, q=2-31, 25 fps, 25 tbr, 15360 tbn Stream mapping: Stream #0:0 -> #0:0 (copy) Press [q] to stop, [?] for help [mp4 @ 0000020bce548780] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly frame= 363 fps=0.0 q=-1.0 Lsize= 1798kB time=00:00:12.06 bitrate=1220.7kbits/s speed=2.16e+03x video:1796kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.130085% |
[링크 : https://blog.naver.com/winsweet/222340783544]
[링크 : http://slydiman.me/eng/mmedia/recover_mp4.htm]
[링크 : https://restore.media/blog/how-to-fix-corrupted-mp4-files]
ffmpeg을 이용한 원하는 동영상 구간 자르기 (0) | 2022.07.28 |
---|---|
ffmpeg을 이용하여 동영상을 프레임 별로 jpeg 로 변환하기 (0) | 2022.04.15 |
ffmpeg을 이용한 rgb565 to bmp (0) | 2021.10.18 |
ffmpeg 재생 어렵다 -_ㅠ (0) | 2021.02.22 |
ffmpeg fbdev (0) | 2021.02.09 |
아놔.. rdp랑 동일하네.. wayland 자체가 현재 사용중인 세션은 어떻게든 끌어갈 수 없는 구조인가?
This is a VNC server for wlroots-based Wayland compositors (⛔ Gnome and KDE are not supported). It attaches to a running Wayland session, creates virtual input devices, and exposes a single display via the RFB protocol. The Wayland session may be a headless one, so it is also possible to run wayvnc without a physical display attached. |
[링크 : https://github.com/any1/wayvnc]
As of 2020, there are several projects that use these methods to provide GUI access to remote computers. The compositor Weston provides an RDP backend. GNOME has a remote desktop server that supports VNC. WayVNC is a VNC server that works with compositors, like Sway, based on the wlroots library. Waypipe works with all Wayland compositors and offers almost-transparent application forwarding, like ssh -X. |
[링크 : https://wayland.freedesktop.org/faq.html]
느리긴 해도 라즈베리 파이 3 에서도 돌아가긴 한다는 건가?
New features since v0.1.2:
|
wayland-scanner (0) | 2022.02.16 |
---|---|
wayland wl_fixed_t 변수 (0) | 2022.02.07 |
weston client 메모리 누수 (0) | 2022.01.17 |
wayland buffer (0) | 2022.01.13 |
wayland client example (0) | 2022.01.06 |
상세 내용이 있으나 너무 길어서 눈에 안들어 오는데..
아무튼 요약하면 Direct는 일반 포인터, indirect는 링크드 리스크나 멀티 포인터 인데
이중할당해서 이전 할당을 추적하지 않을 경우라고 보면 될 듯.
Pointer chain AAA Leak Case BBB Leak Case
------------- ------------- -------------
(1) RRR ------------> BBB DR
(2) RRR ---> AAA ---> BBB DR IR
(3) RRR BBB DL
(4) RRR AAA ---> BBB DL IL
(5) RRR ------?-----> BBB (y)DR, (n)DL
(6) RRR ---> AAA -?-> BBB DR (y)IR, (n)DL
(7) RRR -?-> AAA ---> BBB (y)DR, (n)DL (y)IR, (n)IL
(8) RRR -?-> AAA -?-> BBB (y)DR, (n)DL (y,y)IR, (n,y)IL, (_,n)DL
(9) RRR AAA -?-> BBB DL (y)IL, (n)DL
Pointer chain legend:
- RRR: a root set node or DR block
- AAA, BBB: heap blocks
- --->: a start-pointer
- -?->: an interior-pointer
Leak Case legend:
- DR: Directly reachable
- IR: Indirectly reachable
- DL: Directly lost
- IL: Indirectly lost
- (y)XY: it's XY if the interior-pointer is a real pointer
- (n)XY: it's XY if the interior-pointer is not a real pointer
- (_)XY: it's XY in either case
Every possible case can be reduced to one of the above nine. Memcheck merges some of these cases in its output, resulting in the following four leak kinds.
"Still reachable". This covers cases 1 and 2 (for the BBB blocks) above. A start-pointer or chain of start-pointers to the block is found. Since the block is still pointed at, the programmer could, at least in principle, have freed it before program exit. "Still reachable" blocks are very common and arguably not a problem. So, by default, Memcheck won't report such blocks individually.
"Definitely lost". This covers case 3 (for the BBB blocks) above. This means that no pointer to the block can be found. The block is classified as "lost", because the programmer could not possibly have freed it at program exit, since no pointer to it exists. This is likely a symptom of having lost the pointer at some earlier point in the program. Such cases should be fixed by the programmer.
"Indirectly lost". This covers cases 4 and 9 (for the BBB blocks) above. This means that the block is lost, not because there are no pointers to it, but rather because all the blocks that point to it are themselves lost. For example, if you have a binary tree and the root node is lost, all its children nodes will be indirectly lost. Because the problem will disappear if the definitely lost block that caused the indirect leak is fixed, Memcheck won't report such blocks individually by default.
"Possibly lost". This covers cases 5--8 (for the BBB blocks) above. This means that a chain of one or more pointers to the block has been found, but at least one of the pointers is an interior-pointer. This could just be a random value in memory that happens to point into a block, and so you shouldn't consider this ok unless you know you have interior-pointers.
[링크 : https://valgrind.org/docs/manual/mc-manual.html#mc-manual.leaks]
"still reachable" (memory that is pointed to by a pointer). "directly lost" (memory that is not pointed to be any live pointer) "indirectly lost" (memory that is pointed to by a pointer that is in memory that is "directly lost) "possibly lost" (memory that is pointed to, but the pointer does not point to the start of the memory). |
[링크 : https://stackoverflow.com/questions/24201561/valgrind-memory-leak-log]
valgrind callgrind (0) | 2023.07.07 |
---|---|
vaglind 사용 (0) | 2022.01.14 |
valgrind 지원 플랫폼 (0) | 2014.10.15 |
valgrind GUI frontend- kcachegrind / valkyrie (0) | 2014.10.15 |
누수는 누수인데 늘어나진 않는 누수인 것 같아서 일단 패스.
[링크 : https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/18]
wayland wl_fixed_t 변수 (0) | 2022.02.07 |
---|---|
wayvnc (0) | 2022.01.24 |
wayland buffer (0) | 2022.01.13 |
wayland client example (0) | 2022.01.06 |
weston window transform (0) | 2022.01.06 |
valgrind callgrind (0) | 2023.07.07 |
---|---|
valgrind 누수 종류 (0) | 2022.01.18 |
valgrind 지원 플랫폼 (0) | 2014.10.15 |
valgrind GUI frontend- kcachegrind / valkyrie (0) | 2014.10.15 |
wayland screenshooter에서 shared memory를 이용하여
캡쳐한 이미지를 공유하는데 해당 내용에 대한 정리가 잘되어 있어서 링크!
[링크 : https://nemoux00.wordpress.com/2014/02/13/wayland-버퍼-관리/]
wayvnc (0) | 2022.01.24 |
---|---|
weston client 메모리 누수 (0) | 2022.01.17 |
wayland client example (0) | 2022.01.06 |
weston window transform (0) | 2022.01.06 |
weston-screenshooter 실행에러 (0) | 2022.01.05 |
두개 방송국이 같이 보이는데 동시에 땡~! 해주니까 파형도 이쁘게 종모양으로 나온다.
어떻게 보면.. AND 게이트 3개가 보이는 느낌이네 ㅋㅋ
rtl sdr 다중 채널 디코딩 (0) | 2022.08.30 |
---|---|
ubuntu 18.04에 사운드 카드가 갑자기 사라졌다? (0) | 2022.07.20 |
gqrx 오디오 스트리밍 (0) | 2022.01.07 |
rpi gqrx (0) | 2022.01.07 |
rtl sdr am (0) | 2022.01.07 |