Tone2 Warlock (synthesizer) - available now!

[Markus Krause]

The directory is write-protected. It is not necessary to run the host or computer in admin mode. You can also right-click on the directory and set the permissions. Or he can copy the bank manually to the loction

[Teksonik]

Yes the problem with running FL Studio as Admin is:

Warlock 021121-2.png

[chk071]

@Markus: I would still argue that it's better style to write the user files to a directory in the installing user's Documents folder. Not everyone is so computer savy that he knows how to change a directory's write-protection.

Your decision, of course. It's your synth. I'm just saying that I don't consider it good practices to write to folders which aren't really used for user data, for the reasons I stated. It might be no problem with VST2, because, in most cases, people have a custom VST2 folder, which isn't in a write protected directory, but, VST3's are in C:\Program Files\Common Files\VST3, so...

[Teksonik]

Or he can copy the bank manually to the loction

That works but is this really the best solution ? After seeing how people complain about patch and bank handling in other plugins I imagine this will generate some complaints as well.

[fisherKing]

the mac installer (at least, here) does not install the AU (the vst3 is installed). so, nothing in logic. just reporting this! will be patient (but i do want to get a shot at the demo contest)...

EDIT: so, no AU (ie, not available for logic). shame (i mean, icarus2 works here). so it goes. anyway, will still check out the demo contest entries...

[Teksonik]

@Markus: I would still argue that it's better style to write the user files to a directory in the installing user's Documents folder. Not everyone is so computer savy that he knows how to change a directory's write-protection.

I know how I'm just not going to bother to save a simple bank of patches. Saving to another location and moving to the VST3 folder works but is probably the worst bank handling method of all the hundreds of plugins I own.

Oh well it's not that big of a deal. Saving and moving a bank only takes a few seconds and there are only three User slots so it's not something you'll be doing all that often.

But as I said I imagine this is going to generate some complaints.

[Markus Krause]

Big drama because of the smallest niggles. As always on kvr.

Right click on the directory or the file. Then choose security. Enable 'write' for the user.
https://www.online-tech-tips.com/comput ... s-windows/

The installer of the next update will fix possible permission problems for user created soundbanks. The issue is a non-issue

[DMuzik]

What?! Why no AU?

[Markus Krause]

Because Apple introduced M1 chips and I am not able to create a stable AudioUnit for these machines. It is currently impossible to find the source of the problem. AUval (a tool provided by Apple) can not be debugged. Neither by myself nor by Steinberg.
Reference: https://forums.steinberg.net/t/unable-t ... l/693455/2

[revvy]

Man, I dodged a bullet here.

[AnX]

true dat

[Teksonik]

Big drama because of the smallest niggles. As always on kvr.

Not all feedback is positive Markus. Don't start insulting KVR. Without it I would have never purchased Warlock.

The installer of the next update will fix possible permission problems for user created soundbanks. The issue is a non-issue

There wouldn't be an issue at all if you hadn't chosen the VST3 folder for a place to put Warlock banks instead of the Documents or Program Data folders like many if not most other developers do. None of the hundreds of other plugins I own put presets or banks into the VST 3 folder.

Requiring people to change permissions for a folder no matter how simple that task is just to save a bank is not the right way to do things. It might have been convenient for you but is in no way convenient for your paying customers.

The fact that you're issuing a "fix" means there was something broken.

So let's all just chill out and try to keep a professional exchange going on here.

[CinningBao]

Well, I completely missed the 'no AU' line in this thread or on the share-it page.

@Markus, are you actually stating that there is no AU for this product anywhere? Can you at least compile it for Intel?

If not, I'll be asking for a refund, which is a shame because I used Firebird in literally every thing I wrote back.. then (some years ago)

[AnX]

If not, I'll be asking for a refund, which is a shame because I used Firebird in literally every thing I wrote back.. then (some years ago)

warlock can load firebird banks, so you should be OK to keep using firebird.

no point buying the same product twice, unfortunately you already have

[fisherKing]

Because Apple introduced M1 chips and I am not able to create a stable AudioUnit for these machines. It is currently impossible to find the source of the problem. AUval (a tool provided by Apple) can not be debugged. Neither by myself nor by Steinberg.
Reference: https://forums.steinberg.net/t/unable-t ... l/693455/2

not sure what's happening. a lot of developers (fabfilter, for example) have created AU versions that work with M1 & intel. anyway, would be great if this gets sorted; if not, so it goes. good luck with it either way, seems like ppl like it.