Sur d’autres sites (6089)

• Inscriptions3 + Champs Extra

  6 août 2018

  Bonjour,

  Voici quelques points liées à l’utilisation de Champs Extra dans Inscription 3. Je vais détailler un peu mais dans l’idée, il s’agit d’adapter l’affichage de champs ou de leur valeur selon leur nature (input, radio, select ou fieldset), pour l’heure cela semble bien pensé pour les inputs et textarea, mais pour le reste ça pèche un peu.

  Page des utilisateurs (ecrire/ ?exec=inscription3_adherents) :

  Bug :
  Les champs fieldset et explication provoque une erreur alors qu’il devrait être ignorer. Il va de soit qu’on ne devrait pas cocher la colonne ’table’ pour ces champs dans la page de configuration, mais malheureusement c’est une erreur fréquente.

  Soucis d’affichage :

  1. Pour les selects, les entêtes des colonnes sont erronées, on voit par exemple ’label_nom_champs’ au lieu du nom du champs
  2. Pour les selects, on voit dans les cellules du tableau et non des valeurs
  3. Les dates sont au format SQL, pas si simple à lire pour les utilisateurs.

  Page de configuration (ecrire/ ?exec=configurer_inscription3) :

  Bug :

  • Dans la première colonne dans la partie des champs extras, le label est vide pour les checkbox, impossible de les identifier sinon par l’ordre dans la liste.
  • Idem avec les champs ’explication’
  • Il faut supprimer les cases à cocher de la colonne ’Table’ pour les champs ’explication’ et ’fieldset’, ils créés l’erreur fatales dans la page des utilisateurs.
  • Il faut supprimer les cases à cocher de la colonne ’Obligatoire’ pour les champs ’explication’ et ’fieldset’, car si ils sont cochés, le formulaire d’inscription ne pas être validé par l’utilisateur, c’est une erreur fréquente chez moi...

  Groupe de champs :

  Par le passé, j’ai voulu exploiter les fieldsets (Groupe de champs) de champs extra, pour grouper des champs...
  Malheureusement, cela ne semble pas être pris en charge par Inscription3.
  Les champs groupés disparaissent de la page de configuration, ils en deviennent inconfigurable...
  Et on perds les options d’affichage conditionnel par groupe par exemple...

  Vous pouvez compter sur moi pour des tests suite à la correction de ces bugs.

  Merci d’avance,

  Jul

• Full HD video converted to FLV, slow playback in browser

  12 février 2012, par Boyan Georgiev

  I rendered a full HD video using Adobe AfterEffects CS5 in mp4 format. It plays just fine. I've got this video app to which I fed the mp4 file. The video app converts the mp4 to flv format and makes the video available via a web page. I've downloaded the resulting flv file to my local PC - it plays just fine in my VLC player. But, the problem is I'm getting awful playback inside my browser.

  I've made sure the issue is not bandwidth related.
  Both original mp4 file, and ffmpeg-converted FLV file, play perfectly using VLC player.
  I've tested the FLV file with two players - Agryia FLV Player Elite and JW Player. Both players play the video awfully - really slow and very choppy.

  Here's my ffmpeg -i myflvfile.flv :
  `

  Seems stream 0 codec frame rate differs from container frame rate: 119.88 (120000/1001) -> 59.92 (719/12)
  
  Input #0, flv, from '94044631305552037.flv':
  
  Metadata:
  
  duration        : 146
  
  width           : 1920
  
  height          : 1080
  
  videodatarate   : 684
  
  framerate       : 60
  
  videocodecid    : 7
  
  audiodatarate   : 62
  
  audiosamplerate : 22050
  
  audiosamplesize : 16
  
  stereo          : true
  
  audiocodecid    : 2
  
  major_brand     : mp42
  
  minor_version   : 0
  
  compatible_brands: mp42mp41
  
  creation_time   : 2012-02-10 00:55:19
  
  encoder         : Lavf52.111.0
  
  filesize        : 61969316
  
  Duration: 00:02:25.77, start: 0.034000, bitrate: 764 kb/s
  
  Stream #0.0: Video: h264 (High), yuv420p, 1920x1080 [PAR 3:4 DAR 4:3], 700 kb/s, 59.92 tbr, 1k tbn, 119.88 tbc
  
  Stream #0.1: Audio: mp3, 22050 Hz, stereo, s16, 64 kb/s`

  Can any one point me in the right direction here ? Why is playback perfect with VLC player of both the mp4 and the flv file on my local PC, yet in my browser, using two different players, the playback is so bad ?

  PS Here's my convert command :

  ffmpeg -y -i /var/www/sandverlag.com/htdocs/rmtk/videos/originals/94044631305552038.mp4 -vcodec libx264 -ar 22050 -ac 2 -vb 700000 -s 1920x1080 -crf 22 -threads 0 -f flv /var/www/sandverlag.com/htdocs/rmtk/videos/converted/94044631305552038.flv > /dev/null &    

