USB Audio Player PRO (UAPP): 24- and 32-bit playback, ubiquitous USB audio support for Android
Feb 3, 2015 at 4:41 PM Post #271 of 6,187
don't forget to get a Y cable and power the geek out separately if your source device can't supply all the current the geek out needs.


Thanks, I've got that in place.
 
Feb 3, 2015 at 10:24 PM Post #272 of 6,187
Regarding *.CUE support, I found something for Android here
 
https://github.com/tguillem/android-mpd/tree/master/src/cue
cue_playlist_plugin.c
cue_playlist_plugin.h
embcue_playlist_plugin.c
embcue_playlist_plugin.h
https://github.com/tguillem/android-mpd/tree/master/src/playlist
 
Also did a quick search and got something else
 
https://github.com/cmus/cmus
https://github.com/mpdflaccuesupport
https://github.com/vchimishuk/cue-go
https://github.com/justlaputa/cue-parser
https://github.com/relikd/CUE-Sheet_sublime
https://github.com/xiph/flac/blob/master/test/cuesheet.ok
https://github.com/smgoller/flactag/blob/master/Cuesheet.cc
https://github.com/mewkiz/flac/blob/master/meta/cuesheet.go
 
Maybe MPD could be a good place to start?
 
http://git.musicpd.org/cgit/master/mpd.git
 

 
Usually we'll find these combos when we prefer to keep metadata inside the CUE sheet itself instead of modifying the file with the audio, it's often a single file instead split tracks:
 
*.CUE + *.APE
*.CUE + *.FLAC (or *.ALAC)
*.CUE + *.TTA
*.CUE + *.WAV (or *.AIFF)
*.CUE + *.WV
 
For mirroring the entire redbook CD image, it's closer to ISO format like this:
 
*.CUE + *.BIN
 

 
As always it would be fantastic if Unicode support for CUE sheets could be implemented properly
 
https://github.com/kuyur/unicue
http://code.google.com/p/unicue/
 
Feb 4, 2015 at 11:58 AM Post #273 of 6,187
   
Yes, it's being worked on. But unfortunately, if people talk about the UI, it's never clear if they mean just the looks or something else. So, if you can elaborate on what you want changed, this is your chance.

 
Could you release some code which allowed the community to make their own skins Davy? 
 
Feb 4, 2015 at 12:04 PM Post #274 of 6,187
   
I am looking into it, but all information I find on the subject suggests that cue is just a small text file pointing to audio files somewhere else on disk. So I tried ImgBurn on Windows and indeed, it just creates a tiny text file with references to existing audio files. Do you really want this (which is kinda pointless since you can just select the folder with the audio files) or are there other types of cue files and if so, how can I make them for testing?

 
Sorry I guess I was not clear. A cue file allows you to rip albums as single files but play them as multiple. For example, on my macbook a folder may have a single flac file comprising a whole album but using my music programme audirvana, if there is a cue file in that folder, the programme recognises that there are in fact 9 or so songs in that single FLAC file and divides them up in its playlist. pretty handy. 
 
Feb 5, 2015 at 3:20 AM Post #275 of 6,187
Why every time the app launches the volume is defaulted at such a high level? First time running this app almost deafened me. I would appreciate if the default startup volume is at zero(or better, user customizable). Other than that the app is great.

(sorry if someone else mentioned about it before)
 
Feb 5, 2015 at 4:39 AM Post #277 of 6,187
   
Sorry I guess I was not clear. A cue file allows you to rip albums as single files but play them as multiple. For example, on my macbook a folder may have a single flac file comprising a whole album but using my music programme audirvana, if there is a cue file in that folder, the programme recognises that there are in fact 9 or so songs in that single FLAC file and divides them up in its playlist. pretty handy. 

 
Now, that we can do. What I was worried about was that you wanted the .cue file to reference a .bin or .iso file, which is certainly not something we would be able to parse/read.
 
Feb 5, 2015 at 4:41 AM Post #278 of 6,187
Why every time the app launches the volume is defaulted at such a high level? First time running this app almost deafened me. I would appreciate if the default startup volume is at zero(or better, user customizable). Other than that the app is great.

(sorry if someone else mentioned about it before)

 
The hardware volume is saved in the preferences when you change it. But if you have the option turned on to enable the hardware volume buttons, then it will take the current volume of what your Android device is set to, otherwise there would be a discrepancy between the two.
 
