npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

m2s

v1.1.0

Published

takes fcpxml markers and generates stills

Downloads

22

Readme

m2s

This is a utility that grabs markers from an .fcpxml file and generates stills for each, naming each still (and changing its creation date) to match its timecode. We typically install it globally:

npm i -g m2s

and then run it using the cli:

m2s /path/to/fcpxml [options]

setup

Before you can start using the script, you need to set a couple of config variables, which you can do with the --config flag. The bare minimum you need to do is set a desired output folder:

  m2s --config --outputDir=/path/to/directory

The script will look for ffmpeg in your PATH, and if it finds the command works, it will set --ffmpegPath='ffmpeg'. If your ffmpeg is elsewhere, you can manually set this variable. If you don't have ffmpeg, install it with homebrew (brew install ffmpeg) or visit the ffmpeg site.

Other variables you can set include

--html // create html displaying images and open
--relink // point to media folder for relinking
--pdf // coming soon
--jpg // coming soon

use

You need to specify an .fcpxml file, and you need to make sure that that fcpxml file is pointed at the media (currently there's no way to relink from within this script). If your media gets unlinked, go back into FCPX, relink the media, and generate a new .fcpxml file.

Type your command like so:

   m2s --fcpxml [path/to/your/fcpxml]

Your mileage may vary---this script breaks pretty easily. Send any advice our way :)