Hi everyone,
I am having a strange issue. I am trying to watch a live stream, using Web video caster. I have a reasonable understanding of audio and video codecs and things of that nature. However, this particular stream will have audio sometimes and not others. I've checked all the settings on the player and nothing seems to help. I am definitely no expert but it seems to me that if it was a codec problem it would consistently not play audio.
Also, if I'm playing the Stream and the audio is coming through, it will remain consistent. It is not until I stopped the Stream for whatever reason and go to play it again later that I have the audio issue.
I'm not sure what to do, and any information would be greatly appreciated. Also I would like to apologize in advance if I posted in the wrong section as I seem to have a problem with that
Related
i tried the search, but couldn't find anything remotely covering my problem.
in the default htc youtube player you can change the settings to high quality. But the stream loads to 100% and plays for 30 seconds and then it starts loading again.... This is no streaming to me, is the defaut htc youtube player unable to stream? In the registry i found the location hklm\software\htc\youtube, but i have no idea wat i can change here. Also google was very little to no help. Hopefully you guys can provide a solution, because i kindof like the little app.
nobody got this problem? or we all got this problem, but there is no solution?
guess nobody got this issue.......
Hi - I can shed some light on it I think. I was fiddling with youtube player yesterday and found some movies did this and others didn't. Depending on the content and the size (and the quality obviously), the video buffers the first few seconds, and then buffers in the background as it starts to play. Depending on your connection, the player might play the video back quicker than your device is downloading/buffering the stream.
so basically my provider connection is too slow..... CRAP! Cuz i just tested wit wifi and the same vid didn't have the problem...... sigh.........
I've searched high and log and cant find a definitive solution. I just picked up a Tilt 2, i'm running Energy.RHODIUM.21903.Sense2.5.Cookie.May.16. Great rom, i've tried beyond pod, TCPMP, WMP. And no matter what, straight video podcast dls either A)Play great with no audio or B)Play horrible with audio.
I've been researching drivers, trying different codecs, but to no avail.
Please help, i had this same problem on my 8925. Was really hoping it was fixed.
I noticed this issue in Google Listen.
I used to be able to download several audio podcasts, play one of them but decided to pause halfway and begin another podcast, pause the second one and then be able to go back to the first and resume playback.
Now it seems the bookmarking spot is lost and the audio restarts from the beginning. I thought it might be an issue with Google Listen so i uninstalled and reinstalled. No fix. I Googled a solution and none came up but I see a few people complaining of the issue from last year and I've seen recent posts saying the new Stagefright is at fault and is affecting other audio playback apps.
I was wondering if anyone has an idea what's going on and if it is an issue for most/all apps with bookmarking abilities. The MyPod app seems unaffected but I saw the Doggcatcher had an issue (and might have been fixed with an recent update)
I really like Listen as an audio podcast fetcher/player and would rather not give up on it.
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
I have the same problem, running stock 4.2.2 on my Galaxy Nexus. I think it's a device problem, not an app/background process problem.
I don't use TuneIn so I can't speak to the quality of its streams, but I have used Rdio, Slacker, Pandora and Google Play Music and they all play flawlessly.
ONLY Spotify plays audios with occasional snaps, crackles and pops, like a bowl of Rice Krispies. Some songs will play without a blip, some with a few, some with many. The songs are not interrupted...just marred by this defect. And it's never the same way twice with the same song.
It happens whether the song is streaming, or playing locally.
My guess is that the Nexus has difficulty playing Ogg Vorbis files, which is the format for Spotify streams and downloads. As far as I know, the other services I mentioned stream in AAC or MP3. While the Nexus supports Ogg Vorbis, it appears it does not support it very well. I'm going to test this theory by transcoding one of my Apple Lossless audio files to Ogg and then uploading it to the Nexus. My hunch is that it will demonstrate the same issues.
I guess we should consider ourselves lucky; before Jelly Bean the Nexus suffered from more dramatic playback problems. Do a Google search on "Music Stutters when playing long files and screen off: Galaxy Nexus" and read through it. There are a couple of posts that deal specifically with Ogg playback.
I've decided to live with it. I've been hopping from music service to music service trying to find the right one, and I always come back to Spotify. As long as the issue doesn't become more severe, I think I can re-program my brain to tolerate it.
Skyh said:
Hello all,
I love the audio quality on CM, however ever since using it on my Verizon Galaxy Nexus, the audio on Spotify has constantly popped and stuttered and sputtered and whatever other word you want to use when playing through the headphone jack.
I feel like I've tried everything outside of switching ROMs. Tiny Kernel, Franco Kernel, CPU Governors, etc etc etc, doesn't matter.
I've also done search after search after search, and I feel like I'm completely alone in having this issue. I can't find anyone asking about this anymore, now that Spotify claims to have fixed it in an app release months ago (which makes me think it isn't necessarily Spotify's fault, but who knows).
I should mention that this does not happen with Pandora or Songza, for instance. Only Spotify and TuneIn.
Of course, it doesn't seem to be a coincidence that both Pandora and Songza process the audio in some different way from Spotify and TuneIn, since normal use of CM's DSP Manager has no effect on those apps but does work on Spotify.
So, is there anyone else out there who has this issue with CM (or other ROMs)?? At this point I'm just hoping there are others out there who have had this problem just so it isn't an "only my phone" issue -- because those ones have no hope of being fixed.
Click to expand...
Click to collapse
---------- Post added at 11:20 AM ---------- Previous post was at 11:02 AM ----------
My theory was incorrect. I used XLD to transcode Boston's "Hitch A Ride" from Apple Lossless to Ogg Vorbis (VBR, quality 4.0), then put the file on my phone. I used Winamp to play the file and it played beautifully.
So I'm thinking there's something specific with Spotify's encoding that the Nexus doesn't like.
What's odd is that I have run Spotify on other mobile devices and have never had an issue. That's why I have trouble putting the blame on them.
OP, after checking many Google leads, posts, etc. I believe--for Spotify anyway--I have found a way to stop (or at least greatly reduce) the Rice Krispies.
If you have Google Play Music on your phone, make sure it's fully updated and then launch it.
Within Play Music, go to Settings, then select Equalizer.
Turn the equalizer on, select the Normal preset, and move the Bass Boost and 3D Effect sliders all the way to the left to turn them off...unless you like them on.
Back out of Google Play Music to the home screen, then launch Spotify.
Go to Settings within Spotify, choose Audio Effects and verify the Equalizer is OFF in that app.
Using this combination of settings/conditions, I have heard just a couple of pops over a string of a half-dozen songs. I'm keeping my fingers crossed that it lasts.
I'm guessing that having the Google Play Music equalizer on, some additional processing is taking place that alleviates whatever is causing the popping to occur.
Good luck!
Hi there,
I noticed problems with some of my podcasts. They would restart from the beginning when I tried to skip within the track or the player would crash and skip to the next track. I discovered that this only happens with MP3s that are encoded with either VBR (variable bitrate) or ABR (average bitrate) settings, and it is happening with every player (play music, music, pocketcasts) I tried. I converted some of those podcasts using constant bitrate (CBR) and everything worked fine then. I found an old thread (https://code.google.com/p/android/issues/detail?id=8154) describing pretty much exactly my problem.
I tried the same MP3 on my old S4, and that seems to be able to deal with the variable bitrate just fine.
Can anyone try to verify this? There is an ABR MP3 here which gives me those problems. If you skip towards the end it will start playing from the beginning ("Hey everybody this is Sam")
Cheers.
I just played your mp3 straight from the default Files app on my (stock) OP3 and tested two players: the default Music player and Google Play Music. Both were able to skip around just fine. Are you playing the file from a music player or from a podcast app? (Edit: I see where you said which players you tested. Hmm.)
The problem seems to happen after skipping to somewhere past the halfway mark of the file. I just tested it on a colleague's OP3 (3.2.4, all stock) and it happens there as well.
Funnily enough, I just listened to a podcast today when the host mentioned that one of the listeners wrote in with this exact same problem. A quick look into their backcatalog revealed them switching from CBR to VBR a couple of episodes ago.
I don't know what I was doing the first time when I tested, but yeah, now that I'm looking for it, I definitely see the issue. The very first time I played it this time, it auto skipped to the end and would have played the next track in the queue if one existed. From that point on, skipping around did a variety of things. Sometimes it worked; sometimes it played the audio from the very beginning ("Hey everybody, this is Sam") but the slider indicated I was still like 66% of the way through - not at the beginning. Very strange. I'm on the latest 3.2.6, btw.
When you're encoding to VBR, are you using any switches / arguments (e.g. --alt-preset standard)? If so, maybe try something else?
I haven't done any encoding myself (but for back converting some VBR tracks to CBR), I only noticed it in a couple of podcasts I was following, and the thing they had in common was NOT using CBR. I don't know if a certain switch in the VBR/ABR encoding settings might be the problem, but what I find more worrying is that my former sony xperia z5c running marshmallow as well as my s4 active running lollipop do not have this problem. It would be interesting if someone with CM or another ROM but stock could try this to see if it is a ROM specific problem.
A podcast I listen to (The Bayesian Conspiracy) has some episodes as CBR and some as VBR. All of the VBR episodes have issues trying to seek past half-way. This happens on ALL methods of playback that I've tried (streaming, Pocket Cast, Google built-in player, Podcast Addict) on my OnePlus 3.
Found an article ("The First and last word on CBR vs VBR questions" - sorry can't create links yet) talks about why VBR is bad, in general and why podcasts shouldn't use it anymore, but it sure does suck that OxygenOS doesn't handle this properly (because not every podcast is encoded with CBR).
I have contacted the podcasts which I discovered used VBR and ABR and so far I was lucky in that they switched back to CBR, but that can't be the solution.
I have this problem with my config: DailyTechNewsShow with either BeyondPod or PodcastAddict, same problem when reaching 2/3 of the time.
Using OnePlus3 stock with rom 3.2.8.
2 years later, i have the same issue on a Xiaomi Mi A2 Lite. i guess it won't be fixed any time soon...
does anyone know a place where we could report this bug to Xiaomi?
AFAIU, the bug is in their playback code, not in Android. i listen to podcasts a lot, some of them use VBR, and it's annoying me to no end...