Recherche avancée

Sur d’autres sites (6994)

• Updated revision.txt

  17 février 2013, par Grandt

  Updated revision.txt
  Need more coffee. I keep forgetting the little things.
  

• Video Processing via Bluetooth

  16 juillet 2012, par kerim yucel

  The application I am currently developing processes each frames using a native code and it should record the video as well. I tried SDK for this purpose but certain restrictions didn't allow me to do so, so I switched to NDK for a video recording code piece.

  Apparently, my algorithm seriously uses CPU, upto %70 percent in the worst case. Before I actually start working on a video recorder, I wanted to try the following approach.

  I will process the preview frames using an android phone and send it to another phone (which uses same application and same model) for recording. My questions are :

  1.Should I try WiFi instead of Bluetooth ? I am developing the application for API 8 so I don't have WiFi-Direct, therefore I should do some socket programming, which would possibly complicate things a bit for me since Bluetooth can easily be set up using SDK.

  2- Will I be available to record the frames as a video at the receiving end ? I will receive each frame with certain metadata embedded to it and should record them using the other phone. I doubt I will be able to do it using SDK, so NDK along with ffmpeg seems to be the best choice ? Any suggestions related to this question will be more than welcome.

  3-Here comes the best part. I am recording the video with the lowest resolution that,after compressed, takes no more than 14mb space for a 10 minute long video. I have to reach the raw frames to send it to other end, encode and compress it. Any ideas related to possible flooding of Bluetooth/Wi-Fi because of big-sized raw frames ?

  Any other approaches and answers will be much appreciated. Thanks.

• Size Discrepany in the ‘du’ Command

  22 juin 2012, par Multimedia Mike — General

  I had a problem today while using the common Unix command ’du’. As a refresher, ’du’ stands for disk usage and is a handy tool for understanding how much disk space is being occupied.

  I think ’du’ is probably doing the right thing. The problem might be that I’m getting strange (read : 1/2 the expected number) when running the tool against directories on vmhgfs, the VMware filesystem.

  Science Project
  On an Ubuntu Linux VMware session, my home directory is on the main file system, which is ext4. The directory /mnt/hgfs is reported by ’mount’ to be of type vmhgfs and is shared with the host machine.

  Create a directory in the home directory and generate a 10 MiB file :

  mkdir /home/melanson/dir
  dd if=/dev/urandom of=/home/melanson/dir/random-file bs=1048576 count=10
  

  Create a directory on the shared drive and copy the same file :

  mkdir /mnt/hgfs/vmshare/dir
  cp /home/melanson/dir/random-file /mnt/hgfs/vmshare/dir
  

  Run ’du’ on each directory using the -k and -h options :

  du -k /home/melanson/dir /mnt/hgfs/vmshare/dir
  10244   /home/melanson/dir
  5120    /mnt/hgfs/vmshare/dir
  du -h /home/melanson/dir /mnt/hgfs/vmshare/dir
  
  11M    /home/melanson/directory
  
  5.0M   /mnt/hgfs/vmshare/directory
  

  I noticed this discrepancy when I was trying to pack a set of files (akin to ’tar’-ing) living in a directory in the shared location. I was going mad trying to understand why the original directory was only 2 MB as reported by ’du’ but the final packed file was 4 MB.

  To be fair, the man page for ’du’ succinctly states that the tool’s purpose is merely to "estimate file space usage".