Now, trying to play the video from appwrite:
player.open(
Media(
"http://178.128.120.48/v1/storage/buckets/65d16fe863975f4dc588/files/66d3416b79c3a12462e9/view?project=65c5df06933e47ebdec4&mode=admin"
// "https://pixeldrain.com/api/file/n4qUcfEb"
// AppwriteClient.getUrl(
// bucketId: attachment.bucketId,
// fileID: attachment.id,
// ),
// httpHeaders: {
// "x-appwrite-jwt": attachment.token,
// },
),
play: false,
);
If you try to observe the video, trying to jump a specific duration but it seems it failed to load
Got an error on docker logs
actually I did not use a custom domain on my self hosted
Oh wait this is the storage service yes?
Happens on custom domain(function) and storage
Recently I blame the package I use but, I curious if I am trying to play a video that is long duration and not from appwrite. ANd I saw that there is no wrong in package because it plays well
Appwrite Storage seems has bugs
yes
Does the package rely on content-length?
What package is it
This one
Played the video on web and the warning in docker still occured
I dont kno what could be the issue here actually.
I'll save this thread for later
I have made similiar experiences
alrights thank you @Joshi
Can you do me a favor and try other packages and then tell me if the issue persist there as well
I think appwrite storage does return the proper parts of the file when you specify the content-range
but from my testing it still does not play properly sometimes idk why
Good to know I'm not alone
will do that
https://github.com/appwrite/appwrite/issues/8600
Create an issue for this
I just fixed it, I used video player , chewie, and video_player_win
and yeah it goes well
Recommended threads
- Session Token not saving
On several devices, the session token is not saved as a cookie during creation. This results in a 401 error when checking out the account. The Appwrite instance...
- Memory error during migration
Appwrite migration crashes with the following message: Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 33554440 bytes) in /usr/...
- type generation on same columns in table
is there way to prevent this ? or only need to update column name like table prefix?