jl91569

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

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

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.

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

It's impossible to see the seek bar for albums with mostly white/light coloured art.

ReplayGain still isn't working on Opus files that work fine on PCs (VLC, foobar2000). Are you aware of this problem, and if you are then are you planning to fix this before the "stable" v3 releases?

Pretty much just the title. This happens regardless of whether they're tagged in Mp3tag or dBpoweramp.

Are you sure the CUE is pointing at the correct file?

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.

This beta will be released to the Google Play Store?

Great, so is there going to be another community poll for v4 features? Of course this is assuming you are continuing Poweramp development.

Amazing work Does this mean betas will be more frequent now?

Max said this around a year ago: Good one: everything works and I'm on finishing steps. So why is stuff still not working?

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.

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. Sounds good. OK, Dec 25 seems reasonable Still, going by the massive delays this project has experienced so far I'll hope for a June 2018 release haha