Have there been any updates to this issue? When I called Audible about this, they told me they would "escalate" my questions about this issue and call me back. The person I spoke with on the phone couldn't tell me why this was changed or if it would ever be changed back, but I'm unclear if the rep fully understood the issue.
A couple weeks ago, John said (in this thread):
There is one alternative that might work, I haven't looked closely at it yet.
Is this "alternative" still a possibility.
It would *really* help us if Audible listeners would communicate their desire to Audible, as I asked before. Otherwise it's just me asking them.
I've already done so, and I'll follow up on the "escalated" issue if I don't hear back from them. The problem, however, is that it seems fairly impossible to get such a request to the right people. When a customer such as myself calls, the reps that respond just don't know that much about this subject, and it seems like the "request" just goes into a black hole.
My "fallback" plan was to revert back to MC 11.0 or 10.0 (where aa files DID work over Media Server), but with the recent support for gapless mp3 playback in MC11.1 (via the LAME tags), I just can't get myself to go back to 11.0 or 10.0 anymore. This Audible limitation with Media Server in 11.1 has therefore become even more important to me lately.
The "workaround" of having to manually navigate to the aa files is a REAL pain since I don't have any tag info when doing this, and since the aa filenames don't contain all the necessary information on "magazine" type aa files in the filename (i.e. I can't tell which one I want to listen to.) This means I have to find the one I want to play via the tags using the "pane" view in MC, then look at the specific name of the file, then manually navigate through my audio library via "Drives and Devices" and find the cryptic filename, after which I can finally play it. This makes poking around for potentially interesting subject matter effectively impossible -- it's just way too clunky.
I'm pretty confident that if this issue is ever going to be solved, the solution will have to come from JRiver and NOT from Audible since JRiver is simply FAR more responsive and vastly more qualified at solving this sort of issue.
Is there still hope? Is there anything else I can do at my end to help?
Thanks,
Larry