Skip to content

Commit

Permalink
Renamed Metaburner Pro to just Metaburner
Browse files Browse the repository at this point in the history
- Now releasing on FxFactory instead of the Mac App Store.
  • Loading branch information
latenitefilms committed Jan 2, 2024
1 parent 7bb49db commit 99450ca
Show file tree
Hide file tree
Showing 16 changed files with 68 additions and 80 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
<img src="https://github.com/latenitefilms/MetaburnerPro/raw/main/docs/static/logo.png" align="right" width="15%" height="15%" />
<img src="https://github.com/latenitefilms/Metaburner/raw/main/docs/static/logo.png" align="right" width="15%" height="15%" />

# Metaburner Pro
# Metaburner

Metaburner Pro is a Metadata Generator for Final Cut Pro.
Metaburner is a Metadata Generator for Final Cut Pro.

You can download & learn more [here](https://metaburner.pro).
22 changes: 9 additions & 13 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,30 +5,26 @@
}
}
</style>
<img class="rightLogo" src="https://github.com/latenitefilms/MetaburnerPro/raw/main/docs/static/logo.png" align="right" style="width: 100px !important; height: 100px !important;" />
<img class="rightLogo" src="https://github.com/latenitefilms/Metaburner/raw/main/docs/static/logo.png" align="right" style="width: 100px !important; height: 100px !important;" />

# Metaburner Pro
# Metaburner

**Metaburner Pro** is a Metadata Generator for Final Cut Pro.
**Metaburner** is a Metadata Generator for Final Cut Pro.

> Metaburner Pro is currently being publicly beta tested on Apple's TestFlight.
> Metaburner is currently being publicly beta tested on Apple's TestFlight.
>
> If you're interested in helping with development, you can learn more [here](/how-to-use/).
You can access it via a **Title** in the Titles sidebar.

Metaburner Pro gives you **25 text layers** that you can populate with whatever metadata you want.
Metaburner gives you **25 text layers** that you can populate with whatever metadata you want.

You can even stack multiple Metaburner Pro Titles on top of each other for **unlimited** titles!
You can even stack multiple Metaburner Titles on top of each other for **unlimited** metadata fields!

To begin, simply drag your Final Cut Pro Project from the Browser into the Metaburner Pro Title Inspector via a drop zone, and then Metaburner Pro has full access to everything that's in the FCPXML.
To begin, simply drag your Final Cut Pro Project from the Browser into the Metaburner Title Inspector via a drop zone, and then Metaburner has full access to everything that's in the FCPXML.

There's also a **Lua scripting environment** built-in, so you can even "code" your own text for unlimited possibilities.

You can even share Lua variables between multiple Metaburner Pro titles for some crazy possibilities!
You can even share Lua variables between multiple Metaburner titles for some crazy possibilities!

![](/static/metaburner-pro-screenshot.jpeg)

<!--
> [:icon-desktop-download: **Click here to buy on the Mac App Store**](/buy/)
-->
![](/static/metaburner-pro-screenshot.jpeg)
12 changes: 3 additions & 9 deletions docs/buy.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,7 @@
# Buy on Mac App Store
# Buy on FxFactory

Metaburner Pro is still in **active development**, and not yet for sale. We hope to release in early January.
**Metaburner** is still in **active development**, and not yet for sale. We hope to release by the end of January 2024.

