Two letters better than MetaX
Clone or download
Latest commit 5743288 Apr 19, 2018
Permalink
Failed to load latest commit information.
App Add prerelease update preference Apr 20, 2018
Externals Update Sparkle using carthage Apr 20, 2018
Extras Moved stuff to extras directory Apr 3, 2014
Framework Handle case where no plugin can load file Mar 29, 2018
MetaZ.xcodeproj Update Sparkle using carthage Apr 20, 2018
Plugins Use https for TheTVDB Oct 7, 2017
Release First crack at automatic releases Sep 10, 2017
Scripts Trigger site rebuild after deploy Apr 18, 2018
.gitignore Update Sparkle using carthage Apr 20, 2018
.gitmodules Add GTM as submodule Sep 9, 2017
.travis.yml Update Travis Xcode to 9.3 Apr 20, 2018
Cartfile Update Sparkle using carthage Apr 20, 2018
Cartfile.resolved Update Sparkle using carthage Apr 20, 2018
Credits.html Switched to MGViewAnimation Aug 23, 2011
Document.scpt Finished the rough first version of applescript support Nov 1, 2012
Gemfile Try different way of setting release notes Sep 22, 2017
Gemfile.lock Change Gemfile.lock to support ruby 2.0.0 Sep 24, 2017
License.txt Update copyright Sep 12, 2017
README.markdown Add build status icon to README Sep 27, 2017
Selection.scpt Finished the rough first version of applescript support Nov 1, 2012
Tags.scpt Finished the rough first version of applescript support Nov 1, 2012
bisect.sh Added a small bisect script Dec 4, 2012
init.sh Added init script to simplify build from fresh checkout Oct 8, 2013
sparkle_private.pem.enc First crack at automatic releases Sep 10, 2017
sparkle_public.pem Added Sparkle sign script Sep 4, 2009
version.plist Initial import of MetaZ Sep 4, 2009

README.markdown

Introduction Build Status

MetaZ is an mp4 meta-data editor for OS X.
It started its life when another great meta-data editor MetaX stopped getting updated, some of the web-services it used changed in ways that broke functionality and it had some really anoying (to us at least) little missing things like no proper window resizing. This lead to us starting MetaZ as a reimplementation of MetaX with a few ideas of our own sprinkled in there.

Bugs / Feature request

For bugs and feature requests you can use our issue tracker at github

Extras

We have created some extra resources and small plugins that were deemed to small or silly to be included with the main program.

The classic moo from MetaX is finally available via a small MetaZ plugin you can download from here. To install it simply unpack the zip file and drop the unpacked script onto the MetaZ dock icon.

If you use Script Debugger from Late Night Software you are in luck because we have created a Script Debugger template for MetaZ plugins which illustrate the different types of events plugins can respond to. To get the template click here

Helping out

Building

There are some files missing in the git repository that you will need if you are going to build your own version of MetaZ.

Plugins/Amazon/Access.h
This file contains Amazon AWS access credentials.
Copy Plugins/Amazon/Access_template.h and insert your own credentials.

App/resources/CowHead.png
App/resources/faded_cow*.png
App/resources/presets.png
These files are mostly just taken from MetaX but since I don't have the rights to use them they are not included in the repository.
I have though made a tar with these files and uploaded it to github: missing.tar.gz

Building with Xcode 5

It seems possible to build the project with Xcode 5 while still compiling with the 10.5 SDK. What you need to do is manually install the SDK from the Xcode 3.2.6 DMG.

# Download and mount the Xcode 3.2.6 DMG from Apple

open /Volumes/Xcode\ and\ iOS\ SDK/Packages/MacOSX10.5.pkg
# Install the SDK and choose a location like your user home 
# You should now have the directory MacOSX10.5.sdk in ~/SDKs

# Make a link from the Xcode 5 install location to the installed SDK
cd /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
sudo ln -s ~/SDKs/MacOSX10.5.sdk MacOSX10.5.sdk

Contribution steps

We follow GitHub flow, as a workflow. Basically:

  • Create a feature branch in your fork
  • Make your change with documentation as appropriate
  • Please run and test a release build before submitting a pull request!
  • Submit a pull request from your branch
  • Someone with commit access will review the code and merge it. This applies even if you also have commit access.

Becoming a committer

Going forward we will follow rubinius' lead and once you have one pull request accepted into MetaZ, we will add you to a team that has push+pull access. Basically you will get a big green merge button on other people's pull requests, and you will be able to commit those pull requests to the griff/metaz master branch.

This also means that you could push your commits directly to griff/metaz without going through a pull request. We ask that you not do this, however, so that any code on master has been reviewed. This does not apply to branches other than master; if there is long-term collaboration happening, create a feature branch and feel free to push directly to that (but have commits reviewed before merging that branch into master).

We reserve the right to take away this permission, but in general we trust you to give it to you.