Recherche avancée

Sur d’autres sites (6089)

• Podcast Producer 2 REST api

  11 septembre 2009

  I’ve been working on documenting the REST api that PCP2 uses for client server communication as part of a new project. I thought it might be useful to other folks. Consider this a work in progress - I’ve only documented the workflow for doing a multisource recording so far. Follow the job for the info.

  Each section gives a sample command and a sample response.

  All pages are behind basic HTTP auth.

  General sequence of events

  * get workflow list
  * get cameras
  * request status for camera (including thumbnail)
  * start cameras
  * create recording enclosure
  * stop cameras, provide submission_UUID returned by above step, include title

  ---

  *URL : https://pcpserver:8170/podcastproducer/info

  *Type : GET

  *Content : version=2

  *Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <plist version="1.0">
  <dict>
  <key>server_version</key>
  <string>2.0</string>
  <key>http_auth_type</key>
  <array>
  <string>basic</string>
  <string>digest</string>
  <string>kerberos</string>
  </array>
  <key>krb_service_principals</key>
  <array>
  <string>pcast/x101-186-103-dhcp.cla.umn.edu@X101-186-103-DHCP.CLA.UMN.EDU</string>
  </array>
  <key>server_uuid</key>
  <string>DB31DA49-10AE-472C-B3B9-86A8F8112399</string>
  <key>cluster_members</key>
  <dict>
  <key>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</key>
  <dict>
  <key>date_added</key>
  <string>Tue Sep 01 10:23:49 -0500 2009</string>
  <key>last_update</key>
  <string>Tue Sep 08 10:35:17 -0500 2009</string>
  <key>server_host</key>
  <string>x101-186-103-dhcp.cla.umn.edu</string>
  <key>server_port</key>
  <string>8170</string>
  <key>tunnel_agent_host</key>
  <string>x101-186-103-dhcp.cla.umn.edu</string>
  <key>tunnel_agent_port</key>
  <string>8175</string>
  <key>network_addrs</key>
  <array>
  <string>128.101.186.103</string>
  </array>
  </dict>
  </dict>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/workflows
  * Type : GET
  * Content : version=2&language=en
  * Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>user_fullname</key>
  <string>podcast</string>
  <key>user_shortname</key>
  <string>podcast</string>
  <key>workflows</key>
  <array>
  <dict>
  <key>name</key>
  <string>Montage</string>
  <key>title</key>
  <string>Montage</string>
  <key>description</key>
  <string>Montage workflow</string>
  <key>uuid</key>
  <string>F797D54D-1539-42AA-B6AC-3CB3A4C15EF5</string>
  <key>version</key>
  <string>2.0</string>
  <key>editor</key>
  <string>Podcast Composer</string>
  <key>sources</key>
  <array>
  <dict>
  <key>contentTypes</key>
  <array>
  <string>com.apple.quicktime-movie</string>
  <string>com.adobe.pdf</string>
  <string>com.apple.iwork.keynote.key</string>
  <string>com.apple.iwork.pages.pages</string>
  <string>org.openxmlformats.wordprocessingml.document</string>
  <string>com.microsoft.word.doc</string>
  <string>org.openxmlformats.presentationml.presentation</string>
  <string>com.microsoft.powerpoint.ppt</string>
  <string>com.microsoft.bmp</string>
  <string>com.compuserve.gif</string>
  <string>public.jpeg-2000</string>
  <string>public.jpeg</string>
  <string>com.adobe.pdf</string>
  <string>com.apple.pict</string>
  <string>public.png</string>
  <string>com.adobe.photoshop-image</string>
  <string>com.sgi.sgi-image</string>
  <string>com.truevision.tga-image</string>
  <string>public.tiff</string>
  </array>
  <key>description</key>
  <string>Any Document</string>
  <key>isFolder</key>
  <true/>
  <key>isOptional</key>
  <false/>
  <key>sourceTypes</key>
  <array>
  <string>File</string>
  </array>
  </dict>
  </array>
  <key>user_requirements</key>
  <array>
  <string>Title</string>
  <string>Description</string>
  </array>
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  <dict>
  <key>name</key>
  <string>Single Source</string>
  <key>title</key>
  <string>Single Source</string>
  <key>description</key>
  <string>Single Source workflow</string>
  <key>uuid</key>
  <string>DEFA1587-A650-426E-92DA-01C5EB811705</string>
  <key>version</key>
  <string>2.0</string>
  <key>editor</key>
  <string>Podcast Composer</string>
  <key>sources</key>
  <array>
  <dict>
  <key>contentTypes</key>
  <array>
  <string>com.apple.quicktime-movie</string>
  </array>
  <key>description</key>
  <string>Any Video</string>
  <key>isFolder</key>
  <false/>
  <key>isOptional</key>
  <false/>
  <key>sourceTypes</key>
  <array>
  <string>Video</string>
  <string>Screen</string>
  <string>Audio</string>
  <string>File</string>
  </array>
  </dict>
  </array>
  <key>user_requirements</key>
  <array>
  <string>Title</string>
  <string>Description</string>
  </array>
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>
  ----

  * URL : https://pcpserver:8170/podcastproducer/cameras
  * Type : GET
  * Content : version=2
  * Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <plist version="1.0">
  <dict>
  <key>cameras</key>
  <array>
  <dict>
  <key>name</key>
  <string>150-A Camera</string>
  <key>uuid</key>
  <string>307682A5-B552-4AFA-B7E2-3811D772C9A1</string>
  <key>connected_to_member_uuid</key>
  <string>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</string>
  <key>in_use</key>
  <string>false</string>
  <key>recording_status</key>
  <string>online</string>
  <key>preview_url</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  <dict>
  <key>name</key>
  <string>150-A Epiphan</string>
  <key>uuid</key>
  <string>CE610AB0-CA50-49EB-8FFE-78E57CDCA550</string>
  <key>connected_to_member_uuid</key>
  <string>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</string>
  <key>in_use</key>
  <string>false</string>
  <key>recording_status</key>
  <string>online</string>
  <key>preview_url</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/CE610AB0-CA50-49EB-8FFE-78E57CDCA550.jpg</string> ;
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/start
  * Type : POST
  * Content : action=pause&version=2&camera_name=150-A%20Camera&controller=cameras
  * Response :
  <pre>
  <podcast_producer_result>
  <action>start</action>
  <status>success</status>
  <results>OK</results>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/status
  * Type : POST
  * Content : delay=0&action=start&version=2&camera_name=150-A%20Epiphan&controller=cameras
  * Response :
  <pre><podcast_producer_result>
  <action>status</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>preview</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>preview_image_data</key>
  <string>RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA</string>
  <key>recording_status</key>
  <string>online</string>
  <key>started_at</key>
  <string>Tue Sep 08 09:31:40 -0500 2009</string>
  <key>stopped_at</key>
  <string>Tue Sep 08 09:32:10 -0500 2009</string>
  <key>elapsed</key>
  <string>41</string>
  <key>last_error</key>
  <string>805306368</string>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/pause
  * Type : POST
  * Content : action=pause&version=2&camera_name=150-A%20Camera&controller=cameras
  * Response :
  <pre><podcast_producer_result>
  <action>status</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>preview</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>recording_status</key>
  <string>online</string>
  <key>started_at</key>
  <string>Tue Sep 08 09:31:40 -0500 2009</string>
  <key>stopped_at</key>
  <string>Tue Sep 08 09:32:10 -0500 2009</string>
  <key>elapsed</key>
  <string>41</string>
  <key>last_error</key>
  <string>805306368</string>
  </dict>
  </plist>
  </podcast_producer_result></pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/stop
  * Type : POST
  * Content : workflow_name=&UserMetadata_Description=&submission_uuid=7497E3AC-0A75-4C7C-8C66-26294C9274FE&action=stop&version=2&camera_name=150-A%20Epiphan&controller=cameras&UserMetadata_Title=Test123
  * Response :
  <pre><podcast_producer_result>
  <action>stop</action>
  <status>success</status>
  <results>OK</results>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/recordings/create
  * Type : POST
  * Content : version=2&workflow_uuid=C6EF52A7-04E3-477D-9F38-6B61F108D7B9
  * Response :
  <pre>
  <podcast_producer_result>
  <action>create</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>workflow_uuid</key>
  <string>C6EF52A7-04E3-477D-9F38-6B61F108D7B9</string>
  <key>recording_uuid</key>
  <string>FD5A1459-F7CE-41FA-8155-049DF774298B</string>
  <key>submission_uuids</key>
  <array>
  <string>A626D8E4-E439-4E57-9982-DB4BD035CB41</string>
  <string>CFBCCB74-A41F-42D3-BEAA-58165B1116C6</string>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

