
Recherche avancée
Autres articles (77)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (14099)
-
ffprobe : report field order for video streams
4 octobre 2016, par Rodger Combsffprobe : report field order for video streams
- [DH] doc/ffprobe.xsd
- [DH] ffprobe.c
- [DH] tests/ref/fate/concat-demuxer-extended-lavf-mxf
- [DH] tests/ref/fate/concat-demuxer-extended-lavf-mxf_d10
- [DH] tests/ref/fate/concat-demuxer-simple1-lavf-mxf
- [DH] tests/ref/fate/concat-demuxer-simple1-lavf-mxf_d10
- [DH] tests/ref/fate/concat-demuxer-simple2-lavf-ts
- [DH] tests/ref/fate/ffprobe_compact
- [DH] tests/ref/fate/ffprobe_csv
- [DH] tests/ref/fate/ffprobe_default
- [DH] tests/ref/fate/ffprobe_flat
- [DH] tests/ref/fate/ffprobe_ini
-
avformat/id3v2 : Don't reverse the order of id3v2 APICs
13 avril 2021, par Andreas Rheinhardtavformat/id3v2 : Don't reverse the order of id3v2 APICs
When parsing ID3v2 tags, special (non-text) metadata is not applied
directly and unconditionally ; instead it is stored in a linked list
in which elements are prepended. When traversing the list to add APICs
(or private tags) at the end, the order is reversed. The same also
happens for chapters and therefore the chapter parsing code already
reverses the chapters.This commit changes this : By keeping pointers to both head and tail
of the linked list one can preserve the order of the entries and
remove the reordering code for chapters. Only the pointer to head
will be exported : No current caller uses a nonempty list, so exporting
both head and tail is unnecessary. This removes the functionality
to combine the lists of special metadata read from different ID3v2 tags,
but that doesn't make really much sense anyway (and would be trivial
to implement if desired) and allows to remove the now unnecessary
initializations performed by the callers.The FATE-reference for the id3v2-priv test had to be updated
because the order of the tags read into the dict is reversed ;
for id3v2-priv-remux only the md5 and not the ffprobe output
of the remuxed file changes because the order of the private tags
has up until now been reversed twice.The references for the aiff/mp3 cover-art tests needed to be updated,
because the order of the attached pics is reversed upon reading.
It is still not correct, because the muxers write the pics in the order
in which they arrive at the muxer instead of the order given by
pkt->stream_index.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
- [DH] libavformat/aacdec.c
- [DH] libavformat/aiffdec.c
- [DH] libavformat/asf.c
- [DH] libavformat/dsfdec.c
- [DH] libavformat/id3v2.c
- [DH] libavformat/id3v2.h
- [DH] libavformat/iff.c
- [DH] libavformat/omadec.c
- [DH] libavformat/wavdec.c
- [DH] tests/ref/fate/cover-art-aiff-id3v2-remux
- [DH] tests/ref/fate/cover-art-mp3-id3v2-remux
- [DH] tests/ref/fate/id3v2-priv
- [DH] tests/ref/fate/id3v2-priv-remux
-
How to install pytorch and opencv using a fixed conda channel order ?
7 juin, par progquesterConda creates a pristine environment, configures a fixed channel order, and then starts installing pytorch torchvisioni pytorch-cuda and opencv, and it prompts for dependency conflicts. Do I have to install opencv via pip ?


The same thing happens with python 3.10


$ conda create -n my_env3.9 python=3.9
$ conda activate my_env3.9
$ conda install pytorch torchvision pytorch-cuda=11.8 opencv
Channels:
 - pytorch
 - nvidia
 - conda-forge
 - defaults
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: failed

LibMambaUnsatisfiableError: Encountered problems while solving:
 - nothing provides libopencv 4.2.0 py36_5 needed by opencv-4.2.0-py36_5

