Recherche avancée

Sur d’autres sites (3914)

• tests/fate/hevc : add a test for selecting view by position

  13 septembre 2024, par Anton Khirnov

  tests/fate/hevc : add a test for selecting view by position
  Using a real-world iPhone-recorded file.
  

  • [DH] tests/fate/hevc.mak
  • [DH] tests/ref/fate/hevc-mv-position

• Pack ffmpeg executable insde myProject's executable to run

  8 décembre 2023, par zur

  TLDR ;

  


  I would like to pack the ffmpeg executable inside my own executable. Currently I am getting

  


  FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'
Skipping ./testFile202312061352.mp4 due to FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'


  


  Details :

  


  I am creating executable file using following command :

  


  pyinstaller cli.py \&#xA;  --onefile \&#xA;  --add-binary /Users/<machineuser>/anaconda3/envs/my_env/bin/ffmpeg:bin&#xA;</machineuser>

  


  The code that uses ffmpeg is not authored by me. And I would like to keep that part the same. I hope that when I run from command line while conda environment is active I can successfully run it as python (or perhaps anaconda) knows where the binaries are. May be there is some environment variable that is pointing to /Users/<machineuser>/anaconda3/envs/my_env/bin/</machineuser> I have a pretty empty cli.py. That seems to be the entry point and I hope if it is possible I can set the bin directory's path there ...

  


  I am able to successfully run the application like following :

  


  (my_env) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to run like following :

  


  (base) machineUser folder % "dist/cli_mac_001202312051431" ./testFile202312061352.mp4


  


  I would like to keep the world out side my executable's tmp folder the same. I would not want to change something that will be "left behind" after the exec is terminated.

  


  Question :

  


  Can some one please mention how to modify the pyinstaller command or what to change in cli.py to achieve it successfully ?

  


• Expanding media capabilities of Win Embedded CE 6.0

  1er décembre 2014, par Simo Erkinheimo

  I have an embedded device with WinCE 6.0 as OS. The manufacturer provides an IDE for 3rd party development to it. The IDE pretty much allows nothing else than

  • .NET 3.5 Compact Framework scripting that’s invoked from various events from the main application
  • Adding files to the device.

  The included mediaplayer seems to be using DirectShow and the OS has media codec only for mpeg-1 encoded video playback. My goal is to to be able to play media encoded with some other codecs as well inside that main application.

  I’ve already managed to use DirectShowNETCF (DirectShow wrapper for .NET Compact Framework) and successfully playback mpeg-1 encoded video.

  I’m totally new with this stuff and I have tons of (stupid) questions. I’ll try to narrow them down :

  • The OS is based on WinCE, but as far as I’ve understood, it’s actually always some customized version of it (via Platform Builder). Only "correct way" of developing anything for it afterwards is to use the SDK the manufacturer usually provides. Right ? In my case, the SDK is extremely limited and tightly integrated into IDE as noted above. However, .NET CF 3.5 is capable for interop so its possible to call native libraries -as long as they are compiled for correct platform.

  • Compiled code is pretty much just instructions for the processor (assembler code) and the compiler chooses the correct instructions based on the target processor setting. Also there’s the PE-header that defines under which platform the program is meant to be run. If I target my "helloworld.exe" (does nothing but returns specific exit code) to x86 and compile it with VC, should it work ?

  • If the PE-header is in fact the problem, is it possible to setup for WINCE without the SDK ? Do I REALLY need the whole SDK for creating a simple executable that uses only base types ? I’m using VS2010, which doesn’t even support smart device dev anymore and I’d hate to downgrade just for testing purposes.

  • Above questions are prequel to my actual idea : Porting ffmpeg/ffdshow for WinCE. This actually already exists, but not targeted nor built for Intel Atom. Comments ?

  • If the native implementation is not possible and I would end up implementing some specific codec with C#...well that would probably be quite a massive task. But having to choose C# over native, could I run into problems with codec performance ? I mean.. is C# THAT much slower ?

  Thank you.