Saturday, April 14, 2018

2.2.7 Released

2.2.7 (04/09/2018):
-Fixed reading embedded album art in ogg containers
-Added error check to hopefully prevent the "Cleaning database" notification from being stuck
-Jumping to a letter in the album list in android auto should now correctly take you to the right spot in the list
-Clicking search button will no longer remove focus on the search text field
-Additional workarounds for invalid unlocker issue

2.2.6 (04/03/2018):
-Taglib update to 0.11.1
-Fixed handling of unicode TXXX album artist tags
-Added workaround for invalid unlocker error caused by updating some devices to oreo
-Fade out if the next audio source isnt prepared when crossfading

3.0 WIP 19: On Queue Completion, Android Auto, Improved Voice Commands and Auto Pause/Play

The last two weeks were mostly spent refactoring / rewriting the remaining Music Service code that i had previously disabled.  That includes the MediaSession, Android Auto Support, Audio Focus handler, On Queue Completion, Voice Commands, and Auto Pause/Play.  The only thing remaining I believe is the auto volume adjust and the ability to handle multiple remote control presses.  At this point it looks like a realistic release date of the first alpha should be in May.  I am probably a week out from starting internal testing, which basically means i start deploying the app to all my test devices and actually use it as my main driver on my phone.  Up until now i have still been using 2.2.x.  I am not expecting that many bugs, but what I am expecting is a lot of things i just forgot to implement that are crucial to making GMMP usable.

3.0 working in Android Auto

Audio Focus

The new audio focus handling is mostly the same as 2.x.  Google did add some new capabilities for oreo which I did add.  When GMMP requests audio focus, sometimes something else has to keep focus for a bit while longer.  In this case the request returns that the focus request was denied temporarily, but will let gmmp know when it can take focus.  When this happens gmmp will wait for the go ahead and then start playback after the OS says it can take focus.  I am not sure how useful this is, but I figured i'd mention it.

On Queue Completion

I made some minor changes when re-implementing this feature.  Play Random Track was replaced with a simple Shuffle.  It will load all your music into the queue and turn on shuffle.  Another nice improvement is the music selected by on queue completion will now be preloaded when you are playing the last track in the queue.  This will allow gapless and/or crossfade to work.

I had mentioned this in a previous post, but in 3.0 many of the options will be right in the UI instead of being hidden away in the general preferences.  This should make it much easier to change options quickly.  On most of the views, they will be in a "Customize" section of the 3 dot menu on the toolbar.

Before 3.0 is fully released I will most likely add a few more on queue completion options, but for now I think its good.

Improved Voice Commands

While testing voice searching in android auto, I had noticed it was sending unstructured voice command .  An unstructured voice command is basically a voice search that you do not know what it is looking for (ie an album search, track search, artist search, etc).  Now gmmp will run through a bunch of queries to try to find what the user is requesting to play.  Previously in this situation it will only search the track name.  

Auto Pause / Play

The auto pause / play functionality was simplified a bit.  Since GMMP was first written for android 1.6, it was previously looking for a huge list of different events to determine whether to pause or auto resume.  Now to keep it simple, GMMP basically just listens for a "NOISY" intent when playing over a wired connection, bluetooth, or speaker.  This intent is broadcast in many situations like when you unplug your headset or receive a phone call, so it basically has everything covered.  Another minor change is gmmp will only look for a2dp connections (this is what is used for playing music) instead of all BT connections in general.  

I also added some new pause / play triggers which include: 
  • HDMI plug/unplug
  • Phone Power plug/unplug
For each type of connection / audio routing there will be the option to do a smart play or an always play.  Smart auto play will basically only automatically resume playback when GMMP was auto paused.  This has always been my preferred behavior.  I've always found it super annoying when a music player that i was not using at all decides to automatically start playing just because i plugged in my headphones.

Saturday, March 31, 2018

3.0 WIP 18: Add To Playlist, Sleep Timer, Improved Drag and drop and more

