- How do I install fireworkweb/smpte in a Laravel application?
- Install it with composer require fireworkweb/smpte. There is no service provider, facade, config file, or publish step because it is a framework-agnostic PHP utility. You can use it directly in your domain or application layer, or wrap it behind a small adapter class.
- Is fireworkweb/smpte a Laravel package or a framework-agnostic PHP library?
- It is a framework-agnostic PHP utility for SMPTE timecode parsing, formatting, and conversion. It ships no Laravel service provider, facade, config, migration, or container binding. It works fine inside Laravel, but treat it as a vendor utility rather than a Laravel integration package.
- Which SMPTE frame rates does fireworkweb/smpte support, including 29.97 drop-frame?
- The package is built to handle drop-frame and non-drop-frame rates for video and media use cases. Before committing, build a fixture table covering 24, 25, 29.97DF, 29.97NDF, 30, 50, 59.94, and 60, plus minute rollovers and 24-hour wraps. Also verify how 23.976 is modeled, since some libraries treat it as 24 with a pulldown factor.
- How do I convert SMPTE timecode to frames or seconds with fireworkweb/smpte?
- The package covers parsing, formatting, and conversion between timecodes, frames, and seconds. Choose one canonical storage representation, with frames as an integer being the safer default, and convert at your application boundaries. Keep the vendor call behind an internal converter interface so you can swap implementations later.
- Does fireworkweb/smpte support drop-frame timecode formatting with a semicolon separator?
- It is designed for both drop-frame and non-drop-frame timecode, which is the core use case it targets. The documentation does not guarantee every formatting detail, so test the semicolon separator explicitly with strings such as 01:00:00;00. Include drop-frame boundary cases at every minute except every tenth minute in your test suite.
- Can I use fireworkweb/smpte safely with Laravel Octane and queue workers?
- Yes, it is stateless and pure CPU with no I/O and no global configuration, which suits long-running workers. Verify that the code has no static mutable state before relying on it at scale. Because it is framework-agnostic, there is also no Laravel version matrix to reconcile for Octane compatibility.
- Does fireworkweb/smpte include timecode arithmetic such as add, subtract, and compare?
- The package's focus is parsing, formatting, and conversion between timecodes, frames, and seconds. Arithmetic such as adding durations, comparing, clamping, and timeline accumulation is best kept in your own domain layer. If you need those operations, build them around the package and cover them with your own conformance tests.
- How should I store SMPTE timecodes in a Laravel database with Eloquent?
- fireworkweb/smpte ships no Eloquent cast or migration, so persistence remains your responsibility. Store frames as an integer as the safer default, or store the timecode string consistently if that better matches your ingest format. Create a custom Eloquent cast and handle boundary cases such as 24-hour wrap and negative values explicitly.
- What PHP and Laravel versions does fireworkweb/smpte support?
- Because it is framework-agnostic, it declares no Laravel version matrix. Check its composer.json PHP constraint against your current and next LTS runtime before adopting it. Then run its test suite and your own conversion fixtures on the exact PHP version you deploy.
- Is fireworkweb/smpte actively maintained and production-ready, or should I look for alternatives?
- Ecosystem signals are thin: seven stars, zero dependents, and single-vendor stewardship, so treat abandonment as plausible. The recent November 2024 release suggests it is not dormant, and MIT licensing means you can fork if needed. Read the small code surface in full, run drop-frame conformance vectors, and keep the vendor boundary one adapter class wide.