restfb
RestFB is a simple and flexible Facebook Graph API client written in Java.
It is open source software released under the terms of the MIT License.

Features

restfb has been designed with several objectives in mind. The most important of these are defined as follows.

Zero runtime dependencies

You don't need to include additional libraries in your project. There are no dependency conflicts. In addition, RestFB is highly portable and can be used in both Android projects and normal Java applications.

Maximal extensibility

Although we provide a standard implementation for our core components, each component can be replaced with a custom implementation. This allows RestFB to be easily integrated into any kind of project. Even Android projects are supported.

Minimal public API

TThe RestFB API is really minimal and you only need to use one method to get information from Facebook and one to publish new items to Facebook. We provide default implementations for all the core components, so you can drop the jar into your project and be ready to go.

Simple metadata-driven configuration

Our Facebook types are simple POJOs with special annotations. This configuration is designed for ease of use and can be used to define custom types very easily.

Download

RestFB can be downloaded from Github or used as a Maven dependency. There is also a sample project on Github.

Download from Github

Newest Version of the library is available from RestFB's home on Github.
View the changelog here.

Download from Maven

RestFB is a single JAR - just drop it into your application and you're ready to go. Download it from Maven Central:
maven central restfb version

Restfb example

You can find a sample project on Github. This project can help you get up and running quickly.

Transvst Fixer -

: Go to your Pro Tools plugin directory (typically C:\Program Files\Common Files\Avid\Audio\Plug-Ins ). Run the Fixer : Open your TransVST-fixer.exe tool.

is a specialized utility developed by Sugar Bytes designed to adapt VST plugins into the format for use within Avid Pro Tools

If you are a music producer running Avid Pro Tools, you have likely run into a frustrating wall: your favorite refuse to load because Pro Tools exclusively requires the AAX format . While the legendary utility Sugar Bytes TransVST was designed to solve this exact problem by wrapping VSTs into AAX formats, the software faces compatibility hurdles in modern operating systems, forcing users to rely on a community-made "TransVST fixer" executable or alternative routing workflows. transvst fixer

Which would you like?

Whether it is a specialized proofreader, a copy editor, or a software tool designed to smooth out AI errors, the transcript fixer is the unsung hero of the information age. They ensure that when we speak, our words are not only heard but read exactly as we intended. : Go to your Pro Tools plugin directory

Enter : the specialized utility designed to "patch" these wrapped plugins so they actually show up in your session. What is TransVST Fixer?

Today, investing in native AAX plugins or adopting modern bridging tools like Blue Cat's PatchWork will save you hours of troubleshooting, crashes, and manual patching. The TransVST Fixer is a piece of audio history—powerful for its time, but best left in the past as a reminder of how far plugin compatibility has come. While the legendary utility Sugar Bytes TransVST was

Enter and its companion utility, TransVST Fixer . This software duo became an essential workaround for countless producers working with Pro Tools 12 and earlier versions of Pro Tools 10 and higher, providing a method to bridge the gap between the versatile VST ecosystem and Pro Tools' proprietary AAX format.

This step is critical. Because TransVST was originally designed with an older architecture, it sometimes incorrectly sends plugins to the 32‑bit (x86) folder. A 64‑bit version of Pro Tools will not scan this location for plugins, so moving the files to the correct 64‑bit folder is essential.

The TransVST_Fixer.exe acts as a patching tool. Users drag wrapped plugin folders into the executable to modify the underlying binaries, essentially "fixing" the registration so they are recognized by the host software. 3. Usage & Workflow The typical workflow for an audio engineer involves: Scanning: Using TransVST to scan existing VST folders. Wrapping: Generating an AAX equivalent.

If a plugin developer never compiled an official AAX version of their software, that plugin cannot natively be opened inside Pro Tools.

The restfb Team

Mark Allen picture

Mark Allen

Founder

Norbert Bartels picture

Norbert Bartels

Maintainer and Lead Developer

many contributors picture

many contributors

restfb source code is placed on Github and the library itself evolves with the help of many great people. A lot of Github users contribute to restfb. We get many hints and questions, and of course many pull and feature requests. And we'd like to say thank you to everyone who has helped along the way!

Sponsors

The development of restfb is sponsored by these great companies and individuals. If you also like to sponsor us, please check the sponsor button on our RestFB Github page or send us a short note .

Licensing

restfb is open source software released under the terms of the MIT License:

Copyright (c) 2010-2025 Mark Allen, Norbert Bartels.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.