Recherche avancée

Sur d’autres sites (4424)

• Android ffmpeg command shows java.io.IOException : Error running exec()

  13 avril 2015, par Jamal

  I would like to use ffmpeg binary executable in my Android project.for this purpose I have used pre built ffmpeg Android binary from this(https://github.com/hiteshsondhi88/ffmpeg-android/releases/download/v0.3.3/prebuilt-binaries.zip) link.

  As per procedure I have to place the executable file into /data/data/com.example.rampedsample directory, here com.example.rampedsample is my project packageName.I couldn’t find this location in my device as it is un rooted.So I pasted that executable into Android emulator’s com.example.rampedsample directory using DDMS perspective.

  In my Activity used the below code

   try {
  
              Process p = Runtime.getRuntime().exec("/data/data/com.example.rampedsample/ffmpeg "+Environment.getExternalStorageDirectory()+"/Movies/ramp_video.mp4"
  
                      +" -map 0:v -codec copy "+Environment.getExternalStorageDirectory()+"/Movies/ramp_video2.mp4");
  
  
  
  
  
          } catch (IOException e) {
  
              // TODO Auto-generated catch block
  
              e.printStackTrace();
  
          }

  AndroidManifest permission

  error

  04-13 16:59:55.314: W/System.err(11387): java.io.IOException: Error running exec(). Command: [/data/data/com.example.rampedsample/ffmpeg, /mnt/sdcard/Movies/ramp_video.mp4, -map, 0:v, -codec, copy, /mnt/sdcard/Movies/ramp_video2.mp4] Working Directory: null Environment: null
  
  04-13 16:59:55.314: W/System.err(11387):    at java.lang.ProcessManager.exec(ProcessManager.java:211)
  
  04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:168)
  
  04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:241)
  
  04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:184)
  
  04-13 16:59:55.355: W/System.err(11387):    at com.example.rampedsample.MainActivity.onCreate(MainActivity.java:18)
  
  04-13 16:59:55.355: W/System.err(11387):    at android.app.Activity.performCreate(Activity.java:5008)
  
  04-13 16:59:55.355: W/System.err(11387):    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)

• Android ffmpeg command shows java.io.IOException : Error running exec()

  26 mai 2023, par Jamal

  I would like to use ffmpeg binary executable in my Android project.for this purpose I have used pre built ffmpeg Android binary from this(https://github.com/hiteshsondhi88/ffmpeg-android/releases/download/v0.3.3/prebuilt-binaries.zip) link.

  



  As per procedure I have to place the executable file into /data/data/com.example.rampedsample directory, here com.example.rampedsample is my project packageName.I couldn't find this location in my device as it is un rooted.So I pasted that executable into Android emulator's com.example.rampedsample directory using DDMS perspective.

  



  In my Activity used the below code

  



   try {
            Process p = Runtime.getRuntime().exec("/data/data/com.example.rampedsample/ffmpeg "+Environment.getExternalStorageDirectory()+"/Movies/ramp_video.mp4"
                    +" -map 0:v -codec copy "+Environment.getExternalStorageDirectory()+"/Movies/ramp_video2.mp4");


        } catch (IOException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }


  



  AndroidManifest permission

  



  


  



  error

  



  04-13 16:59:55.314: W/System.err(11387): java.io.IOException: Error running exec(). Command: [/data/data/com.example.rampedsample/ffmpeg, /mnt/sdcard/Movies/ramp_video.mp4, -map, 0:v, -codec, copy, /mnt/sdcard/Movies/ramp_video2.mp4] Working Directory: null Environment: null
04-13 16:59:55.314: W/System.err(11387):    at java.lang.ProcessManager.exec(ProcessManager.java:211)
04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:168)
04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:241)
04-13 16:59:55.355: W/System.err(11387):    at java.lang.Runtime.exec(Runtime.java:184)
04-13 16:59:55.355: W/System.err(11387):    at com.example.rampedsample.MainActivity.onCreate(MainActivity.java:18)
04-13 16:59:55.355: W/System.err(11387):    at android.app.Activity.performCreate(Activity.java:5008)
04-13 16:59:55.355: W/System.err(11387):    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)


  


• How to distinguish a physical D3D adapter from a virtual adapter used by the Remote Desktop Protocol ?

  31 octobre 2023, par rustak

  I'm currently developing a desktop application(c#/wpf) that decodes video using FFmpeg. I would like to give the user the option to select an adapter for video decoding. I'm using Direct3D method EnumAdapters to list available adapters on current device which works fine. The list of available adapters looks something like this :

  


  Adapter 0
  Description: Intel(R) HD Graphics 630
  Vendor ID:   0x8086
  Device ID:   0x5912
  SubSys ID:   0x86941043
  Revision:    4
  Luid:    46459
  Flags:    None
  Dedicated Video Memory:    128 MB
  Dedicated System Memory:  0 MB
  Shared System Memory:     8092 MB
Adapter 2
  Description: Microsoft Basic Render Driver
  Vendor ID:   0x1414
  Device ID:   0x8C
  SubSys ID:   0x0
  Revision:    0
  Luid:    50158
  Flags:    Software
  Dedicated Video Memory:    0 MB
  Dedicated System Memory:  0 MB
  Shared System Memory:     8092 MB


  


  I have noticed that an additional adapter appears in the list of available adapters when RDP is used. The additional adapter has the same properties as the physical one ; the only difference is in the LUID. The output looks something like this :

  


  Adapter 0
  Description: Intel(R) HD Graphics 630
  Vendor ID:   0x8086
  Device ID:   0x5912
  SubSys ID:   0x86941043
  Revision:    4
  Luid:    46459
  Flags:    None
  Dedicated Video Memory:    128 MB
  Dedicated System Memory:  0 MB
  Shared System Memory:     8092 MB
Adapter 1 // <- additional addapter
  Description: Intel(R) HD Graphics 630 
  Vendor ID:   0x8086
  Device ID:   0x5912
  SubSys ID:   0x86941043
  Revision:    4
  Luid:    1322913970
  Flags:    None
  Dedicated Video Memory:    128 MB
  Dedicated System Memory:  0 MB
  Shared System Memory:     8092 MB
Adapter 2
  Description: Microsoft Basic Render Driver
  Vendor ID:   0x1414
  Device ID:   0x8C
  SubSys ID:   0x0
  Revision:    0
  Luid:    50158
  Flags:    Software
  Dedicated Video Memory:    0 MB
  Dedicated System Memory:  0 MB
  Shared System Memory:     8092 MB


  


  I'm aware that the additional adapter is some kind of virtual adapter used by RDP. I have tried both of them, and it seems that both are suitable for video decoding using FFmpeg.

  


  However, from a UX perspective, it doesn't look or feel right that the combo box contains two adapters with the same name. So my question is : how can I distinguish a physical adapter from a virtual adapter used by the Remote Desktop Protocol ?