Improvements
Category | Description | Priority | Difficulty | Comments | Documents |
Media Library | Artists can not change his audio file when uploaded one, even if the track is not used in any service yet. The user should be able to change the audio file if he makes a mistake, before it is sent to services. | ||||
Distribution / Dashboard / UX | Metadata locked - even if release is put on draft status, artists can't do metadata changes to follow DSP guidelines. | ||||
Distribution (Odoo) + Media section | No way to see which DSP links correspond to which collaborating Artist on a release in the moderation queue. Adding DSP links when creating collaborators would be huge. | There is no way for the moderator which DSP link corresponds to the right featured or with artist. | |||
Trackmetadata / UX | When required track metadata is missing, the platform could do better at specifying which one. | We receive a lot of tickets about artists confused when they are missing metadata and they are not able to identify what is it exactly that they are missing. | |||
Track Metadata / Distribution (Dashboard) | Version field should be open for artists to customise, instead of restricted to our options. For example: They Don't Care About Us (Slow Remix) I Love Winamp (Live from Forest National) Song of The Summer (2016 Remake) | Many artists need to customize the version fields and end up using the title, which does not follow DSP Content Guidelines. § | |||
Distribution (Dashboard) | "The release summary could include the Title of the release + the version in brackets + featuring artists So artists have a visual of how it will look on DSPs and what they are sending. They Don't Care About Us (Slow Remix) | ||||
Distribution (Odoo) | Crucial Metadata not visibile to moderator To identify an issue related to the metadata according to content guidelines, such as correct songwriter credits, the moderator needs to upload the release to SonoSuite first, as the information is not visible moderation queue in Odoo. | Suggested improvement: All track and distribution metadata should be visible to moderation in Odoo to ensure DSP content guidelines are followed from the jump. Emphasis on: Composer and Lyricist fields, Remixer, Genre. | |||
Distribution (Odoo) | Bulk actions are not possible in Distribution moderation. In cases where we are moderating for users with large catalogs, or a vast amount of release submission, moderation becomes an excessively manual process, as each release has to be moderated one by one. | Suggested improvement: Moderation could be optimized if bulk acceptances or rejections could be done. This could work alongside adding rejection reasons in an automated flow: - Releases could be rejected or set to 'In Review' in bulk. - This triggers a choice of rejection reason for moderator - This triggers a message to the artist + status change. | |||
Distribution (Odoo) | There is no way to specify a reason for rejection of a release Suggested improvement: Reasons for rejection Bad audio quality AI generated Invalid cover art Ineligible content Copyright infringement Abrupt start or ending" | For reporting, AI agent training and automations in our workflow and emails sent, we need to collect the reasons for rejecting a release. | |||
Distribution (Odoo) | Add the column ""Ok for distribution "" on distribution dashboard. If we add this column in the moderation view, it will be quicker to know which releases were approved by moderators when processing large volumes. This will expedite the creation of the data export and smoothen the procedure. | ||||
Distribution (Odoo) | Show release history of an artist whenever a release is submitted, or on the artist profile. This allows us to prevent fraud and catch it quicker on moderation by knowing repeat offendors as they often submit releases with the same issues they did before. | Suggested improvement: Total Submissions Total Accepted Total Rejected Reasons for Rejection" | |||
Content ID | Tracks rejected by AdRev remain accepted on Winamp and there is no way to find out which they are, unless Adrev provides an export. Artist expect revenue and think all is well when their tracks aren't monetized. | Suggested improvement: Track import in Odoo to change the statuses of tracks in bulk. | |||
Content ID / Distribution | Releases accepted in Distribution and submitted in CID should be automatically accepted or marked as acceptable for CID. Shorten the moderation time for CID + increase volume and potential revenue on CID. | Suggested improvement: | |||
Website Builder | No option to customize the size of the typography | ||||
Account | Underage users are able to accept T&C and make use of the services. Per our T&C, underage individuals can't enter a binding agreement, and as a result, they cannot use our services. | ||||
Copyright Conflict Moderation | Users without KYC can submit copyright challenges. As a result, moderator is not able to determine copyright ownership because we don't know the legal name of the user. | Suggested improvement: Users who have not completed the KYC are prompted to verify identity before challenging the conflict. Other ideas: Users with KYC ≠ ""Verified"" who challenge copyright conflicts are automatically rejected in Odoo." | |||
Copyright Conflict Moderation | Audio details don't refer to the track uploaded by the user, but the matched track from ACR As a result, email templates do not contain the right track information, and require manual changes in order to include the track information. | Suggested improvement: The fields in the Audio Information section of the copyright conflict should include information about the track upoloded by the user. Audio Title = Name of Track impacted by a copyright flag in WFA Audio ISRC = ISRC of the track impacted by the copyright flag in WFA Track UID = The UID of the track impacted by the copyright flag in WFA | |||
Copyright Conflict Moderation | There is no field that includes the user's legal name on copyright challlenge ticket. Relying only on the user first and last name when it comes to moderation does not suffice as we need to verify composer names with Spotify credits, and our users don't always put their legal name in their user first and last name. So, the moderator needs to search for the user details separately on another tab, causing longer processing time. | Suggested improvement: Add a field that includes the legal name of the user for improved moderation." | |||
Copyright Conflict Moderation | When a track that with a conflict has been deleted, the copyright conflict remains active despite the deletion. In these cases, the moderator reviews the conflict, the ticket created, and the audio link, only to find a broken link with a file missing. This increases processing time for copyright conflicts. | Suggested improvement: Automatically delete the copyright conflict if the system can identify that the audio file is missing. | |||
Copyright Conflict Moderation | Bulk actions are not possible in copyright conflict moderation | ||||
Copyright Conflict Moderation | The ACR Scan details don't always contain the right copyright match The automatic scan gives us with a match with an ISRC for a track that's already takendown. As a result, we have to download the track and manually check for any other matches. This is more expensive, as the process takes place under a separate bucket and also leads to a higher processing time. | Suggested improvement: Providing the ISRC codes of more ACR matches if they are available. Number could be between 1-5, as often ACR provides matches with ISRC codes of tracks that have already been taken down. | |||
Copyright Conflitc Moderation | There is no field to add a reason for the rejection. | For reporting, AI agent training and automations we need to collect the reasons for rejecting a copyright challenge. Suggested improvement: Add a Reason for Rejection field when a conflict is rejected. Field options: Full match Insufficient evidence Audio tempering Cover or remix Audiowatermarks | |||
Social Media Manager service | It is now written in this service "Publish real-time or scheduled posts directly to your social media accounts from the Fanzone of Winamp for Artists." | 0 | |||
Llama image on Overview | Delete Llama images from the overview latest activities | ||||
Overview/Revenue | Add Merchandising in the revenue chart on the Overview page | ||||
Reporting | Add Merchandising | ||||
Statistics | Having accurate statistics in it or delete it | ||||
Upsales to Ultra plan | Allow a user to have different kind of subscriptions (plan, duration) under the same label | ||||
In the Overview section of the user, add Merchandising service description |
| ||||
Payment | When I want to upsell from the user view, I can not add a promo code nor see a checkout. It should be possible
| ||||
Subscription page | When with Essential plan, the billing page should be reviewed in terms of design. There is no standard plan any more. We should just highlight the Ultra plan & customs for label. | ||||
Merchandising | We should display the whole price for Merch items on websites shop, including the numbers after the , | ||||
Fanzone price |
We should write €3/month (+VAT) to explain the price discloed does not include VAT, to avoid "bad" suprises when checkout. | ||||
Website builder |
The contact form on websites is not working. I click send message and I'm baclk again on the same page, with no confirmation about if my message has been sent or not. | ||||
Pricing page | The pricing page inside the platform could look more appealing, maybe more aligned with the pricing page on the website, and highlight more the benefits of the Ultra plan | ||||
Pricing page | We should add "Dedicated Account Manager" for Ultra users |




