sere83
01-28-2007, 01:23 PM
I have been messing around with My NX70V a lot lately and think i may be having tcmp playback problems. I installed my new battery which was fine. before I installed the battery I had opened the clie on 2 previous occasions and one ocassion the screen started flickering black and white and it went into a 'hard reset loop' and wouldn't start. I took the battery out again and eventually it started properly. Later on I had an issue with clie files and a normal 128 card not reading properly. Tried to read a file in Filez also and it crashed and I had to soft reset. Also The encoding program vemode also seems to produce corrupt files with bad indexes on my computer.
To cut a long story short I installed my new battery, reset the clie and now it is all fine. But........my tcmp (overclocked with pxa clocker to 266) is not playing back as smooth as it used too. I'm dropping approximatley 10 frames every 2000 is this normal? the files I encoded are Divx at 480x270 or 480X336 at between 430 and 480kbps and audio at 22050k 64kbps. Is this normal surely i should not be dropping any frames? Pxa clocker also benchmarks a lot higher some times at over 30fps but sometimes it goes bellow 20 and i have to press the on-off button on pxa and it goes back up to around 30fps. I am using pxa clocker 4.5 unregistered version. Is this an encoding problem or just they way tcmp plays back?
To cut a long story short I installed my new battery, reset the clie and now it is all fine. But........my tcmp (overclocked with pxa clocker to 266) is not playing back as smooth as it used too. I'm dropping approximatley 10 frames every 2000 is this normal? the files I encoded are Divx at 480x270 or 480X336 at between 430 and 480kbps and audio at 22050k 64kbps. Is this normal surely i should not be dropping any frames? Pxa clocker also benchmarks a lot higher some times at over 30fps but sometimes it goes bellow 20 and i have to press the on-off button on pxa and it goes back up to around 30fps. I am using pxa clocker 4.5 unregistered version. Is this an encoding problem or just they way tcmp plays back?