OmniTag - Tagging Engine for Third Party Omnisphere Libraries [50% off through Dec 31, 2022]

[aMUSEd]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

[noiseboyuk]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

I think the fundamental issue is this - Omnitag conforms to Spectrasonics standards. That's the way it's designed to work.

Just as there are hundreds of different categories from different developers, there are hundreds of different Types, most of which will have just a few patches in them and are therefore really hard to browse. So there's always a trade off - you can't have things set by individual developer, and then expect them to conform to everyone else's, it's pretty much one or the other.

[marclawsonmusic]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

You know what, aMUSEd, you don't seem like a happy customer, so let me just give you a refund. This product is not for you if you're just going to go on the forums and complain about it.

Please contact me at support at omnitag dot net

[zvenx]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

I think the fundamental issue is this - Omnitag conforms to Spectrasonics standards. That's the way it's designed to work.

Just as there are hundreds of different categories from different developers, there are hundreds of different Types, most of which will have just a few patches in them and are therefore really hard to browse. So there's always a trade off - you can't have things set by individual developer, and then expect them to conform to everyone else's, it's pretty much one or the other.

This!!

rsp

[Echoes in the Attic]

OmniTag worked well here. I do think Spectrasonics tagging system is insane, but at least everything is using the same insane categories now.

[aMUSEd]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

You know what, aMUSEd, you don't seem like a happy customer, so let me just give you a refund. This product is not for you if you're just going to go on the forums and complain about it.

Please contact me at support at omnitag dot net

No it's fine thanks - I am honestly not trying to cause problems, I was just trying to fix what had gone wrong and in the process got a better idea of how this works and where the real problems lie with Omnisphere tagging. I guess I thought originally most of the tagging issues in Omnisphere were due to third party sound designers proliferating redundant tags, and maybe it is for some, but I also realise now that this doesn't seem to be an issue with the SD's whose work I own, if anything they have been more logical and economical in their choice of tags than Spectrasonics. I find that interesting, but I have a better understanding of what Omnitag is doing now, and clearly does what it was meant to do so I have no reason to return it and won't say anymore on this. Merry Xmas.

[zvenx]

OmniTag worked well here. I do think Spectrasonics tagging system is insane, but at least everything is using the same insane categories now.

Which is the whole point of the app... Uniform insanity .

rsp

[noiseboyuk]

Uniform insanity .

Now THAT's a tag line...

[GMusic]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

You know what, aMUSEd, you don't seem like a happy customer, so let me just give you a refund. This product is not for you if you're just going to go on the forums and complain about it.

Please contact me at support at omnitag dot net

No it's fine thanks - I am honestly not trying to cause problems, I was just trying to fix what had gone wrong and in the process got a better idea of how this works and where the real problems lie with Omnisphere tagging. I guess I thought originally most of the tagging issues in Omnisphere were due to third party sound designers proliferating redundant tags, and maybe it is for some, but I also realise now that this doesn't seem to be an issue with the SD's whose work I own, if anything they have been more logical and economical in their choice of tags than Spectrasonics. I find that interesting, but I have a better understanding of what Omnitag is doing now, and clearly does what it was meant to do so I have no reason to return it and won't say anymore on this. Merry Xmas.

For what it's worth I didn't see aMUSEd as complaining, but rather just expressing a conflict and uncertainty of what is going on with the tagging process. I think at the end of the day most of us posting here are long time Omnisphere fans just wanting to make it better in anyway possible

Maybe they'll hear our pleas for a better tagging system and implement something in Omnisphere 3.0.

[zvenx]

I am in two minds to responding, because it has been resolved.
But.
The whole point of the app is to:
Comform third party banks to Spectrasonics specifications..
That is the whole point of the app.
Seems he/she wanted it to do something else?

rsp

[Echoes in the Attic]

Oh well that didn't't work for me either - I tried just conforming one of the Luftrum banks - it created categories when none were there to be sure, but it also messed up the types by adding a bunch of useless Spectrasonics types to what was a nice simple organisation by Luftrum. Also putting the patch folders back in the root of Patches rather than in subfolders by developer stops me using categories as a way to browse patches which I was doing since categories and types are basically the same thing anyway I had sacrificed categories to be able to do this which means I don't have to browse patch libraries using the dropdown menu

You know what, aMUSEd, you don't seem like a happy customer, so let me just give you a refund. This product is not for you if you're just going to go on the forums and complain about it.

Please contact me at support at omnitag dot net

No it's fine thanks - I am honestly not trying to cause problems, I was just trying to fix what had gone wrong and in the process got a better idea of how this works and where the real problems lie with Omnisphere tagging. I guess I thought originally most of the tagging issues in Omnisphere were due to third party sound designers proliferating redundant tags, and maybe it is for some, but I also realise now that this doesn't seem to be an issue with the SD's whose work I own, if anything they have been more logical and economical in their choice of tags than Spectrasonics. I find that interesting, but I have a better understanding of what Omnitag is doing now, and clearly does what it was meant to do so I have no reason to return it and won't say anymore on this. Merry Xmas.

For what it's worth I didn't see aMUSEd as complaining, but rather just expressing a conflict and uncertainty of what is going on with the tagging process. I think at the end of the day most of us posting here are long time Omnisphere fans just wanting to make it better in anyway possible

Maybe they'll hear our pleas for a better tagging system and implement something in Omnisphere 3.0.

The current tagging system is their improvement based on all of us complaining about the tagging in Omnisphere 1. They made it infinitely more of a mess. So I’m hoping they don’t “improve” it anymore in Omnisphere 3!

[yellowmix]

Soundsdivine notably uses "RHY" prefix for what would go into ARP + BPM currently. I forced Omnitag to conform them by renaming all of them with a BPM prefix.

Omnitag could check for all-caps 2- and 3-letter prefixes it doesn't recognize and if it finds more than 1 preset with the same prefix perhaps it could ask the user what category they best fit in (optional in settings)? Would also make it more future-proof. Even better, if the prefix matching to category were openly configurable.

[noiseboyuk]

Interesting idea, thanks Yellowmix. I know Marc has added a ton of different prefixes over time, but you’re right that there seems to be no limit to the possible variations…

[marclawsonmusic]

Soundsdivine notably uses "RHY" prefix for what would go into ARP + BPM currently. I forced Omnitag to conform them by renaming all of them with a BPM prefix.

Thanks for the info, yellowmix. I added this prefix to the list so it will be in the next release.

Not sure if I'll put in the effort for a screen or other way for folks to manage their own list of prefixes. With <200 users, OmniTag has turned out to be a VERY niche product. I think my effective hourly rate for building this thing is about $5/hr. At this point, I would make more money working at McDonalds than working on OmniTag.

[zvenx]

...
sorry.
rsp