Recently i was searching for a possible way to use my hero as a usb mic or even a device to link my sharper image bt head set (with mic) to my pc. after reading a lot i realized neither have been aimed for or achieved that i could find.
after snooping i found this description of the protocol used to communicate with BT devices.
("The other main way to get audio out easily is via Bluetooth. The DROID does support the AD2P (Advanced Audio Distribution Protocol) profile, for talking to music quality headphones It is compressed, and by default uses an encoding called SCP, which is simpler than MP3 but kind of the same idea. The protocol handshakes with your headphones, and supports direct distribution of encoded audio without re-compressing if your headphones support it, in MPEG, AAC, and ATRAC formats.
Of course, like every Bluetooth phone, it also supports the HSP "headset" protocol, which is monophonic low-quality audio in one direction, voice in the other direction, each at 64kb/s using the very low complexity CVSD compression, or straight PCM audio (8-bit samples at 8kHz). ")
this made me think why not use AD2P or something simillar to comunicate via usb with a application on the pc end (receiver/sender) to handshake with the droid and transfer high quality audio data over usb.
basically using a form of ad2p to take direct audio from the internal sound driver or card and redirecting it to usb instead of blue-tooth. People said usb audio could not be done, seance this is a data transfer can this be done?
Related
Is it possible to stream music from the Kaiser to a hifi setup by wifi and if so what equipment and software for the phone would I need.
I have done this by bluetooth over the a2dp protocol but quite honestly there is a marked deterioration in quality, so looking for a better solution.
Hmm I have an Airport Express but that uses iTunes to stream the music over Wifi. So that is not gonna work.. unless Apple will make a version of iTunes for Windows Mobile. (in short: never)
Would be quitte nice if it should work though
alanwesty said:
Is it possible to stream music from the Kaiser to a hifi setup by wifi and if so what equipment and software for the phone would I need.
Click to expand...
Click to collapse
Follow my articles; I've presented a fully working solution to this a month ago - if your Hi-Fi is UPnP-capable. See my UPnP Bible in the Wiki.
I'm not sure if I understand exactly what you want to do or what capabilities your Hifi has. Is it connected to a network?
All you need is a ExtUSB-headphone adaptor and a patch lead to the Aux input on your hifi.
This will allow you to play content stored on the Kaiser via the Hifi. If your Hifi has a USB port, you could try WM5torage and/or Card Export and use the Kaiser as a Memory stick.
If you want the Kaiser to play media stored on a PC via the Hifi speakers, then I recomend Orb. If your Hifi is UPnP enabled, checkout the posts by Menneisyys and the links to Pocket Player.
Thanks for the replies, I have already used the Kaiser connected via the headphone out to my HiFi and it works great, just thought it would be even better if I could do this wirelessly but seems a bit of a faf, so proabably I'll just stick with the wired connection.
AFAIK, if you hook up your iDevice to a car-stereo via USB, the sound is transmitted digitally, and the stereo does the analog conversion (superior quality) (is that correct? or is there an analog signal on that wire?)
also AFAIK, there are 3 ways to play music from android to a car:
A2DP (****ty quality, see wikipedia entry)
AUX (****ty quality, no remote control via AVRCP (all steroes I tried only support that if you do A2DP as well)
USB (via mass-storage -> no turn-by-turn navigation, etc.)
so: sucks.
is it possible to emulate the iDevice dock-connection?
or is A2DP really that ****ty? and other choices for audiophiles?
thanks!
I use A2DP from my Tab to my Sony headunit and it sounds fine. There's obvious compression artifacts, but I think that's more a side-effect of using MP3 formatted files than loss from the BT streaming and/or SBC compression. BT 2.0+ offers up to 3Mb/s of throughput, with a dedicated 64Kb/s for voice layer, and the remaining for the data layer, which A2DP uses. Assuming you're using BT just to stream audio, the ~2.95Mb/s remaining should be able to easily handle even files encoded at 320Kb/s. The one other factor that would play into how "clean" it sounds is the bitpool setting that the Tab uses to stream the audio. If it's relatively low, it doesn't matter how much bandwidth you have available as it'll always sound tinny or out of tune. As far as my searching could tell me, bitpool settings aren't adjustable (by user) on the Android platform (unlike simple WinMo registry editing).
The default bitpool value (32) is the root cause of the A2DP BT suck. It's set in the Android kernel at compile time. Cyanogen's CM6 and CM7 ROMs ship with a bitpool rate of 53, and community consensus is that this is the definitive fix. (No disrespect meant to other custom ROM devs who may have fixed this as well.)
The headphone jack is "****ty quality"? Have you tried a Voodoo kernel?
The digital connection also relies on a stereo with a USB jack that supports the iPod interface. You'd have to put in a USB audio proxy that duplicates the iPod's command system to get it to work.
A2DP sounds pretty good to me anyway, when it works.
ok @voodoo kernel, haven't tried that.
but there's (to my knowledge) no car radio that forwards commands via connected a2dp while the audiosource is set to AUX
I'd have to do a lot of magic via some weird CAN-bus-bluetooth-dongle and a selfwritten program to get my steering wheel buttons to work. they do work if bluetooth is connected.
Hello all.
I'm having problems with Bluetooth on my One. The device that I'm trying to use with it is called a Siemens MiniTek. (It's actually a hearing-aid accessory. You clip to the front of your shirt - it looks a bit like an MP3 player - and it plus my hearing aids together then function like a Bluetooth headset. So, when making a call, the sound is sent wirelessly to the hearing aids, and the device itself has a microphone on it.)
Making a call with it works okay; but if I try to use it to get audio out of my One in other conditions (playing a game, say, or watching downloaded video) then the video and audio are always badly out of synch - the sound lags at least one second behind the picture.
I'm using the stock HTC ROM, the latest one available in the UK (2.24.401.8).
Anyone have any thoughts as to why this might be happening and what I can do about it?
Mby there is too much data to deliver via bluetooth (high quality audi/video sound) and the hearing aid device is not meant to recive such a load.
When calling to some1, the sound quality is only like 24kbps or something.
Just a thought
Rendoqoz said:
Mby there is too much data to deliver via bluetooth (high quality audi/video sound) and the hearing aid device is not meant to recive such a load.
When calling to some1, the sound quality is only like 24kbps or something.
Just a thought
Click to expand...
Click to collapse
That might result in there either being no sound at all or in the sound quality being very poor, but I don't see that it would result in reasonable-quality sound running 1 second behind the picture...?
The device itself is designed to handle fairly high quality sound: as well as receiving Bluetooth signals it can take analogue audio input via a 2.5mm stereo jack socket, and it also has a separate "base station" transmitter which you can plug into (say) the headphone socket of your TV: the transmitter then sends a signal wirelessly to the MiniTek (using a proprietary version of Bluetooth) and the MiniTek relays it to the hearing aids. Using either the direct-line input or the wireless transmitter works quite nicely, and there's no perceptible lag problem there.
I should have said, I've been onto Siemens tech support about it, and they're adamant that it shouldn't be doing this, and they don't know why it is. So I'm looking for a problem at the phone end.
Shasarak said:
I should have said, I've been onto Siemens tech support about it, and they're adamant that it shouldn't be doing this, and they don't know why it is. So I'm looking for a problem at the phone end.
Click to expand...
Click to collapse
i've experienced the same issues on various BT-Receivers and Smartphones. Seems to be a general issue. So far, this 1 second lag was present on all combinations of:
Phones: Samsung Galaxy S2 / iPhone 4 / HTC One
Receivers: Creative D100 / Creative D200 / Belkin BT Adapter
As i found out so far, this problem occours when the receiver can't handle the apt-x codec and audio has to be resampled to the older SBC codec. Found one thread kinda dealing with this topic, but haven't tried it out for myself at the moment. I'll do some testing later when i'm at home.
http://forum.xda-developers.com/showthread.php?t=1256407
Here is my set-up:
A Vivo LTV42FHDN 42” Full HD TV (2x HDMI inputs, 1x RCA stereo audio output, few other audio and video input connectors, and a set of really crappy built-in speakers)
A Logitech 2.1 Speaker system connected to TV's RCA audio output
An old DELL XPS M1330 notebook running Windows 7 hooked up to the TV via one HDMI port
A new Chromecast I’m trying to setup connected to the other HDMI port.
When I watch TV and switch to the HDMI input of the PC I get audio through both the TV’s crappy built in speakers as well as the much better sounding Logitech Speakers. However, when I switch to the Chromecast I only hear audio through TV’s built-in speakers. I have connected other PCs and tablets through HDMI before and from what I recall, sound always came out external speakers.
Is there any reason for the PC and Chromecast to behave differently when connected via HDMI ? I tried both HDMI ports, went through TV's audio settings (which only has very few settings like bass, treble, and some sound profiles), but couldn't get the chromecast to output audio through external speakers.
Does this mean Chromecast doesn’t support somesort of an HDMI specification/standard my old PC does, therefore the TV can't split and reroute the audio ? Is there any way to get around this without buying new hardware ? Other than audio, rest of it works great ! For me spending $50 or so extra on additional hardware really defeats the purpose of buying a Chromecast, because for that price I could've bought a DLNA enabled media player.
Any help appreciated. Thanks.
I'm not sure about your LG, but my Sony correctly re-routes audio from Chromecast to SPDIF (optical) output connected to AVR, so the Chromecast isn't a problem. I'm not sure about analog RCA output though.
Just go through your TV settings again. There must be an option burried somewhere in menus.
peca89 said:
I'm not sure about your LG, but my Sony correctly re-routes audio from Chromecast to SPDIF (optical) output connected to AVR, so the Chromecast isn't a problem. I'm not sure about analog RCA output though.
Just go through your TV settings again. There must be an option burried somewhere in menus.
Click to expand...
Click to collapse
Thanks for your reply, I did go through all the settings on the TV and even read the manual. But couldn't find anything there. Its not a very high-end TV, hence no optical output, all I have is that stereo analogue output.
Few minutes after posting I again connected my new notebook, and a Windows 8 tablet, audio works fine with all of them. But the Chromecast just doesn't work the same way. When I tested I connected all devices to the same HDMI port and didn't change anything on the TV, all I did was plug one in > test > unplug > plug the next one in > test etc.. that's all.. the fact that everything but the Chromecast work has to mean there is something different in Chromecast's HDMI signal.
PhoenixFx said:
Thanks for your reply, I did go through all the settings on the TV and even read the manual. But couldn't find anything there. Its not a very high-end TV, hence no optical output, all I have is that stereo analogue output.
Few minutes after posting I again connected my new notebook, and a Windows 8 tablet, audio works fine with all of them. But the Chromecast just doesn't work the same way. When I tested I connected all devices to the same HDMI port and didn't change anything on the TV, all I did was plug one in > test > unplug > plug the next one in > test etc.. that's all.. the fact that everything but the Chromecast work has to mean there is something different in Chromecast's HDMI signal.
Click to expand...
Click to collapse
Try switching the audio output in whatever application you're casting from to Stereo.
If Chromecast is sending multichannel audio, your TV might be smart enough to decode and play it on its speakers, but not smart enough to downmix to the analog output.
PhoenixFx said:
Here is my set-up:
A Vivo LTV42FHDN 42” Full HD TV (2x HDMI inputs, 1x RCA stereo audio output, few other audio and video input connectors, and a set of really crappy built-in speakers)
A Logitech 2.1 Speaker system connected to TV's RCA audio output
An old DELL XPS M1330 notebook running Windows 7 hooked up to the TV via one HDMI port
A new Chromecast I’m trying to setup connected to the other HDMI port.
When I watch TV and switch to the HDMI input of the PC I get audio through both the TV’s crappy built in speakers as well as the much better sounding Logitech Speakers. However, when I switch to the Chromecast I only hear audio through TV’s built-in speakers. I have connected other PCs and tablets through HDMI before and from what I recall, sound always came out external speakers.
Is there any reason for the PC and Chromecast to behave differently when connected via HDMI ? I tried both HDMI ports, went through TV's audio settings (which only has very few settings like bass, treble, and some sound profiles), but couldn't get the chromecast to output audio through external speakers.
Does this mean Chromecast doesn’t support somesort of an HDMI specification/standard my old PC does, therefore the TV can't split and reroute the audio ? Is there any way to get around this without buying new hardware ? Other than audio, rest of it works great ! For me spending $50 or so extra on additional hardware really defeats the purpose of buying a Chromecast, because for that price I could've bought a DLNA enabled media player.
Any help appreciated. Thanks.
Click to expand...
Click to collapse
Hi,Were you able to resolve this problem? Chromecast works great except for this exact same annoying problem. Also have the same TV. Thanks.
I'm working on a multi-room audio system with both AirPlay and Chromecast as input sources. It utilizes forked-daapd and Shairport (for AirPlay input) running on a Raspberry Pi. For Chromecast, I'm using an (AGPtek® HDMI to HDMI + SPDIF + RCA L / R) audio extractor and (AFUNTA USB 6 Channel 5.1 Optical) USB sound card. I've written a small C program to capture the audio input and feed it to a pipe that forked-daapd can then play to AirPlay speakers throughout the house.
So far, it works with analog audio, but I can't get the S/PDIF capture to work. I've hooked the Chromecast and audio extractor to my Yamaha receiver over S/PDIF, and it works. The receiver displays "PCM" and plays 2-channel stereo. I've also run S/PDIF out of my Windows 7 PC to the USB sound card, and I am able to capture that audio with no problem.
What could be different between the S/PDIF stream from the Chromecast/audio extractor and the S/PDIF stream from my PC?
I'm still struggling with this. Could there be copy-protection that is surviving the audio extractor and preventing capture?