Skip to content

Possible CLUB/Nightclub features? #7

Description

@lewiselwynjohn10-cpu

Hi! 👋

Firstly, I just wanted to say a massive thank you for developing RootlessViPER4Android. I've tried a lot of Android EQ/DSP solutions over the years, and this has genuinely become my favourite. The fact that you've managed to provide this level of processing without requiring root is seriously impressive, and I honestly think far more Android audio enthusiasts should know about this project.

I've been using it extensively with Bluetooth speakers, headphones and my car audio system, particularly for house/club music where I'm trying to reproduce the character of a properly tuned club or PA system rather than simply boosting the bass.

I wondered whether you'd ever consider expanding the app with some more club/PA-oriented DSP functionality or presets.

What I'd particularly love to see is a proper Club / PA / Sound System mode designed around things such as:

• Deep controlled sub-bass extension and rumble without destroying headroom
• Separate control over sub-bass and upper-bass/kick impact
• Strong, tight kick-drum punch rather than just a generic bass boost
• Dynamic bass processing so the low end remains powerful at different listening levels
• Better control of the crossover/interaction between sub-bass, mid-bass and mids
• Club-style dynamics/compression that can create that dense, energetic PA-system character without excessive clipping
• Adjustable high-frequency “air” for that crisp large-system top end
• Presets inspired by different environments, for example Club, Festival/PA, Warehouse, Deep House and Car Sound System
• The ability to achieve a large, physical sound while keeping vocals and the centre image clean

Something else I'd love is more advanced dynamic DSP, where bass, punch and perhaps stereo width could react intelligently to the signal instead of being fixed boosts. I think the existing processing gives you an amazing foundation for this.

There's also one issue I'd really love to see investigated: Android Auto audio routing with the rootless version.

When connected through Android Auto, I've experienced situations where the media/audio routing behaves incorrectly or glitches while RootlessViPER4Android is processing audio. I understand that the rootless implementation has to capture an application's audio, process it and then create/output another stream, so Android Auto may be handling that processed stream differently.

If a future global-output processing method could process the Android mix directly without the capture → DSP → separate output-stream approach, I'd be extremely interested in it. If that could eventually make processing reliable through Android Auto as well, it would solve probably the biggest remaining limitation for my use case.

I'd also love continued improvements to Bluetooth routing and Android 15/16 compatibility, especially making it as seamless as possible when switching between the phone speaker, Bluetooth headphones/speakers, car Bluetooth and Android Auto without having to restart processing.

I appreciate some of this may be technically impossible because of Android's audio restrictions, and I'm definitely not expecting all of it! I mainly wanted to share the ideas because I'm genuinely impressed with what you've already achieved.

For someone who loves audio tuning, deep sub-bass, house/club music and experimenting with different sound systems, your app is basically an Android DSP playground. 😆

Thanks again for continuing to develop it. I'd be very happy to test experimental club/PA presets or routing changes and provide feedback if that would ever be useful.

Keep up the brilliant work! 🔊
— LJ

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions