
In the mean time, 1.0.1.6 is out. For the information of everyone, I have also been turning in "Tickets" through the member portal. When I updated, a change log was not offered, so I can't say what was or wasn't worked on. I have only been "Playing" with it a short time, but this is what I noticed.
The Whine List:
1, The "Protected Content" screen in Spotify, and the "This Version Of Edge Is Not Supported" in Amazon are still there and a major issue. When the "Protected Content" screen is up in the Spotify section, MusicFab is essentially unless. Although, through rebooting and restarting MusicFab (often many times), the "Protected Content" screen can be bypassed, this is still a serious issue. Nobody wants to have to struggle to use a program.
Note: As long as I'm not logged in, Spotify seems to come up normally. As soon as I try to log in through the "Fab Browser" however, the "Protected Content screen immediately appears. This does not happen going through my regular browsers outside of MusicFab.
2. After finally getting past the "Protected content" screen and when I finish downloading several tracks, the track selection screen did not show up to select new tracks after pulling up a new artist and album. This forced me to restart MusicFab, and deal with the "Protected Content" screen all over again. If I am unable to select tracks, MusicFab is (again) useless while the issue is happening.
3 MusicFab is still dumping all of the tracks from multiple disc albums into single directory. The album I chose to test this problem was a five disc album. MusicFab dumped all the songs from all five discs into a single directory making a tangled mess that will take a huge amount of time to unravel. (if I can at all)
I haven't had time to see if the "Crash" issue is still there. Nor some of the more (to me) minor issues. I can report back on those later as I have the time to investigate.
The Issues I mentioned above are part of what I have privately refer to as the "Big Four". Although there are more minor issues that I didn't address, those are the (current) major issues that (I feel) most severely impact functionality, usability and the serviceability of the program as a whole. While I'm sure that the Team is concerned, is working on them, and will eventually solve them; finding the cause of, and a way to solve "The Big Four" issues seems to have eluded the "Fab Team" for a while. When the major issues are solved, I will start recommending MusicFab to my friends and Family, and start endorsing it far and wide. I am very much looking forward to the next update.
Leave a comment: