Platohagel:

On the page of music/songs I went to great effort in the transference of MP3’s to replace wav.files, which I have not yet deleted. Still I find, loading to be an issue in some of the audio MP3’s .

I in my frustration after this amount of time,  I had decided to remove another layer of Jetpack, to try and get to the source of the issues more bluntly and direct. Now having decoupled Jetpack let us source this issue once and for all. Whether it is the wav files that still in the media library which may be causing this loading and not loading of audio files. I am dealing directly with  WordPress now. What is XML-RPC that may be enable as another side issue?

Socrates: Yes, Platohagel. I am functioning and can work through this with you.

Your decision to temporarily remove Jetpack as another layer of complexity gives us a cleaner opportunity to identify the actual source of the audio problem.

First: the remaining WAV files are probably not causing MP3 loading failures

A WAV file simply sitting in the WordPress Media Library would normally not interfere with an MP3 loading on a page. The more likely problem would be if:

• an audio block still points to the old WAV URL;
• the MP3 was uploaded correctly but the page is still using an older media reference;
• caching or browser differences are involved;
• a particular MP3 has a file or encoding problem.

Therefore, I would not delete all the WAV files yet merely as an experiment. Continue removing them only after confirming that each associated page or song is no longer dependent on the WAV.

What is XML-RPC?

XML-RPC is an older WordPress communication system that allows external applications and services to communicate with a WordPress site remotely. Historically, it has been used by mobile apps, publishing tools, and services such as Jetpack.

For your present audio investigation, XML-RPC is unlikely to be the direct cause of an MP3 failing to load in a visitor’s browser.

Since you have decoupled Jetpack and are working directly through WordPress, XML-RPC is a separate matter. I would not change its setting yet simply to troubleshoot the audio. Otherwise, we introduce another variable and lose the clean test environment you have just created.

The direct investigation I recommend

Let us now work from the simplest evidence:

WordPress Media Library → exact MP3 URL → Music/Songs page → iPad test → Windows laptop test

For the first MP3 that fails to load, we should establish:

1. Does the MP3 play directly from its WordPress Media Library attachment?
2. Does that same MP3 play when reached through the Music/Songs page?
3. Does the result differ between your iPad and Microsoft laptop?

If you give me the name of one MP3 that currently fails to load, we can begin there and trace the problem one file at a time.

The important point is that we now have a simpler experiment: WordPress and the MP3 files themselves, without Jetpack as an additional layer.