Jump to content

jl91569

Approved Members
  • Content Count

    30
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Gallery

Downloads

Knowledge Base

База знаний

知识库

Posts posted by jl91569


  1. On 3/16/2019 at 3:15 AM, andrewilley said:

    It does sound like the issue is with the file encoding, especially if re-tagging them causes them to work with Poweramp and other apps.

    If you can upload a sample file though, maybe Max can decide whether a workaround is possible or viable for this case?

    Andre

    Okay, tagging files with R128 tags appears to work, but the vast majority of tools don't use that standard.


  2. 6 hours ago, andrewilley said:

    It does sound like the issue is with the file encoding, especially if re-tagging them causes them to work with Poweramp and other apps.

    If you can upload a sample file though, maybe Max can decide whether a workaround is possible or viable for this case?

    Andre

    Oops, forgot to mention that both VLC and foobar2000 can see them on Windows. Seems like dBpoweramp is a bit broken (see this standards compliance post about beets on GitHub).

    It'd be nice to have it working, but I'll see if using the compliant tags works.

    noise.opus


  3. Device: Samsung Galaxy S7

    ROM: Stock Samsung Experience 9.0 (Android 8.0 Oreo with February security patches)

    Poweramp Version: v3 build 820 (Play Store beta)

    This problem has existed since before v3 officially launched (check my post history).

    It's worth noting that other Android apps aren't able to see the ReplayGain tags either 😕

    Adding them through a ReplayGain app works, but I feel like Poweramp should be able to see the tags correctly.


  4. 13 minutes ago, maxmp said:

    RG does indeed work for all the test files I have. Please PM me the files you think should support RG, but don't work for you in PA. (You mentioned apev2 tags, but these are not primary tags for mp3 and if id3v2 exists, ape tags won't be read).

    Same thing happens to me with Opus with correct tags from dBpoweramp, should I PM you the files as well? 


  5. I've applied ReplayGain to an Opus file using dBpoweramp and it's successfully read by VLC, but Poweramp isn't displaying it in the track information.

    foobar2000 on Android doesn't appear to read the tags correctly either.

    Is this normal? 

    Edit: I'm using build 793 from the Play Store on an Exynos Galaxy S7.


  6. 10 hours ago, maxmp said:

    Regarding release schedule - May is set as month for a feature-complete Beta release (with the all missing parts finished), and the end of May/beginning of June'18 is the final v3 release planned period. It depends on bugs and specific device issues.

     

    Great, so is there going to be another community poll for v4 features?

    Of course this is assuming you are continuing Poweramp development.


  7. On 5/23/2017 at 11:06 PM, maxmp said:

    Two news.
    The bad one: an additional round of device specific optimizing and polishing is required for Poweramp v3.0, this delays release. As indicated before, v3 will run on Androids 5.0+ (O included). Poweramp v2 stays for 2.3-4.4.
    Good one: everything works and I'm on finishing steps. 

    (snip, emphasis mine) 

     

    If everything worked around a year ago and Max was just working on device-specific optimisations, why not just release the new UI as an alpha build only on the forum? 

    That way people who know the issues could download it and people who want to stay on the current alpha could also do that.


  8. On 11/9/2017 at 5:05 PM, SynekPablo said:

    There are AAA video games that finished faster.

    Yeah, but then you also have the Blizzard-esque companies that have games in development for years and cancel them because they didn't feel good enough to ship.

    On 11/10/2017 at 10:15 PM, andrewilley said:

    All I can say is that Max assures me he is almost done with the work on the new ground-up rebuild of the UI, and compatibility checks and fixes with hundreds of devices and OS versions (not specifically Samsung).

    Sounds good.

    On 11/10/2017 at 10:15 PM, andrewilley said:

    I would hope that the next beta will be released within the next month or so, but please don't be too surprised if that slips to the end of the year.

    OK, Dec 25 seems reasonable :D

    Still, going by the massive delays this project has experienced so far I'll hope for a June 2018 release haha


  9. 7 hours ago, Brainscollector said:

    No, it won't be worth the wait. Check retro player for example. This app was build in a year from scratch by person that don't have super experience in Android coding, yet made MORE than what Max did in 2 years. Sorry.

    It's probably much easier to create a music player based on existing libraries than custom-building all of the frameworks required to have hi-res output on tens of devices.

    Creating a standard API to make everything skinnable is probably also more difficult than having a set interface.

    It's also highly likely that Max has a day job as well, so if he was busy he wouldn't be able to spend as much time as normal working on it. I don't think Poweramp would sell enough consistently to earn enough to live on.

    I'm not saying that it's not disappointing to have ETAs constantly being pushed back, forcing users to deal with bugs because he can't release a new version based on half-baked code. All I'm trying to get across is that Max is also a person, and that it's incredibly difficult to give accurate estimations on how long complex software takes to develop, especially on a one-man team working part-time. 


  10. 8 hours ago, clever_man said:

    Not what I was expecting given the previous mock-ups, but it's decent.

    I'm hoping there will be a way to customise the gestures and layout, but it's most likely not going to happen.

    Edit 1: Looks like a Samsung device, so hopefully this means the driver problems have been fixed and a release will be out soon. Also, thanks @clever_man


  11. 8 hours ago, utahman1971 said:

    I don't understand the impatience at all. I been using it and it runs just fine without problems for an Alpha stage. I can't really tell if it is in beta or not. It runs fine for me, and I am willing to just wait it out. I for one would go back to BlackPlayer EX if they made a separate charge for the new version. One v2 is way out of date, and the reason is to use v3 but willing to wait out for the release because it runs perfectly fine for me right now.

    Poweramp is the only reason I'm not upgrading my phone to Android Nougat. I don't want to risk it breaking when it's working on Marshmallow, so I'm stuck with security updates from December of 2016.


  12. 2 hours ago, maxmp said:

    Currently, planned v3 beta release month is set to May. This will be full featured v3 (it's basically alpha3 + new UI + fixes for recent ROMs, but not more).

    Thanks!
     

    Thank you for the update. It's really great to see that development is moving along, even if estimated times are pushed back from what was previously expected :)

    Do you have any plans to add a dark mode? 


  13. This has already been discussed in the testing forum, but I'll repost it here. 

    The S7's volume output for headphones is abnormally low when not using the hi-res audio output. Disabling DVC seems to help slightly, but it's still not as loud as the stock players unless I push the preamp all the way up. 

    The hi-res output is as loud as the stock output with preamp at default settings. 

    Details:

    Samsung Galaxy S7 SM-G930F (Exynos) 

    Android 6.0.1 Marshmallow, December 2016 Security Updates, stock TouchWiz, not rooted.

    Poweramp build 703, Google Play. 

    MusicFX and Adapt Sound disabled. 


  14. As much as I love Poweramp, if there isn't a dark mode or black skin available in the next alpha I might have to either hold back from updating or switch to a different app as I have everything else on my phone set to a dark theme. Having a mostly black interface also helps when using the app at night. Skins are currently disabled, so I'm not really expecting there to be a dark skin in the alpha test (but I'm still kind of hoping there will be one). 

    Can Max perhaps include a dark mode and maybe a accent colour selector (if applicable) in an update some time in the future if they're not in the app already? 

    It's great to see that the app's development is moving along nicely, though :) 

×
×
  • Create New...