For a large portion of the time since the last post, I worked on redesigning the data access portion of GMMP which doesnt really have much to show off visually but I will briefly talk about it.  In the first WIP post I talked about the complex metadata view customization 3.0 will provide.  Now playing and all the metadata lists let you customize how they will look and what metadata they will display.  This was working pretty well for the layouts i had set up for demo purposes, but there was a problem of being able to get all the necessary data in order to populate the metadata views.  I had a bunch of hard coded database queries that were good enough to get some screenshots, but would not completely if i would add a lot of other fields to show.  An example would be in the track list I believe it previously only showed the trackname and time.  What if i wanted to also show the artist?  Well previously i would have had to either make the track query more complex by joining with the artist table or add separate query that did the track/artist join.  The problem with the first option is this would make every track query take longer regardless if the user wanted to show the artist or not.  The problem with the second option is this would require thousand of custom queries to get every possibly combination of metadata for the view.  Neither were acceptable to me so I decided to rework how data was being accessed.

My new solution was to design a database query builder.  It basically contains a few public methods so i can specify what type of query to do (track list query, artist list query, album list, etc).  I then specify what metadata fields are wanted, along with any conditions (like artist = so and so) and it will return the query to use against the database.  In most cases the metadata fields are generated automatically by scanning the metadata lines and the sort order selected.  So what does this all mean?  If your track list metadata line is something like "%ar% - %tn%" and the sort order is by album, the generated query will retrieve only the artist, trackname, and album.  This should lead to the best performance possible and the least amount of memory being used.

Add To Playlist

I readded Add To Playlist and it is mostly the same as it was in 2.x.  Behind the scenes its much better but UI wise it works the same.

More Now Playing Actions

I added volume control, stop after current, sleep timer, and the share option.  The sleep timer also now has an option to wait until the end of the playing song before pausing.

Drag and Drop Improvements

When I initially did the drag and drop, I couldn't find a way to use anything but the default behavior which was to long press to start the drag.  After some more research I did eventually find a way to add "handle" to start the drag and drop.  This is much more usable in certain situations like in the car.  To turn this behavior on, I added 2 new view modes to the view mode menu.  Handle and Card Handle

For whatever reason youtube would not let me upload the drag and drop video i created, so Im using the blogger video capability instead.

The preference UI is the only remaining UI task still need to be done before i can release alpha 1, the rest is basically just restoring the remaining music service capabilities that I had took out when starting with 3.0

Friday, March 9, 2018

3.0 WIP 17: Landscape Support + Jump To Time/Playing + More

There is a lot to show off this update so I will get right to it.  WIP 17 brings landscape support plus a few other things.  The majority of the views are the same as the portrait version except for now playing and the album details view.  That is not to say more landscape specific views will not be coming in the future. 

Lansdcape Now Playing:

The now playing view is one of the most important views in a music player and I felt GMMP 2.x did not full take advantage of the space as well as it could have.  In 3.0 there are a bunch of changes.  I do plan on having additional Now Playing layouts (like one that users the blurred album art as a background and one that doesnt bleed through the toolbar/status bar) but they will come at a later point.

In landscape there will be 2 extra button slots that you can use.  In the image above I included a fullscreen / immersive mode toggle, and a direct button for the queue (instead of having a FAB).  As mentioned before, these buttons will be configurable.  You can leave empty slots or change the number of total buttons (so if you set it to 5, all 5 buttons will be equally spread out in the view).  In code I combined the gesture actions, context menu actions, and the media button actions into shared modules, so the idea is you will be able to make buttons for many of the gestures and all of the menu options.  The menu is also built dynamically now, so instead of having a massive list of 12-15 options, you will be able to choose which show up the menu. 

Full Screen / Immersive Mode
Dynamically built menu (only 2 actions listed so far)

