Nomad Factory prices have been re-evaluated

[phaded]

Indeed, actions speak louder than words, we all know, what have been said, then and now, and all the noble intentions lately

You know, maybe a hair of slack needs to be extended here. I feel concern was justified in this thread and subsequently properly addressed. Shouldn't a bit of time be given to let the new team at NF get their legs under them?

And it has to be said again- it was not just a business associate that they lost, it was the primary developer of Nomad Factory plugins, and a dear friend to many.

You cannot plan for these kind of losses in life. I would imagine in addition to the challenge of diving into someone's code that there would be a strong sense of heavy-heartedness in doing so considering the circumstances.

So give a little credit for the Plugivery team for showing up and being forthcoming and transparent thus far. .

its the hole culture and way of thinking that need to change, not just fixing the code, btw, most likely it would be both better and easyer to build new code from buttom up, there have been plenty of years, also before the tragic illness and loss,..

I'm completely talking out of my ass here because I have no idea whats going on with the code, but someone noted the prior release of Magma had better stability, and afaik so does the 'close relative' of Magma (Plug n Mix Chainer). If that is the case then I would venture to guess it is likely fixable once the Devs get their heads wrapped around Bernie's coding. Again- just speculation, but overall I think a little benefit of the doubt I think is in order.

[jens]

No in all seriousness - did ANYONE of you actually try to contact the support and ask for a previous installer?

Why would I? I rarely ever contact support. I know some people love to mail developers, I don't.
Instead of talking they should simply act and make the newest a lot less buggy version available
and be done with it. (together with a mail to Magma license-owners and some info on the website that says "if you use the following hosts ... please use the installer for V1.x as it came to our attention, that unfortunately certain bugs crept into the latest version yadda yadda yadda")

