MASTERING in GarageBand iOS is no longer possible. R14 and/or GB issue.

So as this is the only support route I am aware of for Apple, I have to post this here, but how anybody out there could possibly fix this, is beyond me. Here we go anyway...

Mastering, can no longer be performed on my ipad with 512Gb SSD, and the 4Gb RAM that Apple fit it seems, and the release 14 of their Operating System, and the GarageBand latest version 2.3.9 (5067). The device is an iPad Pro 2.

The method of mastering, involves outputting a stereo audio file from a GB multitrack song, then taking that ‘mixed’ file as I term it, and bringing it into a song specifically for the purposes of mastering within GarageBand iOS.

Some people take the audio at some stage, elsewhere, I do not, I only use GB on iOS as my DAW. This is not a lack of choice (I have Cubase 9.5, Studio One V4 on a very good SSD PC, and so on). I rate this DAW by Apple as the very best fit for me. It is an extraordinary piece of software. It’s simply got such serious issues now, I cannot get it to work.

The mastering stage workflow I don’t wish to bore people with, but basically, outputting a stereo file from a song using the ‘share’ process, happens multiple times during said mastering stage. It is this outputting of a stereo file, where the complete inability to alter the volume/gain level of the stereo file has become apparent.

Up until two weeks ago, it was fine, if a little convoluted and imperfect. It worked and was workable. Now, nothing alters the dB level of the outputted song...

• not the TRACK volume inside the mastering song
• not the MAIN ipad volume inside the mastering song
• not even the plugin - ProQ3 alters the outputted file dB

ALL of these, when actually listening to the song inside the song editor, on the ipad, DO alter the volume the ipad outputs, exactly as you would expect, as it always has. They simply have no effect when using ‘share’ to output a stereo audio file.

Many other issues, some I posted, this forum limits wordage. Help appreciated, but fixing this is non-trivial due to the complications of having valuable files involved.

my best to all.