Could not solve for environment specs
The following packages are incompatible
├─ opencv =* * is installable with the potential options
│ ├─ opencv [4.10.0|4.11.0] would require
│ │ └─ libopencv [==4.10.0 headless_py310h05fcec3_10|==4.10.0 headless_py310h2251c23_11|...|==4.11.0 qt6_py39hd96f159_602], which requires
│ │ └─ ffmpeg >=7.1.0,<8.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [4.10.0|4.9.0] would require
│ │ └─ libopencv [==4.10.0 headless_py310h3d4b477_1|==4.10.0 headless_py310hef7d0a5_0|...|==4.9.0 qt6_py39hed63795_614], which requires
│ │ └─ ffmpeg >=6.1.1,<7.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.10.0 would require
│ │ └─ libopencv [==4.10.0 headless_py310h8d94708_2|==4.10.0 headless_py38h5642e36_2|...|==4.10.0 qt6_py39hfd9fb6d_602], which requires
│ │ └─ ffmpeg >=7.0.1,<8.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.10.0 would require
│ │ └─ libopencv [==4.10.0 headless_py310h5bfabb9_4|==4.10.0 headless_py310h5bfabb9_5|...|==4.10.0 qt6_py39hdeb11db_605], which requires
│ │ └─ ffmpeg >=6.1.2,<7.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.10.0 would require
│ │ └─ libopencv [==4.10.0 headless_py311h63eac36_5|==4.10.0 headless_py311h63eac36_6|...|==4.10.0 qt6_py39h5d2977a_603], which requires
│ │ └─ ffmpeg >=7.0.2,<8.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.11.0 would require
│ │ └─ libopencv [==4.11.0 headless_py310h8ace835_4|==4.11.0 headless_py310h8ace835_5|...|==4.11.0 qt6_py39hbfaaa73_603], which requires
│ │ └─ ffmpeg >=7.1.1,<8.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [4.5.3|4.5.5|4.6.0] would require
│ │ └─ libopencv [==4.5.3 py310hc72b5f5_8|==4.5.3 py38hc6b509d_8|...|==4.6.0 py39hf4bb9d8_2], which requires
│ │ └─ ffmpeg >=4.4.2,<5.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [4.6.0|4.7.0] would require
│ │ └─ libopencv [==4.6.0 py310h5bd1119_9|==4.6.0 py310h6214075_5|...|==4.7.0 py39hf99ad11_5], which requires
│ │ └─ ffmpeg >=5.1.2,<6.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [4.7.0|4.8.0|4.8.1] would require
│ │ └─ libopencv [==4.7.0 py310h245f934_4|==4.7.0 py310h3e876cf_5|...|==4.8.1 py39hf605482_5], which requires
│ │ └─ ffmpeg >=6.0.0,<7.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.9.0 would require
│ │ └─ libopencv [==4.9.0 headless_py310hae237af_14|==4.9.0 headless_py38h0f7b093_14|...|==4.9.0 qt6_py39h067c833_615], which requires
│ │ └─ ffmpeg >=7.0.0,<8.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [2.4.12|2.4.13|3.1.0|3.2.0] would require
│ │ └─ python =2.7 *, which can be installed;
│ ├─ opencv [2.4.13.4|3.2.0|3.3.0|3.4.1] would require
│ │ └─ ffmpeg >=3.2.3,<3.2.6 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 3.1.0 would require
│ │ └─ python =3.4 *, which can be installed;
│ ├─ opencv [3.1.0|3.2.0] would require
│ │ └─ python =3.5 *, which can be installed;
│ ├─ opencv [3.1.0|3.2.0] would require
│ │ └─ python =3.6 *, which can be installed;
│ ├─ opencv [3.4.1|3.4.3|3.4.4|3.4.7] would require
│ │ ├─ ffmpeg >=4.0.2,<4.1.0a0 *, which conflicts with any installable versions previously reported;
│ │ └─ libopencv ==3.4.7 hc173e35_5, which requires
│ │ └─ ffmpeg >=4.0.2,<4.1.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 3.4.1 would require
│ │ └─ ffmpeg >=4.0.1,<4.1.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [3.4.4|3.4.7|...|4.1.1] would require
│ │ ├─ ffmpeg =4.1 *, which conflicts with any installable versions previously reported;
│ │ └─ libopencv [==3.4.7 h0cc45ee_4|==4.1.1 h0cc45ee_3], which requires
│ │ └─ ffmpeg =4.1 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [3.4.7|3.4.8|...|4.2.0] would require
│ │ └─ libopencv [==3.4.7 h32d60f7_6|==3.4.7 py27_7|...|==4.2.0 py38_4], which requires
│ │ └─ ffmpeg >=4.1.3,<4.2.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.2.0 would require
│ │ └─ libopencv ==4.2.0 py36_5, which does not exist (perhaps a missing channel);
│ ├─ opencv [4.2.0|4.3.0|4.4.0] would require
│ │ └─ py-opencv [==4.2.0 py36h0b673f9_6|==4.3.0 py36h0b673f9_2|==4.4.0 py36h0b673f9_2], which requires
│ │ └─ python >=3.6,<3.7.0a0 *, which can be installed;
│ ├─ opencv [4.2.0|4.3.0] would require
│ │ └─ libopencv [==4.2.0 py36_7|==4.2.0 py37_7|...|==4.3.0 py38_1], which requires
│ │ └─ ffmpeg >=4.2.3,<4.3.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv [4.2.0|4.3.0|4.4.0] would require
│ │ └─ py-opencv [==4.2.0 py37h43977f1_5|==4.2.0 py37h43977f1_6|==4.3.0 py37h43977f1_2|==4.4.0 py37h43977f1_2], which requires
│ │ └─ python >=3.7,<3.8.0a0 *, which can be installed;
│ ├─ opencv [4.2.0|4.3.0|4.4.0] would require
│ │ └─ py-opencv [==4.2.0 py38h23f93f0_5|==4.2.0 py38h23f93f0_6|==4.3.0 py38h23f93f0_2|==4.4.0 py38h23f93f0_2], which requires
│ │ └─ python >=3.8,<3.9.0a0 *, which can be installed;
│ ├─ opencv [4.4.0|4.5.0|4.5.1|4.5.2] would require
│ │ └─ libopencv [==4.4.0 py36_3|==4.4.0 py37_3|...|==4.5.2 py39h70bf20d_1], which requires
│ │ └─ ffmpeg >=4.3.1,<4.4.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.5.0 would require
│ │ └─ libopencv ==4.5.0 py36_5, which does not exist (perhaps a missing channel);
│ ├─ opencv 4.5.0 would require
│ │ └─ libopencv ==4.5.0 py36_6, which does not exist (perhaps a missing channel);
│ ├─ opencv [4.5.3|4.5.5] would require
│ │ └─ libopencv [==4.5.3 py31hbd5a65a_6|==4.5.3 py31he7a5e20_7|...|==4.5.5 py39hfb30bf4_6], which requires
│ │ └─ ffmpeg >=4.3.2,<4.4.0a0 *, which conflicts with any installable versions previously reported;
│ ├─ opencv 4.5.5 would require
│ │ └─ libopencv [==4.5.5 py310h1897127_9|==4.5.5 py310hc83fb77_10|...|==4.5.5 py39he64e9e9_10], which requires
│ │ └─ ffmpeg >=4.4.1,<5.0a0 *, which conflicts with any installable versions previously reported;
│ └─ opencv [3.3.1|3.4.1|...|4.6.0] conflicts with any installable versions previously reported;
└─ pin on python 3.9.* =* * is not installable because it requires
 └─ python =3.9 *, which conflicts with any installable versions previously reported.

Pins seem to be involved in the conflict. Currently pinned specs:
 - python=3.9