3 bugs found

luckygandalf · February 18

I am a big music consumer and an IT trainer, and I haven't found any service like yours! This deserves that I conduct a training for my clients to make your service known.

That said, I have found 3 bugs:

We sometimes use apostrophes in French. Example: "L’emprise" And the system does not find the titles when there are apostrophes in them and when conducting a search.
An error is displayed (Slim Application Error A website error has occurred. Sorry for the temporary inconvenience.) when clicking on an artist who actually has 2 artists, separated by a comma. Example: "David Bowie, Trevor Jones"
At least half of the AIFF files are unreadable. I had to convert them to WAV, then there were no problems!

So far, I haven't found anything else that wasn't working, and believe me, I am picky and I see all the problems :-D

Best regards,

gravelld · February 18

Thanks @luckygandalf ! I'll look into the cause of those in the coming few days...

gravelld · February 19

We sometimes use apostrophes in French. Example: "L’emprise" And the system does not find the titles when there are apostrophes in them and when conducting a search.

I just ran some tests on this. I can see that by playing about with the underlying text search I can make this work, but the queries we are sending don't result in any results. If you just search for "emprise" I think it should work - but does that not make much sense? My limited knowledge of French is that "l'" is just the shortened form of "the".

An error is displayed (Slim Application Error A website error has occurred. Sorry for the temporary inconvenience.) when clicking on an artist who actually has 2 artists, separated by a comma. Example: "David Bowie, Trevor Jones"

Looks like this is the same bug as one we're just fixing - hopefully the fix should be out on Tuesday. In the meantime, if you replace "artist" with "band" in the URL it should work:

https://play.asti.ga/band/David%20Bowie,%20Trevor%20Jones

At least half of the AIFF files are unreadable. I had to convert them to WAV, then there were no problems!

Could you give me a path to an example file of this?

luckygandalf · February 20

Hello, thank you for the response. Unfortunately, I no longer have AIF files; I've replaced everything with WAV. But I'm not surprised because AIF is very proprietary and often has recognition issues on some systems.

gravelld · February 20

Yeah... but would've liked to have looked into that all the same. No worries! 🙂

luckygandalf · February 21

You're right, it's not a solution to circumvent the problem. So, I have uploaded an AIF album that was problematic among others for you to take a look at. The playback of some tracks never starts. Here is the path: https://play.asti.ga/album/Violator/Depeche%20Mode

Another thing I've noticed is that if we want to switch to an annual subscription, we don't have that option in the account. Am I required to cancel the current one (monthly) to then take out an annual one?

gravelld · February 21

Thanks for the AIFF files.

Erggh - yes we need an upgrade option. For now, if you could cancel your current one and restart with annual that would be easiest. I'll refund the remainder of the monthly plan. Let me know you've done it, because it's a manual process.

gravelld · February 21

No. 2 should be fixed now... https://community.asti.ga/discussion/comment/3158/#Comment_3158

gravelld · February 22

I've worked out the AIFF problem and... wow.

I just worked on one file - the first track in the album you mentioned. I suppose other tracks could have different problems, but let's ignore that possibility for now.

The problem is that the cover art embedded in the file is declared as a PNG, when it's actually a JPEG. If I change the metadata about the image to say it's a JPEG, it plays fine.

For file types like AIFFs, and because they aren't supported for playback for the Web, we convert them to FLACs. We use a common tool called ffmpeg for this. When we perform the conversion, this fails.

I've tried working with ffmpeg to ignore this, but the only way I can get it to work is if it ignores all encoding, including the audio encoding. I don't think this is useful because we want the error message for such cases. So I'll look into whether we can better communicate the underlying issue.

luckygandalf · February 23

Thank you for looking into the problem so quickly... Does this mean it's better to use WAV or FLAC then? Because I'm not looking for compression, I find it a shame to compress when storage is no longer an issue. That might have been true 5 or 10 years ago, but today... Otherwise, I have a tool to convert all my AIF files to WAV or FLAC.

gravelld · February 23

FLAC is always my recommendation unless there's something else in your setup which precludes its use (it can be a pain in the Apple ecosystem, although not insurmountable).

The formats that are not transcoded are:

aac
flac
mp3
ogg
oga
opus
wav

gravelld · May 28

I had another report of this so I wanted to update with a few more findings.

In the latest case, the input AIFF file was using an ID3v2.3 tag which had an embedded image with a MIME type of `image/jpeg`.

When we convert the file using ffmpeg, it creates a FLAC with an embedded PNG rather than JPEG:

   Stream #0:1: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 500x500 [SAR 1:1 DAR 1:1], 90k tbr, 90k tbn, 90k tbc (attached pic)
...
Stream mapping:
 Stream #0:1 -> #0:0 (mjpeg (native) -> png (native))
 Stream #0:0 -> #0:1 (pcm_s16be (native) -> flac (native))
...
Output #0, flac, to 'output.aiff.flac':
   Stream #0:0: Video: png, rgb24(progressive), 500x500 [SAR 1:1 DAR 1:1], q=2-31, 200 kb/s, 90k fps, 90k tbn, 90k tbc (attached pic)
   Metadata:
     comment        : Cover (front)
     encoder        : Lavc58.91.100 png
...

This results in a FLAC streamed to the browser than embeds a PNG rather than a JPEG, and this is what the browser seems to fail on. In Firefox we get "Failed to init decoder". In Chrome it's "DEMUXER_ERROR_COULD_NOT_OPEN: FFmpegDemuxer: open context failed".

~~I think there are two clear issues - why is ffmpeg transcoding the PNG, and why can't the browser play an audio file with an embedded PNG? I'll look into those.~~

I did some more digging and I think the above was actually caused by our server in development which, despite transcoding to FLAC, still reports the file as audio/x-aiff. In production it's reported as audio/x-flac and it works ok for me.

So now I'm trying to find out why the Content-Type is incorrectly reported in some cases...

3 bugs found

Comments