Agonizer agonies -- is it just me?

Zerozerozero

@day_empire said:

@gravytop said:
I fired up Agonizer yesterday and again today, and was able to produce nothing other than a rumbling buzz with a fast and muddy staccato flavor. This happened while hosted in both ApeMatrix and AUM. Is anyone else using this app and experiencing this lately? Haven't tried reinstalling it yet, on the theory it might have been corrupted, but I'm wondering if its buggy recently for anyone else. I have a 4th generation iPad pro, running iPadOS 16.1.1. Thanks.

I had this problem. Turning down AUM's sample rate fixed it for me.

Which sample rate caused the problem?

day_empire

@Zerozerozero said:

@day_empire said:

@gravytop said:
I fired up Agonizer yesterday and again today, and was able to produce nothing other than a rumbling buzz with a fast and muddy staccato flavor. This happened while hosted in both ApeMatrix and AUM. Is anyone else using this app and experiencing this lately? Haven't tried reinstalling it yet, on the theory it might have been corrupted, but I'm wondering if its buggy recently for anyone else. I have a 4th generation iPad pro, running iPadOS 16.1.1. Thanks.

I had this problem. Turning down AUM's sample rate fixed it for me.

Which sample rate caused the problem?

Not sure. Lowered the rate and the problem disappeared.

ZankFrappa

Since the update to iOS 17.4, Agonizer does not load in EG Nodes, AUM or Cubasis. Standalone works.
Anyone else with this problem?

cuezaireekaa

@ZankFrappa said:
Since the update to iOS 17.4, Agonizer does not load in EG Nodes, AUM or Cubasis. Standalone works.
Anyone else with this problem?

Agonizer working for me on 17.4 iPhone 14 Pro.

yaknepper

Both Agonizer and Shockwave have been flaky for some time in my setup. App crashing, sound distorted, state saving problems and UI not resizing properly.

For me, both apps are pretty much unusable, and will be deleted in the next app purge.

It is a shame, as these were awesome apps, and i really hope they will be propper updated.

cuezaireekaa

Yeah shockwave doesn’t work on my iPhone 14 at all. Standalone or auv3

Fear2Stop

@yaknepper said:
Both Agonizer and Shockwave have been flaky for some time in my setup. App crashing, sound distorted, state saving problems and UI not resizing properly.

For me, both apps are pretty much unusable, and will be deleted in the next app purge.

It is a shame, as these were awesome apps, and i really hope they will be propper updated.

@cuezaireekaa said:
Yeah shockwave doesn’t work on my iPhone 14 at all. Standalone or auv3

Shockwave works as an AU for me but no sound in standalone…but “works “ is a relative term in that it’s glitchy af.

HighlandSpring

I’m glad I saw this thread today.
I have been using agonizer in Zenbeats and I was sure it didn’t sound right and was buggy. The sound is distorted and nasty despite initialising and working on patches from scratch. The sound will be fine then become distorted (definitely not from controls on synth, rather its glitching ) Disappointed as when it isn’t glitching it sounds good, but I’ve found it to be unreliable. Using iPad Pro m1 2021

uncledave

You could try changing the buffer size (or "latency") setting, aiming for a middlng value, 256 or 512. The app may have trouble with more extreme values, especially larger ones. To do this, you need to shut down all your audio apps, maybe even reboot, because only the first app started is able to change the setting.

Fear2Stop

@uncledave said:
You could try changing the buffer size (or "latency") setting, aiming for a middlng value, 256 or 512. The app may have trouble with more extreme values, especially larger ones. To do this, you need to shut down all your audio apps, maybe even reboot, because only the first app started is able to change the setting.

Is that something that is changed in the DAW or the app itself? I don’t own Agonizer but I’m wondering if the ability to do so would fix some other issues I’m having.

Not sure if GarageBand has that option though

uncledave

@Fear2Stop said:

@uncledave said:
You could try changing the buffer size (or "latency") setting, aiming for a middlng value, 256 or 512. The app may have trouble with more extreme values, especially larger ones. To do this, you need to shut down all your audio apps, maybe even reboot, because only the first app started is able to change the setting.

Is that something that is changed in the DAW or the app itself? I don’t own Agonizer but I’m wondering if the ability to do so would fix some other issues I’m having.

Not sure if GarageBand has that option though

It's normally set in the DAW. Everything else has to use the same value. It looks like you cannot change it in Garage Band. You might be able to change it by opening e.g. AUM first, and changing it there.

espiegel123

Make sure to report the problems you are having to the developer. If you have AUv3 crashes, you should send them the crash logs, too. They can be found in od settings>privacy and analytics

ZankFrappa

The developer contacted me yesterday and had a very quick and easy solution.
Delete and reinstall Argonizer and the problem was solved!
You should also try this if you have any problems with Agonizer (or Shockwave). But don't forget to backup your own presets.

Fear2Stop

@ZankFrappa said:
The developer contacted me yesterday and had a very quick and easy solution.
Delete and reinstall Argonizer and the problem was solved!
You should also try this if you have any problems with Agonizer (or Shockwave). But don't forget to backup your own presets.

The delete/ reinstall didn’t work for shockwave

espiegel123

@Fear2Stop said:

@ZankFrappa said:
The developer contacted me yesterday and had a very quick and easy solution.
Delete and reinstall Argonizer and the problem was solved!
You should also try this if you have any problems with Agonizer (or Shockwave). But don't forget to backup your own presets.

The delete/ reinstall didn’t work for shockwave

if you haven't, contact the developer with the details of the problems. A demonstration often helps.