What is your receiver ? Can you share the file ?It may be a bug in VLC since my receiver does support Dolby and the audio format used in the file I was casting (AAC), sometimes it would work with the option checked while other times it would not (for the same file), but with it unchecked it always worked.
Can you share the file too ?I'm having the same problem. I tried updating my VLC with the latest nightly build, but that didn't fix the problem.
Is this indeed a problem related to an update Google made?
The Google reps want to steer me away from using VLC. But no other methods of casting have worked as reliably as VLC.
Is there a known fix to this issue?
Hi,
What is your receiver ? Can you share the file ?It may be a bug in VLC since my receiver does support Dolby and the audio format used in the file I was casting (AAC), sometimes it would work with the option checked while other times it would not (for the same file), but with it unchecked it always worked.
Can you share the file too ?I'm having the same problem. I tried updating my VLC with the latest nightly build, but that didn't fix the problem.
Is this indeed a problem related to an update Google made?
The Google reps want to steer me away from using VLC. But no other methods of casting have worked as reliably as VLC.
Is there a known fix to this issue?
Here's what happened. This is extremely bizarre. After hearing me say that VLC said it was due to Google making some updates, Google said I should not use VLC. I had been having basically three different results when attempting to cast YouTube (when YouTube could be cast just fine from any of our mobile devices):Hi,
What is your receiver ? Can you share the file ?It may be a bug in VLC since my receiver does support Dolby and the audio format used in the file I was casting (AAC), sometimes it would work with the option checked while other times it would not (for the same file), but with it unchecked it always worked.
Can you share the file too ?I'm having the same problem. I tried updating my VLC with the latest nightly build, but that didn't fix the problem.
Is this indeed a problem related to an update Google made?
The Google reps want to steer me away from using VLC. But no other methods of casting have worked as reliably as VLC.
Is there a known fix to this issue?
Sorry, what chromecast settings in VLC?Check your chromecast settings in VLC, I've seen this happen when I checked the Audio Passthrough option, turning it off and restarting VLC fixed it.
It may be a bug in VLC since my receiver does support Dolby and the audio format used in the file I was casting (AAC), sometimes it would work with the option checked while other times it would not (for the same file), but with it unchecked it always worked.
Code: Select all
sudo /sbin/iptables -A INPUT -p tcp --dport 8009 -j ACCEPT
sudo /sbin/iptables -A INPUT -p tcp --dport 8010 -j ACCEPT
Wrong. Turning off Windows firewall worked for me instantly after having this exact problem with the "conversion" warning and all.firewall issue would mean you don't see the chromecast at all. If it renders black screen, it means the issue is on our side (well, usually either because of a chromecast update that remove features, or a format that wasn't transcoded previously in chromecast).
Return to “General VLC media player Troubleshooting”
Users browsing this forum: No registered users and 19 guests