Martinic TG100 Reverb v1.0.0 - classic early-90s reverb plugin (AAX/AU/CLAP/VST2/VST3)
- KVRist
- Topic Starter
- 288 posts since 2 Jan, 2017 from The Netherlands
- KVRAF
- 20890 posts since 22 Nov, 2000 from Southern California
https://www.martinic.com/en/devmartinic wrote: Thu Jul 09, 2026 11:10 pm The TG100 instrument on our development page is basically a development version that runs on the original Yamaha ROMs.
- KVRian
- 1243 posts since 25 Jan, 2017
I'm loving the instrument actually.
It took me a while to figure out how to navigate through patches and alter some key parameters (especially 'ReverbSend' value to get the dry sounds), but I've always been kinda attracted to those 90's ROMplers often heard in videogame soundtracks.
Definitely checking out the reverb plugin as well.
It took me a while to figure out how to navigate through patches and alter some key parameters (especially 'ReverbSend' value to get the dry sounds), but I've always been kinda attracted to those 90's ROMplers often heard in videogame soundtracks.
Definitely checking out the reverb plugin as well.
- KVRist
- Topic Starter
- 288 posts since 2 Jan, 2017 from The Netherlands
Yes, agreed — usability matters.metalifuxx wrote: Thu Jul 09, 2026 8:08 pm 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 faceanytime a plugin developer does that.
Just to clarify: the plugin already stores the last selected view in the DAW project state. So if you leave it on the FX or Settings view, save your project, and reopen it later, it should come back in that same view.
So while there isn’t a separate “default view” preference, the project itself remembers the view you were using.
-
- KVRAF
- 2325 posts since 24 Jun, 2006 from London, England
Perhaps an alternative is to ditch the - & + buttons and replace the 'dry/wet' dial on the right with a 'universal' rotary encoder - you click on a parameter button at the bottom e.g. 'type', 'time' and then that dial changes to adjusting the 'reverb time' and 'reverb type' etc.
- KVRAF
- 20890 posts since 22 Nov, 2000 from Southern California
Those buttons should be knobs.
- KVRist
- Topic Starter
- 288 posts since 2 Jan, 2017 from The Netherlands
- KVRian
- 1243 posts since 25 Jan, 2017
Demoed and bought at the end.
I honestly thought it would sound way more "lo-fi" than it actually does, but it's still an interesting flavor, sitting below the no-brainer pricepoint.
Yes the skeumorphic GUI is unnecessarily hard to use, but the flat alternative is perfectly fine for modern workflow.
I honestly thought it would sound way more "lo-fi" than it actually does, but it's still an interesting flavor, sitting below the no-brainer pricepoint.
Yes the skeumorphic GUI is unnecessarily hard to use, but the flat alternative is perfectly fine for modern workflow.
- KVRAF
- 4893 posts since 3 Jan, 2003 from Vancouver
I really appreciate it. My first computer music experience was Cakewalk on a 486 with a SCC-1 card installed. This brings back good memories.martinic wrote: Thu Jul 09, 2026 11:10 pm 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.
Since it requires Program Change to do more than piano sounds, I thought I'd let you know that the VST3 version ignores Program Change when loaded in Waveform (13.5 Pro or 14 Free). The VST 2 version works fine.
I've just spent some time testing various plugins in various DAWs. Program Change is very rare and inconsistent for plugins. I only found three vendors that include it at all in their plugins and not a single one works consistently across DAW and plugin architecture.
I can use the VST 2 version, but I thought I would let you know regardless. The VST3 versions of AX73 and Elka Panther also aren't affected by Program Change.
Surely there must be consensus by now...
- KVRist
- Topic Starter
- 288 posts since 2 Jan, 2017 from The Netherlands
Thanks! VST3 does not support MIDI, but we hacked it back in, including Program Change. It works in all DAWs that support MIDI, as far as we know. So we will check Waveform and come back with our findings. It was never reported as a bug.pough wrote: Sat Jul 11, 2026 11:48 pm I really appreciate it. My first computer music experience was Cakewalk on a 486 with a SCC-1 card installed. This brings back good memories.
Since it requires Program Change to do more than piano sounds, I thought I'd let you know that the VST3 version ignores Program Change when loaded in Waveform (13.5 Pro or 14 Free). The VST 2 version works fine.
I've just spent some time testing various plugins in various DAWs. Program Change is very rare and inconsistent for plugins. I only found three vendors that include it at all in their plugins and not a single one works consistently across DAW and plugin architecture.
I can use the VST 2 version, but I thought I would let you know regardless. The VST3 versions of AX73 and Elka Panther also aren't affected by Program Change.