• Evolution #4749 (Nouveau) : [UX] Comportement des labels : quoi par défaut, quoi ponctuel ?

  27 avril 2021, par RastaPopoulos ♥

  Ce ticket sert à réfléchir et possiblement reconcevoir les choix par défaut pour les labels des formulaires.

  État des lieux¶

  On le sait, l’ergo c’est normalement beaucoup d’objectif : certains placements, certaines tailles, épaisseurs, etc fonctionnent mieux que d’autres, et ceci est prouvable par tests utilisateurs.

  Or cela fait des années que les tests par eye-tracking montrent que les formulaires sont
  1) lu plus rapidement
  2) avec une meilleure compréhension
  lorsque les labels sont au-dessus des champs.

  Ça ne veut pas dire qu’il faut totalement interdire autrement mais : ça veut clairement dire que ça devrait être le comportement par défaut. Et seulement ponctuellement, par choix explicite, pouvoir mettre les labels sur le côté.

  Par ailleurs les pros de l’ergo (sur base des mêmes tests) préconisent tou⋅tes : dans les rares cas où on met les labels sur le côté, ça devrait être calé à droite sur le champ, pour les mêmes raisons de compréhension.

  Les avantages des labels au-dessus :
  - prouvé que c’est bien mieux compris par tout le monde
  - lecture plus rapide
  - fonctionne de base sur tous les écrans, pas d’adaptation à faire
  - polyvalent et générique sur le contenu des labels : marche mieux quelque soit la longueur, et donc à prioriser dans un contexte multilingue
  => cela correspond bien au maximum de notre utilisation : un CMS multi-lingue, allant enfin vers le responsive, se souciant d’accessibilité.

  Le seul désavantage : allonge la hauteur des formulaires, mais ça n’a un impact surtout que pour les formulaires ayant vraiment vraiment beaucoup de champs, ce qui est rare !
  Quand un formulaire est extrêmement long, il y a même plusieurs méthodes qui peuvent être utilisées sans pour autant passer les labels sur le côté :
  1) placer certains champs sur le même ligne (prénom + nom, etc)
  2) découper le formulaire en plusieurs étapes.

  Proposition pour le futur¶

  - tous les labels doivent être au-dessus comme comportement par défaut
  - pour certains cas, une classe permet de mettre sur le côté : valable uniquement en grand écran, ça reste au-dessus en mobile first
  - si sur le côté : c’est mieux si aligné sur le champ (donc à droite en LTR)
  - ex de rare formulaire candidat : changement des dates

  Quelques sources¶

  Tests utilisateurs
  https://www.uxmatters.com/mt/archives/2006/07/label-placement-in-forms.php

  Placing a label above an input field works better in most cases
  Placing labels above input fields is preferable
  In most cases, when placing labels to the left of input fields, using left-aligned labels imposes a heavy cognitive workload on users
  if you choose to place them to the left of input fields, at least make them right aligned

  Chez le très connu cabinet d’ergo Nielsen Group
  https://www.nngroup.com/articles/form-design-white-space/

  We recommend placing field labels above the corresponding text fields [en gras chez eux !]
  it makes the form easier to scan, because users can see the text field in the same fixation as the label. Top placement also allows for longer field labels
  If the labels are too far to the left, it can be difficult to associate the correct label with its corresponding field

  Chez Adobe, ils préconisent de suivre les recommandations de la première source
  https://xd.adobe.com/ideas/principles/web-design/best-practices-form-design/

  Matteo Penzo’s 2006 article on label placement suggests that forms are completed faster if labels are on top of the fields. Top-aligned labels are good if you want users to scan the form as quickly as possible.
  The biggest advantage of top-aligned labels is that different-sized labels and localized versions can more easily fit the UI.
  Takeaway : If you want users to scan a form quickly, put labels above the fields. The layout will be easier to scan because the eye will move straight down the page. However, if you want users to read carefully, put labels to the left of the fields. This layout will slow down the reader and make them scan in a Z-shaped motion.

  Chez une appli de conception d’interface
  https://phase.com/magazine/usability-of-forms/

  from a cognitive point of view, the association is powerful
  Also, the eyes move only in one direction since the scanning is top down as compared to Z shape (left-right and top-bottom) for inline labels
  Design is space efficient and hence adaptable to all resolutions ; in short, responsive in nature
  We also get flexibility regarding the length of labels. This proves useful while working with variable label lengths like multilingual support for applications
  One drawback of this approach is the increased height of the form. However, it can be solved with alternate designs like a grouping of fields or stepper forms

