nanoevil
Head-Fier
- Joined
- May 31, 2013
- Posts
- 86
- Likes
- 26
Ill try to verify it with the e17 I tested...I just borrowed that from my friend...was playing flac and wav tracks when I tested it
Android phones and USB DACs
- Thread starter NZtechfreak
- Start date
nicks9
New Head-Fier
- Joined
- May 31, 2013
- Posts
- 23
- Likes
- 10
Quote:
Thanks, that was really helpful.
I guess for now that particular app is the only way to do it. Too bad it has such minimal functionality as a player.
It's probably not a good idea to let it downsample the audio on the fly, right?
I can actually play hi-res on Poweramp with no problems, but the E17 shows it as 16/48.
In order to interface to the 32/384 capable ALSA USB audio driver, generic music players have to use the Android media player framework which currently has some hi-res limitation instructions.
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/975#post_8940230
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1005#post_8950416
The USB Audio Recorder PRO can play hi-res music files, because it doesn’t use the Android media player framework. It includes its own USB audio "soft driver".
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1440#post_9084579
Thanks, that was really helpful.
I guess for now that particular app is the only way to do it. Too bad it has such minimal functionality as a player.
It's probably not a good idea to let it downsample the audio on the fly, right?
I can actually play hi-res on Poweramp with no problems, but the E17 shows it as 16/48.
James1776
Head-Fier
- Joined
- Mar 1, 2010
- Posts
- 87
- Likes
- 13
NZtechfreak
Headphoneus Supremus
- Joined
- Jan 19, 2012
- Posts
- 3,328
- Likes
- 729
James1776
Head-Fier
- Joined
- Mar 1, 2010
- Posts
- 87
- Likes
- 13
Is there any doubt? perhaps on $3 earbuds but with any sort of a real system, Hi-Rez simply sounds better...
nicks9
New Head-Fier
- Joined
- May 31, 2013
- Posts
- 23
- Likes
- 10
Maybe I just have hi-res music that I would rather not convert to a lesser quality for no reason.
It's funny that I have to defend myself on a site full of people who spend thousands of dollars on hi-fi equipment.
It's funny that I have to defend myself on a site full of people who spend thousands of dollars on hi-fi equipment.
Benny-x
1000+ Head-Fier
Hey guys, a couple pages back NZtechfreak talked about the Apex Glacier, RSA Intruder, and the HeadAmp Pico.
From my findings, all based on 32ohm headphone load (V-Moad M100) the Apex Glacier has 90mW output, RSA Intruder has 300-350mW output, and the HeadAmp Pico has 90mW or 700mW?! Can anyone clarify this?
From the HeadAmp website it says output of 0.7mW @ 32ohms, but that's pretty crazy. Can anyone tell me a solid answer?
From my findings, all based on 32ohm headphone load (V-Moad M100) the Apex Glacier has 90mW output, RSA Intruder has 300-350mW output, and the HeadAmp Pico has 90mW or 700mW?! Can anyone clarify this?
From the HeadAmp website it says output of 0.7mW @ 32ohms, but that's pretty crazy. Can anyone tell me a solid answer?
DanBa
Headphoneus Supremus
- Joined
- Nov 12, 2009
- Posts
- 1,721
- Likes
- 263
"A plain "Shut up!" from Google on top starred Android issues" [a rather severe judgment]
http://showlabor.blogspot.fr/2013/05/a-plain-shut-up-from-google-on-top.html
"Issue trackers are a great facility for getting feedback from the customer base. And they are a great facility for the customers to actually give feedback. But what if there are lots of customers who give feedback and nobody cares? Well, even in those cases issue trackers are great: You, as a customer, can clearly see how responsive the team behind the product is.
Let's take a look at two of Android's most starred issues:
Issue 24614: Add support for USB Audio
Issue 3434: Add APIs for low-latency audio
They are starred by 4904 and 2442 people and rank at place 4 and 7 on the list of Android's most starred issues:
Not only do both issues have been starred by many people but there have also been lots of comments made in the issue tracker. But neither of both got even a single comment or response from the Android developers - until today!
An answer - finally
So great news: Google has responded! Yeah, finally, after 1332 comments on issue 24614 and 485 comments on 4855. And here's the long awaited answer from Google: Shut up!
Yes, that's it. No further comment. They haven't responded on issue 4855 for almost 4 years now and all they say is: Shut up! Is this really how they care for feedback?
OK, to be fair, they haven't literally said "Shut up!" they have just closed both issues for comments. But that isn't very different from "Shut up!".
To make it clear, most of the comments at least in #24614 are useless 'me too' comments. Nobody want to see them, that's what starring is for. But actually Google could have stopped this kind of comments by just answering even once. Just once! That would have been enough. Closing the "discussion" wihtout any further remarks is what makes it feel like a 'Shut up!' "
https://code.google.com/p/android/issues/detail?id=24614&sort=-stars&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
"Well, the USB Audio issue feels like it could've belonged at LG, or Asus or whoever the maker of each specific device happens to be.
It's the OEMs and platform vendors that actually implement the USB Audio support (I happened to be involved in this when I was at Sony Mobile).
Google (as of Android 4.1) essentially just provides some of the higher-level mechanisms for detection of USB Audio accessories, while the OEM / platform vendor fills in the blanks. Those blanks can either be very small if you only want audio output at a fixed sample rate, or they can grow quite big if you want more features like recording, voice calls, etc.
You could argue that Google should provide a complete basic solution for USB Audio, but that's not the setup today."
http://music.columbia.edu/pipermail/andraudio/2013-May/000833.html
http://showlabor.blogspot.fr/2013/05/a-plain-shut-up-from-google-on-top.html
"Issue trackers are a great facility for getting feedback from the customer base. And they are a great facility for the customers to actually give feedback. But what if there are lots of customers who give feedback and nobody cares? Well, even in those cases issue trackers are great: You, as a customer, can clearly see how responsive the team behind the product is.
Let's take a look at two of Android's most starred issues:
Issue 24614: Add support for USB Audio
Issue 3434: Add APIs for low-latency audio
They are starred by 4904 and 2442 people and rank at place 4 and 7 on the list of Android's most starred issues:
Not only do both issues have been starred by many people but there have also been lots of comments made in the issue tracker. But neither of both got even a single comment or response from the Android developers - until today!
An answer - finally
So great news: Google has responded! Yeah, finally, after 1332 comments on issue 24614 and 485 comments on 4855. And here's the long awaited answer from Google: Shut up!
Yes, that's it. No further comment. They haven't responded on issue 4855 for almost 4 years now and all they say is: Shut up! Is this really how they care for feedback?
OK, to be fair, they haven't literally said "Shut up!" they have just closed both issues for comments. But that isn't very different from "Shut up!".
To make it clear, most of the comments at least in #24614 are useless 'me too' comments. Nobody want to see them, that's what starring is for. But actually Google could have stopped this kind of comments by just answering even once. Just once! That would have been enough. Closing the "discussion" wihtout any further remarks is what makes it feel like a 'Shut up!' "
https://code.google.com/p/android/issues/detail?id=24614&sort=-stars&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
"Well, the USB Audio issue feels like it could've belonged at LG, or Asus or whoever the maker of each specific device happens to be.
It's the OEMs and platform vendors that actually implement the USB Audio support (I happened to be involved in this when I was at Sony Mobile).
Google (as of Android 4.1) essentially just provides some of the higher-level mechanisms for detection of USB Audio accessories, while the OEM / platform vendor fills in the blanks. Those blanks can either be very small if you only want audio output at a fixed sample rate, or they can grow quite big if you want more features like recording, voice calls, etc.
You could argue that Google should provide a complete basic solution for USB Audio, but that's not the setup today."
http://music.columbia.edu/pipermail/andraudio/2013-May/000833.html
Theogenes
Headphoneus Supremus
- Joined
- Mar 28, 2010
- Posts
- 2,036
- Likes
- 182
Wow, that's... upsetting. In that case, I'm even happier to throw a few bucks at whomever can figure out how to make USB audio a service that can be accessed by multiple players. $10? No problem. $20? Yeah, I'd probably do it. I just want SOMEBODY to make this work consistently...
Hey, be more positive,
maybe the Google team are just now dealing with the problem and preparing to give us a surprise
![size]](http://files.head-fi.org/images/smilies/etysmile.gif[size=13px][/size])
Okay, they probably won't, I know
![size]](http://files.head-fi.org/images/smilies/confused_face.gif[size=13px][/size])
maybe the Google team are just now dealing with the problem and preparing to give us a surprise
Okay, they probably won't, I know
Davy Wentzler
Member of Trade: eXtream Software Development / Audio Evolution
- Joined
- Dec 18, 2012
- Posts
- 1,057
- Likes
- 583
Davy Wentzler
Member of Trade: eXtream Software Development / Audio Evolution
- Joined
- Dec 18, 2012
- Posts
- 1,057
- Likes
- 583
Quote:
To take away the misconception of a lot of people: Google did not provide higher-level mechanisms for detection of USB audio devices as we know them. They only provided something for USB devices that work in 'accesorry mode': "USB accessory mode allows users to connect USB host hardware". That's right: 'host' hardware, so the audio device would be the host and your Android device would be the slave. There are hardly any devices around that work like this: all USB audio devices are slaves where the Android devices must function as the host, hence the needed OTG cable.
To take away the misconception of a lot of people: Google did not provide higher-level mechanisms for detection of USB audio devices as we know them. They only provided something for USB devices that work in 'accesorry mode': "USB accessory mode allows users to connect USB host hardware". That's right: 'host' hardware, so the audio device would be the host and your Android device would be the slave. There are hardly any devices around that work like this: all USB audio devices are slaves where the Android devices must function as the host, hence the needed OTG cable.
Theogenes
Headphoneus Supremus
- Joined
- Mar 28, 2010
- Posts
- 2,036
- Likes
- 182
Quote:
Man, as soon as you have that sucker finished, I am absolutely THERE. Really glad to hear this and can't wait to see what you come up with!!
Waiting with baited (or maybe just "bad") breath
Man, as soon as you have that sucker finished, I am absolutely THERE. Really glad to hear this and can't wait to see what you come up with!!
Waiting with baited (or maybe just "bad") breath
bangdomarkin
Head-Fier
- Joined
- Nov 28, 2012
- Posts
- 63
- Likes
- 10
So, for work with a Motorola Droid Razr Maxx HD, and FiiO E07K i need to make
Maxx HD>>USB Audio Recorder PRO>>E07K>>Headphone?
Works for someone?
Maxx HD>>USB Audio Recorder PRO>>E07K>>Headphone?
Works for someone?
crabbdaddy
New Head-Fier
- Joined
- Jun 5, 2013
- Posts
- 1
- Likes
- 0
i have successfully tested Nexus7 32G Android version 4.2.2 and USB audio recorder PRO with FLAC file out 44100, 24bit with MiniDSP USBStreamer optical out to Alpine PXA-H701
Users who are viewing this thread
