Recherche avancée

Sur d’autres sites (13771)

• How do I add a dependency to my application ?

  30 juin 2017, par Aang

  I’m currently working on an application called SatStressGUI, a GUI application written in Python, which was passed down to me from previous interns who have worked on it. It relies on dependencies such as wxPython (which, as most of you probably know, must be installed on the user’s own computer before the application the user is trying to run runs properly if the application calls on the the wxPython library). In the gitHub, under contents->resources->lib->python2.5->sitepackages, you’ll see all the libraries which the application is dependent on (wxPython is under the name wx, for example) copied and pasted. If I am correct, the existence of these libraries in sitepackages makes it so that the user does not have to manually install libraries such as wxPython themselves : the user can simply run the GUI application by downloading the whole package under "clone or download" in the main page and run the satstressgui executable file located in contents->MacOS. I believe there is a file somewhere, perhaps boot.py (located in contents->resources) that says, "hey, before the user runs this executable file, download the libraries under contents->resources->lib->python2.5->sitepackages."

  All that being said, I want to add a new dependency to the program. I am trying to use FFMPEG, which is an external program that allows you to take a sequence of images and convert it to a video. In satstressgui.py, which is the main source code file for this application (located in contents->resources) I use the subprocess python module to call on the external program FFMPEG. Here is the code snippet :

  #FFMPEG is an external program that converts a sequence of images to a video. 
  
  subprocess.call(['/usr/local/bin/ffmpeg', '-framerate', \
  
                           framerate, '-f', 'image2','-pattern_type', \
  
                           'glob', '-i', self.directory + '/orbit_*.png', \
  
                           '-r', '10', '-s', '620x380', self.directory + 
  
                           ".avi"])

  At the moment, this works on my own computer because I have FFMPEG installed (in case it matters, I installed it using homebrew). How do I make it so that FFMPEG becomes a dependency in my program just like wxPython (i.e., I make it so that FFMPEG is "installed" on my user’s computer before they run the application) ? I’ve looked on FFMPEG’s website and it looks as if there is a gitHub for it, but other than that I’m quite lost.

  NOTE : I’ve also tried to use imageio (another Python library) to convert a sequence of images to a video in my application, but I’ve failed. I tried to copy and paste the files from imageio’s gitHub to contents->resources->lib->python2.5->sitepackages, but whenever I try to "import imageio" it fails. This might be because I am adding the dependency wrong or because imageio only works on Python 2.6 and above and my program is written in Python 2.5. If someone could give me an answer to any of these questions and help me import a module such as imageio or add an external program such as FFMPEG as a dependency in my application, that’d be very much appreciated ! I can’t link imageio’s main website because of some restrictions by Stack Overflow, but you should be able to find it by simply searching it up on google (the main website has a photo of an astronaut in it’s top banner). I would more prefer a solution using FFMPEG, however, seeing as I’ve already implemented it in my code.

  Thank you so much in advance for your help ! I’m quite new to computer science and programming so I apologize if a lot of the clarifications or questions I’m asking are rudimentary.

  Here is the link to the gitHub of my application : https://github.com/nhudoan/SatStressGUI

  Here is the link to FFMPEG’s main website : https://ffmpeg.org/download.html#repositories

• How to flatten a VR video to display in normal screen ? [closed]

  14 mai 2023, par d-b

  I am not sure about the terminology here, but I have a VR-video that is intended to be shown using a headset with separate screens for each eye. It is not 3D in the sense that when you turn your head you will see something different, it is just "2,5D" so you get a sense of depth when looking at it. There are two video channels that are more or less identical, they are just recorded with slightly different angle, similar to how human eyes see the world. I hope this makes it clear what type of video I have, otherwise please ask for clarification in a comment (and if there is a special terminology for this type of video, please let me know).

  


  More details : the original video is 4320x2160, basically 2 square channels at 2160 x 2160.

  


  I want to show this video undistorted on a regular screen.

  


  I have read the following questions here on SO :

  


  


  1. How to reproject and join these two clips with ffmpeg ?

     


  


  2. Flatten 360 fisheye video

     


  


  3. How to de-warp 180 degree or 360 degree fisheye video with ffmpeg ?

     


  


  4. Flatten 360 fisheye video

     


  


  5. Unwarping 180 VR Footage with FFmpeg v360 Filter

     


  


  


  (and problably a few more).

  


  I think I want to extract the two video channels (note that they are in the same video stream, not like in a movie where you can have several separate audio streams for different languages) into separate files and then "undistort" them.

  


  (3) gave me a command to splitting the video into two files :

  


  ffmpeg -i -myclip.mp4 -filter_complex "[0]crop=iw/2:ih:0:0[left];[0]crop=iw/2:ih:ow:0[right]" -map "[left]" -map 0:a /tmp/left.mp4 -map "[right]" -map 0:a /tmp/right.mp4


  


  That seemed to have worked as expected but then I also need to "undistort" the content because it was filmed with some fisheye lens or something like that (straight lines not in the absolute centre of the image are more or less circular).

  


  (5) suggested this command :

  


  ffmpeg -i left.mp4 -vf "v360=input=hequirect:output=flat:h_fov=100:v_fov=67.5:w=1280:h=720" leftfixed.mp4


  


  but that produced an output that was 4320x2160 (obviously only from one channel, since input was just one channel) but just the centre of the original image, I estimate the content to be the 500x250 px (upscaled to 4320x2160, so very blocky) of the midpoint of the original image.

  


  How can I "undistort" this video so it looks good on a 2D-screen while the size is preserved ?

  


• Anomalie #3281 (Nouveau) : remarques sur le nouveau thème graphique de la 3.1

  9 octobre 2014, par tcharlss (*´_ゝ｀)

  J’ai noté quelques points que je trouve problématiques avec le nouveau thème graphique de la 3.1.
  Il ne s’agit pas de questions cosmétiques (les goûts les couleurs tout ça), mais de problèmes de lisibilité.
  Essentiellement, Certains textes sont pénibles à lire à cause d’un manque de contraste avec la couleur de fond, ou quand celle-ci est trop saturée.
  L’effet est plus ou moins présent en fonction de la couleur choisie dans les préférences, en tout cas il saute au yeux avec la couleur verte par défaut.

  Tout est noté dans l’image en pièce-jointe, mais reprenons ici.

  D’abord les points les plus problématiques, visibles sur la page d’un article :
  - bandeau supérieur (nom, langue etc.) : contraste un peu faiblard entre le texte et la couleur du fond
  - header des formulaires latéraux (« logo de l’article » par ex.) : texte blanc sur fond clair très pénible à lire.
  - boutons des formulaires latéraux : idem, contraste trop faible, texte peu lisible.

  D’autres points moins importants, mais génants :
  - la couleur de la bordure et des boutons des formulaires latéraux attire beaucoup l’attention, quasiment plus que la boîte info.
  - pas de marge entre le texte de l’article et le dernier formulaire de « afficher_milieu ».
  - bon, l’ombre portée autour de la fiche, c’est subjectif, mais je trouve ça très moche.

  Voilà pour les « bugs ».

  Allez j’en profite pour donner mon impression sur ce nouveau thème. Soyons brutalement honnête : en l’état, je le trouve inférieur à celui de la 3.0.
  Il y a bien un point que j’aime beaucoup : les textes éditoriaux en serif bien lisible et distinct du reste de l’interface. Mais en général, je trouve les couleurs trop « acidulées » et mal balancées.
  D’une façon générale, je pense qu’il faudrait se diriger vers un thème plus « flat » : moins de dégradés, moins de bordures, pas d’ombres portées, et des couleurs plus sobres.