Martinic TG100 Reverb v1.0.0 - classic early-90s reverb plugin (AAX/AU/CLAP/VST2/VST3)

[martinic]

At Martinic, we’ve just released TG100 Reverb, a focused reverb plugin based on the reverb section of our modeled TG100 sound module.

TG100 Reverb brings the character of classic early-90s algorithmic digital reverb into a modern DAW workflow. It is designed for situations where a modern reverb feels too smooth, too wide, or too anonymous - adding compact digital ambience to vocals, guitars, drums, synths, and retro productions.



TG100 Reverb includes:

• 8 classic reverb and delay types: Hall 1, Hall 2, Room 1, Room 2, Plate 1, Plate 2, Delay 1, and Delay 2

• Early-90s algorithmic digital reverb character

• Modeling based on Martinic’s TG100 work

• Early reflections, pre-delay, high-frequency damping, and dedicated delay memory behavior

• Mono input / stereo output signal path

• Adjustable send, decay, output level, and dry/wet mix

• 16 presets, including 8 presets from the original TG100 sound module

• Support for insert use or bus/send workflows

The original TG100 was released in 1991 as a compact General MIDI sound module. Its reverb could only be used on the internal TG100 sounds. With TG100 Reverb, we extracted that character from our software model and made it available as a standalone effect for any source.

Intro offer: TG100 Reverb is available with 20% off via tg100.nl.

A free 30-day trial is available.

More info / download:
https://www.martinic.com/tg100-reverb

[audiojunkie]

At Martinic, we’ve just released TG100 Reverb, a focused reverb plugin based on the reverb section of our modeled TG100 sound module.

TG100 Reverb brings the character of classic early-90s algorithmic digital reverb into a modern DAW workflow. It is designed for situations where a modern reverb feels too smooth, too wide, or too anonymous - adding compact digital ambience to vocals, guitars, drums, synths, and retro productions.



TG100 Reverb includes:

• 8 classic reverb and delay types: Hall 1, Hall 2, Room 1, Room 2, Plate 1, Plate 2, Delay 1, and Delay 2

• Early-90s algorithmic digital reverb character

• Modeling based on Martinic’s TG100 work

• Early reflections, pre-delay, high-frequency damping, and dedicated delay memory behavior

• Mono input / stereo output signal path

• Adjustable send, decay, output level, and dry/wet mix

• 16 presets, including 8 presets from the original TG100 sound module

• Support for insert use or bus/send workflows

The original TG100 was released in 1991 as a compact General MIDI sound module. Its reverb could only be used on the internal TG100 sounds. With TG100 Reverb, we extracted that character from our software model and made it available as a standalone effect for any source.

Intro offer: TG100 Reverb is available with 20% off via tg100.nl.

A free 30-day trial is available.

More info / download:
https://www.martinic.com/tg100-reverb

Still no Linux support on your products?

[martinic]

Still no Linux support on your products?

Still no Linux support, sorry. It’s something we’re aware people want, but we don’t have short-term plans for it. We’d rather not promise it until we can support it properly. Thanks for keeping the pressure on us though

[Nug Wrangler]

Thanks Martinic

[Vortifex]

Curious UX choice. Why not just make everything on the main skeuomorphic UI scrollable with the mouse instead of having a bland looking 2nd page with scrollable controls? I doubt many users would want to put up with the annoyance or the carpal tunnel risk of the extremely click-heavy classic hardware experience.

[martinic]

Curious UX choice. Why not just make everything on the main skeuomorphic UI scrollable with the mouse instead of having a bland looking 2nd page with scrollable controls? I doubt many users would want to put up with the annoyance or the carpal tunnel risk of the extremely click-heavy classic hardware experience.

Fair question. Our approach for most Martinic plugins is to keep the main Keys/FX screen close to the original hardware, but with the controls actually usable as plugin controls.

At the same time, we don’t want users to be forced into the full “classic hardware” workflow if they don’t want that. That’s why we also provide the Settings screen: all extra parameters are there, and the controls from the Keys/FX screen are available there too in a more direct layout.

This has become the Martinic standard after many years: one screen for the original instrument/effect experience, and one screen for practical, modern plugin control.

The exceptions are Doctor Mix AI Synth and TG100 Tone Generator, which have their own UI logic because they are different kinds of products.

[Teksonik]

Why not allow GUI resize from within the plugin rather than at install or am I missing something?

Did you get expressed permission from Yamaha to host and share and the TG100 Rom files (for the instrument version)?

Is there a purpose for the underscore on the first letter?

tg vERB.png

[martinic]

Why not allow GUI resize from within the plugin rather than at install or am I missing something?

Dynamic GUI resizing from inside the plugin is on our roadmap, but it is not something we are prioritizing right now.

The main reason is host compatibility. Resizing works reliably in all DAWs when the plugin is reloaded after the size change. Live resizing from inside the plugin can work too, but it can also introduce host-specific issues, and we prefer not to ship that until we are confident it behaves consistently.

Did you get express permission from Yamaha to share and host the TG100 Rom files (for the instrument version)?

We have been in contact with Yamaha about this. We are not going to discuss the details of private correspondence or licensing matters on the forum, but it is not something we are treating casually.

