Jump to content

Tristan Young

Approved Members
  • Content Count

    29
  • Joined

  • Last visited

About Tristan Young

  • Rank
    Member

Recent Profile Visitors

1,260 profile views
  1. Why would you need to get out of the beta program? I am in the beta program, and I was able to revert to 828 without uninstalling or re-installing. And reverting to 828 definitely helped, as I'm now able to use Poweramp while connected to a bluetooth audio device. I just need to make sure I don't update Poweramp to the buggy version, which won't be a problem. So, what ill-effects will I experience by not getting out of the beta program? I want to remain in the beta program, albeit skip 829.
  2. I'm trying to install the previous version build 828, but keep getting apk appears corrupt errors. Tried even earlier versions, same corrupt error. Edit: Figured it out. If you're having problems downgrading, do the following: 1. Export your Poweramp settings. 2. Uninstall Poweramp. 3. Install the earlier build (eg: 828). <-- now it installs fine 4. Import your Poweramp settings.
  3. Since the latest build 829, Poweramp crashes immediately on startup when connected to a bluetooth audio device. Phone: Samsung Galaxy S6 Edge Android: 7.0 Poweramp works fine when not connected to a bluetooth device. The previous build I had installed of Poweramp worked well without crashing. Tested with multiple bluetooth audio devices, results are identical.
  4. Hello. Enjoying Poweramp v3. A recent update forced audio ducking in my config. I've never used ducking before in a player. Now that I've tried it, I actually like the idea a little bit, but it could use some improvement. I would like to only have the audio duck when a sound/notification from specific apps play. (ducking app whitelist) I would also like to configure the ducking volume level when an app is playing sound.. Finally, I would love to also configure the ducking volume level when an app is recording audio. For example: I never want notifications/sounds causing audio
  5. Ok, here are some basics... 1. Don't just go with the simple cliche-esque smile-shaped EQ curve. And yes, that's what I used to do. Wouldn't doubt that everyone does this at first. 2. Ideally, you need to find settings that sound good for you. This takes into account the kinds of music you enjoy listening to, and the amplifiers, speakers and headphones you'll be replaying through. You may end up creating several EQ curve presets, because there may not be one best one if you like a variety of music, or play poorly recorded/mastered source material. 3. I would use either tone controls
  6. I play music 100% of the time through bluetooth. Upon disconnect, it would be nice if the launcher would re-appear. I can't remember exactly, but I think the old behaviour was it would return to the launcher. I am continually hitting controls accidentally when undocking my phone after shutting off my car. Sometimes I'll accidentally change the current song play location - which I attribute to the new seek bar (not really liking it), and Poweramp remaining on-screen. Tested with Poweramp v3 build 793.
  7. There is a v3 bug report forum. Might be good to put it there, since this thread is going to get polluted.
  8. Very disappointed? LOL. This is a beta release, not a pre release or a final release. You're supposed to discover bugs and report them, and there's even a dedicated bug report forum for v3 right here: https://forum.powerampapp.com/forum/19-bug-reports-Poweramp-v3/ I notice you haven't filed it as a bug yet in the appropriate forum.
  9. Wow, that seems like a gross amount of bass. You're cranking the bass, AND you're boosting the low frequencies. No, I don't see any problem with that. I keep the bass and treble controls flat, and rather than boosting the frequencies I want to enhance, I cut the other frequencies. Gives the same effective boost - with none of the issues associated with boosting a lot. Sometimes you have to boost, but generally you should make small adjustments. I like bass and highs, but not at the expense of distortion, artifacts, etc. The kind of music I listen to is bass-he
  10. Two simple issues: 1. Transparency % for the panels, etc. The % is reversed. Transparency should be 0% - no transparency, and 100% - full transparency. When I set transparency to 100, the controls lack transparency, or from another point of view, are 100% opaque. Oops 2. Visualization full-screen: The transition from showing the player controls to full-screen visualization happens too soon. I need a chance to see the screen, and press the buttons before the visualization takes over. This delay should be configurable. Keep in mind the target audience - some have visual impa
  11. Thank you for the update Max. It's great. I found a few things that are odd. 1. Transparency % for the panels, etc. The % is reversed. Transparency should be 0% - no transparency, and 100% - full transparency. When I set transparency to 100, the controls lack transparency, or from another point of view, are 100% opaque. Oops 2. Visualization full-screen: The transition from showing the player controls to full-screen visualization happens too soon. I need a chance to see the screen, and press the buttons before the visualization takes over. This delay should be co
  12. I disagree with the partial refund idea. Development is progressing, but not at the rate you prefer, and not with the communications or with a beta release schedule you've become accustomed to with other projects.
  13. I am not all that surprised at the behaviour of some users. Impatient, thinking they are owed stuff, etc. Let's look at the details: - People voted for a Material Design upgrade. This doesn't make Poweramp truly better, but, sigh.... the majority want it. Redesign and re-coding is required. - Poweramp v2.x works great. That's what people paid for. It doesn't matter that it's several years old. People got what they paid for. Did I mention it works great? - Poweramp v3.x is going to be a free upgrade. That should be enough to keep people happy, but sadly, it isn't. - P
  14. Why couldn't it be re-compiled to use a different database area? There's no reason why an alpha or beta has to use the same app directories and data. Considering alphas are advertised as being potentially unstable, I would want people to test my product as much as possible, yet still have a way to easily revert to the current official and working release. I used to keep the official Firefox for android release and the Firefox beta for android on my phone, so it must be possible.
  15. So, is there a way we can install Poweramp v3 alpha side-by-side with Poweramp v2.x, and still be able to make use of our license? I would like to continue testing when I'm not using a bluetooth audio device, but need to use Poweramp v2.x while in my car.
×
×
  • Create New...