Re: Why sound isn't working on the TP2.
 

ditto, i run a TP2 and my wife a hero

Re: Why sound isn't working on the TP2.
 

Hi All. I've been hacking away here. Still no interrupts. But I am fairly close to being able to use wince DEX,SPM,RPC,SHM,KLT. which hopefully will get things moving along in the right way.

If there are any linux experts out there. I am having trouble mmap'ing contiguos regions. Like mmap(0xfu,0x1000,somephys), then mmap(0xfu+0x1000,0x1000,someotherphys)

Seems like it needs at least 3 pages for it to work. I *need* it to be contiguous though. Anything including hacking the kernel would be fine. I'm just not sure what the trouble is.

Re: Why sound isn't working on the TP2.
 

Have you been able to replicate the half second of sound that was reported early this week?

Re: Why sound isn't working on the TP2.
 

I haven't got that half second of sound. I've talked to the guy, but he is pretty closed lipped about exactly how they got it to work.

Re: Why sound isn't working on the TP2.
 

been silently watching this post mainly because im an electrical engineer who was never into programing or software dev in general but the fact that the rhodium port has been in the works since february and that people are holding back is just crazy and frustrating, specially when the HD2 went up and running in no time.

Re: Why sound isn't working on the TP2.
 

Agreed. There's a reason most professional development teams have more than 1 single person. Everyone has different skills and ideas that should all be used together to solve complex issues like this. Your work will be greatly appreciated by many, whether you do it by yourself or with the aide of other like and different minded people other than yourself.

Regardless, thank you everyone involved and keep up the good work!

Re: Why sound isn't working on the TP2.
 

That is the first I have heard about any sound. Thats sounds like a buffer issue.

Re: Why sound isn't working on the TP2.
 

Lol.. Cotulla himself said the tp2 is very difficult.

Frustrating yes.. but imagine how we feel. I been banging my head on irq issues for months now. Out of desperation i decided to make a nand version which we got booting and we are in the same boat.

Re: Why sound isn't working on the TP2.
 

ACL i know how you feel and YES the TP2 is a nightmare, if only i ever run into the engineer behind it, that would be interesting lol

sometimes when your working on something else is when you figure out what you were working on initially.
how is it on nand ? compared to a 16gb class 2?
im sure you guys might have heard this before but i was recently tinkering with a friend's HTC Dream/G1 and i gota admit, huge hardware similarities.
oh well i shall wait but wish i could help and sorry if i took this thread off course

Re: Why sound isn't working on the TP2.
 

I found this post on a different thread and figured I would share it in case it helped. It is obviously about the Rhodium sound problem.

"Something just occured to me... I'm a sound engineer... so i know all about feedback, sends/returns etc in a live environment, which is basically the same wherever you have a live microphone near a speaker....

In my industry there are 2 devices you can insert into the "sound chain"...

1. If an artist screams into a microphone, you insert a compressor, which essentially brings the input gain down, preventing the microphone from distorting....
This is practically achieved by "routing" the microphone VIA a compressor 1st, the compressor does it's processing, which you set manually, consisting of:
- Threshold (Input Gain)
- Ratio (How much of the threshold to process)
- Output Gain (How loud the output is)

2. If your microphone environment is too noisy, in otherwords if you are scared of feedback occuring, you can insert a GATE into the sound chain. This basically keeps the microphone "off" (or gated) waiting for input signal to be loud enough, which then switches the microphone on. Practically a simple example would be on a drumkit, where the drum A must not pick up drum B when the drummer hits drum B... the microphone on drum A is "Gated" and only opens when it is hit and the signal is loud enough (or close enough to the microphone)

You also set gates manually, consisting mainly of:
- Threshold (Input Gain)
- Ratio (How much of the threshold to process)
- Attack time (How quickly to process)
- Decay time (How quickly to release)
- Output Gain (How loud the output is)


In our industry, it is a common mistake where new engineers under stress forgets to take the "insert button" out of the chain... so they struggle to get any sound going to the speakers until they take out the insert button.

So with example a (compressors) and example b (gates), either of those 2 components may cause the speaker to stop working, if the device is inserted.

If you say that everything is being routed to the 3.5mm jack, what are the chances the designers have some sort of gating/compressor system in the sound chain, to prevent feedback/echo from happening... and the default settings are simply set to "off" or "maximum"... and its inserted by default.

...like i said - these devices are found everywhere... just in my industry it's something inserted physically as a separate device. So maybe everything works... it's just something in the chain which doesn't....

...hope it makes sense to someone"


Now, this makes me think that the problem has to do with the dual microphones the rhodium uses for noise cancellation. I hope this isn't old news and maybe it is helpful to someone...