Questions about MusicFab

[supine]

Update on my last post. - I was unable to download anything for the rest of that day, but the next day everything is normal, and my allotment has been restored. Glitch? If so, I believe it might be an occasional but repetitive one.

[supine]

I know this thread has been idle for a while, however I have a question.
A while back, I had an issue with the 322 error code. I was rather embarrassed when someone pointed out that I had zero downloads left, and that was the reason for the 322 error code. I had thought that I had waited long enough to reset the number of downloads, and so never looked at that number.

Yesterday evening, I used up my quota for the day, around 11:15pm. Since I still had files in the que, I took a shower, got ready for bed and basically waisted time for 45 minutes. At 12:01AM, I refreshed the screen and looked again. The screen still showed zero downloads left. I closed the program, rebooted the computer, and kept refreshing the screen until 12:30 AM, and still had zero downloads left. Exhausted, I left the program up, and went to bed. I didn't check the screen again until a little after 10:00AM. to cut to the chase, it's 1:30PM. I have rebooted the computer, and refreshed the screen several times today, and still have zero downloads.

Is this a known issue, and if it is; is there a work around?

[supine]

For those who noticed MusicFab erroring out on downloads (Spotify), I have turned in a ticket on this issue, and the reply was that it is a known issue and they are working on it. --Info--

[HAMsmoke]

Did you not read my top post? I describe the same issue as you just did. And yes, I have had similar sign-in issues, however, I could always log in using Chrome by closing the browser entirely (after signing out and signing back in again). Not now though. I cannot sign in, and cannot browse.

[supine]

Hello again. @StPeterOrding2015, thank you for your reply back in April. It's nice to hear from you. Greetings again! Sadly, I didn't get the E-mail when you posted your reply. I hope you are doing well.

Now... to the point.
I am having trouble with the Youtube portion of MusicFab. The instructions in MusicFab, say to log in with Chrome or Edge from a browser, then close the browser leaving it active in "Task Manager".
1. In stead of close, I believe they should have said Minimize. When you close the browser, it disappears from Task Manager, and MusicFab will not log in.
2. Although the instructions say I can use either Chrome or Edge, I have only had success logging in using the Edge browser. Chrome did not work at all to log into MusicFab.
3. Once I do get logged into Youtube in MusicFab (Which is a small struggle.), The search Window remains blank after any search, and I am unable to select any content. Search and play works fine in any browser, but does not work in Musicfab. The Youtube Downloader will not work for me at all.

Is anyone else having this issue?
Does anyone have a Fix, or Work-Around?

[StPeterOrding2015]