Something along these lines - or they could simply list the bugs and say "if you come across the following problems... then please use...".
Something like this would imo clearly be the decent thing to do (and not much work - in any case A LOT less work than having to keep answering e-mails from customers who can't use the shit they paid for).

In between my previous mail and now they could easily have done that twice already - let's say during a coffee-break.

And I'm pretty sure that's what the guys from Klanghelm, Hornet, Valhalla, Audiority, etc. would do (if they couldn?t provide a quick fix - but then again none of their plugins are ever nearly that buggy - because they test them properly before the offcial release) - all without a dedicated support team.

But that would of course mean having to officially admit errors in the product - and part of the typical (US-style) corporate bullshit is to never do that.

[phaded]

Why would I?

Because your product isn't working for you?

...

..

.

But that would of course mean having to officially admit errors in the product.

I think they already did. But more importantly-

...and part of the typical US-style corporate bullshit is to never do that

[rasmusklump]

I am done with Nomad.
I still have a Blue Tubes fx bundle that I can no longer activate since years as they don't find me in their database...

[jens]

...and part of the typical US-style corporate bullshit is to never do that

I wrote "US-style", not "US-based" - if you don't grasp the difference, then what can I do?

Why would I?

Because your product isn't working for you?

I'm not gonna beg for what I paid for...

and if they have time to answer my individual support request, then they have time to make it available for everyone. Support e-mails are systematically inefficient and should be a last solution to individual problems - my problem however isn't an individual one.

[Compyfox]

Okay, I just checked my backup HDD's, but apparently, I only snagged v1.0.1 of MAGMA - and that is from 2012. I don't think that this would be of any help to you. And sadly, the "whole bundle" doesn't have Magma as installer (and I do happen to have lost a couple of in-between versions as well in terms of backups... hm...).



Still... don't get me wrong, but some of your comments are a bit unreasonable. At least to me.

Why would I? I rarely ever contact support. I know some people love to mail developers, I don't.

See, and this is a problem IMO. People take for granted that developers read web boards like KVR and GS. Of course they are present in some form, to "control the hype", but without contacting support in parallel, nothing can advance.

Yes, I have my own fair share of "support stories", but I always try to get in touch with the devs first. Unless they clearly state "this is(!) our support section" - then that's definitely a problem (been there...).

Instead of talking they should simply act and make the newest a lot less buggy version available
and be done with it. (together with a mail to Magma license-owners and some info on the website that says "if you use the following hosts ... please use the installer for V1.x as it came to our attention, that unfortunately certain bugs crept into the latest version yadda yadda yadda")

Again, I'd cut them some slack with the workload and what happened in recent months.

Though there is a limit to waiting times of course.

In between my previous mail and now they could easily have done that twice already - let's say during a coffee-break.

Yes they could, but on the other hand... maybe something got lost in translation as well. So throwing another mail and asking what's up wouldn't hurt.

which brings me to...

and if they have time to answer my individual support request, then they have time to make it available for everyone. Support e-mails are systematically inefficient and should be a last solution to individual problems - my problem however isn't an individual one.

We don't know at this point how long the backlog of support inquiries is. Then again, if it's longer than 3 weeks for you, maybe ask them again. Like "hey, I filed a report, did you get it?". Had that several times with other companies, got an apology and (mostly) immediate fix (exceptions are the norm of course)...

And I'm pretty sure that's what the guys from Klanghelm, Hornet, Valhalla, Audiority, etc. would do (if they couldn?t provide a quick fix - but then again none of their plugins are ever nearly that buggy - because they test them properly before the offcial release) - all without a dedicated support team.

I can only speak for Klanghelm and Hornet. But sometimes a "lower version" isn't that better either. Still... if you ask the company in question, you can get access to an earlier version. Doesn't mean a need for "mass distribution" - which is the main point of argument for a lot of support topics here: "one person with severe issues among many users that can use the software in question". (I've been there, SEVERAL times)

I get your point, I get your frustration. HOWEVER... this is why I usually keep backups of older versions. Especially during beta testing for companies. So my first question would be: do you have a backup? It looks like you don't. So the next question I'd ask at KVR would be "who has an older version than v #xyz and can help out?". I tried to help out, but I only have v1.0.1 lying around.

But that would of course mean having to officially admit errors in the product - and part of the typical (US-style) corporate bullshit is to never do that.

They admitted that something his wrong and needs to be addressed - when, they just can't tell (yet).

I can't (and won't) comment on the other part of this commentary as this can happen for EVERY company no matter where they are based, and what "corporate style" they sport.

I am done with Nomad.
I still have a Blue Tubes fx bundle that I can no longer activate since years as they don't find me in their database...

This is a special case - and I've had this a couple of times myself with other companies (database loss). If you happen to still have the original purchase data, I'd get in touch with them again and say "you database doesn't list me, I bought it legit - please add/unlock me - here is confirmation of my purchase".

Doesn't sound like a big problem to me.
Unless you don't have these infos anymore (can happen, loss of purchase mail, etc)... then it's turning out to be tricky of course.





Looks people - again, I do understand your frustration and annoyance. I'm in the same boat as you as longtime NF user. But at least the new team tries to fix things, and there are very capable people behind the support. So maybe try to get in touch with them again.

[jens]

this is why I usually keep backups of older versions. Especially during beta testing for companies. So my first question would be: do you have a backup? It looks like you don't. So the next question I'd ask at KVR would be "who has an older version than v #xyz and can help out?". I tried to help out, but I only have v1.0.1 lying around.

Well, actually I think I'd take that 1.01 over the current version if it's stable. If it is, it means it can be used, which is more than I can say about the most recent version.

I never had the chance to download an earlier version b.t.w., since when I purchased Magma, the current version had already been released.

[Compyfox]

Maybe check your PM folder?

[audiosabre]

Magma, I have 1.5 & 1.6.4, win64.

NF bundle - 5.0 win32 & 64, 5.1 win32 & 64.

[Fleer]

Great posts Compyfox, the voice of reason

[HM]

On a more constructive note What else is there on the market, loading diffrent vst-effekts in a matrix, with free assignable controllers, modulation, midi, etc, etc, and automatation working ALSO, so a proffesional inviroment, and total recal is possible ????

[Compyfox]

MuTools MUX? (Mac port in the making)

[Ashley_Plugivery]

Hi all,

Our team had a great meeting yesterday to discuss updating products post our acquisition of Nomad Factory, fixing niggly bugs and reskining with new features etc. Our developers have "a lot" of hard drives to dig through though as mentioned, to locate Bernie's source code and resources, so this may take some time. Nevertheless, we're on the case... 100%!

I've uploaded older 1.6.5 to my Dropbox account in the interim if anyone should need it, to keep our page clean as we work updates...

Magma 1.6.5 [Mac]
Magma 1.6.5 [Win 32] | [Win 64]

Please note that there may well be inherant issues with older versions too (as they were built on older framework, not that used for 1.6.6). We recommend you back up your sessions before using any earlier version(s) and advise all to use the latest and most up-to-date 1.6.6.

All the best,

[TEKing66]

Hi All,

First, I want to thank Ashley for the previous post and the re-assurance of the situation.

Next, I'd like say what I think is the best way the users of any of Nomad Factories plugins to move forward at this point.
Simply use the software and report the bugs. Keeping a nice little log of what you were doing, what was loaded, the host, and exactly what happened just before the crash. Then send that log along with the bug report, sometimes such info goes along way it catching the bug.

Now, I'd like to add that I do like what Magma brings to the table, bugs aside. As an owner of MUX as well, which is also very capable for the same purpose (and more). Personally, I find that I prefer the workflow in Magma a bit more than MUX, and I much prefer the built in effects in Magma over those in MUX. That being said, I still use MUX simply because it is much more than what Magma was ever intended to be and both fit into my workflow very nicely. Given those two and Studio One's built in plugin chaining, I have three options for setup my sound mangling, over the top, out of this world plugin chains (sometimes I get a bit crazy with my guitar signal chains).

Just my 3 cents worth!

[TEKing66]

Edit: Oops, double post