VPS Avenger 2.4 [RELEASED - FAQ in OP]

[Musical Gym]

Will Friggin Audio be releasing anything else this year?

[moonchunk]

[my original post] How do I get the expansions I bought installed. When I drag them in I get errors, then I go back into V Man and I see that the files I downloaded and activated (green ) are now yellow, and the files do not any longer appear in the external drive I had set up?

[Now I've "fixed" it - but only by giving up on using the external location. It seems that the new content folder was created in the only location, but the expansions were all downloaded to the default location anyway (ProgramData folder). So I tried to enter the default location (ProgramData folder), replacing my prior external drive folder. At which point I got a prompt asking if I would like to move the old data (unfortunately not what I just downloaded) to the new (default) location. I clicked "cancel" (not sure if it was correct, but I immediately panicked because it seemed to have a mind of it's own and started the process of overwriting my new files in the ProgramData folder. So in the file write window I clicked the quit button immediately. Hopefully nothing bad was done to the new files.

Then, after immediately exiting, V-Man refreshed and the yellow text is now back to green. So I went into the DAW and opened Avenger 2 and now the expansions DO show up. But I need some stress relief.

I guess I'll just leave the stuff here since it doesn't seem to work with an external drive and is super scary to work with.

[Oops, unfortunately now I'm plagued with missing content in the new Expansions.]

You just had to repoint it in V Manager to your old location on External Drive. (Content Location/Choose)
I think after that I restarted V Man and everything was in place as before.

V-Man was already pointed at my original folder when I reopened it after getting the initial error (this said something about a "write" error which signaled me to make sure my anti-virus was off, which it was - This error was while attempting to drag the contents because I couldn't figure out what else to do when the expansions were not showing.) - in fact my original folder location (external S. drive) was prepopulated for me conveniently. Unfortunately the contents were marked yellow later, when I went back in to investigate not seeing my expansions. So I re-loaded V-Man and (after being marked green) all the downloads were then marked yellow.

The external location did show some changes with yesterdays date when I checked before giving up on using an external location. Possibly there's something about the interface I don't understand which makes it default to the old location for part of the installation, but not to prompt the user and ask if they want to change the location for "new" expansion downloads. That would make sense.

[moonchunk]

Hello friends, please help a visually impaired guy out.

I'm not finding the drum sequence files - which is where I would place my user drum sequences - I don't find them in any "drum sequences" folder in ProgramData under Vengeance (which is where my expansions are deposited). I also checked a few other places.

The manual states: "There are folders for drumkits and drum sequences in your Avenger folder."
What I have in ProgramData does have drum kits, but not drum sequences or Shapes, etc.

I think I figured this out - apparently you can only load these things if you create your own expansion file with them, is that right?

[noiseboyuk]

[

I've raised it a lot of times as well - not one single confirmation that they have contacted support. Why?

I have contacted support last year about Logic and Avenger.
I had idle cpu jumps, glitches or playhead jumping back while playing.
and they said that they got similar tickets but they did not have these issues with their Logic Rig, so hard to pinpoint.
Funny thing is these used to happen on my Full speced M1 Max Macbook Pro but not on my plain M1 Macbook Air.

With Avenger 2 I get occasional CPU spikes with dense patches but nothin terrible like before.

i alo use Automatic Setting for Processing Threads in Logic. Found out that selecting the highest setting degrades the performance.

This is grea - somone who DID contact support! And that sounds like you have very useful info. Have you passed that most recent info on to them?

To repeat - Omnisphere has had a very slow GUI that only affects a subset of customers, that they've never been able to reproduce. Has been going on for years. I persisted with their support, took dozens of tests over a long period of time, and several weeks ago they repro'd for the first time. They're now working on a fix.

This is how you do it. However slow or frustrating, so keep at it with them.

[medienhexer]

[

I've raised it a lot of times as well - not one single confirmation that they have contacted support. Why?

Funny thing is these used to happen on my Full speced M1 Max Macbook Pro but not on my plain M1 Macbook Air.

That is consistent with the issue the JUCE developers ran into. No issues with the low-end M1, whereas on the high performance M1s, there seem to be just too many efficiency cores for the CPU to be forced to use the performance cores for live tracks.

[Hanz Meyzer]

Jfyi i think logic has a similar mechanism as asio guard in cubase… maybe let’s call it dynamical latency or so. That’s why and also for comparison reasons, please test with bitwig (demo) instead, since it provides the best cpu monitoring.

[medienhexer]

[

I've raised it a lot of times as well - not one single confirmation that they have contacted support. Why?

I have contacted support last year about Logic and Avenger.
I had idle cpu jumps, glitches or playhead jumping back while playing.
and they said that they got similar tickets but they did not have these issues with their Logic Rig, so hard to pinpoint.
Funny thing is these used to happen on my Full speced M1 Max Macbook Pro but not on my plain M1 Macbook Air.

With Avenger 2 I get occasional CPU spikes with dense patches but nothin terrible like before.

i alo use Automatic Setting for Processing Threads in Logic. Found out that selecting the highest setting degrades the performance.

This is grea - somone who DID contact support! And that sounds like you have very useful info. Have you passed that most recent info on to them?

To repeat - Omnisphere has had a very slow GUI that only affects a subset of customers, that they've never been able to reproduce. Has been going on for years. I persisted with their support, took dozens of tests over a long period of time, and several weeks ago they repro'd for the first time. They're now working on a fix.

This is how you do it. However slow or frustrating, so keep at it with them.

Thing is: neither Eric nor any of the developers communicate directly on kvr. In this thread, the developer advertises and communicates directly. When you contact support only, there is a high risk that you will always be treated like you're the only one having that issue. Which very obviously is not the case.

Here, we can exchange information which will hopefully help find the issue and/or help the developer improve on the Mac OS implementation. If there are any questions or if they need someone to verify an update fixes the issue, just DM us. Whoever beta-tests for this company, seems to have either missed or not experienced or given up on this topic.

To me, it feels like they are pretty handy in the Windows environment, but Mac OS appears a little inconsistent with system standards (download default is desktop, settings don't seem to be stored in .plist files, I'm pretty sure they don't subscribe to change notifications from the file system, hence the manual refresh, the DMG is not ejected after installation and perhaps they don't use the latest and greatest in Mac OS scheduling, yet).

Which is why I hope they investigate the information discussed in the JUCE forum. Because that's completely Mac OS specific.

[Hanz Meyzer]

One question: does vps avenger 2 support audio rate modulation?

[noiseboyuk]

Jfyi i think logic has a similar mechanism as asio guard in cubase… maybe let’s call it dynamical latency or so. That’s why and also for comparison reasons, please test with bitwig (demo) instead, since it provides the best cpu monitoring.

People are not going to install another daw to do tests, that's not our job.

Also ASIOguard can't have anything to do with this, as it doesn't work on live tracks, the exact scenario some are getting here.

[ozinga]

This is grea - somone who DID contact support! And that sounds like you have very useful info. Have you passed that most recent info on to them?

Not yet,
Still testing and comparing it with Logic against to Live, Studio One and their support system changed I think. My old tickets are gone so cannot do a follow up. No option to create new support ticket anymore either. Just email link for support inquiries.

[noiseboyuk]

Thing is: neither Eric nor any of the developers communicate directly on kvr. In this thread, the developer advertises and communicates directly. When you contact support only, there is a high risk that you will always be treated like you're the only one having that issue. Which very obviously is not the case.

Here, we can exchange information which will hopefully help find the issue and/or help the developer improve on the Mac OS implementation. If there are any questions or if they need someone to verify an update fixes the issue, just DM us. Whoever beta-tests for this company, seems to have either missed or not experienced or given up on this topic.

To me, it feels like they are pretty handy in the Windows environment, but Mac OS appears a little inconsistent with system standards (download default is desktop, settings don't seem to be stored in .plist files, I'm pretty sure they don't subscribe to change notifications from the file system, hence the manual refresh, the DMG is not ejected after installation and perhaps they don't use the latest and greatest in Mac OS scheduling, yet).

Which is why I hope they investigate the information discussed in the JUCE forum. Because that's completely Mac OS specific.

They're not going to follow a thread and start DMing people. That's not how support works.

If you get rubbish replies from support, by all means complain about it here. Refer to threads here with support. But expecting or demanding that they follow us here is crazy. Manuel does not look after the tech side anyway, he can't weigh in on it all. I'm glad to have him here, but he repeatedly says to use support for, well, support.

[noiseboyuk]

This is grea - somone who DID contact support! And that sounds like you have very useful info. Have you passed that most recent info on to them?

Not yet,
Still testing and comparing it with Logic against to Live, Studio One and their support system changed I think. My old tickets are gone so cannot do a follow up. No option to create new support ticket anymore either. Just email link for support inquiries.

Go for it, however imperfect. All those tests will be helpful.

[ozinga]

That is consistent with the issue the JUCE developers ran into. No issues with the low-end M1, whereas on the high performance M1s, there seem to be just too many efficiency cores for the CPU to be forced to use the performance cores for live tracks.

That is helpful to know that it is known, thanks!
Although my M1 Max has 8 performance and 2 efficiency cores unlike Air which has 4/4.

[medienhexer]

Thing is: neither Eric nor any of the developers communicate directly on kvr. In this thread, the developer advertises and communicates directly. When you contact support only, there is a high risk that you will always be treated like you're the only one having that issue. Which very obviously is not the case.

Here, we can exchange information which will hopefully help find the issue and/or help the developer improve on the Mac OS implementation. If there are any questions or if they need someone to verify an update fixes the issue, just DM us. Whoever beta-tests for this company, seems to have either missed or not experienced or given up on this topic.

To me, it feels like they are pretty handy in the Windows environment, but Mac OS appears a little inconsistent with system standards (download default is desktop, settings don't seem to be stored in .plist files, I'm pretty sure they don't subscribe to change notifications from the file system, hence the manual refresh, the DMG is not ejected after installation and perhaps they don't use the latest and greatest in Mac OS scheduling, yet).

Which is why I hope they investigate the information discussed in the JUCE forum. Because that's completely Mac OS specific.

They're not going to follow a thread and start DMing people. That's not how support works.

If you get rubbish replies from support, by all means complain about it here. Refer to threads here with support. But expecting or demanding that they follow us here is crazy. Manuel does not look after the tech side anyway, he can't weigh in on it all. I'm glad to have him here, but he repeatedly says to use support for, well, support.

Why are you on such a mission? Yes, that’s how support works. If a developer wants to benefit from the free marketing provided by product announcements in a forum of users, they better be opening a communication channel back. We‘re not just here for free hype, but for a realistic view of a product, especially when there’s no demo.

I know that the big players have either social media people monitoring the forums or sales people reporting back with issues. If you’re a small developer, you typically have VERY short communication paths. If you’re not the developer, you literally sit next to them.

And sorry, but statements like ‚people are obsessing over cpu spikes‘ make me really question the 200 bucks investment I made. I think it’s necessary to call out such position openly.

[Hanz Meyzer]

Jfyi i think logic has a similar mechanism as asio guard in cubase… maybe let’s call it dynamical latency or so. That’s why and also for comparison reasons, please test with bitwig (demo) instead, since it provides the best cpu monitoring.

People are not going to install another daw to do tests, that's not our job.

Also ASIOguard can't have anything to do with this, as it doesn't work on live tracks, the exact scenario some are getting here.

No, as far as i understand asio guard, it will prerender all the non selected tracks, so a test with it enabled is completely useless. Simply deactivate it.

Also bitwig demo is installable with 5 clicks or so, unlike cubase. Simply delete it again after test. I really have no idea how lazy the people are you are mentioning…