Feb 5, 2015 at 8:59 AM Post #279 of 6,187
The hardware volume is saved in the preferences when you change it. But if you have the option turned on to enable the hardware volume buttons, then it will take the current volume of what your Android device is set to, otherwise there would be a discrepancy between the two.

unfortunately, the problem persists. No matter I enabled the hardware button or using the onscreen slider, the volume jumps back to high level everytime the app is restarted. (In the mean time the usb dac stays plugged) If I use the hardware button, there is no visual indication to remind me how loud it's playing. Actually the moment I press Vol+ or Vol- immediately after starting up the app, the system volume bar will be showing the correct value(lower value),but the sound coming out is LOUD. It only resumes after any change of volume. Which means I have to remeber to adjust the volume after every startup. Luckily I don't have any heart issues. Not the end of the world though. I still like this app and of course bought the paid version already. Any clue why it's happening?

Phone: Moto X 2013, stock 4.4.4
DAC: Resonessence Labs Herus+
 
Feb 6, 2015 at 6:47 PM Post #281 of 6,187
ok, the problem solves itself.
weirdly, It's not happening anymore.
But I do can observe, even when nothing is plugged(no dac, no headphone), the volume slider does jump back to a certain level at each startup. Davy is it a normal behaviour?
 
Feb 8, 2015 at 11:08 AM Post #282 of 6,187
  Regarding *.CUE support, I found something for Android here
 
https://github.com/tguillem/android-mpd/tree/master/src/cue
cue_playlist_plugin.c
cue_playlist_plugin.h
embcue_playlist_plugin.c
embcue_playlist_plugin.h
https://github.com/tguillem/android-mpd/tree/master/src/playlist
 
Also did a quick search and got something else
 
https://github.com/cmus/cmus
https://github.com/mpdflaccuesupport
https://github.com/vchimishuk/cue-go
https://github.com/justlaputa/cue-parser
https://github.com/relikd/CUE-Sheet_sublime
https://github.com/xiph/flac/blob/master/test/cuesheet.ok
https://github.com/smgoller/flactag/blob/master/Cuesheet.cc
https://github.com/mewkiz/flac/blob/master/meta/cuesheet.go
 
Maybe MPD could be a good place to start?
 
http://git.musicpd.org/cgit/master/mpd.git
 

 
Usually we'll find these combos when we prefer to keep metadata inside the CUE sheet itself instead of modifying the file with the audio, it's often a single file instead split tracks:
 
*.CUE + *.APE
*.CUE + *.FLAC (or *.ALAC)
*.CUE + *.TTA
*.CUE + *.WAV (or *.AIFF)
*.CUE + *.WV
 
For mirroring the entire redbook CD image, it's closer to ISO format like this:
 
*.CUE + *.BIN
 

 
As always it would be fantastic if Unicode support for CUE sheets could be implemented properly
 
https://github.com/kuyur/unicue
http://code.google.com/p/unicue/

 
Thanks, we have found a library. Note that we cannot use GPL libraries, such as mpd.
 
Feb 8, 2015 at 11:58 AM Post #283 of 6,187
UPDATE:
It's fine now. probably I did not stop playback before changing the option. My bad. Next time I shall do more trials before posting. I'm sorry Davy.



Davy, from 1.5.1 hardware volume control doesn't work with my dac anymore. i.e. the slider does nothing, instead the physical button works('use volume button' option is NOT enabled, so it shouldn't be happening)
that means the volume is now limited to a very low level. It was working perfectly in 1.5.0. Are you noticing this problem yet?
 
Feb 9, 2015 at 11:21 AM Post #284 of 6,187
UPDATE:
It's fine now. probably I did not stop playback before changing the option. My bad. Next time I shall do more trials before posting. I'm sorry Davy.



Davy, from 1.5.1 hardware volume control doesn't work with my dac anymore. i.e. the slider does nothing, instead the physical button works('use volume button' option is NOT enabled, so it shouldn't be happening)
that means the volume is now limited to a very low level. It was working perfectly in 1.5.0. Are you noticing this problem yet?

 
No problem. I just tested with 3 DAC's and they all controlled the volume just fine.
 
Feb 9, 2015 at 10:22 PM Post #285 of 6,187
UPnP Support - Render and Control Point!
 

Users who are viewing this thread

Back
Top