Make sure you are not blocking content.

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

One issue that seems more common lately is Firefox's Tracking Protection feature. When it is blocking content in a page, a shield icon will appear at the left end of the address bar next to the padlock icon. This article has more info on managing this feature: Tracking Protection {web link}

https://support.mozilla.org/en-US/kb/fix-video-audio-problems-firefox-windows

https://support.mozilla.org/en-US/kb/fix-common-audio-and-video-issues

https://support.mozilla.org/en-US/kb/html5-audio-and-video-firefox

Hello!

Running a HP Laptop, Win 10 and I7 Processor, fyi. Also did full Defrag and optimization.

The problem is there in Safe Mode as well. Full stop at exactly 29 seconds, lol. I see no shield icon on the left.

Use recommended settings in the Performance section is checked.

What else should I try?

Thank you.....

Here? https://music.amazon.com/home

When I click a song to play, Firefox retrieves numerous files about 1/3 megabyte in size which all seem to added up to the full track. (Just guessing, there's no way to read the contents of these files.)

I'm attaching an example of what I see in Firefox's Network Monitor tool when starting a track. If you want to compare yours:

First, stop the player.

Next, open the Network Monitor in the lower part of the tab using either:

• "3-bar" menu button > Web Developer > Network
• (menu bar) Tools > Web Developer > Network
• (Windows) Ctrl+Shift+e

There's a bar with content type filters, so I suggest clicking Media.

Now, click a different track to play that you haven't played recently (so not in the cache), and Firefox should start listing all the files it is requesting, along with information about whether the request was successful.

Are the requests going through?

By the way, I'm assuming you do not see either:

• Gah, the tab crashed
• Mozilla Crash Reporter window

If you do: your Firefox may have logged some data that would help track down the cause of the problem. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox crashes - asking for support" for steps to get those crash report IDs from the about:crashes page, and then post some of the recent ones here.

I did that exactly and got just one line like yours. Then it stopped.

Hummm..... Thoughts??

Did the one line have a "200" success code at the left end? I wonder what happened to the other requests. Usually the way it works is that the page has or retrieves a playlist (for example, a .m3u file) that lists all the pieces needed for the audio/video media. Maybe that part isn't working. I'll try to look at it again tonight, but if you turn off the Media filter and look at whatever is requested just before that first chunk, maybe you can see the playlist.

Here's that one line:

Here's more lines when I play an initial song.

Notice the "Finish" on the bottom - it keeps counting up.

It still stops at 29 Seconds, the Lyrics stop, but the 3 blue equalizer bars keep moving up and down.

What to try next??

Ok, this is weird............

I unchecked "Play digital rights management". See attached image.

Opened up a new tab and full songs play!! See attached image with the Yellow Bar on the top saying I must have DRM enabled to play audio or video....

BUT on the same tab that stopped, it will not play any part of any song.

Thoughts??

I think paid music services generally require DRM to be enabled, so the stopped player makes more sense than the working one...

The media retrievals are very small. I don't know how many seconds fit in 65KB, but I suspect not many. Do you think Amazon could support us on this and recognize the problem?

Yea, it's backwards; it plays a new tab with DRM unchecked.....

I talked to Amazon and all they could come up with was do not use Firefox; they recommend Chrome. Ugh.

Next?