Migration Guide
Migrate from local media analysis tools to the Probe.dev API
Overview
Migrating from local FFprobe, MediaInfo, or other media analysis tools to Probe.dev is straightforward. Our API maintains compatibility with existing tool parameters while providing cloud-scale reliability and enhanced features.
Why Migrate?
Scalability
No Infrastructure Management
Process thousands of files without server provisioning
Auto-scaling
Handles traffic spikes automatically
Reliability
99.9% Uptime
Redundant infrastructure across multiple regions
Error Handling
Robust retry mechanisms and failure recovery
Enhanced Features
ML-Enhanced Analysis
Probe Report with trained heuristics
Multiple Tool Support
FFprobe, MediaInfo, and custom analysis in one call
Cost Efficiency
Pay Per Use
No idle server costs
Reduced Maintenance
No software updates or security patches
Migration Examples
FFprobe Migration
Before (Local FFprobe):
After (Probe.dev API):
That’s it—you’ve migrated the command to a secure HTTPS call while preserving every original ffprobe flag.
MediaInfo Migration
Before (Local MediaInfo):
After (Probe.dev API):
Python Migration
Before (Local subprocess):
After (Probe.dev API):
Node.js Migration
Before (Local execution):
After (Probe.dev API):
Parameter Mapping
FFprobe Parameters
Most FFprobe parameters are supported with the same names in snake_case:
Local FFprobe | Probe.dev API | Description |
---|---|---|
-print_format json | ffprobe[output_format]=json | Output format |
-show_format | ffprobe[show_format]=true | Show container info |
-show_streams | ffprobe[show_streams]=true | Show stream info |
-probesize 1000000 | ffprobe[probesize]=1000000 | Probe buffer size |
-analyzeduration 5000000 | ffprobe[analyzeduration]=5000000 | Analysis duration |
MediaInfo Parameters
Local MediaInfo | Probe.dev API | Description |
---|---|---|
--Output=JSON | mediainfo[output]=JSON | Output format |
--Full | mediainfo[full]=true | Complete information |
--Language=raw | mediainfo[language]=raw | Language setting |
Migration Checklist
Common Migration Patterns
Batch Processing
Before:
After:
Webhook Integration
Replace local processing with webhook callbacks:
Performance Considerations
Optimization Tips
- Use
only
parameter for single-tool analysis - Enable
inject_json
to combine multiple tool outputs - Batch similar requests to reduce overhead
- Cache results for frequently analyzed files
- Use webhooks for long-running analysis
Expected Performance
Analysis Type | Typical Response Time | Notes |
---|---|---|
FFprobe only | 2-5 seconds | Fast technical analysis |
MediaInfo only | 2-4 seconds | Quick format detection |
Probe Report | 5-10 seconds | ML-enhanced processing |
All tools | 8-15 seconds | Comprehensive analysis |
Support & Resources
Need help with your migration? Contact our support team at support@probe.dev for personalized assistance.