Vox app and AU plugins

#1

Hello guys,

thanks for the Vox app first. To be honest I still use the old small black Vox app on my Mac, since it is more the app I am looking for.

But since OSX 10.9.4 one problem arised with the old Vox app. Maybe you can give me a hint how to fix that, since you are the expert. I don't expect support here from you, the version is outdated - I got this :)

If I play a m4a/mp3 in the old Vox app, since 10.9, it _always_ starts to scan the whole Audio Unit directory first. This is done by the core audio daemon. Also on boot up this nasty daemon always scans the whole audio unit structure again. This is so annoying since I am doing music and like to use your old Vox app as an quick preview player of my productions...

I also wonder why this only happens if I play a m4a or a mp3 in Vox, it happens _not_, if I play a wav... Very strange...

Do you have any idea why this happens?

This leads me into some critics about your recent Vox app for OSX:

There are three reasons why it's unacceptable for me to use it as a music producer (and I really would like to use it):
- On Apple-Q, it won't quit. Instead it stays loaded all the time. I don't need that.
- It loads lot of slower than the old vox app. Also it seems to consume a gigantic amount of ram and after a time, it tends to crash, maybe because of memory leaks?
- It heavily connects to the internet to various online services - Guys, common, are you serious? It also starts the app store daemon all the time (which is activated here only if I need it). This kind of heavy communication is not quite ok if you look to common privacy standards... If you have a contract with the NSA, ok... Or not. But if claim yourself as a serious part of the society, you really should think about it and make all connections OPT-IN and OPTIONAL.

Thanks and greetings

Jurek

#2

The discussion is now public.

#3

Jurek,

How many AU's approx You have in Your Audio unit folder?

Could not get from Your message, which exactly VOX version You are using.
For me this behaviour looks very strange so I would see what can be done if I can find source code for that version.

Regarding command-Q - it should quit, there is some bug that probably prevents it from quitting on Your mac. It's first time I hear about this bug though.

  • it loads slower - sure because we want to serve more users with more inquiries for different features. It takes using more libraries & code. However I must say it takes a fraction of second to load on my 2013 mac book pro, so the problem might be again in core audio scanning things on Your mac. if You don't use iTunes integration and Your library is not very big it should load really fast on modern mac.

  • it connects to internet. Yes, I know VOX makes a lot of connections, and we are revisiting that part. but those connections are not for spying. This is the only way we can collect the usage crash data to help make app better. Having app used on large scale results in so many unordinary usage cases we cannot reproduce in our lab, so we have to rely on online crash/hang data sent back from VOX. It would not be possible to develop the app if not online services. Many, many other well known apps do the same. Other than this, VOX connects to SoundCloud for new tracks and to Loop service, when enabled.

But we will see what we can do regarding this issue You mention and make all this optional.

#4

SOLVED