• ffmpeg recoded mp4 files error on mobiles in Video JS

  10 janvier 2019, par KJS

  We are converting seriously old .flv files to MP4 with FFMPEG. These are at least 10 years old.
  Back then all were rendered with early versions of Adobe Premiere.

  On desktop browsers all the files work and stream (...watching them feels like going back a century !)

  But when requesting the videos on the same pages on mobile devices (android and ios) Video JS doesn’t even show up.
  Perhaps the codec is just too old, but I was wondering if there could be another reason when converting them with this line :

  for i in *.flv; do ffmpeg -i "$i" "${i%.*}.mp4"; done

  If not, is it possible to detect this in Video JS, so we can show an announcement that the video is only visible on desktops ?

  I hope someone here has this knowledge !

  added on request of llogan

  ffmpeg version N-78967-gbaec6d8 Copyright (c) 2000-2016 the FFmpeg developers   built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4)   configuration: --prefix=/root/ffmpeg_build
  
  --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --pkg-config-flags=--static --enable-gpl --enable-nonfree --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265   libavutil      55. 19.100 / 55. 19.100   libavcodec     57. 28.100 / 57. 28.100   libavformat    57. 28.100 / 57. 28.100   libavdevice    57.  0.101 / 57.  0.101   libavfilter     6. 39.102 / 
  
  6. 39.102   libswscale      4.  0.100 /  4.  0.100   libswresample   2.  0.101 /  2.  0.101   libpostproc    54.  0.100 / 54.  0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'a_4293_06.mp4':   Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.28.100   Duration: 00:01:40.10, start: 0.023220, bitrate: 492 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 320x240, 376 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 123 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler At least one output file must be specified