|
Post by nachomagic on Feb 28, 2013 2:59:34 GMT -5
Ok, the I will try with another rom
What rom do you use?
|
|
xrad
New Member
Posts: 9
|
Post by xrad on Feb 28, 2013 3:01:37 GMT -5
Thanks for considering my input. 1) You are still able to seek the track during the crossfade.. so what happens if during those last 5 seconds the user moves the seek bar back to the middle of the song. The UI would have changed tracks but the old song still plays Well - not if you really define the *start* of a track to be the track change. The way I see it is this: if cross fade is enabled, than any track will be cut by the length of the cross fade duration. The remainder thus truncated will be merged into the new track as it plays. So once cross fade kicks in, your are already in the new track and everything -- artwork, position, avrcp information -- refers to that song. The longer I think about it the more certain I am that you need to move the track change to the very first byte you play of the next song. Yesterday I had another odd thing happening: 5000ms cross fade started, and I recognized the song and didn't like it, so I pressed next. But I was still in the middle of cross fading, so next actually proceeded to the song which was being faded in! And I had to press next again. Not cool. 2) The track change triggers the next song (song after the one being crossfaded into) to be queued into the audioengine. The engine only handles the current playing track and the next playing track. By queuing this in.. it would change the song being crossfaded into and everything would get all messed up. I'd say this is covered as well by the approach I suggested.
|
|
|
Post by nachomagic on Feb 28, 2013 4:26:49 GMT -5
xrad please, tell me what rom are you using to test with your one and gonemad one
|
|
xrad
New Member
Posts: 9
|
Post by xrad on Feb 28, 2013 6:55:10 GMT -5
|
|
|
Post by nachomagic on Feb 28, 2013 7:27:35 GMT -5
I've tried with AOKP ROM Resurrection Remix (4.2.1) and works so the problem is the ROm or maybe that is a CM rom
Do you guys have tried with a CM rom?
Thanks in advance
|
|
xrad
New Member
Posts: 9
|
Post by xrad on Feb 28, 2013 8:05:17 GMT -5
I've tried with AOKP ROM Resurrection Remix (4.2.1) and works so the problem is the ROm or maybe that is a CM rom Do you guys have tried with a CM rom? Thanks in advance AOSP 4.2.x and thus also CM 10.1 does not do AVRCP 1.3 (media metadata), only 1.0 (basic controls).
|
|
|
Post by nachomagic on Feb 28, 2013 8:10:55 GMT -5
Theoretically the rom support it because is CM-AOKP
|
|
|
Post by GoneMAD on Feb 28, 2013 9:05:37 GMT -5
Thanks for considering my input. 1) You are still able to seek the track during the crossfade.. so what happens if during those last 5 seconds the user moves the seek bar back to the middle of the song. The UI would have changed tracks but the old song still plays Well - not if you really define the *start* of a track to be the track change. The way I see it is this: if cross fade is enabled, than any track will be cut by the length of the cross fade duration. The remainder thus truncated will be merged into the new track as it plays. So once cross fade kicks in, your are already in the new track and everything -- artwork, position, avrcp information -- refers to that song. The longer I think about it the more certain I am that you need to move the track change to the very first byte you play of the next song. Yesterday I had another odd thing happening: 5000ms cross fade started, and I recognized the song and didn't like it, so I pressed next. But I was still in the middle of cross fading, so next actually proceeded to the song which was being faded in! And I had to press next again. Not cool. 2) The track change triggers the next song (song after the one being crossfaded into) to be queued into the audioengine. The engine only handles the current playing track and the next playing track. By queuing this in.. it would change the song being crossfaded into and everything would get all messed up. I'd say this is covered as well by the approach I suggested. yup I said there were solutions to the problems.. and what you said was what I would do, it just involves a lot of rework to the engine
|
|
|
Post by GoneMAD on Feb 28, 2013 9:07:48 GMT -5
I've tried with AOKP ROM Resurrection Remix (4.2.1) and works so the problem is the ROm or maybe that is a CM rom Do you guys have tried with a CM rom? Thanks in advance AOSP 4.2.x and thus also CM 10.1 does not do AVRCP 1.3 (media metadata), only 1.0 (basic controls). i dont have any bluetooth devices that support 1.3 so i can only go on teh word of others but i was fairly certain CM added 1.3 support a long time ago.. unless they never added it back in for cm10.1
|
|
xrad
New Member
Posts: 9
|
Post by xrad on Feb 28, 2013 10:24:49 GMT -5
i dont have any bluetooth devices that support 1.3 so i can only go on teh word of others but i was fairly certain CM added 1.3 support a long time ago.. unless they never added it back in for cm10.1 Yes, CM has it -- but only up to CM10. But in 4.2.x Google completely changed the BT stack, leaving only basic AVRCP 1.0 support in and rendering existing AVRCP 1.3 useless. As far as I can tell, nobody @ CM is really actively working on this. I guess everyone had hoped that 4.2.2 would fix this, now that it hasen't, well... In fact this is one reason I'm glad NOT to have an N4. To everyone suffering from this: go google the many bug reports on this and star them, as a feeble attempt to make Google fix this embarrassing shortcoming of Android.
|
|
|
Post by GoneMAD on Feb 28, 2013 10:39:52 GMT -5
i do know 4.2.x had a lot of bluetooth issues.. from what i read it was a lot of disconnects or stability issues.. didnt realize they broke 1.3 support as well
|
|
|
Post by nachomagic on Mar 1, 2013 1:19:14 GMT -5
Thanks GoneMAD and xrad xrad, what rom do you use? I would like to have the AVRCP 1.3 fully working
|
|
xrad
New Member
Posts: 9
|
Post by xrad on Mar 4, 2013 3:00:13 GMT -5
|
|
|
Post by nachomagic on Mar 4, 2013 6:00:35 GMT -5
Thanks
|
|
|
Post by nachomagic on Mar 8, 2013 2:04:17 GMT -5
Hi again mates Finally I've installed an stock Rom and avrcp 1.3 works Anyway I have a problem that would be great if could be solved. When I'm listening music and the song end, the next one starts and the song info is changed flawlessly. If I press next(or back) in Gonemad also happens flawlessly but I press next in the card buttons the song info is not displayed, appears "waiting" till the next song when the info is updated to the new song. When I see "waiting" I can use the car remote control without any problem just the song info is not displayed, the unique way I've found is pressing pause in the car and the again pause, if I do it, the info song is displayed till the next time I press netx/back in the car remote control. Do I explain successfully? Thanks in advance
|
|