Metadata Viewer/Editor
in progress
Ben Bowler
in progress
We have the first version of metadata viewing in development right now. Editor to come afterwards.
Joe Belham
Thank you so much to everyone who's been commenting in this post - your feedback is invaluable! 🙏
Please do let us know if there are other features you'd like to see implemented by adding new posts to the roadmap 🙌
Ben Bowler
planned
Based on several suggestions from users we are planning to work on enhanced metadata editing in the app. Please continue to add details to this page on how you would like to see this implemented.
Ben Bowler
Antony Darvill did any specific files fail to process? If so can you send the URL to those files to hello@aux.app so we can investigate.
A
Antony Darvill
Ben Bowler: initially all .wavs were successful and all .aifs failed. Will try again and report back any upload issues.
Ben Bowler
Antony Darvill: OK, the tech team will take a look. We might drop you a line to see if there is anything about those AIF files that we need to adjust our systems for.
A
Antony Darvill
Ben Bowler: just confirming that the old .aifs I uploaded now have a waveform image and a playing time. However, they won't play and list as an "other" file type. Same can be said for newly uploaded .aifs. Their true file type is "AIFF-C audio". Happy to investigate further with you or your team.
Ben Bowler
Antony Darvill: We're taking a look. What DAW did you use to generate these?
A
Antony Darvill
Ben Bowler: I exported them from DISCO. I’ll try an AIF from my DAW (Studio One).
A
Antony Darvill
Confirming that my DAW (Studio One) also exports .aifs as "AIFF-C", once uploaded the file type is still listed as "Other" but IT PLAYS!
I thought it might be a file size issue with AIFs but it's playing a 76MB file. Perhaps DISCO is rendering their exports in way that Aux doesn't like. ¯\_(ツ)_/¯
Ben Bowler
Antony Darvill: Good news! We've deployed a fix to the app to support AIF files correctly. You'll need to re-upload the tracks for them to be processed correctly. Give it a go and let us know how it works for you.
A
Antony Darvill
Nice development, Ben. Works just like .wavs. :-)
I honestly believe that AIFs ability to carry more and better structured meta data will see it eclipse .wav files (probably the current industry standard).
Thanks.
G
Gareth Simpson
Antony Darvill: Can confirm, Disco does mess with file names and meta-data.
A
Antony Darvill
Gareth, that's interesting. Do you think it's a quirk or a defensive strategy to keep things in their environment - or something else?
G
Gareth Simpson
Antony Darvill: I think it's more to do with keeping convention with their data schema and CMS than anything defensive or sinister - it is, however, annoying for certain use-cases - Disco however is a distribution tool.
Ben Bowler
Ben Bowler
Hey Antony, you can upload AIFs and you should be able to preview them in the app. But you're right, metadata editing is not supported currently.
Ben Bowler
We have the start of the actions metadata here in the form of file history, is there anything you would want to see here? ...
nonconformist
Ben Bowler: yepp, like this, file history (of interactions)
although I explored the site and I've seen since, there is a kind of three-month lifespan for uploaded files so it wouldn't make much sense to maintain such records in that case.
Ben Bowler
nonconformist: That text is actually incorrect on the site. All files are uploaded perminanently - there is no 3 month limit. The file history is perminant too so you can keep track of all interaction on these files.
I love the metadata editor idea. Looking at it now.
nonconformist
Ben Bowler: happy days :D
Ben Bowler
Hey nonconformist, what kind of metadata are you refering totoo? Do you mean all of this metadata as you see in Apple Music:referring
nonconformist
furthermore, the kind of metadata I'd also find interesting --especially in case of open files/projects-- is keeping records of certain interactions like count of plays, -projects been added to, -downloads, -comments etc.
nonconformist
maybe even make it a record of events logging the above mentioned entries with link to user's aux account. Except in case of plays, no one shall have too much privacy concerns just for playing a track.
With the consent of the user cautiously informed about the rest prior to letting one interacting with the content -I think- is reasonable.
Well, it can be an opt-in condition set by the initial uploader, that other users need to accept in order to enable anything beyond playing content.