Explore related resources

Find more information about the topics in this Learning Path:

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which FFmpeg executable should I pass to the scripts for Arm64 versus x86_64?
Set the exePath parameter to the specific FFmpeg or FFplay binary that you want to run. Use the Arm64-native build for Arm execution, or point to an x86_64 build to run under Windows instruction emulation.
How do I know the resource monitoring script is recording data?
While the decode task runs, the script writes samples to a CSV file. Check that the CSV file appears and grows over time, and that it contains headers and rows with CPU and memory values.
What should I check if FFmpeg fails to encode or decode the sample video?
Verify the input and output file paths and confirm the arguments match the media you’re using. Ensure exePath points to a valid FFmpeg or FFplay binary and review the console output for specific errors.
Where does the script save the CSV files and what should be in them?
The output file name and path are defined in each script. Open the script to confirm or change the location. Expect timestamped rows with the recorded metrics, such as CPU and memory for resource sampling, or battery-related fields for power sampling.
How do I run a like-for-like comparison between the Arm64 and x86_64 builds?
Use the same media file, the same command arguments, and the same sampling settings for both runs. Point exePath to each build in turn and compare the resulting CSV files.

Share

Tell others about this Learning Path.

Back
Return to Laptops and Desktops