DMG x AFX : ODDSound MTS-ESP Microtuning System

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

Damon @ ODDSound wrote: Tue Mar 30, 2021 11:45 am
Ploki wrote: Tue Mar 30, 2021 11:07 am In logic - only the first selected scale registers in Hive - if i select load another one (or select it in a loaded folder), hive keeps playing the first selected scale for some reason
That sounds pretty strange, not seen that issue with the Hive beta I've been using. Can you send an email to info at oddsound . com with your OS and Logic version? We'll try to get repro.
no no - i'm stupid, forgot to license the demo. :dog:
works fine.
Image

Post

Because we released Hive 2.1 before Oddsound went live: In Hive, when you use its internal .tun file support, MTS-ESP gets disabled. Switch the internal microtuning off and you'll automagically get MTS-ESP. The user guide will be updated in a few weeks (or months...) once we are able to provide for AAX support on Mac again.

Post

Urs wrote: Tue Mar 30, 2021 11:53 amautomagically
My word of the week so far. :) Need to stop it.

Post

Ploki wrote: Tue Mar 30, 2021 11:49 am no no - i'm stupid, forgot to license the demo. :dog:
works fine.
That's the sort of issue we like, one that doesn't need fixing!

Post

Urs wrote: Tue Mar 30, 2021 11:53 am Because we released Hive 2.1 before Oddsound went live: In Hive, when you use its internal .tun file support, MTS-ESP gets disabled. Switch the internal microtuning off and you'll automagically get MTS-ESP. The user guide will be updated in a few weeks (or months...) once we are able to provide for AAX support on Mac again.
Actually this is really the preferred implementation. To avoid having to ask plug-in devs to save state in their plug-ins, we kept things simple and only have 1 global MTS-ESP tuning table (for now!). So if you want to use multiple tunings toghether, having the option to override in a synth with local tuning via a .tun or .scl file gives you that.

Post

This is pretty cool. I've been having a lot of fun with the micro pitch device in Bitwig and this seems like the next logical step in that evolution. Looking forward to giving it a go.

Small technical critique, don't put anything in the system directory on windows (i.e. system32). This is a bad idea and is guaranteed to come back to haunt you.

Post

This is an awesome piece of work, opened a whole microtonal universe.
I really hope Elektron get on board :)

I bought it tonight and really hope this is a big success and other hardware and software companies jump onboard,

Post

simmo75 wrote: Wed Mar 31, 2021 7:06 am This is an awesome piece of work, opened a whole microtonal universe.
I really hope Elektron get on board :)
This...I'd love an A4 with MTS SysEx support. If you have one...email them and ask!

Post

Dozius wrote: Tue Mar 30, 2021 3:13 pmSmall technical critique, don't put anything in the system directory on windows (i.e. system32). This is a bad idea and is guaranteed to come back to haunt you.
Ohhhh yes, that's a no-no!

Post

EvilDragon wrote: Wed Mar 31, 2021 9:20 am
Dozius wrote: Tue Mar 30, 2021 3:13 pmSmall technical critique, don't put anything in the system directory on windows (i.e. system32). This is a bad idea and is guaranteed to come back to haunt you.
Ohhhh yes, that's a no-no!
We use GetSystemDirectory to let windows tell us where it wants us. That appears to be Microsoft’s recommended practice but we’re happy to review any technical material on the subject if you’d like to guide us otherwise.

Post

AFAIK unless you're doing a system driver, an application shouldn't write into the system folder. Should probably write into ProgramData if you want to be installed for all users, or current user's Roaming folder in a current user only install.

I might be wrong! But a plugin of this kind (VST, AU, AAX...) has nothing to do in system32, that alone is true, I think.

Post

EvilDragon wrote: Wed Mar 31, 2021 12:57 pm I might be wrong! But a plugin of this kind (VST, AU, AAX...) has nothing to do in system32, that alone is true, I think.
We're not at all suggesting putting VST etc. plug-ins in the system folder. They go in your usual plug-in folders. It's the dynamic library that they all load and connect through that goes there (LIBMTS.dll). That is not a plug-in and is independent of plug-in format. It is more akin to a system library, or at least it acts like one, so seemed a logical place to put it that can be reliably accessed.

Post

Gotcha. I guess it's fine then, but I'm aware of a number of other plugins who put their own related DLLs in Program Files and just use them from there (for example, newer NI plugins put D3Dcompiler and qtANGLE DLLs inside their own Program Files folder).

Post

I'm not sure where you saw that this is best practice from Microsoft. This is generally considered bad practice. Even the documentation for GetSystemFunction says "Applications should store code in the Program Files folder and persistent data in the Application Data folder in the user's profile. " This is application code, even if it's shared, it doesn't belong in system.

Just off the top of my head, you will have problems with windows 10 feature releases silently blowing away your DLL. This alone is enough to steer clear.

Post

Please contact companies to let them know about MTS-ESP. I already did with a few. I feel that would increase the chance of this becoming the new standard of microtuning.
Imagine in a year, if every major DAW and synth company has this stuff integrated. A new world..

Post Reply

Return to “Effects”