Recherche avancée
Médias (1)
-
Collections - Formulaire de création rapide
19 février 2013, par
Mis à jour : Février 2013
Langue : français
Type : Image
Autres articles (74)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (5763)
-
FFMPEG Output File is Empty Nothing was Encoded (for a Picture) ?
4 mars 2023, par Sarah SzaboI have a strange issue effecting one of my programs that does bulk media conversions using ffmpeg from the command line, however this effects me using it directly from the shell as well :


ffmpeg -i INPUT.mkv -ss 0:30 -y -qscale:v 2 -frames:v 1 -f image2 -huffman optimal "OUTPUT.png"
fails every run with the error message :
Output file is empty, nothing was encoded (check -ss / -t / -frames parameters if used)

This only happens with very specific videos, and seemingly no other videos. File type is usually .webm. These files have been downloaded properly (usually from yt-dlp), and I have tried re-downloading them just to verify their integrity.


One such file from a colleague was : https://www.dropbox.com/s/xkucr2z5ra1p2oh/Triggerheart%20Execlica%20OST%20%28Arrange%29%20-%20Crueltear%20Ending.mkv?dl=0


Is there a subtle issue with the command string ?


Notes :


removing
-huffman optimalhad no effect

moving
-ssto before-ihad no effect

removing
-f image2 had no effect

Full Log :


sarah@MidnightStarSign:~/Music/Playlists/Indexing/Indexing Temp$ ffmpeg -i Triggerheart\ Execlica\ OST\ \(Arrange\)\ -\ Crueltear\ Ending.mkv -ss 0:30 -y -qscale:v 2 -frames:v 1 -f image2 -huffman optimal "TEST.png"
ffmpeg version n5.1.2 Copyright (c) 2000-2022 the FFmpeg developers
 built with gcc 12.2.0 (GCC)
 configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-shared --enable-version3 --enable-vulkan
 libavutil 57. 28.100 / 57. 28.100
 libavcodec 59. 37.100 / 59. 37.100
 libavformat 59. 27.100 / 59. 27.100
 libavdevice 59. 7.100 / 59. 7.100
 libavfilter 8. 44.100 / 8. 44.100
 libswscale 6. 7.100 / 6. 7.100
 libswresample 4. 7.100 / 4. 7.100
 libpostproc 56. 6.100 / 56. 6.100
[matroska,webm @ 0x55927f484740] Could not find codec parameters for stream 2 (Attachment: none): unknown codec
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, matroska,webm, from 'Triggerheart Execlica OST (Arrange) - Crueltear Ending.mkv':
 Metadata:
 title : TriggerHeart Exelica PS2 & 360 Arrange ー 16 - Crueltear Ending
 PURL : https://www.youtube.com/watch?v=zJ0bEa_8xEg
 COMMENT : https://www.youtube.com/watch?v=zJ0bEa_8xEg
 ARTIST : VinnyVynce
 DATE : 20170905
 ENCODER : Lavf59.27.100
 Duration: 00:00:30.00, start: -0.007000, bitrate: 430 kb/s
 Stream #0:0(eng): Video: vp9 (Profile 0), yuv420p(tv, bt709), 720x720, SAR 1:1 DAR 1:1, 25 fps, 25 tbr, 1k tbn (default)
 Metadata:
 DURATION : 00:00:29.934000000
 Stream #0:1(eng): Audio: opus, 48000 Hz, stereo, fltp (default)
 Metadata:
 DURATION : 00:00:30.001000000
 Stream #0:2: Attachment: none
 Metadata:
 filename : cover.webp
 mimetype : image/webp
Codec AVOption huffman (Huffman table strategy) specified for output file #0 (TEST.png) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.
Stream mapping:
 Stream #0:0 -> #0:0 (vp9 (native) -> png (native))
Press [q] to stop, [?] for help
Output #0, image2, to 'TEST.png':
 Metadata:
 title : TriggerHeart Exelica PS2 & 360 Arrange ー 16 - Crueltear Ending
 PURL : https://www.youtube.com/watch?v=zJ0bEa_8xEg
 COMMENT : https://www.youtube.com/watch?v=zJ0bEa_8xEg
 ARTIST : VinnyVynce
 DATE : 20170905
 encoder : Lavf59.27.100
 Stream #0:0(eng): Video: png, rgb24, 720x720 [SAR 1:1 DAR 1:1], q=2-31, 200 kb/s, 25 fps, 25 tbn (default)
 Metadata:
 DURATION : 00:00:29.934000000
 encoder : Lavc59.37.100 png
frame= 0 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.00 bitrate=N/A speed= 0x 
video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Output file is empty, nothing was encoded (check -ss / -t / -frames parameters if used)


Manjaro OS System Specs :


System:
 Kernel: 6.1.12-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
 parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.1-x86_64
 root=UUID=f11386cf-342d-47ac-84e6-484b7b2f377d rw rootflags=subvol=@
 radeon.modeset=1 nvdia-drm.modeset=1 quiet
 cryptdevice=UUID=059df4b4-5be4-44d6-a23a-de81135eb5b4:luks-disk
 root=/dev/mapper/luks-disk apparmor=1 security=apparmor
 resume=/dev/mapper/luks-swap udev.log_priority=3
 Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
 Distro: Manjaro Linux base: Arch Linux
Machine:
 Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
 serial: <superuser required="required"> UEFI: American Megatrends v: 4408
 date: 10/27/2022
Battery:
 Message: No system battery data found. Is one present?
Memory:
 RAM: total: 62.71 GiB used: 27.76 GiB (44.3%)
 RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
 Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
 level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
 model-id: 0x21 (33) stepping: 0 microcode: 0xA201016
 Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
 L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
 L3: 64 MiB desc: 2x32 MiB
 Speed (MHz): avg: 4099 high: 4111 min/max: 2200/6358 boost: disabled
 scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 4099 2: 4095
 3: 4102 4: 4100 5: 4097 6: 4100 7: 4110 8: 4111 9: 4083 10: 4099 11: 4100
 12: 4094 13: 4097 14: 4101 15: 4100 16: 4099 17: 4100 18: 4097 19: 4098
 20: 4095 21: 4100 22: 4099 23: 4099 24: 4105 25: 4098 26: 4100 27: 4100
 28: 4092 29: 4103 30: 4101 31: 4100 32: 4099 bogomips: 262520
 Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
 bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
 constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
 cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms extapic
 extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
 hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
 misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
 nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
 pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
 pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
 skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
 svm svm_lock syscall tce topoext tsc tsc_scale umip v_spec_ctrl
 v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
 x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
 Vulnerabilities:
 Type: itlb_multihit status: Not affected
 Type: l1tf status: Not affected
 Type: mds status: Not affected
 Type: meltdown status: Not affected
 Type: mmio_stale_data status: Not affected
 Type: retbleed status: Not affected
 Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
 prctl
 Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
 sanitization
 Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
 STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
 Type: srbds status: Not affected
 Type: tsx_async_abort status: Not affected
