„Intensity“ = dry/wet is phasing, no latency compensation?
EDIT: as an answer to the developer: yes, that‘s exactly what I‘m talking about? I just think the implementation is bad, it shouldn‘t phase or develop comb filtering with the dry signal when you reduce intensity/ dry-wet.
Response from developer
You supposed to use the Intensity slider to blend from the combined effects and dry mix.
„Intensity“ seems to be just dry-wet w/o latency compensation I guess
Scroll issue on iPhone pro max
Response from developer
The interface is designed to collapse on small screens. However, you can turn on FULL screen mode if you wish in the Settings. Since each effect slot also scrolls itself you have to be careful where you tap to scroll. You can drag on the meters and in the global settings panel to scroll back up. Probably not the most logical but it does work once you get the hang of it.
Nice and above stable FX Modules
Really pleased to have this great app!
Response from developer
There is a new version on its way that should fix the crashing issue on iOS26.5.
App crashes on my IPad Pro
Response from developer
There is a new version on its way that should fix the crashing issue on iOS26.5. This is an issue with iOS26.5 which was released after I released RetroLab. I can't help it if Apple release an OS which causes issues. Please test 1.07 when it goes live.
The jury is still out
Doesn’t work with AUM
Response from developer
There is a new version on its way that should fix the crashing issue on iOS26.5. This is an issue with iOS26.5 which was released after I released RetroLab. It caught me out because it worked fine on all my devices even on iOS26.5. Look out for version 1.07 which should fix the issue.
Great multi fx app not just for vintage fx
Works great!
Response from developer
Sorry for the inconvenience and rest assured I am looking into the issue which seems to only be affecting certain configurations of iOS and iPad, so I'm trying to figure out what is going on and issue a fix ASAP.
Looks like a mis directed Apple App Store LFO is driving the price; but it is fixed now. 😊
25 May 2026: Well it appears that there are rotten 🍏 issues on the App Store. The price of this app as reported on AppRaven has cycled back and forth at least 9 times now between $14.99 and $$7.99. I jumped out to the App Store and it is doing the same thing, so the problem is in Appleland somewhere. Pressing on the AppStore’s blue $7.99 shows it coming up as $14.99 and visa versa. Finally caught it when it said $7.99 (I hope … but, I am still going to check the Apple receipt). Good luck to all those also attempting to jump on the $7.99 sale price.
I’ll re-write and rate the app more appropriately when this anomaly is resolved. Thanks Paul for trying to tame the feral 🍏.
🍏 🍎 🍏 🍎 😠
Response from developer
This was an App Store related issue, as I'd put the app on sale from the 22nd to the 29th at $7.99 does from $14.99, and for some reason the price was alternating every hour. I'm not sure why this is my fault, or why you are posting a negative review against my app for something outside of my control? I understand the frustration because I lost out on sales too.
Doesn’t work on my 2022 iPad Pro or brand new 2025 model iPad
Response from developer
Sorry for the inconvenience and rest assured I am looking into the issue which seems to only be affecting certain configurations of iOS and iPad, so I'm trying to figure out what is going on and issue a fix ASAP.
Can’t even use this app
Response from developer
This has now been long fixed, can you please consider updating your review in response to my fix?
Still crashing M4 iPad Pro
Response from developer
Can you give me some explanation about what host app you are using and when the crash occurs? Are you using a specific module that is giving you the issues? Is it an issue loading the plugin or on a session restore? Anything you can provide would be great as the crash logs are not showing me any issues. One thing you can try is reducing your hosts Buffer Size to 256 ideally or 512 to see if that helps. I've filed a bug related to this in v1.03 coming soon. NOTE: Version 1.04 is out now and I've still not heard from you. The issue should be fixed now so please consider amending your review.
