soliton4
soliton4
the compiler parameters do not reflect 100% what is neccessary to build broadway. they are the resulot of trial and error where a functional broadway reflects success and faster running...
you could try to use ALLOW_MEMORY_GROWTH=1 see if that changes your memory issues. i dont recommend using that parameter for the final version as i belive it has performance compromises....
@myjimmy sorry i am not working full time on broadway. just got back to it compile broadway with higher memory setting and you should be fine
without testing it out myself, but i believe the c code assumes its a complete nalu unless there is a 00 00 00 01 separator sequence. so if you feed...
00 00 01 is most likely separator between slices. it makes sense to decode them all at once there is no way i know of to wait for a full...
it depends on your application. in one of my demos / apps i get the stdout from ffmpeg, which doesnt tell me the length of each nalu, in this case...
is this issue resolved?
browadway was compiled with full hd max resolution in mind. you can chane the allocated memory and build your own broadway. that should solve the issue
hi! hard to say. the rendering with webgl works on the gpu and is highly parallelized. so i would guess your performance bottleneck is in the decoding itself. there might...
i have not forgotten you, just being busy with other stuff. i would like to know some numbers, what time difference are we talking about comparing the 2560x1440 stream with...