Jump to content

TeutonJon78

Approved Members
  • Posts

    30
  • Joined

  • Last visited

Recent Profile Visitors

1,864 profile views

TeutonJon78's Achievements

Advanced Member

Advanced Member (3/3)

  1. I don't know what to tell you, I have zero problem with my UTF-8 playlists coming from MusicBee -- umlauts and all.
  2. You can just set Musicbee to export m3u8 files, and Poweramp will import them correctly. I've been doing this for awhile. "Menu > Edit> Edit Preferences" ---> "Devices" -> "Configure" -> "Settings > Playlist storage > save as format" and pick m3u8. Then you'd sync your device again. You'd want to delete the old m3u playlists off of your phone. Musicbee actually follows the standard where it output the playlists with the expected character type. m3u is supposed to be ascii, m3u8 is supposed to be UTF-8.
  3. As more and more tags are finally starting to use UTF characters over ASCII, it would be nice if the search feature could have an option to ignore those diacritical marks. For example, searching for "Celine Dion" should find "Céline Dion". It would be helpful for when you remember a name but not necessarily all the special characters.
  4. I just noticed a bug in v3-build-838. If there is an album song that is exactly one hour long, 1:00:00, in the list view the time will show up as ":00" rather than "1:00:00". Longer and shorter albums show up correctly. I'd imagine it probably has the same problem if the album is exactly 1 min long as well, but I didn't test it. If you go to the indiviual song listing (the album is one long track), the individual track will show up correctly as "1:00:00", so it's only something with the format string in the album list portion. This also worked correctly for a 1:00 song.
  5. That's kind of a requirement. All Android Auto does is pass along the assistant command to the actual app -- that's how GoneMad works. There is also some sort of app glue to get the menus to show up I think, and maybe to control the UI, but only Google-selected apps are allowed to actually fully interact in Android Auto (like Google play Music). They are kind of strict about it. For maps you can only use Google Maps or Waze, not any secondary program like HERE! or OSM-based apps.
  6. 24-bit snapdragon output works on the Axon 7 US, but it doesn't use the built in DACs. Using the normal GL ES path actually sounds better than the hi-res output since they system will use the external DACs then. I had previously provided the audio_policy.conf from the Chinese version (same audio hardware) on the request thread.
  7. ZTE Axon 7 stock (ships with 6.0.x) AKM 4961 HiFi Recording Processor+ AKM 4490 HiFi Audio Amplifier chips included for hi-res audio /etc/audio_policy.conf included from the Chinese B05 ROM. The US/international versions should have the same chipset. audio_policy.conf Edit: just for note, with an actual US release phone in hand, it has the option for hi res audio for the internal Snapdragon 24-bit PCM, but not the special DAC chips in the phone.
  8. The guy that made N7 Player made ToasterCast for just this purpose. And he allows others to link into it (which of course, get's him cash from the purchase). So, if MaxMP wanted the features but not the dev time, he could just build in support for that API and then could have access to all that streaming and litte of the support (just working with any API changes).
×
×
  • Create New...