haiwwen otskae elvain

0 views

Skip to first unread message

Deidamia Bassiti

unread,

Aug 2, 2024, 12:07:55 PM8/2/24

to noheliho

This query is actually a double duplicate. I initially queried several months ago, and I'm repeating this updated query in the hopes that things have changed. I recently posted a related query that was poorly formatted and omitted pertinent details. I've deleted that query and am re-posting.

I am in the United States. There are several streaming video sites, including Cox Cable and HBO.com, that require a "Windows environment" and either Firefox or Chrome as a browser. I have both of those browsers installed on Fedora, but neither will work. I can dual-boot into Windows 7, but I would like to access these sites from within Fedora. Is this possible?

This mostly works, but with 1 core and 8GB of RAM the websites have choppy audio and video and my system temperature gets up to 45C. With a second core, the choppiness is mostly eliminated but the temperature spikes to 60C, and I suspect more cores/memory would be even worse. I don't want to habitually run at over 40C.

b. specifying more cores to Virtual Box; no joy. I received responses that after I had maxed the Virtual Box cpu-cores allocation, Virtual Box's processsing of the video stream would still be onerous enough to drive up the temperature. Apparently, the only effective cooling alternative is to stream the video outside of VirtualBox.

Given a choice between consistently running upwards of 55C with VirtualBox(guest=Windows 7) or dual booting into Windows 7, I choose the dual boot. Therefore, I have to reject the VirtualBox alternative.

Just re-tried on 10-8-2018. From within the google-chrome browser, I installed the user-agent-switcher package and then switched the user-agent from chrome to internet explorer 10. Still no joy trying to play an hbo movie.

This inconclusively suggests that I do not (? also) have a missing codecs problem. When I installed Fedora 26, I followed the standard suggestion re installing additional codecs and then installing the VLC media player. Since the installation, I've played movies in fedora 26 with no problem. Unsure whether there are other codecs that I am missing.

I have tried both firefox and chrome. For each, I tried both with or without user agent switching. On none of these 4 attempts was I able to stream an hbo-go movie from within fedora. Also, I attempted a wine-install of the windows version of both firefox and chrome. Both wine-installation attempts failed.

My Problem
I recently tried using my old Ubuntu laptop (2012 13" MacBook Pro) to watch a movie. I connected to a Bose SoundLink Mini II, but I started experiencing audio quality issues. Approximately once every couple of minutes the audio would either drop completely or sound convoluted for about 1-2 seconds. The symptoms were identical on both Impish (21.10) and Jammy (22.04)[1].

My Resolution:
In an online forum, I found a comment that suggested that switching from the default PipeWire session manager (pipewire-media-session) to WirePlumber resolved a similar issue for someone else. Being unfamiliar with either of these applications I did some reading[2][3][4][5], and decided to give it a try.

Firstly, if PipeWire is being used for audio at all in jammy then that is unintentional. We intend for jammy to use PulseAudio for audio, including Bluetooth. Although how to audit that this happens when we have dependencies requiring that both are installed, is unclear.

I had audio issues similar to yours but only on Steam while using the compatibility layer Proton with a bluetooth headset, which have now been solved (hopefully) by installing pipewire instead.
I used the instructions on their website ( pipewire.org). However, I did have to install some dependencies manually (through pip), if anyone wants to follow those steps.

Actually it did work. Strange I thought I did it exactly that way yesterday. But perhaps I did not do it in this order after all. Thanks! I can connect to my music device again, but the original issue remains unfortunately.

This addressed my BT issue. The intresting part with my ubuntu was that it was initially working - then stopped working for some unknown reason. I was able to hear the volume up/down feedback on wireless headset; I could also play a locally downloaded file. However any audio from browser would play from laptop speakers for some reason. Tried reinstalling BT audio drivers. But finally this one addressed it.

My initial symptoms were, terrible choppy, laggy sound on bluetooth while wifi was transmitting data, and also disconnect after 30seconds and then re-connect. Now I still have disconnect, but the audio quality is very good.

I just installed one of the lorex 8 channel (6 camera) 1080P NVR systems (Lorex LNR382). Everything seemed to go ok, but video playback using the iphone app, or the nethd pc client software is really slow and choppy.

It takes several seconds per second of recorded footage to display. The fast forward modes (x2, x4) don't play any faster. This happens when I connect with a wired connection over the LAN or if I go somewhere offsite and view it remotely.

There's something wrong if the NVR and a PC are wired to the same router. That should be fluid. I have win7 running in virtualbox and I can get 25fps (seems to be the max through web interface) on a swann NVR I just got.

I found that if you use the "Device ID" instead of the "IP/DDNS" for your connection settings, you are directing the NVR to use Lorex's Stratus cloud servers. I believe that this method limits your data rate to that of your Internet connection. In my case I have DSL. So looking at my network meter widget, the data rate going through their cloud was only 2.5 to 3 Mb/s. Once I switched the connection setting for the NVR to its IP address, the data rate jumped to around 40 Mb/s since it was going directly through my router to my computer.

Thanks for your reply. I am concerned that it is a system problem. The problems seem to have started after upgrading to El Capitan. having said that, today I played one of the videos on on of our studio macs at work and it played fine. Some of the videos have pIayed fine before and now don't.

I have repaired permissions using disk utility and it has rectified some minor issues. Unfortunately that hasn't sorted anything out. The videos are on an external USB hardrive. I have tried playing the videos when nothing else is running but that doesn't seem to rectify anything. I have downloaded videos on occasion and they have ran OK. Steaming video is OK too.

Unsure what you mean by "downloaded videos" here. If you're saying videos have a problem playing directly from the USB drive but play fine when "downloaded" to an internal drive, then the problem could be a disparity in the manner in which the videos are encoded as compared with the throughput capacity of your USB device and/or connection. (E.g., an older USB 1 thumb drive delivers data much slower than a full-feature, externally powered USB 3 drive,) Data in video files encoded to play directly from a computer hard drive are often encoded differently from videos targeted for playback from an optical DVD drive or those targeted for streaming over the internet. So, please confirm more specifically how the videos are being played, as well as encoding target specifics if known. (E.g., were files encoded for Download, CD/DVD-ROM, streaming, or device specific playback?)

Unfortunately, we are still trying to determine what factors may be contributing most to your problem. I.e., is this a UHD resolution file with exceptionally wide data rate excursions, a playback connectivity issue, or a platform system problem?

I'm not very techy with sound & vid stuff, so having trouble following your conversation. But what I can contribute is this: up until a couple months ago, everything I downloaded with Download Helper on Firefox played fine. Then the choppy started.

2 different OS: 10.6.8 and 10.7.5 (yeah I know, I can't afford upgrades or new computer; will lose too much valuable licensed software that would have to be replaced at great cost. I'm stuck with this for a while longer)

QuickTime's default playback settings may have been recently adjusted. The audio and video tracks may have been modified to stream at different rates. It is also possible that a timing offset was programmed between the two tracks. Users can investigate QuickTime playback settings by going to "Window" and "Show A/V Controls."

The video may have been compressed with a codec that is not supported by the computer. A codec is an algorithm that codes and decodes streams of media like audio and video. When a media player is not equipped to stream a particular video codec, playback may be choppy. Users can identify a video's codecs by running the media through an analyzer like GSpot, VideoInspector or MediaInfo. Once users have identified the video's codecs, they can install free plug-ins to enable playback for the media.