> If you're interested in helping with development, you can learn more [here](/how-to-use/).
<!--
> [:icon-desktop-download: **Buy on the Mac App Store**](https://apps.apple.com/us/app/metaburner-pro/id6474466386)
-->

**Metaburner Pro** will be a one-time payment of **USD$150**.

You can find information about Educational Pricing [here](/educational/).
**Metaburner** will be a one-time payment of **USD$149** on FxFactory.
2 changes: 1 addition & 1 deletion docs/buy.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
label: Buy on Mac App Store
label: Buy on FxFactory
icon: desktop-download
order: 9000
4 changes: 2 additions & 2 deletions docs/credits.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Credits

Metaburner Pro has been thrown together by [Chris Hocking](https://github.com/latenitefilms) at [LateNite](https://latenitefilms.com).
**Metaburner** has been thrown together by [Chris Hocking](https://github.com/latenitefilms) at [LateNite](https://latenitefilms.com).

The Metaburner Pro icon was designed by the amazing [Matthew Skiles](http://matthewskiles.com).
The **Metaburner** icon was designed by the amazing [Matthew Skiles](http://matthewskiles.com).

Chris also created [CommandPost](https://commandpost.io), [Transfer Toolbox](https://transfertoolbox.io), [BRAW Toolbox](https://brawtoolbox.io), [Marker Toolbox](https://markertoolbox.io) and [Gyroflow Toolbox](https://gyroflowtoolbox.io).

Expand Down
5 changes: 0 additions & 5 deletions docs/educational.md

This file was deleted.

3 changes: 0 additions & 3 deletions docs/educational.yml

This file was deleted.

8 changes: 2 additions & 6 deletions docs/faq.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,5 @@
# Frequently Asked Questions

Metaburner Pro is currently in **early development**.
This page will eventually be populated with frequently asked questions.

We are aiming to release on TestFlight in late 2023.

We'll update this page once we have a TestFlight release.

Got ideas or questions? Post them on our [Discussions page](https://github.com/latenitefilms/metaburnerpro/discussions)!
Got ideas or questions? Post them on our [Discussions page](https://github.com/latenitefilms/metaburner/discussions)!
38 changes: 19 additions & 19 deletions docs/how-to-use.md
Original file line number Diff line number Diff line change
@@ -1,40 +1,40 @@
# How To Use

Metaburner Pro is currently in **active development**. We are aiming to release sometime in January 2024.
Metaburner is currently in **active development**. We are aiming to release sometime in January 2024.

If you're interested in helping with development, you can sign up to **TestFlight** (Apple's beta-testing service) for free [here](https://testflight.apple.com/join/dw7S2veN).

We will be posting regular beta builds to TestFlight as we add new features and functionality.

Got ideas or questions? Post them on our [Discussions page](https://github.com/latenitefilms/metaburnerpro/discussions)!
Got ideas or questions? Post them on our [Discussions page](https://github.com/latenitefilms/metaburner/discussions)!

![](/static/overlay-example.png)

---

### Known Issues & Bugs

Please check the [Issues page](https://github.com/latenitefilms/metaburnerpro/issues) for any known bugs or issues.
Please check the [Issues page](https://github.com/latenitefilms/metaburner/issues) for any known bugs or issues.

You can find the full release notes [here](/release-notes/).

---

### Final Cut Pro Bug

**UPDATE:** As of Metaburner Pro 1.0.0 (Build 20) we now workaround this issue.
**UPDATE:** As of Metaburner 1.0.0 (Build 20) we now workaround this issue.

There is currently a bug in Final Cut Pro 10.7.1, where it incorrectly exports FCPXML `v1.11` when projects have Multicam Clips with individual Audio Role Voice Isolation.

Because Metaburner Pro only accepts valid FCPXML files, if you have a project that has Multicam Clips with individual Audio Role Voice Isolation, it won't import into Metaburner Pro.
Because Metaburner only accepts valid FCPXML files, if you have a project that has Multicam Clips with individual Audio Role Voice Isolation, it won't import into Metaburner.

You can confirm this is the issue by exporting a FCPXML to your Desktop, then bringing it back it.

If you're hitting this bug you'll see something like this:

![](static/invalid-fcpxml.png)

The workaround is to instead export a FCPXML `v1.10` instead, then use the **Controls > Import Project via FCPXML** to bring it into Metaburner Pro.
The workaround is to instead export a FCPXML `v1.10` instead, then use the **Controls > Import Project via FCPXML** to bring it into Metaburner.

You can learn more about the bug on FCP Cafe [here](https://github.com/CommandPost/FCPCafe/issues/314).

Expand All @@ -51,7 +51,7 @@ You can press the **Reveal Log Files** button in the **Controls** section of the
The log file is located here:

```
~/Library/Containers/com.latenitefilms.MetaburnerProRenderer/Data/Library/Application Support/FxPlug.log
~/Library/Containers/com.latenitefilms.MetaburnerRenderer/Data/Library/Application Support/FxPlug.log
```

You can press the **Reveal Crash Logs** button in the **Controls** section of the Inspector to access the `DiagnosticReports` folder in Finder.
Expand All @@ -64,7 +64,7 @@ The crash logs are located here:
~/Library/Logs/DiagnosticReports
```

The crash logs will have file names like `Metaburner Pro Renderer-2023-12-24-103301.ips`. They might also be in the `Retired` sub-folder (these are reports that have already been posted to Apple).
The crash logs will have file names like `Metaburner Renderer-2023-12-24-103301.ips`. They might also be in the `Retired` sub-folder (these are reports that have already been posted to Apple).

Alternatively, you can access your User Library, by clicking on your **Desktop**, then holding down **OPTION** as you click the **Go** menu item in Finder. A **Library** option will appear:

Expand Down Expand Up @@ -100,15 +100,15 @@ The button will now be disabled, and will say **Motion Template Installed**. You

### Accessing in Final Cut Pro

After installing the Motion Template, you can find the Metaburner Pro Title at the top of the Title sidebar in Final Cut Pro:
After installing the Motion Template, you can find the Metaburner Title at the top of the Title sidebar in Final Cut Pro:

![](static/title-browser.png)

---

### Title Inspector

Simply add the Metaburner Pro Title to the top of your timeline as an adjustment layer.
Simply add the Metaburner Title to the top of your timeline as an adjustment layer.

It should start at the very start of your timeline.

Expand Down Expand Up @@ -146,11 +146,11 @@ For example, if you have **Project** selected in the **Content Source**, and **N

You can add a **Prefix** and a **Suffix** to all text fields, regardless of the **Content Source** and **Content Field**.

When you first add the Metaburner Pro Title, it will display this image in your Viewer:
When you first add the Metaburner Title, it will display this image in your Viewer:

![](static/no-project-loaded.png)

As the image explains, so that Metaburner Pro can access all the metadata in your project/timeline, you need to drag your project/timeline from the **Browser** to the drop zone at the top of the Inspector:
As the image explains, so that Metaburner can access all the metadata in your project/timeline, you need to drag your project/timeline from the **Browser** to the drop zone at the top of the Inspector:

![](static/drop-zone.png)

Expand All @@ -170,17 +170,17 @@ After a short time, if successful, the status should change to **Project Loaded*

![](static/project-loaded.png)

> Final Cut Pro can be a bit temperamental in terms of updating the status, so you may need to click away from the Metaburner Pro Title and then go back to it for the text to update.
> Final Cut Pro can be a bit temperamental in terms of updating the status, so you may need to click away from the Metaburner Title and then go back to it for the text to update.
Once done, Metaburner Pro has access to all the metadata within the FCPXML to populate all the Content Sources.
Once done, Metaburner has access to all the metadata within the FCPXML to populate all the Content Sources.

If you make changes to the project/timeline, you'll need to drag the project back again to update the contents of Metaburner Pro.
If you make changes to the project/timeline, you'll need to drag the project back again to update the contents of Metaburner.

If Metaburner Pro was unable to import the FCPXML, you'll get an error status, which you can hover over with your mouse to get more detail:
If Metaburner was unable to import the FCPXML, you'll get an error status, which you can hover over with your mouse to get more detail:

![](static/error-in-inspector.png)

If you do run into an error, it's most likely a bug in Metaburner Pro, so please share your Error Log and FCPXML on GitHub [here](https://github.com/latenitefilms/metaburnerpro/issues).
If you do run into an error, it's most likely a bug in Metaburner, so please share your Error Log and FCPXML on GitHub [here](https://github.com/latenitefilms/metaburner/issues).

---

Expand All @@ -207,9 +207,9 @@ If you then export a FCPXML with the **Extended** Metadata View:
</metadata>
```

You can then use **com.apple.proapps.studio.reel** in the **Custom Field** within the Metaburner Pro Inspector to display the Reel.
You can then use **com.apple.proapps.studio.reel** in the **Custom Field** within the Metaburner Inspector to display the Reel.

Keep in mind that Metaburner Pro only has access to whatever metadata you have visible in the **Info Inspector**, so make sure you select the correct **Metadata View** before dragging your project to Metaburner Pro's Drop Zone.
Keep in mind that Metaburner only has access to whatever metadata you have visible in the **Info Inspector**, so make sure you select the correct **Metadata View** before dragging your project to Metaburner's Drop Zone.

---

Expand Down
8 changes: 4 additions & 4 deletions docs/lua-scripting.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Lua Scripting

An incredible powerful feature of Metaburner Pro is the ability to code your own Lua scripts.
An incredible powerful feature of Metaburner is the ability to code your own Lua scripts.

Simply use the **Lua** Content Source, then use the **Custom Field** to type your code.

Anything you write to the `result` global variable will be displayed in Metaburner Pro.
Anything you write to the `result` global variable will be displayed in Metaburner.

For example:

Expand All @@ -14,12 +14,12 @@ You have access to the full FCPXML via the `fcpxmlData` global variable, which i

![](/static/lua-fcpxml.png)

You have access to Metaburner Pro's processed data via the `processedData` global variable, which is stored as a `table`:
You have access to Metaburner's processed data via the `processedData` global variable, which is stored as a `table`:

![](/static/lua-processed-data.png)

You can manipulate this data any way you want.

The Lua environment is shared between all instances of the Metaburner Pro plugin, so you can even pass information between different Metaburner Pro Titles!
The Lua environment is shared between all instances of the Metaburner plugin, so you can even pass information between different Metaburner Titles!

You can learn more about Lua Scripting on the [CommandPost website](https://commandpost.io/developer/lua-overview/).
10 changes: 5 additions & 5 deletions docs/privacy.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Privacy Policy

This is the privacy policy for the Metaburner Pro, macOS Application that is available on the macOS App Store and TestFlight.
This is the privacy policy for the Metaburner, macOS Application that is available on the macOS App Store, TestFlight and FxFactory.

Metaburner Pro does not collect any user data. No personal information is transmitted, stored, or used by this application.
Metaburner does not collect any user data. No personal information is transmitted, stored, or used by this application.

Metaburner Pro does not use any third-party analytics or tracking tools. It does not contain any in-app purchases or advertisements.
Metaburner does not use any third-party analytics or tracking tools. It does not contain any in-app purchases or advertisements.

Metaburner Pro does not communicate with any external servers or services, and it does not access any data on your device beyond what is necessary for the application to function properly.
Metaburner does not communicate with any external servers or services, and it does not access any data on your device beyond what is necessary for the application to function properly.

Apple may collect and use certain usage and performance data from the apps that are available on the App Store. This data is used to help improve the App Store and the overall user experience.

Expand All @@ -16,4 +16,4 @@ You can read Apple's App Store Privacy Policy [here](https://www.apple.com/legal

We use this GitHub Repository for documentation hosting and technical support. You can read GitHub's Privacy Policy [here](https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement).

If you have any questions or concerns, you can [submit an issue](https://github.com/latenitefilms/metaburnerpro/issues), or email us: support@latenitefilms.com
If you have any questions or concerns, you can [submit an issue](https://github.com/latenitefilms/metaburner/issues), or email us: support@latenitefilms.com
14 changes: 12 additions & 2 deletions docs/release-notes.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,15 @@
# Release Notes

### 1.0.0 (21)

**🎉 Released:**
- 3rd January 2024

🔨 **Changes:**
- We've renamed **Metaburner Pro** to just **Metaburner** for eventual release on FxFactory.

---

### 1.0.0 (20)

**🎉 Released:**
Expand Down Expand Up @@ -66,7 +76,7 @@
- 25th December 2023

🔨 **Improvements:**
- We now have a single shared Lua virtual machine, which means you can pass global variables between different Metaburner Pro Titles.
- We now have a single shared Lua virtual machine, which means you can pass global variables between different Metaburner Titles.
- Improved how we update the status in the Final Cut Pro Inspector. It should now update more reliably and faster.
- Updated credits in the main Wrapper application.
- Added a **Reveal Crash Logs** button in the **Controls** section of the Titles Inspector.
Expand Down Expand Up @@ -253,4 +263,4 @@
**🎉 Released:**
- 16th December 2023

This is the first release of Metaburner Pro Beta on TestFlight. Woohoo!
This is the first release of Metaburner Beta on TestFlight. Woohoo!
8 changes: 4 additions & 4 deletions docs/retype.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,23 +4,23 @@ output: .retype
url: metaburner.pro # Add your website address here

branding:
title: Metaburner Pro
title: Metaburner
#label: Docs
logo: static/logo.png

links:

- text: Buy on Mac App Store
- text: Buy on FxFactory
link: /buy/
icon: desktop-download

- text: Issues
link: https://github.com/latenitefilms/metaburnerpro/issues
link: https://github.com/latenitefilms/metaburner/issues
icon: issue-opened
target: blank

- text: Discussions
link: https://github.com/latenitefilms/metaburnerpro/discussions
link: https://github.com/latenitefilms/metaburner/discussions
icon: comment-discussion
target: blank

Expand Down
4 changes: 2 additions & 2 deletions docs/support.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Support

If you run into any bugs, crashes, or you have a feature request, you can post an issue [here](https://github.com/latenitefilms/metaburnerpro/issues).
If you run into any bugs, crashes, or you have a feature request, you can post an issue [here](https://github.com/latenitefilms/metaburner/issues).

If you have any general questions or feedback, you can discuss [here](https://github.com/latenitefilms/metaburnerpro/discussions).
If you have any general questions or feedback, you can discuss [here](https://github.com/latenitefilms/metaburner/discussions).

GitHub registration is free, and this GitHub repository is actively monitored by the developer, [Chris Hocking](https://github.com/latenitefilms).

Expand Down
2 changes: 1 addition & 1 deletion docs/system-requirements.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# System Requirements

Metaburner Pro requires **Final Cut Pro 10.6.5** or later, although we recommend **Final Cut Pro 10.7.1**.
Metaburner requires **Final Cut Pro 10.6.5** or later, although we recommend **Final Cut Pro 10.7.1**.

It requires **macOS Ventura** or later, although we recommend **Sonoma**.

Expand Down
2 changes: 1 addition & 1 deletion docs/uninstall.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# Uninstall

To uninstall Metaburner Pro, simply drag the application to the trash/bin.
To uninstall Metaburner, simply drag the application to the trash/bin.

0 comments on commit 99450ca

Please sign in to comment.