Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 2 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 6 hrs ago - more...
 |
|
2010-08-04
, 02:08
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#102
|
Did you read back and try my tracker/indexer disabling? In my case, N900 delivered smooth recording on eMMC with tracker off.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
|
|
2010-08-04
, 09:21
|
|
Posts: 47 |
Thanked: 21 times |
Joined on Jan 2010
|
#103
|
Originally Posted by ndi
Could you please write a super small tutorial? the Tracker tool has A LOT of options, which ones to disable and what to leave on?
Did you read back and try my tracker/indexer disabling? In my case, N900 delivered smooth recording on eMMC with tracker off.
| The Following User Says Thank You to dof250 For This Useful Post: | ||
|
|
2010-08-04
, 09:30
|
|
Posts: 323 |
Thanked: 180 times |
Joined on Oct 2009
@ Gent, Belgium
|
#104
|
I second this 
|
|
2010-08-04
, 10:20
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#105
|
Disable indexing and watching, reboot.
Shoot video.
--
In theory, it's the watching that triggers index and thumbnailing whan shooting, but indexing could kick in, too. Also, due to memory fragmentation bug, high uptime (48h is "high") can hit performance. Make sure it's fresh.
Shoot video.
--
In theory, it's the watching that triggers index and thumbnailing whan shooting, but indexing could kick in, too. Also, due to memory fragmentation bug, high uptime (48h is "high") can hit performance. Make sure it's fresh.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
|
|
2010-10-12
, 01:31
|
|
Posts: 3,664 |
Thanked: 1,530 times |
Joined on Sep 2009
@ Hamilton, New Zealand
|
#106
|
Spark up the debate of 720p 
__________________
Install Preenv games into eMMC| Click Here to get rid of Uboot screen
My N900 running at 250-1150Mhz
Unlocking your FM-transmitter to 76.0Mhz - 107.9Mhz range - CLICK HERE.
Install Preenv games into eMMC| Click Here to get rid of Uboot screen
My N900 running at 250-1150Mhz
Unlocking your FM-transmitter to 76.0Mhz - 107.9Mhz range - CLICK HERE.
|
|
2010-12-01
, 09:05
|
|
Posts: 508 |
Thanked: 130 times |
Joined on Sep 2009
|
#107
|
Originally Posted by ndi
SSD connected to PCI-e allready has speeds of up to 650 MB a second. so you should leave that storage device out of the picture here.
That would be correct for a raw sensor dump - it never leaves the camera, as it actively works differently in video and camera mode. It delivers a partially compressed stream in whatever mode that is, otherwise there would be no HD cameras, at 250M/s the data is too much for any portable storage system (even a SSD).
|
|
2010-12-04
, 08:05
|
|
Posts: 214 |
Thanked: 256 times |
Joined on May 2010
|
#108
|
Originally Posted by ndi
I was reading about the fragmentation problem, but where do you read it was 48hrs exactly? I know the N900 becomes slow with high uptime but didn't know there was a number
In theory, it's the watching that triggers index and thumbnailing whan shooting, but indexing could kick in, too. Also, due to memory fragmentation bug, high uptime (48h is "high") can hit performance. Make sure it's fresh.
|
|
2010-12-04
, 09:36
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#109
|
Originally Posted by JorgeFX
There is a lengthy discussion in bugs.maem.org, a bug about audio chopping and high cpu usage after unlocking. I'm on the road now, so it's tedious and expensive, but if you can't find it I'll link later tonight (my timezone).
I was reading about the fragmentation problem, but where do you read it was 48hrs exactly? I know the N900 becomes slow with high uptime but didn't know there was a number
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
|
|
2010-12-10
, 07:07
|
|
Posts: 124 |
Thanked: 52 times |
Joined on May 2010
@ Sweden
|
#110
|
Originally Posted by shadowjk
actually, this might be sufficiently proper documentation:
I've understood that the IVA2 component of the omap3 CPU is entirely undocumented, and that there are some third parties which have been supplied documentation on it, and have created an enhanced decoder capable of 720p decode, and is selling it at enormously high cost.
http://focus.ti.com/dsp/docs/dspsupp...ocCategoryId=6
for example:
http://www.ti.com/litv/pdf/spru732j (C64x+ DSP CPU and Instruction Set Reference Guide)
or it may as well not be sufficient.
im not sure what IVA2 represents... if its software or hardware based?
maybe its TI's name for a software suite for the C64+ DSP?
maybe its standalone silicon in the SoC?
personally i think IVA2 mostly reffers to TI's software that comes bundled with the C64+ DSP - everything ranging from compilers/SDK's to pre-built codecs (coded with those SDK's).
but like u said - it seems quite undocumented, unless the link above provides some info reffering to the IVA2.
im still investigating if its worth undertaking the task to create a clean "Camera OS" for the N900, and code some lightweight capture codecs...
Im not even sure that i can learn all relevant documents, since its so much.
...about undertaking the task to coding a new codec:
* the DSP have very limited cache resources and it cant process a complete 1280x720 picture in one sweep (of course).
* if regular RAM is used instead - it will hog the BUS.
therefore, i think the best approach is to compress each frame - segment by segment (which will cause blockiness), and save them one by one to RAM... writing to the eMMC will have to wait until the video is finished.
Using this approach, will put a time-limit on how long the recorded videos can become, but it will atleast provide plenty of resources/speed for capturing in HQ and high fps.
...still i know too little to make qualified judgements - so all of the above should be taken with a grain of salt... we'll see if i manage to learn enough to undertake this task.
Last edited by S0urcerr0r; 2010-12-10 at 07:09.
| The Following 2 Users Say Thank You to S0urcerr0r For This Useful Post: | ||
but i guess in this case its easier to start completely over than fix whats broken, hence meego... i hope meego will feature a fluid UI and smooth video-recording.