We have moved to a new Sailfish OS Forum. Please start new discussions there.
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bugreport about not being able to play it back or upload it to youtube - this is not about this bug, this is solely about file-size)!
2 | retagged |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bugreport about not being able to play it back or upload it to youtube - this is not about this bug, this is solely about file-size)!
3 | No.3 Revision |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much.
I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bugreport bug-report about not being able to play it back or upload it to youtube YouTube - this is not about this bug, this is solely about file-size)!
4 | No.4 Revision |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bug-report about not being able to play it back or upload it to YouTube - this is not about this bug, this is solely about file-size)!
According to http://www.ic.tu-berlin.de/fileadmin/fg121/Source-Coding_WS12/selected-readings/2012_12_IEEE-HEVC-Performance.pdf you can lower the bitrate by 45-65% without loosing device performance or reducing quality.
5 | No.5 Revision |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bug-report about not being able to play it back or upload it to YouTube - this is not about this bug, this is solely about file-size)!
According to http://www.ic.tu-berlin.de/fileadmin/fg121/Source-Coding_WS12/selected-readings/2012_12_IEEE-HEVC-Performance.pdf you can lower the bitrate by 45-65% without loosing device performance or reducing quality.
Just another TJC popped up requesting hardware support for HEVC https://together.jolla.com/question/91133/x265-hevc-hardware-codec-support/ how about we get some better multimedia support?
6 | retagged |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bug-report about not being able to play it back or upload it to YouTube - this is not about this bug, this is solely about file-size)!
According to http://www.ic.tu-berlin.de/fileadmin/fg121/Source-Coding_WS12/selected-readings/2012_12_IEEE-HEVC-Performance.pdf you can lower the bitrate by 45-65% without loosing device performance or reducing quality.
Just another TJC popped up requesting hardware support for HEVC https://together.jolla.com/question/91133/x265-hevc-hardware-codec-support/ how about we get some better multimedia support?
7 | No.7 Revision |
The video recording file-size is exorbitantly high - 25MB for 17sec of video is way to much. I know that you need G/CPU power for real-time conversion but what do you do besides recording a video when you actually record a video? Give the camera-app and the conversion some more system-juice and let it convert to a suitable file-size and of course a format that is widely recognized (there is a bug-report about not being able to play it back or upload it to YouTube - this is not about this bug, this is solely about file-size)!
According to http://www.ic.tu-berlin.de/fileadmin/fg121/Source-Coding_WS12/selected-readings/2012_12_IEEE-HEVC-Performance.pdf you can lower the bitrate by 45-65% without loosing device performance or reducing quality.
Just another TJC popped up requesting hardware support for HEVC https://together.jolla.com/question/91133/x265-hevc-hardware-codec-support/ how about we get some better multimedia support?
EDIT: In 2016 already, TV manufacturers adapt to HEVC (h.265) for streaming, recording and playback. New dvb will be hevc and old stuff will vanish till end of 2018. So how does it look for us 3 years after the initial request?