• Android : Recording and Streaming at the same time

  29 mars 2016, par Bruno Siqueira

  This is not really a question as much as it is a presentation of all my attempts to solve one of the most challenging functionalities I was faced with.

  I use libstreaming library to stream realtime videos to Wowza Server and I need to record it at the same time inside the SD card. I am presenting below all my attempts in order to collect new ideias from the community.

  Copy bytes from libstreaming stream to a mp4 file

  Development

  We created an interception in libstreaming library to copy all the sent bytes to a mp4 file. Libstreaming sends the bytes to Wowza server through a LocalSocket. It users MediaRecorder to access the camera and the mic of the device and sets the output file as the LocalSocket’s input stream. What we do is create a wrapper around this input stream extending from InputStream and create a File output stream inside it. So, every time libstreaming executes a reading over the LocaSocket’s input stream, we copy all the data to the output stream, trying to create a valid MP4 file.

  Impediment

  When we tried to read the file, it is corrupted. We realized that there are meta information missing from the MP4 file. Specifically the moov atom. We tried to delay the closing of the streaming in order to give time to send this header (this was still a guessing) but it didn’t work. To test the coherence of this data, we used a paid software to try to recover the video, including the header. It became playable, but it was mostly green screen. So this became an not trustable solution. We also tried using "untrunc", a free open source command line program and it couldn’t even start the recovery, since there was no moov atom.

  Use ffmpeg compiled to android to access the camera

  Development

  FFMPEG has a gradle plugin with a java interface to use it inside Android apps. We thought we could access the camera via command line (it is probably in "/dev/video0") and sent it to the media server.

  Impediment

  We got the error "Permission Denied" when trying to access the camera. The workaround would be to root the device to have access to it, but it make the phones loose their warranty and could brick them.

  Use ffmpeg compiled to android combined with MediaRecorder

  Development

  We tried to make FFMPEG stream a mp4 file being recorded inside the phone via MediaRecorder

  Impediment

  FFMPEG can not stream MP4 files that are not yet done with the recording.

  Use ffmpeg compiled to android with libstreaming

  Development

  Libstreaming uses LocalServerSocket as the connection between the app and the server, so we thought that we could use ffmpeg connected with LocalServerSocket local address to copy the streaming directly to a local file inside the SD card. Right after the streaming started, we also ran the ffmpeg command to start recording the data to a file. Using ffmpeg, we believed that it would create a MP4 file in the proper way, which means with the moov atom header included.

  Impediment

  The "address" created is not readable via command line, as a local address inside the phone. So the copy is not possible.

  Use OpenCV

  Development

  OpenCV is an open-source, cross-platform library that provides building blocks for computer vision experiments and applications. It offers high-level interfaces for capturing, processing, and presenting image data. It has their own APIs to connect with the device camera so we started studding it to see if it had the necessary functionalities to stream and record at the same time.

  Impediment

  We found out that the library is not really defined to do this, but more as image mathematical manipulation. We got even the recommendation to use libstreaming (which we do already).

  Use Kickflip SDK

  Development

  Kickflip is a media streaming service that provides their own SDK for development in android and IOS. It also uses HLS instead of RTMP, which is a newer protocol.

  Impediment

  Their SDK requires that we create a Activity with camera view that occupies the entire screen of the device, breaking the usability of our app.

  Use Adobe Air

  Development

  We started consulting other developers of app’s already available in the Play Store, that stream to servers already.

  Impediment

  Getting in touch with those developers, they reassured that would not be possible to record and stream at the same time using this technology. What’s more, we would have to redo the entire app from scratch using Adobe Air.

  UPDATE

  Webrtc

  Development

  We started using WebRTC following this great project. We included the signaling server in our NODEJS server and started doing the standard handshake via socket. We were still toggling between local recording and streaming via webrtc.

  Impediment

  Webrtc does not work in every network configuration. Other than that, the camera acquirement is all native code, which makes a lot harder to try to copy the bytes or intercept it.