Another nice thing with the landscape now playing is I made it so certain options are orientation specific.  The metadata being a prime example.  In portrait we really only have room for 3 lines, but in landscape there is tons of space for the metadata, so in this example i added an empty line as a separator and 2 additional lines showing genre, year, bitrate and sample rate.

Landscape Album Grid/List

Album Grid is 4 wide in landscape
2 wide in portrait
Right now the landscape specific settings are the grid size and now playing metadata, but in code its as simple as replacing a single line in order to support diff prefs for orientation.  In the album grid i did also finally add the context menu.  I experimented with a few different positions, but it worked best just right next to the metadata.

Landscape Album Details

The landscape view of album details is much more user friendly I feel.  Instead of having the artwork taking up the top 1/3 of the screen (and only being able to see a small portion of the full image), it is now on the left hand side in full.   Album name and artist in the toolbar and some additional song details are on the right as the first entry of the list.  When I finally add an option to disable the FAB, that top metadata entry will contain one of those 3 dot menus on the right so you can play/enqueue/etc the entire album without the need for the FAB.  The album details will be customizable within reason (i think it'll be about 5-6 different variables available for use).  These album details were also added to the portrait view.

FAB was moved to overlap the metadata view and the album art

Album Details view with the list scrolled up

Jump To Playing / Time

I have only coded up a handle of the menu / gesture actions so far (its what I am currently working on).  Jump To Playing works the same way as before.  The look in the image below is not final, its just the default look of the library I am using for the material dialogs.  Below that is the jump to time dialog which is using a.. time wheel i guess you can call it.  Both features are shown in the video at the end of this post.

Sorting Options

I also went through and implemented the majority of the sorting options for the various views.  All that is left is some of the track sort options.  They require a bit of rework of my database queries, rework that I had to do regardless so they have not all been implemented yet.  One change I made from 2.x is that Date Added is no longer the time the entry was added to the database, it uses the last modified time of the associate files on storage at the time it was scanned into the database.  What this means is you will be able to clear your database and rescan without every single song showing up in Recently Added.

Track Sort

Artist Sort

Album Sort

Navigation View Fixes

Finally I made some navigation view improvements.  The highlighted entry is now consistent with the showing view (and if you go into album details, for example, none will be highlighted since that is not in the nav view).  I also added an entry for bookmark view.

Progress in general is going great.  If you look on trello the majority of the TODO list for the first alpha is done.  It seems like we'll see a release in the upcoming months.  How soon will depend on 1) how much more of the music service refactoring work needs to be done (restoring android auto support is required before i can get approved through google play), and how many small TODOs i have left in the code base.  Some areas need a bunch of work like the folder browser, while others are pretty much good to go.  

Sunday, February 25, 2018

3.0 Work in Progress 16: Navigation Menu

For this WIP update I am going to show off the side navigation menu.  I set it up similarly to GMMP 2.x, but behind the scenes it will be customizable.  The only fixed menu options will be library, settings, and exit.  The rest will be able to be customized.  The same goes with the library view.  The tabs shown there will be able to be chosen.  All this customization wont come until a later alpha build but it is planned.

I am not exactly sure what I am going to put up in the top yellow region yet, so i left it blank for now.  To control navigation in general, I am using this nice library called simple-stack.  It handles the backstack instead of the build in android one (which has a lot of issues that I will not go into).  The backstack is basically the list of views you have navigated to, so you can backtrack to the previous view when you hit the back button.  Below is a video of the navigation menu and the other navigation actions (like viewing an artist/genre/album details).  Animations were disabled for the video.  I need to do a bit of restructuring since this allows me to jump to any view at any time.

Also in the past week I implemented context menu actions and the multi select actions (images below).  Right now those actions are just play, play next, and enqueue, but I will bring back all the actions from 2.x.  One nice additional will be the ability to multi select and delete or add to playlist from the folder browser.  All the rework I have done will allow you to multi select files, folders, playlists, and cue files all together.

I changed the play next and enqueue icons.  Not sure if these will stay or if i will return to the old icons.

Next on the TODO list is updating the UI for landscape support.  The majority of the UIs will look the same but some of them like Now Playing will have its own layout.  The plan is to have most of the customizable metadata to be orientation specific meaning that the metadata shown on now playing and the other lists can be changed depending on whether you are in landscape or portrait mode. 

Sunday, February 18, 2018

3.0 Work in Progress 15: Playlists View

Here is a look at the new playlists UI.  Like most of the other views it has some sort options (playlist list only so far.. not when editing the actual playlist) and the ability to be a regular list or a card list.  Also notice in the screen shot below how I threw all the views together as tabs.  The default UI will only contain the library type views as tabs but I designed things in a way where its only a single line of code to just throw whatever view in as a tab.  Also note in these screenshots and the video the album art in the mini player is a bit messed up.  I'll work that out before the first alpha release. 

The context menu right how has the standard play, play next, and enqueue.  At some point I will add an edit option as well (which would allow an option to play the playlist on item selection instead of having to use the context menu)

When selecting a playlist it will open up the edit view which supports the drag and drop like the queue.  Right now its still press and hold to drag items around but there will also be an option to add a handle instead (similar to 2.x).

The playlist will auto save when backing out of the edit view, but I would like to make this optional down the line.  With auto save off there would be a manual save and revert menu option.  One of the reasons I have been hesitant on adding sorting options when viewing the playlist contents is specifically because of the auto save.  I felt that users would be annoyed if they went to sort their playlist to help look for a song, only to find they completely lost their song order.

One minute addition I made is the ability to save wpl playlists.  In 2.x when a user would edit a wpl playlist, it would be replaced with an m3u.  Now it will just modify the original wpl file.

Finally here is a video of the playlist ui.

The playlist UI only took a day or 2 to finish, so I've already started on the next task of implementing all the remaining context menus and list item press actions (I had previously only done a few for demo purposes).  I have also been leveraging RxJava2 to move almost all the actual work for the UI (like grabbing all the songs of an album from the database before playing) off of the UI thread (which would help with responsiveness and prevent freezes). 

Wednesday, February 7, 2018

3.0 Work in Progress 14: Equalizer and Effects UI

Before I get into the new UIs, I want to mention some of the behind the scenes work that has been done since the WIP update.  I mentioned in the last blog post that I completely rewrote the DSP / Effects backend (everything besides whats in the audioengine).  Since then I also ended up replacing the theme engine with a library called Aesthetic.  It was pretty similar to the custom theme engine I had written before, but I felt it was better written and had other users maintaining it which is always a plus.  It also was backed by RxJava2 which is something I've been using throughout the 3.0 rewrite and it makes changing theme colors on the fly much easier than my custom theme engine.  I did a massive cleanup and restructuring of the gmmp project.  I removed all the legacy code that has been rewritten and have split up the project into 4 main modules (this is done for much faster compile times): common, data, playback, ui/main.

When I look at the breakdown of languages used on my gitlab we see these numbers

Java 67.93 %
Kotlin 31.72 %
RenderScript 0.35 %

So despite all the stuff I have rewritten, about 2/3rd of the non audioengine code has still not been touched (all the 3.0 work was done in kotlin).  I dont have any plans to rewrite everything but it just shows how large the project has become over the last 7 years

I decided to split the equalizer into its own view and have the other effects on a separate tab.  I did get a lot of complaints about having to go through a lot of steps just to get to the equalizer.  It is much more accessible now.  Also on the effects UI, I added switches for each effect and sliders for anything that can be adjusted.  Previously some things like bass boost strength, and limiter attack/release were hidden away in the preferences.

I still have a bit of testing to do to make sure all the effects actually are being applied correctly, but from the UI standpoint things are pretty much where i want them to be.

Next up will be the playlist file UI which should be pretty straight forward

Wednesday, January 10, 2018

2018 Plans

Now that the holidays are over I thought I would share my plans for this year and discuss the current state of 3.0.  For those not aware, I track all my active development, future development, and feature requests on trello here:  To see my current progress on 3.0, the ones you want to look at are "3.0 - Alpha 1", "3.0 - In Progress", and "3.0 Complete".

Anyway I just finished up rewriting all the Dsp / Audio Effect management code (essentially everything dsp/eq related that was NOT in the audio engine).  There have been some long standing bugs like the equalizer not applying on startup or the bass boost not being applied until you toggled it off and on that I really hope will not be present in this rewrite.  My original intent with 3.0 was to just rewrite the UI, but I ended up rewriting a lot of the backend in the process.  Tons of the old code was written 6-7 years ago back when gingerbread was present so it had a lot of unnecessary and/or deprecated code in it.  I am also a much better engineer than I was back then so being able to completely redo entire systems has led to a much more efficient and easier to maintain baseline.  The downside is that its taking much more time than I originally planned.

If you look on trello, the 3.0 lists show about 15 remaining tasks before I can release the first alpha.  I will try to estimate how long I think they will take so you guys can get an idea when the first alpha might be released.  Keep in mind my estimates are most likely the best case scenario..  I only get around 12-20 hrs a week (depending on how I spend my weekends) to do android dev, so the odds of this taking longer than I estimate is pretty high.  Sometimes I miss the early days of GMMP when I was able to get 40-50 hrs in a week.

Remaining tasks for Alpha 1 (summarized):

  • Equalizer / Effects UI - Most of the hard work was already done with my recent dsp management refactoring so this task is just pure UI development.  ~ 2 weeks
  • Playlists UI - I already rewrote the playlist file handling 2 months ago and the playlists UI is pretty straight forward in general. ~ 1-1.5 weeks
  • Navigation - Nothing has really been done yet with the side navigation drawer and to efficiently handle swapping back and forth between the different views.  I anticipate this being a pretty large task.  ~ 3-4 weeks
  • Landscape Support - Most of the UIs are pretty usable already in landscape, so this will probably be just designing the landscape version of now playing (for alpha 1.. i definitely plan on optimizing all UIs for landscape/tablets before the final release).  ~ 2 weeks
  • Preferences UI - Will be pretty simple to start (will go into more detail on preferences later) ~ 1-2 weeks
  • Action hookup - A lot of the menu options / gestures / etc are not completely set up.  I finished the frameworks and implemented a few actions for demonstration, but thats it.  ~ 1-2 weeks
  • Bug fixes / Testing before release ~ 3 weeks

Remember this is a best case scenario and if I get emails or questions asking for an ETA, my response is going to be "when its done" (this is my typical response anyway since estimating time is very hard to do.. a single bug can consume weeks before finding a resolution).  If we add up my estimates and look at the current date I would guess the first alpha release will be sometime in April.  As mentioned before the Alpha will be ran through a separate google+ community from the beta.  A lot of people in the beta do not actually frequent the g+ page, so I do not want to push an update to the beta channel until I have restored all the features / customizations from 2.x (or well.. all the ones i plan on restoring).

GMMP will most likely be in alpha for awhile.  There are still a huge list of capabilities to readd and new ones I want to add (check trello).  For customizations I think I will be taking a different approach this time around and not just load everything up in the preferences UI.  Almost all the UI based customizations will be accessible from the toolbar menu in the actual UI.  This should make customizing the UI much faster and easier.

Betas will come once all the features and customizations are complete.  It will be strictly for bug fixes and minor tweaks, so depending on how good of a developer I am.. this period may be short.. or long depending on how many bugs pop up. 

In summary, the 3.0 final release is still a long way off, but I think a usable alpha version will be available in a few months.  Also keep in mind that 3.0 isnt just a pure rewrite.  I have been adding new capabilities as well (multi genre / artist support, new loudness enhancer audio effect, grid view, bookmark ui, improved shuffle, and permissions) and more are planned (auto dj mode, true album shuffle mode, artist images, app shortcuts, song details view, and year view).