In my company we are considering creating a new section in our mobile applications. Currently what we have is basically a video library (hosted by Brightcove).
The idea now is to create an audio library where users could play new content that would be audio only.
Some of that content could be divided into “songs” so to speak, or chapters.
The question is the following:
What would be the best method of storing the content:
upload each “song” as separate assets, or upload them together and then use the chapters (a vtt file) to go to one point or another in the playback? Also, it is very important that the user has the option to hear all the “songs” in a row of the same title, without suffering any interruption between one song and the next.
Thanks in advance
Best answer by Andy Hartono
Hi David,
You may already be aware that Brightcove supports audio-only content:
Rather than considering it the "best" solution, a more effective approach would be to upload each audio track as a separate asset and then curate an audio playlist. This method offers several advantages:
Granular Analytics: Each track has individual analytics, allowing for more detailed performance insights.
Efficient Playlist Management: Playlists can be curated easily without the need to re-transcode files.
Simplified Frontend Integration: Each asset has a unique media ID, making it easier to manage.
Additionally, for instant playback, you can enable "Preload Video Before Playback" in your player settings and configure it to "Preload Video (fastest)" for the best performance.
Preload Video (fastest) -For MP4 videos, this option makes the player load the video immediately (if the browser agrees), even if the user does not eventually watch the video. On the positive side, if the viewer plays the video, it can start playing immediately. On the negative side, this option will increase bandwidth consumption as the preload/load happens even if the viewer does not play the video.
For HLS and DASH, the player loads the metadata of the video and the initial media segments.
Rather than considering it the "best" solution, a more effective approach would be to upload each audio track as a separate asset and then curate an audio playlist. This method offers several advantages:
Granular Analytics: Each track has individual analytics, allowing for more detailed performance insights.
Efficient Playlist Management: Playlists can be curated easily without the need to re-transcode files.
Simplified Frontend Integration: Each asset has a unique media ID, making it easier to manage.
Additionally, for instant playback, you can enable "Preload Video Before Playback" in your player settings and configure it to "Preload Video (fastest)" for the best performance.
Preload Video (fastest) -For MP4 videos, this option makes the player load the video immediately (if the browser agrees), even if the user does not eventually watch the video. On the positive side, if the viewer plays the video, it can start playing immediately. On the negative side, this option will increase bandwidth consumption as the preload/load happens even if the viewer does not play the video.
For HLS and DASH, the player loads the metadata of the video and the initial media segments.
Hi Andy, Thank you very much for your reply. Indeed, by processing audio only, bandwidth consumption is not a concern for me initially. What you say about better organisation and tracking of content makes a lot of sense. The bad news is that I did a small test and the result was a bit disappointing. I'm testing with a Chrome browser, and this will work when publishing to mobile apps only, so the result won't be exactly the same. In any case, I have found that there is a break of almost a second between one track and the next. I don't know if it's possible to improve that behaviour. I have configured the player with the Preload Video option (fastest).
It is not possible to include the player here, is it? Then you could see it.
Thank you for sharing your feedback, and thank you @Andy Hartono for your detailed response!
@David Perez, you can share here the url of your player o player ID to review. Or we can create a Support Ticket in order to follow up your questions.
Additionally, if in any way you think we can improve the pre-load features of our player, please let us know and we will gladly create an enhancement request ticket, so our product team can evaluate it for future releases.
I think the vide have some kind of content restriction and couldn’t reproduce. I’ll create a support ticket in order to ask for additional information and troubleshoot. You will be receiving an email from support.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
