Hi,
with WiMo i was able to play podcasts (h264/aac, 368x208, ~200kBit/s) somewhat smooth with TCMP. With android i get - well - with some luck a frame per minute. I would have said its because of a incomplete/non-optimized GPU-Driver but Youtube (SD) plays fine so for me this looks more like a codec/app-issue. Has anyone already looked for a solution? Any tips on codecs/apps that should work?
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
We're not done with the port... I think this is a pretty minor bug considering the other major ones we have out there....
arrrghhh said:
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
Click to expand...
Click to collapse
...hm… for me exactly this looked like a codec-thing… i dont know the mobile side but for pc i remember something like VP6 for SD and X264 for HD on Youtube. But thanks for the tip, i'll look into this direction too.
arrrghhh said:
We're not done with the port...
Click to expand...
Click to collapse
…and it will never be completely done - otherwise there would be no need for our lovely legacy-forums here
arrrghhh said:
I think this is a pretty minor bug considering the other major ones we have out there....
Click to expand...
Click to collapse
As you already said in another thread: Everyone has his own priorities
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
adlerweb said:
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
Click to expand...
Click to collapse
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
arrrghhh said:
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
Click to expand...
Click to collapse
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
Click to expand...
Click to collapse
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
arrrghhh said:
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
Click to expand...
Click to collapse
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
BigOnes69 said:
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
Click to expand...
Click to collapse
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
BigOnes69 said:
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
Click to expand...
Click to collapse
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
highlandsun said:
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
Click to expand...
Click to collapse
Interesting.
So what do we need to do to get the codec support? I'm assuming the kernel clocks are finally right as well...
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
yankees2450 said:
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
Click to expand...
Click to collapse
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
BigOnes69 said:
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
Click to expand...
Click to collapse
He never gave anyone anything useful from his builds.
He was just slapping stuff together, and would see what stuck to the wall.
I heard people had issues with his builds on HQ youtube, and I even tested his junk and wasn't able to get HQ to work... so I think it's just more BS from him.
yankees2450 said:
another junk from tiad8
could this be true?
http://www.neopeek.com/viewtopic.php?f=84&t=6544
Click to expand...
Click to collapse
There's a reason he's banned here. Let's not repost more of his crap here, thanks.
arrrghhh said:
I've heard it was a scaling issue - have you tried different resolutions?
Click to expand...
Click to collapse
Well... Most of my podcast have different resolutions and none worked so far. Also should scaling not be disabled when the Player is set to "original size"?
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube.
Click to expand...
Click to collapse
I dont know for youtube but most 3rd party video-players i've seen say that supported codecs are device dependent so i guess they are in the rootfs, not the app.
BigOnes69 said:
because HTC needs a way to get around patent laws
Click to expand...
Click to collapse
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
BigOnes69 said:
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
Click to expand...
Click to collapse
As said: 20% cpu left and works on Wimo -
I've managed to get "working" video with ffmpeg's default avi-output (think it was divx/mp3) but colors where disorted. My android died yesterday and i had no time to reinstall so i could not test further atm.
adlerweb said:
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
Click to expand...
Click to collapse
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
toadlife said:
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
Click to expand...
Click to collapse
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
arrrghhh said:
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
Click to expand...
Click to collapse
That would be fine with me.
toadlife said:
That would be fine with me.
Click to expand...
Click to collapse
Ok... My point is, source is preferred.
If we can't get source, so be it - but a proprietary blob does very little good in the scope of this type of project. I want everyone to have the best Android experience possible, I don't want just a few builds working correctly and others borked. That sucks.
I'm fairly new to Android (or any) development in general, I've currently made a camera app for more functionality for filmmakers. My question lies in accessing the raw frame stream from the level that the media recorder/omx native source uses to compress video? Reason being, this is the only sure way to grab the frames at a locked frame rate and without going through Java's bottlenecks in grabbing consecutive frames at a high frame rate. I'm searching through the OPPO FIND CM 10 device and kernel sources to find where the magic happens so to speak. Just locating the binder interfaces for IPC at the moment. Is V4L at work here?
Ehm ....which one you use, Mono Android?
Sent from my SonyX8 using Tapatalk 2
lkd85 said:
I'm fairly new to Android (or any) development in general, I've currently made a camera app for more functionality for filmmakers. My question lies in accessing the raw frame stream from the level that the media recorder/omx native source uses to compress video? Reason being, this is the only sure way to grab the frames at a locked frame rate and without going through Java's bottlenecks in grabbing consecutive frames at a high frame rate. I'm searching through the OPPO FIND CM 10 device and kernel sources to find where the magic happens so to speak. Just locating the binder interfaces for IPC at the moment. Is V4L at work here?
Click to expand...
Click to collapse
You mean an external camera? Like a USB camera? Or an internal camera? Internal cameras may be different, USB cameras might use different drivers. Anyway V4L is available on Android from the NDK, yes. But there are difficulties you'll have to work on.
Hello
I was wondering if its possible to lower the compression and noise of the photos with root and editing some files. Or somehow to enhance photo quality.
I had Nokia N8 which has still awesome quality of photos and now I have this lenovo and I'm thinking about improveing the photo quality as much as possible.
Thanks
I also bought one of these phones.
Poor camera quality, tried several programs.
Have you been able to improve the quality since then?
Android 4.4.4 Kitkat (original).
LENOVO A6000 VIDEO CAPTURE 720p TO 1080p
I have a lenovo a6000 with Lollipop 5.0.2 (S058) latest and TWRP 2.8.7 custom recovery.
I tried all custom roms but not change camera capture resolution to 1080p from 720p (default).
The MSM8916 Snapdragon 410 is support to 1080p video capture.
Ιt is to difficult to changed????? Why nobody? It is important i think.
Maybe somewhere settings in system or script? Or installed zip file?
I change media_profiles.xml to 1080 resolution and I can see in camera settings 1080p but it fail, say wrong parameters to video resolution.
I must change something else in system files?
THANKS to Developers....
Refresh the topic, same question about video and photo anyone?
If I'm not wrong then you need to edit boot.img aka kernel for this, but I'm not sure if it's possible or not, just a theory
Hi there, i'm using lenovo A536 and flash it with LineageOS 6.0.1. Just now i realize that youtube doesn't have the 720p or over resolution option, and youtube limit the resolution only up to 480p. Does anyone know how to unlock 720p res for my phone? i know i can overcome this by editing the build.prop, but i dont know which phone model and which line to edit in it.
Thanks in advance.
mislampes said:
Hi there, i'm using lenovo A536 and flash it with LineageOS 6.0.1. Just now i realize that youtube doesn't have the 720p or over resolution option, and youtube limit the resolution only up to 480p. Does anyone know how to unlock 720p res for my phone? i know i can overcome this by editing the build.prop, but i dont know which phone model and which line to edit in it.
Thanks in advance.
Click to expand...
Click to collapse
it's a hardware limitation bruh, its not software problem and you can't do anything about it.
minimum display resolution required to play 720p video are 1280 by 720 pixels, or 921,600,
and yours is 854x480 display resolution which is required exactly to play 480p videos, and can't go
beyond that. and it's not a youtube problem cause youtube will detect what's your display resolution are
and show the resolution capable for your display to show. Even thought you change or tinkered your phone and suddenly you got the 720p or whatever resolution you want, I don't think it's worth it. it's basically a hardware limitation.
Thunderoar said:
it's a hardware limitation bruh, its not software problem and you can't do anything about it.
minimum display resolution required to play 720p video are 1280 by 720 pixels, or 921,600,
and yours is 854x480 display resolution which is required exactly to play 480p videos, and can't go
beyond that. and it's not a youtube problem cause youtube will detect what's your display resolution are
and show the resolution capable for your display to show. Even thought you change or tinkered your phone and suddenly you got the 720p or whatever resolution you want, I don't think it's worth it. it's basically a hardware limitation.
Click to expand...
Click to collapse
thanks mate, another day another thing to learn huh
I've founded this phone at a great price. I'm thinking t to buy it but I have two questions about the camera:
1) do you confirm slowmotion to be at 960 fps?
2) is the timelapse editable? i like to make them and in my current lg v30 + i can adjust the timelpase to speeds of 15x, 30x, 60x based on how i want to make it. In this phone is it possible?
3) Exist a Google Camera porting for this device with Kirin 980?
4) can it capture the audio of videos in concerts or clubs without distortion?
Let me know and thanks in advance
j0ker69 said:
I've founded this phone at a great price. I'm thinking t to buy it but I have two questions about the camera:
1) do you confirm slowmotion to be at 960 fps?
2) is the timelapse editable? i like to make them and in my current lg v30 + i can adjust the timelpase to speeds of 15x, 30x, 60x based on how i want to make it. In this phone is it possible?
3) Exist a Google Camera porting for this device with Kirin 980?
4) can it capture the audio of videos in concerts or clubs without distortion?
Let me know and thanks in advance
Click to expand...
Click to collapse
1. Yes.
2. No. It is set to 15x and can't be changed.
3. Version 4.4.020.163412804 works best, and even then trying to go to slo-mo or settings causes the app to crash (it just closes, but if you open it again it works normally again. Unless you open one of those two again. Then it crashes again. ). But for photo spheres, a function I haven't found in any other app, it works great as long as you give it enough time to stitch it together.
4. Yes.