Graphics:
 Device-1: NVIDIA GA104 [GeForce RTX 3070] vendor: ASUSTeK driver: nvidia
 v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
 status: current (as of 2023-02) arch: Ampere code: GAxxx
 process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 8
 link-max: lanes: 16 bus-ID: 0b:00.0 chip-ID: 10de:2484 class-ID: 0300
 Device-2: AMD Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
 vendor: VISIONTEK driver: radeon v: kernel alternate: amdgpu arch: GCN-1
 code: Southern Islands process: TSMC 28nm built: 2011-20 pcie: gen: 3
 speed: 8 GT/s lanes: 8 link-max: lanes: 16 ports: active: DP-3,DP-4
 empty: DP-1, DP-2, DP-5, DP-6 bus-ID: 0c:00.0 chip-ID: 1002:683f
 class-ID: 0300 temp: 54.0 C
 Device-3: Microdia USB 2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
 bus-ID: 9-2:3 chip-ID: 0c45:6367 class-ID: 0102 serial: <filter>
 Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
 compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: radeonsi
 gpu: radeon display-ID: :0 screens: 1
 Screen-1: 0 s-res: 5760x2160 s-dpi: 80 s-size: 1829x686mm (72.01x27.01")
 s-diag: 1953mm (76.91")
 Monitor-1: DP-1 pos: 1-2 res: 1920x1080 dpi: 93
 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
 Monitor-2: DP-1-3 pos: 2-1 res: 1920x1080 dpi: 82
 size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
 Monitor-3: DP-1-4 pos: 1-1 res: 1920x1080 dpi: 93
 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
 Monitor-4: DP-3 pos: primary,2-2 res: 1920x1080 dpi: 82
 size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
 Monitor-5: DP-4 pos: 2-4 res: 1920x1080 dpi: 82
 size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
 Monitor-6: HDMI-0 pos: 1-3 res: 1920x1080 dpi: 93
 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
 API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce RTX
 3070/PCIe/SSE2 direct-render: Yes
Audio:
 Device-1: NVIDIA GA104 High Definition Audio vendor: ASUSTeK
 driver: snd_hda_intel bus-ID: 5-1:2 v: kernel chip-ID: 30be:1019 pcie:
 class-ID: 0102 gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16
 bus-ID: 0b:00.1 chip-ID: 10de:228b class-ID: 0403
 Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000
 Series] vendor: VISIONTEK driver: snd_hda_intel v: kernel pcie: gen: 3
 speed: 8 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 0c:00.1
 chip-ID: 1002:aab0 class-ID: 0403
 Device-3: AMD Starship/Matisse HD Audio vendor: ASUSTeK
 driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
 bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
 Device-4: Schiit Audio Unison Universal Dac type: USB driver: snd-usb-audio
 Device-5: JMTek LLC. Plugable USB Audio Device type: USB
 driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:3 chip-ID: 0c76:120b
 class-ID: 0300 serial: <filter>
 Device-6: ASUSTek ASUS AI Noise-Cancelling Mic Adapter type: USB
 driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4:4 chip-ID: 0b05:194e
 class-ID: 0300 serial: <filter>
 Device-7: Microdia USB 2.0 Camera type: USB driver: snd-usb-audio,uvcvideo
 bus-ID: 9-2:3 chip-ID: 0c45:6367 class-ID: 0102 serial: <filter>
 Sound API: ALSA v: k6.1.12-1-MANJARO running: yes
 Sound Interface: sndio v: N/A running: no
 Sound Server-1: PulseAudio v: 16.1 running: no
 Sound Server-2: PipeWire v: 0.3.65 running: yes
Network:
 Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
 chip-ID: 8086:1539 class-ID: 0200
 IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
 IP v4: <filter> type: dynamic noprefixroute scope: global
 broadcast: <filter>
 IP v6: <filter> type: noprefixroute scope: link
 IF-ID-1: docker0 state: down mac: <filter>
 IP v4: <filter> scope: global broadcast: <filter>
 WAN IP: <filter>
Bluetooth:
 Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
 driver: btusb v: 0.8 bus-ID: 5-5.3:7 chip-ID: 0a12:0001 class-ID: e001
 Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
 Message: No logical block device data found.
 Device-1: luks-c847cf9f-c6b5-4624-a25e-4531e318851a maj-min: 254:2
 type: LUKS dm: dm-2 size: 3.64 TiB
 Components:
 p-1: sda1 maj-min: 8:1 size: 3.64 TiB
 Device-2: luks-swap maj-min: 254:1 type: LUKS dm: dm-1 size: 12 GiB
 Components:
 p-1: nvme0n1p2 maj-min: 259:2 size: 12 GiB
 Device-3: luks-disk maj-min: 254:0 type: LUKS dm: dm-0 size: 919.01 GiB
 Components:
 p-1: nvme0n1p3 maj-min: 259:3 size: 919.01 GiB
RAID:
 Message: No RAID data found.
Drives:
 Local Storage: total: 9.1 TiB used: 2.79 TiB (30.6%)
 SMART Message: Unable to run smartctl. Root privileges required.
 ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
 model: WDS100T3X0C-00SJG0 size: 931.51 GiB block-size: physical: 512 B
 logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
 rev: 111110WD temp: 53.9 C scheme: GPT
 ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Western Digital
 model: WDS100T2B0C-00PXH0 size: 931.51 GiB block-size: physical: 512 B
 logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
 rev: 211070WD temp: 46.9 C scheme: GPT
 ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
 model: WD4005FZBX-00K5WB0 size: 3.64 TiB block-size: physical: 4096 B
 logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
 rev: 1A01 scheme: GPT
 ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
 model: WD4005FZBX-00K5WB0 size: 3.64 TiB block-size: physical: 4096 B
 logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
 rev: 1A01 scheme: GPT
 ID-5: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk
 model: Gaming Xbox 360 size: 7.48 GiB block-size: physical: 512 B
 logical: 512 B type: N/A serial: <filter> rev: 8.02 scheme: MBR
 SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
 Message: No optical or floppy data found.
Partition:
 ID-1: / raw-size: 919.01 GiB size: 919.01 GiB (100.00%)
 used: 611.14 GiB (66.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
 mapped: luks-disk label: N/A uuid: N/A
 ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
 used: 40.2 MiB (7.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: EFI
 uuid: 8922-E04D
 ID-3: /home raw-size: 919.01 GiB size: 919.01 GiB (100.00%)
 used: 611.14 GiB (66.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
 mapped: luks-disk label: N/A uuid: N/A
 ID-4: /run/media/sarah/ConvergentRefuge raw-size: 3.64 TiB
 size: 3.64 TiB (100.00%) used: 2.19 TiB (60.1%) fs: btrfs dev: /dev/dm-2
 maj-min: 254:2 mapped: luks-c847cf9f-c6b5-4624-a25e-4531e318851a
 label: ConvergentRefuge uuid: 7d295e73-4143-4eb1-9d22-75a06b1d2984
 ID-5: /run/media/sarah/MSS_EXtended raw-size: 475.51 GiB
 size: 475.51 GiB (100.00%) used: 1.48 GiB (0.3%) fs: btrfs
 dev: /dev/nvme1n1p1 maj-min: 259:5 label: MSS EXtended
 uuid: f98b3a12-e0e4-48c7-91c2-6e3aa6dcd32c
Swap:
 Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
 ID-1: swap-1 type: partition size: 12 GiB used: 6.86 GiB (57.2%)
 priority: -2 dev: /dev/dm-1 maj-min: 254:1 mapped: luks-swap label: SWAP
 uuid: c8991364-85a7-4e6c-8380-49cd5bd7a873
Unmounted:
 ID-1: /dev/nvme1n1p2 maj-min: 259:6 size: 456 GiB fs: ntfs label: N/A
 uuid: 5ECA358FCA356485
 ID-2: /dev/sdb1 maj-min: 8:17 size: 3.64 TiB fs: ntfs
 label: JerichoVariance uuid: 1AB22D5664889CBD
 ID-3: /dev/sdc1 maj-min: 8:33 size: 3.57 GiB fs: iso9660
 ID-4: /dev/sdc2 maj-min: 8:34 size: 4 MiB fs: vfat label: MISO_EFI
 uuid: 5C67-4BF8
USB:
 Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
 Hub-2: 1-2:2 info: Hitachi ports: 4 rev: 2.1 speed: 480 Mb/s
 chip-ID: 045b:0209 class-ID: 0900
 Device-1: 1-2.4:3 info: Microsoft Xbox One Controller (Firmware 2015)
 type: <vendor specific="specific"> driver: xpad interfaces: 3 rev: 2.0 speed: 12 Mb/s
 power: 500mA chip-ID: 045e:02dd class-ID: ff00 serial: <filter>
 Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s
 chip-ID: 1d6b:0003 class-ID: 0900
 Hub-4: 2-2:2 info: Hitachi ports: 4 rev: 3.0 speed: 5 Gb/s
 chip-ID: 045b:0210 class-ID: 0900
 Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0
 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
 Hub-6: 3-1:2 info: VIA Labs Hub ports: 4 rev: 2.1 speed: 480 Mb/s
 power: 100mA chip-ID: 2109:3431 class-ID: 0900
 Hub-7: 3-1.2:3 info: VIA Labs VL813 Hub ports: 4 rev: 2.1 speed: 480 Mb/s
 chip-ID: 2109:2813 class-ID: 0900
 Hub-8: 4-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s
 chip-ID: 1d6b:0003 class-ID: 0900
 Hub-9: 4-2:2 info: VIA Labs VL813 Hub ports: 4 rev: 3.0 speed: 5 Gb/s
 chip-ID: 2109:0813 class-ID: 0900
 Hub-10: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
 Device-1: 5-1:2 info: Schiit Audio Unison Universal Dac type: Audio
 driver: snd-usb-audio interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA
 chip-ID: 30be:1019 class-ID: 0102
 Device-2: 5-2:3 info: JMTek LLC. Plugable USB Audio Device type: Audio,HID
 driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1
 speed: 12 Mb/s power: 100mA chip-ID: 0c76:120b class-ID: 0300
 serial: <filter>
 Device-3: 5-4:4 info: ASUSTek ASUS AI Noise-Cancelling Mic Adapter
 type: Audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 4
 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 0b05:194e class-ID: 0300
 serial: <filter>
 Hub-11: 5-5:5 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
 power: 100mA chip-ID: 05e3:0608 class-ID: 0900
 Device-1: 5-5.3:7 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
 type: Bluetooth driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s
 power: 100mA chip-ID: 0a12:0001 class-ID: e001
 Hub-12: 5-6:6 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
 power: 100mA chip-ID: 05e3:0608 class-ID: 0900
 Hub-13: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
 chip-ID: 1d6b:0003 class-ID: 0900
 Hub-14: 7-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0
 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
 Device-1: 7-2:2 info: SanDisk Cruzer Micro Flash Drive type: Mass Storage
 driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 200mA
 chip-ID: 0781:5151 class-ID: 0806 serial: <filter>
 Device-2: 7-4:3 info: ASUSTek AURA LED Controller type: HID
 driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA
 chip-ID: 0b05:18f3 class-ID: 0300 serial: <filter>
 Hub-15: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
 chip-ID: 1d6b:0003 class-ID: 0900
 Hub-16: 9-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
 Hub-17: 9-1:2 info: Terminus FE 2.1 7-port Hub ports: 7 rev: 2.0
 speed: 480 Mb/s power: 100mA chip-ID: 1a40:0201 class-ID: 0900
 Device-1: 9-1.1:4 info: Sunplus Innovation Gaming mouse [Philips SPK9304]
 type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s
 power: 98mA chip-ID: 1bcf:08a0 class-ID: 0301
 Device-2: 9-1.5:6 info: Microdia Backlit Gaming Keyboard
 type: Keyboard,Mouse driver: hid-generic,usbhid interfaces: 2 rev: 2.0
 speed: 12 Mb/s power: 400mA chip-ID: 0c45:652f class-ID: 0301
 Device-3: 9-1.6:7 info: HUION H420 type: Mouse,HID driver: uclogic,usbhid
 interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 256c:006e
 class-ID: 0300
 Hub-18: 9-1.7:8 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s
 power: 100mA chip-ID: 1a40:0101 class-ID: 0900
 Device-1: 9-2:3 info: Microdia USB 2.0 Camera type: Video,Audio
 driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s
 power: 500mA chip-ID: 0c45:6367 class-ID: 0102 serial: <filter>
 Device-2: 9-4:11 info: VKB-Sim © Alex Oz 2021 VKBsim Gladiator EVO L
 type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
 power: 500mA chip-ID: 231d:0201 class-ID: 0300
 Hub-19: 10-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s
 chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
 System Temperatures: cpu: 38.0 C mobo: 41.0 C
 Fan Speeds (RPM): fan-1: 702 fan-2: 747 fan-3: 938 fan-4: 889 fan-5: 3132
 fan-6: 0 fan-7: 0
 GPU: device: nvidia screen: :0.0 temp: 49 C fan: 0% device: radeon
 temp: 53.0 C
Info:
 Processes: 842 Uptime: 3h 11m wakeups: 0 Init: systemd v: 252
 default: graphical tool: systemctl Compilers: gcc: 12.2.1 alt: 10/11
 clang: 15.0.7 Packages: 2158 pm: pacman pkgs: 2110 libs: 495 tools: pamac,yay
 pm: flatpak pkgs: 31 pm: snap pkgs: 17 Shell: Bash v: 5.1.16
 running-in: yakuake inxi: 3.3.25
</filter></filter></filter></filter></filter></filter></vendor></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></filter></superuser>

-
CCPA vs GDPR : Understanding Their Impact on Data Analytics
19 mars, par Alex CarmonaWith over 400 million internet users in Europe and 331 million in the US (11% of which reside in California alone), understanding the nuances of privacy laws like the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) is crucial for compliant and ethical consumer data collection.
Navigating this compliance landscape can be challenging for businesses serving European and Californian markets.
This guide explores the key differences between CCPA and GDPR, their impact on data analytics, and how to ensure your business meets these essential privacy requirements.
What is the California Consumer Privacy Act (CCPA) ?
The California Consumer Privacy Act (CCPA) is a data privacy law that gives California consumers control over their personal information. It applies to for-profit businesses operating in California that meet specific criteria related to revenue, data collection and sales.
Origins and purpose
The CCPA addresses growing concerns about data privacy and how businesses use personal information in California. The act passed in 2018 and went into effect on 1 January 2020.
Key features
- Grants consumers the right to know what personal information is collected
- Provides the right to delete personal information
- Allows consumers to opt out of the sale of their personal information
- Prohibits discrimination against consumers who exercise their CCPA rights
Key definitions under the CCPA framework
- Business : A for-profit entity doing business in California and meeting one or more of these conditions :
- Has annual gross revenues over $25 million ;
- Buys, receives, sells or shares 50,000 or more consumers’ personal information ; or
- Derives 50% or more of its annual revenues from selling consumers’ personal information
- Consumer : A natural person who is a California resident
- Personal Information : Information that could be linked to, related to or used to identify a consumer or household, such as online identifiers, IP addresses, email addresses, social security numbers, cookie identifiers and more
What is the General Data Protection Regulation (GDPR) ?
The General Data Protection Regulation (GDPR) is a data privacy and protection law passed by the European Union (EU). It’s one of the strongest and most influential data privacy laws worldwide and applies to all organisations that process the personal data of individuals in the EU.
Origins and purpose
The GDPR was passed in 2016 and went into effect on 25 May 2018. It aims to harmonise data privacy laws in Europe and give people in the European Economic Area (EEA) privacy rights and control over their data.
Key features
- Applies to all organisations that process the personal data of individuals in the EEA
- Grants individuals a wide range of privacy rights over their data
- Requires organisations to obtain explicit and informed consent for most data processing
- Mandates appropriate security measures to protect personal data
- Imposes significant fines and penalties for non-compliance
Key definitions under the GDPR framework
- Data Subject : An identified or identifiable person
- Personal Data : Any information relating to a data subject
- Data Controller : The entity or organisation that determines how personal data is processed and what for
- Data Processor : The entity or organisation that processes the data on behalf of the controller
CCPA vs. GDPR : Key similarities
The CCPA and GDPR enhance consumer privacy rights and give individuals greater control over their data.
Dimension CCPA GDPR Purpose Protect consumer privacy Protect individual data rights Key Rights Right to access, delete and opt out of sale Right to access, rectify, erase and restrict processing Transparency Requires transparency around data collection and use Requires transparency about data collection, processing and use CCPA vs. GDPR : Key differences
While they have similar purposes, the CCPA and GDPR differ significantly in their scope, approach and specific requirements.
Dimension CCPA GDPR Scope For-profit businesses only All organisations processing EU consumer data Territorial Reach California-based natural persons All data subjects within the EEA Consent Opt-out system Opt-in system Penalties Per violation based on its intentional or negligent nature Case-by-case based on comprehensive assessment Individual Rights Narrower (relative to GDPR) Broader (relative to CCPA) CCPA vs. GDPR : A multi-dimensional comparison
The previous sections gave a broad overview of the similarities and differences between CCPA and GDPR. Let’s now examine nine key dimensions where these regulations converge or diverge and discuss their impact on data analytics.
#1. Scope and territorial reach
The GDPR has a much broader scope than the CCPA. It applies to all organisations that process the personal data of individuals in the EEA, regardless of their business model, purpose or physical location.
The CCPA applies to medium and large for-profit businesses that derive a substantial portion of their earnings from selling Californian consumers’ personal information. It doesn’t apply to non-profits, government agencies or smaller for-profit companies.
Impact on data analytics
The difference in scope significantly impacts data analytics practices. Smaller businesses may not need to comply with either regulation, some may only need to follow the CCPA, while most global businesses must comply with both. This often requires different methods for collecting and processing data in California, Europe, and elsewhere.
#2. Penalties and fines for non-compliance
Both the CCPA and GDPR impose penalties for non-compliance, but the severity of fines differs significantly :
CCPA Maximum penalty $2,500 per unintentional violation
$7,500 per intentional violation“Per violation” means per violation per impacted consumer. For example, three intentional CCPA violations affecting 1,000 consumers would result in 3,000 total violations and a $22.5 million maximum penalty (3,000 × $7,500).
The largest CCPA fine to date was Zoom’s $85 million settlement in 2021.
In contrast, the GDPR has resulted in 2,248 fines totalling almost €6.6 billion since 2018 — €2.4 billion of which were for non-compliance.
GDPR Maximum penalty €20 million or
4% of all revenue earned the previous yearSo far, the biggest fine imposed under the GDPR was Meta’s €1.2 billion fine in May 2023 — 15 times more than Zoom had to pay California.
Impact on data analytics
The significant difference in potential fines demonstrates the importance of regulatory compliance for data analytics professionals. Non-compliance can have severe financial consequences, directly affecting budget allocation and business operations.
Businesses must ensure their data collection, storage and processing practices comply with regulations in both Europe and California.
Choosing privacy-first, compliance-ready analytics platforms like Matomo is instrumental for mitigating non-compliance risks.
#3. Data subject rights and consumer rights
The CCPA and GDPR give people similar rights over their data, but their limitations and details differ.
Rights common to the CCPA and GDPR
- Right to Access/Know : People can access their personal information and learn what data is collected, its source, its purpose and how it’s shared
- Right to Delete/Erasure : People can request the deletion of their personal information, with some exceptions
- Right to Non-Discrimination : Businesses can’t discriminate against people who exercise their privacy rights
Consumer rights unique to the CCPA
- Right to Opt Out of Sale : Consumers can prohibit the sale of their personal information
- Right to Notice : Businesses must inform consumers about data collection practices
- Right to Disclosure : Consumers can request specific information collected about them
Data subject rights unique to the GDPR
- Right to be Informed : Broader transparency requirements encompass data retention, automated decision-making and international transfers
- Right to Rectification : Data subjects may request the correction of inaccurate data
- Right to Restrict Processing : Consumers may limit data use in certain situations
- Right to Data Portability : Businesses must provide individual consumer data in a secure, portable format when requested
- Right to Withdraw Consent : Consumers may withdraw previously granted consent to data processing
CCPA GDPR Right to Access or Know ✓ ✓ Right to Delete or Erase ✓ ✓ Right to Non-Discrimination ✓ ✓ Right to Opt-Out ✓ Right to Notice ✓ Right to Disclosure ✓ Right to be Informed ✓ Right to Rectification ✓ Right to Restrict Processing ✓ Right to Data Portability ✓ Right to Withdraw Consent ✓ Impact on data analytics
Data analysts must understand these rights and ensure compliance with both regulations, which could potentially require separate data handling processes for EU and California consumers.
#4. Opt-out vs. opt-in
The CCPA generally follows an opt-out model, while the GDPR requires explicit consent from individuals before processing their data.
Impact on data analytics
For CCPA compliance, businesses can collect data by default if they provide opt-out mechanisms. Failing to process opt-out requests can result in severe penalties, like Sephora’s $1.2 million fine.
Under GDPR, organisations must obtain explicit consent before collecting any data, which can limit the amount of data available for analysis.
#5. Parental consent
The CCPA and GDPR have provisions regarding parental consent for processing children’s data. The CCPA requires parental consent for children under 13, while the GDPR sets the age at 16, though member states can lower it to 13.
Impact on data analytics
This requirement significantly impacts businesses targeting younger audiences. In Europe and the US, companies must implement different methods to verify users’ ages and obtain parental consent when necessary.
The California Attorney General’s Office recently fined Tilting Point Media LLC $500,000 for sharing children’s data without parental consent.
#6. Data security requirements
Both regulations require businesses to implement adequate security measures to protect personal data. However, the GDPR has more prescriptive requirements, outlining specific security measures and emphasising a risk-based approach.
Impact on data analytics
Data analytics professionals must ensure that data is processed and stored securely to avoid breaches and potential fines.
#7. International data transfers
Both the CCPA and GDPR address international data transfers. Under the CCPA, businesses must only inform consumers about international transfers. The GDPR has stricter requirements, including ensuring adequate data protection safeguards for transfers outside the EEA.
Other rules, like the Payment Services Directive 2 (PSD2), also affect international data transfers, especially in the financial industry.
PSD2 requires strong customer authentication and secure communication channels for payment services. This adds complexity to cross-border data flows.
Impact on data analytics
The primary impact is on businesses serving European residents from outside Europe. Processing data within the European Union is typically advisable. Meta’s record-breaking €1.2 billion fine was specifically for transferring data from the EEA to the US without sufficient safeguards.
Choosing the right analytics platform helps avoid these issues.
For example, Matomo offers a free, open-source, self-hosted analytics platform you can deploy anywhere. You can also choose a managed, GDPR-compliant cloud analytics solution with all data storage and processing servers within the EU (in Germany), ensuring your data never leaves the EEA.
#8. Enforcement mechanisms
The California Attorney General is responsible for enforcing CCPA requirements, while in Europe, the Data Protection Authority (DPA) in each EU member state enforces GDPR requirements.
Impact on data analytics
Data analytics professionals should be familiar with their respective enforcement bodies and their powers to support compliance efforts and minimise the risk of fines and penalties.
#9. Legal basis for personal data processing
The GDPR outlines six legal grounds for processing personal data :
- Consent
- Contract
- Legal obligation
- Vital interests
- Public task
- Legitimate interests
The CCPA doesn’t explicitly define lawful bases but focuses on consumer rights and transparency in general.
Impact on data analytics
Businesses subject to the GDPR must identify and document a valid lawful basis for each processing activity.
Compliance rules under CCPA and GDPR
Complying with the CCPA and GDPR requires a comprehensive approach to data privacy. Here’s a summary of the essential compliance rules for each framework :
CCPA compliance rules
- Create clear and concise privacy policies outlining data collection and use practices
- Give consumers the right to opt-out
- Respond to consumer requests to access, delete and correct their personal information
- Implement reasonable security measures for consumers’ personal data protection
- Never discriminate against consumers who exercise their CCPA rights
GDPR compliance rules
- Obtain explicit and informed consent for data processing activities
- Implement technical and organisational controls to safeguard personal data
- Designate a Data Protection Officer (DPO) if necessary
- Perform data protection impact assessments (DPIAs) for high-risk processing activities
- Maintain records of processing activities
- Promptly report data breaches to supervisory authorities
Navigating the CCPA and GDPR with confidence
Understanding the nuances of the CCPA and GDPR is crucial for businesses operating in the US and Europe. These regulations significantly impact data collection and analytics practices.
Implementing robust data security practices and prioritising privacy and compliance are essential to avoid severe penalties and build trust with today’s privacy-conscious consumers.
Privacy-centric analytics platforms like Matomo enable businesses to collect, analyse and use data responsibly and transparently, extracting valuable insights while maintaining compliance with both CCPA and GDPR requirements.
no credit card required
-
ffmpeg produces duplicate pts with "wallclock_as_timestamps 1" option on MKV
15 avril 2024, par Jax2171I need to get real time reference of every keyframe captured by an IP camera. The
-wallclock_as_timestamps 1option seems to do the trick for us, however we are forced to replace the TS output container with MKV to get a correct PTS epoch value1712996356.833000.

Here is the ffmpeg command used :


ffmpeg -report -use_wallclock_as_timestamps 1 -rtsp_transport tcp -i rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0 -c:v copy -c:a aac -copyts -f matroska -y rec.mkv


The capture process runs without any relevant worning or error messages.


However, playing the captured video with any player shows very short and evident but very annoying lags. Upon investigation I discovered that many frame PTSs have the same value. The command I used to show duplicate PTSs is as follows :


ffprobe -v error -show_entries frame=pkt_pts_time -select_streams v -of csv=p=0 rec.mkv | sort | uniq -d


On a recording of about 10 minutes the result of the duplicate PTS is the following :


1713086493.367000
1713086493.368000
1713086493.370000
1713086493.372000
1713086543.714000
1713086558.793000
1713086558.817000
1713086558.872000
1713086561.780000
1713086564.642000
1713086564.657000
1713086564.778000
1713086565.794000
...


I'm not sure if the lag problem is caused by this, however the problem does not occur with the TS container, which however I cannot use due to the PTS values being roundly 33 bit.


The
-vsync 0or-vsync 2options on input or output didn't help.

This is the log using the
-reportoption :

ffmpeg started on 2024-04-15 at 09:04:38
Report written to "ffmpeg-20240415-090438.log"
Log level: 48
Command line:
ffmpeg -report -stats -hide_banner -use_wallclock_as_timestamps 1 -rtsp_transport tcp -i "rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0" -c:v copy -c:a aac -copyts -f matroska -y rec.mkv
Splitting the commandline.
Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'.
Reading option '-stats' ... matched as option 'stats' (print progress report during encoding) with argument '1'.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-use_wallclock_as_timestamps' ... matched as AVOption 'use_wallclock_as_timestamps' with argument '1'.
Reading option '-rtsp_transport' ... matched as AVOption 'rtsp_transport' with argument 'tcp'.
Reading option '-i' ... matched as input url with argument 'rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0'.
Reading option '-c:v' ... matched as option 'c' (codec name) with argument 'copy'.
Reading option '-c:a' ... matched as option 'c' (codec name) with argument 'aac'.
Reading option '-copyts' ... matched as option 'copyts' (copy timestamps) with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'matroska'.
Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'.
Reading option 'rec.mkv' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option report (generate a report) with argument 1.
Applying option stats (print progress report during encoding) with argument 1.
Applying option hide_banner (do not show program banner) with argument 1.
Applying option copyts (copy timestamps) with argument 1.
Applying option y (overwrite output files) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0.
Successfully parsed a group of options.
Opening an input file: rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0.
[tcp @ 0x1646660] No default whitelist set
[tcp @ 0x1646660] Original list of addresses:
[tcp @ 0x1646660] Address 192.168.5.21 port 554
[tcp @ 0x1646660] Interleaved list of addresses:
[tcp @ 0x1646660] Address 192.168.5.21 port 554
[tcp @ 0x1646660] Starting connection attempt to 192.168.5.21 port 554
[tcp @ 0x1646660] Successfully connected to 192.168.5.21 port 554
[rtsp @ 0x1645e70] SDP:
v=0
o=- 2251950012 2251950012 IN IP4 0.0.0.0
s=Media Server
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=packetization-supported:DH
a=rtppayload-supported:DH
a=range:npt=now-
a=x-packetization-supported:IV
a=x-rtppayload-supported:IV
m=video 0 RTP/AVP 96
a=control:trackID=0
a=framerate:25.000000
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D4028;sprop-parameter-sets=Z01AKKaAeAIn5ZuAgICgAAADACAAAAZQgAA=,aO48gAA=
a=recvonly
m=audio 0 RTP/AVP 97
a=control:trackID=1
a=rtpmap:97 MPEG4-GENERIC/16000
a=fmtp:97 streamtype=5;profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1408
a=recvonly

[rtsp @ 0x1645e70] video codec set to: h264
[rtsp @ 0x1645e70] RTP Packetization Mode: 1
[rtsp @ 0x1645e70] RTP Profile IDC: 4d Profile IOP: 40 Level: 28
[rtsp @ 0x1645e70] Extradata set to 0x164af98 (size: 39)
[rtsp @ 0x1645e70] audio codec set to: aac
[rtsp @ 0x1645e70] audio samplerate set to: 16000
[rtsp @ 0x1645e70] audio channels set to: 1
[rtsp @ 0x1645e70] setting jitter buffer size to 0
[rtsp @ 0x1645e70] setting jitter buffer size to 0
[rtsp @ 0x1645e70] hello state=0
Failed to parse interval end specification ''
[h264 @ 0x164ab30] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 5(IDR), nal_ref_idc: 3
[h264 @ 0x164ab30] Format yuvj420p chosen by get_format().
[h264 @ 0x164ab30] Reinit context to 1920x1088, pix_fmt: yuvj420p
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[h264 @ 0x164ab30] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3
[rtsp @ 0x1645e70] All info found
Input #0, rtsp, from 'rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0':
 Metadata:
 title : Media Server
 Duration: N/A, start: 1713164678.794625, bitrate: N/A
 Stream #0:0, 22, 1/90000: Video: h264 (Main), yuvj420p(pc, bt709, progressive), 1920x1080, 25 fps, 25 tbr, 90k tbn, 50 tbc
 Stream #0:1, 15, 1/16000: Audio: aac (LC), 16000 Hz, mono, fltp
Successfully opened the file.
Parsing a group of options: output url rec.mkv.
Applying option c:v (codec name) with argument copy.
Applying option c:a (codec name) with argument aac.
Applying option f (force format) with argument matroska.
Successfully parsed a group of options.
Opening an output file: rec.mkv.
[file @ 0x1699f30] Setting default whitelist 'file,crypto,data'
Successfully opened the file.
Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
cur_dts is invalid st:0 (0) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (0) [init:0 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
detected 4 logical cores
[graph_0_in_0_1 @ 0x1682bb0] Setting 'time_base' to value '1/16000'
[graph_0_in_0_1 @ 0x1682bb0] Setting 'sample_rate' to value '16000'
[graph_0_in_0_1 @ 0x1682bb0] Setting 'sample_fmt' to value 'fltp'
[graph_0_in_0_1 @ 0x1682bb0] Setting 'channel_layout' to value '0x4'
[graph_0_in_0_1 @ 0x1682bb0] tb:1/16000 samplefmt:fltp samplerate:16000 chlayout:0x4
[format_out_0_1 @ 0x187f2e0] Setting 'sample_fmts' to value 'fltp'
[format_out_0_1 @ 0x187f2e0] Setting 'sample_rates' to value '96000|88200|64000|48000|44100|32000|24000|22050|16000|12000|11025|8000|7350'
[AVFilterGraph @ 0x164fd70] query_formats: 4 queried, 9 merged, 0 already done, 0 delayed
[matroska @ 0x169c330] get_metadata_duration returned: 0
Output #0, matroska, to 'rec.mkv':
 Metadata:
 title : Media Server
 encoder : Lavf58.45.100
 Stream #0:0, 0, 1/1000: Video: h264 (Main) (H264 / 0x34363248), yuvj420p(pc, bt709, progressive), 1920x1080, q=2-31, 25 fps, 25 tbr, 1k tbn, 90k tbc
 Stream #0:1, 0, 1/1000: Audio: aac (LC) ([255][0][0][0] / 0x00FF), 16000 Hz, mono, fltp, 69 kb/s
 Metadata:
 encoder : Lavc58.91.100 aac
cur_dts is invalid st:0 (0) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (0) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:0 (0) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
[matroska @ 0x169c330] Starting new cluster with timestamp 1713164678731 at offset 770 bytes
[matroska @ 0x169c330] Writing block of size 581 with pts 1713164678731, dts 1713164678731, duration 64 at relative offset 14 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 517 with pts 1713164678795, dts 1713164678795, duration 64 at relative offset 602 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 376900 with pts 1713164678872, dts 1713164678872, duration 40 at relative offset 1126 in cluster at offset 770. TrackNumber 1, keyframe 1
[matroska @ 0x169c330] Writing block of size 8172 with pts 1713164678912, dts 1713164678912, duration 40 at relative offset 378034 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 672 with pts 1713164678912, dts 1713164678912, duration 64 at relative offset 386213 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 550 with pts 1713164679177, dts 1713164679177, duration 64 at relative offset 386892 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7654 with pts 1713164679178, dts 1713164679178, duration 40 at relative offset 387449 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7483 with pts 1713164679213, dts 1713164679213, duration 40 at relative offset 395110 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7703 with pts 1713164679242, dts 1713164679242, duration 40 at relative offset 402600 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 565 with pts 1713164679242, dts 1713164679242, duration 64 at relative offset 410310 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7650 with pts 1713164679271, dts 1713164679271, duration 40 at relative offset 410882 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 585 with pts 1713164679271, dts 1713164679271, duration 64 at relative offset 418539 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 8682 with pts 1713164679301, dts 1713164679301, duration 40 at relative offset 419131 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 8888 with pts 1713164679330, dts 1713164679330, duration 40 at relative offset 427820 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 506 with pts 1713164679330, dts 1713164679330, duration 64 at relative offset 436715 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 8019 with pts 1713164679360, dts 1713164679360, duration 40 at relative offset 437228 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7919 with pts 1713164679361, dts 1713164679361, duration 40 at relative offset 445254 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7822 with pts 1713164679361, dts 1713164679361, duration 40 at relative offset 453180 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 699 with pts 1713164679361, dts 1713164679361, duration 64 at relative offset 461009 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 619 with pts 1713164679361, dts 1713164679361, duration 64 at relative offset 461715 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7768 with pts 1713164679362, dts 1713164679362, duration 40 at relative offset 462341 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 8469 with pts 1713164679362, dts 1713164679362, duration 40 at relative offset 470116 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 601 with pts 1713164679362, dts 1713164679362, duration 64 at relative offset 478592 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 559 with pts 1713164679363, dts 1713164679363, duration 64 at relative offset 479200 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 8265 with pts 1713164679366, dts 1713164679366, duration 40 at relative offset 479766 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7766 with pts 1713164679406, dts 1713164679406, duration 40 at relative offset 488038 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 531 with pts 1713164679415, dts 1713164679415, duration 64 at relative offset 495811 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7753 with pts 1713164679446, dts 1713164679446, duration 40 at relative offset 496349 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 8274 with pts 1713164679486, dts 1713164679486, duration 40 at relative offset 504109 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 569 with pts 1713164679496, dts 1713164679496, duration 64 at relative offset 512390 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 8445 with pts 1713164679526, dts 1713164679526, duration 40 at relative offset 512966 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 522 with pts 1713164679535, dts 1713164679535, duration 64 at relative offset 521418 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7922 with pts 1713164679566, dts 1713164679566, duration 40 at relative offset 521947 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7954 with pts 1713164679606, dts 1713164679606, duration 40 at relative offset 529876 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 503 with pts 1713164679615, dts 1713164679615, duration 64 at relative offset 537837 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 11167 with pts 1713164679646, dts 1713164679646, duration 40 at relative offset 538347 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 503 with pts 1713164679655, dts 1713164679655, duration 64 at relative offset 549521 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 10534 with pts 1713164679686, dts 1713164679686, duration 40 at relative offset 550031 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7607 with pts 1713164679726, dts 1713164679726, duration 40 at relative offset 560572 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 478 with pts 1713164679772, dts 1713164679772, duration 64 at relative offset 568186 in cluster at offset 770. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7842 with pts 1713164679774, dts 1713164679774, duration 40 at relative offset 568671 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 9862 with pts 1713164679806, dts 1713164679806, duration 40 at relative offset 576520 in cluster at offset 770. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Starting new cluster with timestamp 1713164679815 at offset 587166 bytes
[matroska @ 0x169c330] Writing block of size 449 with pts 1713164679815, dts 1713164679815, duration 64 at relative offset 14 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 379456 with pts 1713164679870, dts 1713164679870, duration 40 at relative offset 470 in cluster at offset 587166. TrackNumber 1, keyframe 1
[matroska @ 0x169c330] Writing block of size 415 with pts 1713164679903, dts 1713164679903, duration 64 at relative offset 379934 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7008 with pts 1713164679905, dts 1713164679905, duration 40 at relative offset 380356 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6917 with pts 1713164679925, dts 1713164679925, duration 40 at relative offset 387371 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 513 with pts 1713164679935, dts 1713164679935, duration 64 at relative offset 394295 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7111 with pts 1713164679966, dts 1713164679966, duration 40 at relative offset 394815 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 753 with pts 1713164679975, dts 1713164679975, duration 64 at relative offset 401933 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7091 with pts 1713164680006, dts 1713164680006, duration 40 at relative offset 402693 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7045 with pts 1713164680045, dts 1713164680045, duration 40 at relative offset 409791 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 659 with pts 1713164680055, dts 1713164680055, duration 64 at relative offset 416843 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6983 with pts 1713164680086, dts 1713164680086, duration 40 at relative offset 417509 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6932 with pts 1713164680127, dts 1713164680127, duration 40 at relative offset 424499 in cluster at offset 587166. TrackNumber 1, keyframe 0
frame= 35 fps=0.0 q=-1.0 size= 512kB time=475879:04:40.20 bitrate= 0.0kbits/s speed=3.35e+09x 
[matroska @ 0x169c330] Writing block of size 691 with pts 1713164680135, dts 1713164680135, duration 64 at relative offset 431438 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6990 with pts 1713164680166, dts 1713164680166, duration 40 at relative offset 432136 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 651 with pts 1713164680176, dts 1713164680176, duration 64 at relative offset 439133 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7046 with pts 1713164680206, dts 1713164680206, duration 40 at relative offset 439791 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 7130 with pts 1713164680246, dts 1713164680246, duration 40 at relative offset 446844 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 601 with pts 1713164680255, dts 1713164680255, duration 64 at relative offset 453981 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 7205 with pts 1713164680286, dts 1713164680286, duration 40 at relative offset 454589 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 561 with pts 1713164680295, dts 1713164680295, duration 64 at relative offset 461801 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6936 with pts 1713164680326, dts 1713164680326, duration 40 at relative offset 462369 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6822 with pts 1713164680366, dts 1713164680366, duration 40 at relative offset 469312 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 621 with pts 1713164680375, dts 1713164680375, duration 64 at relative offset 476141 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6845 with pts 1713164680405, dts 1713164680405, duration 40 at relative offset 476769 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6848 with pts 1713164680445, dts 1713164680445, duration 40 at relative offset 483621 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 588 with pts 1713164680455, dts 1713164680455, duration 64 at relative offset 490476 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6828 with pts 1713164680486, dts 1713164680486, duration 40 at relative offset 491071 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 546 with pts 1713164680495, dts 1713164680495, duration 64 at relative offset 497906 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6845 with pts 1713164680526, dts 1713164680526, duration 40 at relative offset 498459 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6924 with pts 1713164680566, dts 1713164680566, duration 40 at relative offset 505311 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 508 with pts 1713164680576, dts 1713164680576, duration 64 at relative offset 512242 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6844 with pts 1713164680606, dts 1713164680606, duration 40 at relative offset 512757 in cluster at offset 587166. TrackNumber 1, keyframe 0
frame= 48 fps= 47 q=-1.0 size= 512kB time=475879:04:40.72 bitrate= 0.0kbits/s speed=1.66e+09x 
[matroska @ 0x169c330] Writing block of size 587 with pts 1713164680615, dts 1713164680615, duration 64 at relative offset 519608 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6859 with pts 1713164680645, dts 1713164680645, duration 40 at relative offset 520202 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 6855 with pts 1713164680686, dts 1713164680686, duration 40 at relative offset 527068 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 573 with pts 1713164680695, dts 1713164680695, duration 64 at relative offset 533930 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6881 with pts 1713164680726, dts 1713164680726, duration 40 at relative offset 534510 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 10773 with pts 1713164680766, dts 1713164680766, duration 40 at relative offset 541398 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 520 with pts 1713164680775, dts 1713164680775, duration 64 at relative offset 552178 in cluster at offset 587166. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6923 with pts 1713164680805, dts 1713164680805, duration 40 at relative offset 552705 in cluster at offset 587166. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Starting new cluster with timestamp 1713164680815 at offset 1146808 bytes
[matroska @ 0x169c330] Writing block of size 580 with pts 1713164680815, dts 1713164680815, duration 64 at relative offset 14 in cluster at offset 1146808. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 380085 with pts 1713164680864, dts 1713164680864, duration 40 at relative offset 601 in cluster at offset 1146808. TrackNumber 1, keyframe 1
[matroska @ 0x169c330] Writing block of size 9916 with pts 1713164680896, dts 1713164680896, duration 40 at relative offset 380694 in cluster at offset 1146808. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 541 with pts 1713164680901, dts 1713164680901, duration 64 at relative offset 390617 in cluster at offset 1146808. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 5877 with pts 1713164680925, dts 1713164680925, duration 40 at relative offset 391165 in cluster at offset 1146808. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] Writing block of size 529 with pts 1713164680935, dts 1713164680935, duration 64 at relative offset 397049 in cluster at offset 1146808. TrackNumber 2, keyframe 1
[matroska @ 0x169c330] Writing block of size 6661 with pts 1713164680966, dts 1713164680966, duration 40 at relative offset 397585 in cluster at offset 1146808. TrackNumber 1, keyframe 0
[matroska @ 0x169c330] end duration = 1713164681006
[matroska @ 0x169c330] stream 0 end duration = 1713164681006
[matroska @ 0x169c330] stream 1 end duration = 1713164680999
frame= 54 fps= 42 q=-1.0 Lsize= 1515kB time=475879:04:40.99 bitrate= 0.0kbits/s speed=1.33e+09x 
video:1493kB audio:20kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.099897%
Input file #0 (rtsp://user:password1@192.168.5.21/cam/realmonitor?channel=1channel1[1]=1subtype=0):
 Input stream #0:0 (video): 54 packets read (1529156 bytes); 
 Input stream #0:1 (audio): 35 packets read (9268 bytes); 35 frames decoded (35840 samples); 
 Total: 89 packets (1538424 bytes) demuxed
Output file #0 (rec.mkv):
 Output stream #0:0 (video): 54 packets muxed (1529156 bytes); 
 Output stream #0:1 (audio): 35 frames encoded (35840 samples); 36 packets muxed (20446 bytes); 
 Total: 90 packets (1549602 bytes) muxed
35 frames successfully decoded, 0 decoding errors
[AVIOContext @ 0x1667620] Statistics: 2 seeks, 7 writeouts
[aac @ 0x1673880] Qavg: 142.738
Exiting normally, received signal 15.


In this short 3 second capture the duplicate timestamps are
1713164679.361000and1713164679.362000.

How can I solve this problem ? What different approach could I use to achieve this goal ?


Thanks in advance.


Syndiquer tout le site
