Related
When I pause the movie and play again.
The movie is getting very lag.
But if I enter preference setting to set the audio page and back to player.
The movie is good again.
WHY.......
I need help...
Not alot of info to go on there dude, which WM version are you running this on?
One thing you could do is download a tweak app such as HTCustom by shadowmite.....and increase the memory cache levels....this has been known to help with video playback on certain devices.........also go into the advanced settings in coreplayer and enable microdrive mode....run the video from the microdrive and see if it helps.
Try the microdrive tweak first.
The OS is WM6
If I check the Microdrive mode.
Should I change the "Microdrive start at"?
Now is 1472 KB.
I have the same problem with core player...but all modification with cache or microdrive settings doesn't help. I think it is a bug in the audiostream, because when i change the audio settings the movie runs well...but when i hit pause and then start again the movie is laggy
Icterus said:
I have the same problem with core player...but all modification with cache or microdrive settings doesn't help. I think it is a bug in the audiostream, because when i change the audio settings the movie runs well...but when i hit pause and then start again the movie is laggy
Click to expand...
Click to collapse
I'm having the same problem playing back basic MP3 files, audio only. Very weird.
**Edit, my problem seems to only be on 48 kbit/s MP3 files, higher bitrate play without issues. Anyone seen this?
Same problems here - the following settings solved my problems:
menu-tools-preferences-select page-buffering-buffer size = 24000KB
menu-tools-preferences-select page-video-video output=raw frameBuffer
In mine I find out that if you go to full screen clicking in the screen then goes to lag thing but if you click the tiny icon in the right-top of the screen then goes to full screen without a problem.
This is happening to me but only with video and only in some videos not all of them.
My fight with Coreplayer is more on video being frozen when the screen contents changes very quickly. For sample on the intro of SouthPark when the hands quickly makes the characters with papper pieces. That scene is very quick and I got the image frozen sometines. I'm playing around with the buffering options but the problem remains.
Best Regards,
mahjong
P.S.: nrm your setting doesn't solve the problems to me. I tried with Direct Draw, ATI, Raw and many other without success. And I got my buffer to 40000 and 100%.
I'm sorry my suggested settings did not fix your problems. There is a vast world of potential settings - both in Coreplayer and registery.
I am running Coreplayer from the Microdrive but the movie is on my storrage card.
Is the SouthPark video short enough to post somewhere for me to try?
I'm using it the same way... program stored at microdrive and movie stored at miniSD.
Unfortunelly is a complete SouthPark chapter so is big (the one banned because "attack" scienciology). Anyway I'll keep on playing with the settings.
Thank you,
mahjong
mahjong said:
My fight with Coreplayer is more on video being frozen when the screen contents changes very quickly. For sample on the intro of SouthPark when the hands quickly makes the characters with papper pieces. That scene is very quick and I got the image frozen sometines. I'm playing around with the buffering options but the problem remains.
Click to expand...
Click to collapse
I'm having the same problem with sections of The Daily Show, usually when returning from a commercial break and the logo flashes across the screen it just stops dead. Very very frustrating, please share if you find a way to resolve this problem.
I will. But looks a matter of playing with settings on memory, buffers, and video configuration.
Something I test is the difference on having the movie in the Microdrive or miniSD. Looks the same to me... and it's not strange since I'm using a buffer size of 40000 KB with a preload at underrun of 100% what as far as I know means that Coreplayer need to load 40000 KB (100%) of the movie into the memory before starting it.
That means (from my point of view) that the problem relays in the procedure of taking images from the memory and not from the SD or microdrive.
I'll keep on testing. And I need to compare those problems with TCPMP.
My problem with TCPMP is that damage the notification queue every single time I install or run the program.
Best regards,
mahjong
nrm said:
Same problems here - the following settings solved my problems:
menu-tools-preferences-select page-buffering-buffer size = 24000KB
menu-tools-preferences-select page-video-video output=raw frameBuffer
Click to expand...
Click to collapse
Perfect for me mate! working 100% thanks
What is the latest version of Core Player?
Is version 1.1.1 the latest version of Core Player?
1.2.5 is the latest.
I've been using version 1.2.5 build 4506
nrm said:
Same problems here - the following settings solved my problems:
menu-tools-preferences-select page-buffering-buffer size = 24000KB
menu-tools-preferences-select page-video-video output=raw frameBuffer
Click to expand...
Click to collapse
I've the same problems and the solution above does fix them.
THANK YOU!!!
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.
Title says it all. I see it all the time in rom threads.
galax5 said:
Title says it all. I see it all the time in rom threads.
Click to expand...
Click to collapse
Hardware acceleration is the fact that the GPU is being used in certain tasks instead of the CPU so it loads off the CPU a lot. You can see it in an example of your computer playing a 1080p video from vlc for example. (don't know if you have nvidia but this is a rough example). Certain apps for android require H/W for example chrome (well it's maybe something related to the drivers though).
I'll attempt to sum up what zaclimon said in layman's terms. In your computer, and nowadays smartphones, you have two critical components to run software: The CPU (your processor) and your GPU (your video card). Normally, your CPU would be responsible for processing general tasks and processes. However, in order to make the computer more efficient, the CPU will offload certain tasks and processes which the video card (GPU) can do better.
For example, in Android 4.x and up Netflix requires hardware acceleration to perform at peak functionality. That's not to say that the CPU doesn't do any of the work, but the CPU is going to offload some processes to the GPU from the Netflix software that the GPU can do better; such as video streaming.
HW also means much smother UI
Sent from my Nexus 7 using xda app-developers app
DZonikg said:
HW also means much smother UI
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Correct, as UI rendering would be offloaded primarily to the video card.
After months of researching why video playback fails on my device, it is because it is using cpu rendering not GPU. That also prevents me from playing +240 videos on YouTube. In VLC beta, I can change the playback device to OpenGL 3.0 and video works awesomely. How can I do this system wide?
You can try SW decoder to play some video
Sent from my GT-I8190 using XDA-Developers mobile app
Anonymous94 said:
You can try SW decoder to play some video
Sent from my GT-I8190 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is not a real solution, we want to have hardware accelerated playback like on any normal system.
There is another problem too, I've seen few people mentioning it. It probably affects only integrated intel gpus, hardware accelerated vids look like ****, they have extremely low color depth.
This problem doesn't occur under recent Androidx86, so I hope that they'll switch to new kernel as soon as possible.
Anonymous94 said:
You can try SW decoder to play some video
Sent from my GT-I8190 using XDA-Developers mobile app
Click to expand...
Click to collapse
Works like real shiiit on my pc. We have GPUs and we want to use them. Maybe the kernel update in the next version will fix it? Let's hope so.
Hi all,
samsung xe700t1c - ao4uk convertible laptop tablet
core i5 quad core 1.7 ghz - 2.6 ghz turbo
4gb ddr3
intel HD 4000 ( 2GB video memory )
running version 3.0101 (Marshmallow) from a 544MB/s 64GB Msata drive in a USB 3.0 Enclosure
everything working very fast system (INCLUDING SLEEP AND WAKE UP but havent tested every sensor etc). Sim card function not working so jide please enable sim card function for calling and internet data. Thank you.
so far with an Antutu score of 124,000 i have tested 1080p 60fps HD video playback which plays smooth and crisp and 3d games like Dead Trigger 2 work perfectly.
by default the remix os is in powersave mode but all cpu cores stay on and high which causes battery drain and cpu heat but with a software called 3 cpu manager the problem can be solved easily by setting the max cpu frequency to 800 Mhz on all cores and you also have the ability to change from powersave to performance mode which is what i used to acheive smooth 1080p 60fps video quality! (without overclocking the system 1080p 60fps footage is not possible and laggy!
please enable HDMI audio and widget capability and please make remix os unrooted and create a method to easily root for users who want root that way you have both audience users!
I think you should post your message to this feedback page so that it reaches the developers
https://docs.google.com/forms/d/e/1FAIpQLSeqaTBTPzHgjwUKtn08zUDusKTYXQtG8mLczmo7D6bDgd_17A/viewform
Seeing similar problems the Pixel 3 had with only 4gb. XP1 camera is closing out any background music after taking the pic, which is dumb.
I don't use my phone all day like most & when I do it's for YouTube , Spotify, Gmail, simple stuff. Why am I averaging usages of 4.3 / 6.0 gb of RAM ? Seems very poor, especially for how I use the phone AND for the fact that it's simply vanilla Android with very little extra added features
What's your opinions?
davey_wavey said:
Seeing similar problems the Pixel 3 had with only 4gb. XP1 camera is closing out any background music after taking the pic, which is dumb.
I don't use my phone all day like most & when I do it's for YouTube , Spotify, Gmail, simple stuff. Why am I averaging usages of 4.3 / 6.0 gb of RAM ? Seems very poor, especially for how I use the phone AND for the fact that it's simply vanilla Android with very little extra added features
What's your opinions?
Click to expand...
Click to collapse
4.3 is fine, I'm getting 4gb with Similar usage. System and Google will take up 3gb+.
Music stopping when taking a pic is strange, any apps taking up more ram than they should?
davey_wavey said:
Seeing similar problems the Pixel 3 had with only 4gb. XP1 camera is closing out any background music after taking the pic, which is dumb.
I don't use my phone all day like most & when I do it's for YouTube , Spotify, Gmail, simple stuff. Why am I averaging usages of 4.3 / 6.0 gb of RAM ? Seems very poor, especially for how I use the phone AND for the fact that it's simply vanilla Android with very little extra added features
What's your opinions?
Click to expand...
Click to collapse
The music stopping is not a RAM problem, but something else. I've had this happen as well on the XZ3. It's annoying, but a bit better on the Xperia 1, since it just pauses the music instead of closing the app.
As for your usage, depends on what apps you have installed. I played a game of pubg, switched over to facebook, messenger, chrome; and about an hour later reopened pubg. It was still minimized.
Mackay53 said:
4.3 is fine, I'm getting 4gb with Similar usage. System and Google will take up 3gb+.
Music stopping when taking a pic is strange, any apps taking up more ram than they should?
Click to expand...
Click to collapse
I figured something out. Not very practical, but def did a lot to open up RAM. Under Home settings I disabled the Google search bar located in the dock. By doing that , it freed up 275mb out of 315 that Google was taking up. RAM usage is now hovering around 2.4 gb over 3 hours. Interesting
Go to settings -> system -> advanced -> programmer's options -> in Applications section check limit of the processes in background. Make sure it is standard and not limited to 1-4.
friends you can turn off the camera sound in camera settings，then the videos and music will not paused