Is there a purpose for the underscore on the first letter?

Yes. That is copied from the original TG100 hardware. The original display shows the selected/editable character that way, and we kept that behavior for authenticity.

[Teksonik]

Dynamic GUI resizing from inside the plugin is on our roadmap, but it is not something we are prioritizing right now.
The main reason is host compatibility. Resizing works reliably in all DAWs when the plugin is reloaded after the size change. Live resizing from inside the plugin can work too, but it can also introduce host-specific issues, and we prefer not to ship that until we are confident it behaves consistently.

I have hundreds of plugins that allow dynamic GUI resizing and there is no issue in any DAW I use. Some require the plugin to be reloaded but that's never been a problem.

We have been in contact with Yamaha about this. We are not going to discuss the details of private correspondence or licensing matters on the forum, but it is not something we are treating casually.

I just want to know if I can use the plugin without any legal or moral issues. I'm not asking for any confidential information.

"In contact with" does not equal legal permission which is something you should get before making the ROM available. If you handle this poorly it could jeopardize any future Yamaha emulations from any developer. Handle it correctly and you could open up many other Yamaha emulations like:

While you're in contact with Yamaha see if you can get permission from them to do an SPX-90 emulation.

Yes. That is copied from the original TG100 hardware. The original display shows the selected/editable character that way, and we kept that behavior for authenticity.

That's one thing you could have kept out as it is visually distracting. It's obvious what parameter is being edited without the underscore.

At any rate trying the demo, it's an accurate sounding reverb from the early 90's so if one is looking for that type of sound it's an inexpensive option.

[martinic]

I have hundreds of plugins that allow dynamic GUI resizing and there is no issue in any DAW I use. Some require the plugin to be reloaded but that's never been a problem.

Sorry, you misunderstood. We are not saying it can't be done.

That's one thing you could have kept out as it is visually distracting. It's obvious what parameter is being edited without the underscore.

Knowing ourselves, we could not leave things like this out

At any rate trying the demo, it's an accurate sounding reverb from the early 90's so if one is looking for that type of sound it's an inexpensive option.

Thanks!

[Teksonik]

I have hundreds of plugins that allow dynamic GUI resizing and there is no issue in any DAW I use. Some require the plugin to be reloaded but that's never been a problem.

Sorry, you misunderstood. We are not saying it can't be done.

I didn't misunderstand the part that it's not a priority for you right now and this part: "we prefer not to ship that until we are confident it behaves consistently". I'm simply pointing out that dynamic GUI resize behaves consistently in hundreds of other plugins I own so it shouldn't be a difficult task for such a simple plugin.

We can select a new size by running the installer again but that's a really crude workaround.

I'm just pointing out things that are more likely to discourage me from making a purchase than encourage me to do so.

[metalifuxx]

There’s a fine line between exact authenticity of old hardware and then the chance to make it better and more easily usable/readable/navigable.

If i have to constantly click to a second alternative view panel for key parameters that are easier to edit and in which i can’t make that default view, that’s a fail and no matter how good the sound quality is, it will make me never want to use a plugin like that. To many clicks.

If you had an option to make the easy edit parameter panel as selectable for default when the UX is open (not hidden by a button click or drop down menu) that would make it way easier and less frustrating. This is 2026 and developers have the chance to make things way easier for the user experience. There is no excuse to make things less useable in exchange for old hardware authenticity. That just makes me palm my face anytime a plugin developer does that.

[jamcat]

There’s a fine line between exact authenticity of old hardware and then the chance to make it better and more easily usable/readable/navigable.

Yeah. I tried out the TG100 instrument, but it's really more trouble than it's worth to have to do something as simple as program change through MIDI messages. I found it quite frustrating that you can't click on anything in the GUI to get access to the sound bank or other parameters.

I just don't have the attention span for a 1991 workflow in 2026.

[simmo75]

NM

[martinic]

There’s a fine line between exact authenticity of old hardware and then the chance to make it better and more easily usable/readable/navigable.

Yeah. I tried out the TG100 instrument, but it's really more trouble than it's worth to have to do something as simple as program change through MIDI messages. I found it quite frustrating that you can't click on anything in the GUI to get access to the sound bank or other parameters.

I just don't have the attention span for a 1991 workflow in 2026.

That is fair feedback, and it is also why we are not positioning the TG100 instrument as a normal full Martinic product.

The TG100 instrument on our development page is basically a development version that runs on the original Yamaha ROMs. We decided to share it with the world because some MIDI/module enthusiasts may enjoy having that original TG100 sound available in a DAW, especially for playing old MIDI files or exploring the hardware as it was.

But yes, the workflow is very much a 1991 workflow. Turning it into a modern, fully edited instrument would mean building something closer to a Midi Quest-style editor/librarian interface, with bank browsing, parameter editing, proper patch management, and so on. That is a much bigger project, and realistically not something we plan to spend half a year on for a General MIDI sound module.

That is also why TG100 Reverb is the actual Martinic product here: it takes one useful, characterful part of the TG100 and turns it into a proper modern plugin workflow.

So I completely understand if the TG100 instrument is not for you. It is there for people who enjoy the original ROM-based MIDI module experience, not because we think everyone wants to work that way in 2026.