Question / Help Animated JPG File wont work as an alert browsersource.

N

Nalfeyn

New Member
So I have got alerts setting up with streamlabs and a animated jpg file, known as ajpg file.
The alert is shown correctly on the Streamlab site, but in OBS the file wont start to animate.

When I put the file in a mediasource it is animated correctly.

Any suggestions or tips?

Cheers, Nalfeyn.
 
Rektroth

Rektroth

New Member
Streamlabs only supports the following: PNG, JPEG, GIF, and WEBM. (LINK)
Not sure how you got it to upload at all.

More than likely, though, OBS's browser viewer is interpreting it like a normal JPEG, and you're gonna have to use a GIF instead.
(I've never even heard of an AJPEG, and a Google search of "ajpeg", "ajpg", and "animated jpeg" don't show anything other than "jpeg's cannot be animated.")
 
N

Nalfeyn

New Member
The filetype is still ".jpg" - but its a animated file.
Therefore, Streamlabs supports the file - but OBS does not in the Browsersource.
If i add the file to obs as an Mediasource everthing is correctly and the image starts to animate.

If I rename it to a gif file, it will be coded into a gif. and the half-transparent is lost.
 
N

Nalfeyn

New Member
2 files.
1 file which shows the difference between jpg and gif.

1 is a ajpg file
 

Attachments

  • demo.png
    demo.png
    18.6 KB · Views: 111
O

Osiris

Active Member
That says APNG not AJPG...
Chromium 57 does not support APNG, which is what the browser source uses.
 
N

Nalfeyn

New Member
There are apng and ajpg files. Both uses a pattern of over 16 billions colours and both support half-transperency.

A gif file uses only 256 colours and DOES NOT support half transparency.
Do you really wanna argue about how the file is named right now?

Because if I convert a apng file to a jpg file, it is still animated and is so called AJPG. And it STILL support half-transparency for each pixel and STILL uses over 16 billions colours, instead of a gif while which does not.
 
You must log in or register to reply here.
Top