Hi supine,
i use the 1.0.2.8 and this version works fine - but slow - for me with no problems (except that every now and then the “You have reached the tab limit.
There are too many tabs open. Close this tab and continue listening to music." appears - and then nothing works again -).

BUT, the 1.0..6. was the fastest version ever.

greetings

[supine]

I haven't been on this thread since MusicFab was stabilized. Just a note: I haven't used MusicFab in a while. Life events kept me busy, and I just wasn't able to "Play" with it for a while. I did however, keep up with the updates. When I recently tried to use it, all of my tracks were dumped into a folder called "Other" regardless of album or artist, and in spite of my output selections in settings.

A total uninstall and re-install; and ensuring that the Log and temp folders were deleted, solved this issue. Hopefully nobody else has run across this, but I figured that I would post my fix for this snag I ran into, and (again, hopefully) save someone a hassle.

[Sylvia]

Well, MusicFab has crashed three times in an hour. (Log attached)

Album art still isn't showing up in Windows until I put it back. It's in the downloaded tag (Metadata), it just does not show up in Windows. Once I resend the album artwork back into the tag, I have no problem.

Adding to the que past a certain point in an artists Discography for a very prolific artist, still bounces me to the top of the album/discography list, forcing me to scroll all the way back down to where I was. By the time that starts happening, it's a very long way down to where I was. (Examples: Barbra Streisand, Kenny Rodgers) I found this after I zipped the log. I can send another if you wish, but a little practical experimentation should confirm this. I don't know if something like that would show up in the log anyway.

On the upside, I have no problem adding to the que. So far, the issue with the selection window not coming up has not shown up. Despite the crashes, the downloads are fast and reliable. A simple restart has brought me rapidly back in service. This instance of MusicFab has been up for over thirty minutes with no issues besides the aforementioned.

We will continue to work on the issues, so stay tuned for a new version!

[supine]

Well, MusicFab has crashed three times in an hour. (Log attached)

Album art still isn't showing up in Windows until I put it back. It's in the downloaded tag (Metadata), it just does not show up in Windows. Once I resend the album artwork back into the tag, I have no problem.

Adding to the que past a certain point in an artists Discography for a very prolific artist, still bounces me to the top of the album/discography list, forcing me to scroll all the way back down to where I was. By the time that starts happening, it's a very long way down to where I was. (Examples: Barbra Streisand, Kenny Rodgers) I found this after I zipped the log. I can send another if you wish, but a little practical experimentation should confirm this. I don't know if something like that would show up in the log anyway.

On the upside, I have no problem adding to the que. So far, the issue with the selection window not coming up has not shown up. Despite the crashes, the downloads are fast and reliable. A simple restart has brought me rapidly back in service. This instance of MusicFab has been up for over thirty minutes with no issues besides the aforementioned.

[supine]

Suc-Cess! 1.0.2.7 has picked up from the existing que and seems to be working (with Spotify) like a champ. More as I put the software through a little more testing. StPeterOrding2015: please let me know what you find on your end.

[Sylvia]

BTW: If the "Protected content" screen doesn't show. or I restart several times until it goes away, I can add whatever I want to the download que, but it will not download. It still says analyzing until it fails.

Yes, the "Protected content" screen and download issues are due to this drm upgrade; the dev team is still working on it and will have a new version available soon!

[supine]

BTW: If the "Protected content" screen doesn't show. or I restart several times until it goes away, I can add whatever I want to the download que, but it will not download. It still says analyzing until it fails.

[supine]

I just updated to 1.0.2.6. Still no success.

Patiently waiting.

[supine]

It may be that, as a person from G...., I stand for honesty and openness. In any case, my experience in the IT is: don't bury your head in the sand and wait until the customer notices the error, proactively informing as early as possible and showing solutions is the way forward.

I agree whole heartedly about informing as early as possible and four days without a word was troubling. Showing possible solutions is also part of the open information concept... as long as you have some idea of what that solution may be. In this case, the development team was probably blind to any solutions until the DRM package was deployed and they could get a good look at it. Yes, It would have been nice if the team had jumped right in and assured customers that they were aware of the problem and are working on a solution as fast as possible; even if there is no definitive estimated time to repair (ETR). Well, there is no turning back the clock and the Staff has distributed that message (even if it WAS late). I, myself, can either stay upset, or get over it. The later seems more beneficial to my health. The circumstances leading to my strife were beyond my control. We have been assured by the Staff that the Development Team is working on a solution as fast as they are able, and will deploy the fix as soon as they have a working solution. Right now, I'm kind of stuck.. The only thing I can do now, is try to have some faith in the Fab Team, and wait for a solution to be found and deployed.

StPeterOrding2015 : On a side note: You have been with this project as long or longer than I have. I'm pretty sure you remember the abomination they were actually charging people for when this software first deployed. Although the road has been long and there have been missteps along the way; the difference between what this software was then and what it is now is vast and somewhat impressive. I had a VERY long list of grievances with this software when it deployed, and if you remember, thought that it should have never left Beta. So far, given time, the Development Team have addressed almost every issue. I would like to think that this major "snag" is not beyond this teams capabilities as their track record has shown; and that a solution will be forthcoming if we just have patience. I am absolutely certain that you are already aware of all of this, and have the patience it takes. ...If you were not already aware of this or lacked the patience needed, I'm betting that you would not still be around to read this diatribe.

[StPeterOrding2015]

Hmmm,
so if I tried a demo version and it didn't work I would be off the hook fpr a while, especially since the trial version only supports downloading 3 songs per service.

If I were to buy the product without trying it out - which you should never do these days - and it doesn't work/not right away but only at some point, then I would feel cheated.

It may be that, as a person from G...., I stand for honesty and openness. In any case, my experience in the IT is: don't bury your head in the sand and wait until the customer notices the error, proactively informing as early as possible and showing solutions is the way forward.