Re: Handbrake Windows 10
Julia Heaslet
Basically, I'll be playing GTA VC/GTA3 for a while. I'll randomly hop into a car or something, floor it, and it just won't go anywhere. As if the handbrake is jammed on. Nothing. Get out, get back in, nothing. From this point on, the jump button also ceases to do anything. Everything else works fine. I jumped into the Sea Sparrow which automatically kept firing constantly, presumably becuase the handbrake button fires the canon.
This is not the worst bit. If I then quit the game, and go into Windows, Windows is more or less completely screwed. If I click on an icon and highlight it, and then click on another, it selects both, as if control is held down. I am unable to select applications on the taskbar to view them - it has no effect, and alt+tab won't work either. I am also unable to switch between IRC channels by clicking them in mIRC.
The only way out of this is to reboot, although this prooves difficult becuase the machine refuses to either reboot or shut down. You select shutdown, the background goes grey as per usual, and then nothing. Whack any key and you are back into Windows. The only way to shut down or restart is to whack the reset button or the power off button on the case.
Sounds like its something to do with your PC if it doesn't restart or shut down correctly. I would suggest backup all your data and then format and install Windows again, Sometimes its good to start with a clean slate.
2 days ago Handbrake was working just fine, but now it won't start at all. When I run ghb in terminal, it reads it can't find a library called libvpx.so.6. Searching for libvpx says both 32-bit and 64-bit libvpx are installed. Any ideas what might be going on?
I understand (sort of). Downgrading handbrake doesn't fix the problem and neither does (work) downgrading libvpx. I also tried downgrading ffmpeg but that breaks other dependencies, so that's a no go. Other than completely uninstalling and forgetting about handbrake, I don't see a way to fix this.
The problem is that the installed libvpx is version/number 7 but the program is looking for version/number 6 and IDK how to fix that. The only thing I haven't tried yet is to try and compile handbrake from source.
I did run them. Either they have changed the default location of the executable file and that's why it returns errors or there's something else going on that I'm not getting. If it's the former, I'll simply edit the desktop file.
handbrake 1.4.2-2 owns /usr/bin/ghb, the first command says there's no package owning /local/bin/ghb. If I run just "ghb", for some reason it's looking for it in /usr/local/bin and since it can't be started, that brings up the error about libvpx.so.6. But if I run /usr/bin/ghb, then handbrake starts ok, that's why I figured that if I edit the desktop file to point to the new location, it should fix the problem. Which I did a moment ago. IDK if that's the right way to do it, but at least it works.
and that's ok and by design - you simply don't want to have the wrong and likely very dated version of handbrake around that you've so far been using unknowingly.
Editing the desktop file is not a sustainable approach as the next handbrake update will revert that.
=> So rid your system of the hadbrake installation in /usr/local/bin - likely from when you at some point compiled it yourself. If you have those sources still around, "sudo make uninstall" will likely remove it (but might also hit files of the pacman version, so in doubt re-install handbrake w/ pacman afterwards)
I have a Threadripper 3995WX with 64 cores. I will run a quick test with 8,16,32 and 64 cores on a small sample file. Since this is related have you though about hardware transcoding with a GPU? I know people say the quality can be better and the file size can be smaller with software encoding, but honestly I can not see a difference when encoding with my GPU and the file size is also not that much worse. These days I mostly encode to AV1, but as I said with my GPU, which is so much faster.
The 6900XT can in fact not encode AV1. It is missing the hardware encoders on the chip. AV1 is a new encoding standard that is slowly supported by many devices. The files can be smaller, or the bitrate lower while maintaining the same quality as H264 or H265. It is interesting for the web, since it means you need to transfer less data, but also for your own libraries since it saves disc space. However you need to be aware that the encoding process is more demanding than H265, since the compression algorithm is more complicated and requires more work by the CPU.
The link I provided is a table with hardware support and should answer your question. It shows that Intel Arc GPUs can encode in hardware while Intel Xe iGPUs can only decode in hardware. I brought up GPU hardware encoding since it is not only a big time saver a Intel Arc or AMD RX7600 should be significantly cheaper than to buy a Threadripper. But this is up to you to decide.
I have a 24 core 48 thread thread ripper 2970 and the 12 core 1920 that I have used to transcode in hand brake. The 1920 was pretty close to maxed out when a handbrake task was started. The 2970 does not get all threads pinned. I have tried doing two transcodes at once but I crashed the system the few times I tried.
What settings are you using for your encodes, and have you tried the latest nightly build of handbrake that can keep the dolby vision data if that works on your GPU and the quality drop is not too bad then that could be a viable option for me.
My problem is that some programs (Handbrake, NordVPN for example) only comes up with a white window when launching them. You can see the Title on top of the window and you have the "X" to the top right to close the program, but that's it.
Funny thing is that when I launch the program in front of the host and then later connect remotely the program does display everything correctly. Same thing if I reboot the computer and launch the program remotely.
Not sure what just happened, it was working just fine and suddenly applications just start showing completely white?? Just like that. No changes of drivers, applications, configuration, absolute nothing different than an hour ago... and bam, Teamviewer completely useless. How is that possible?
I think someone must have shut down the display/monitor connected to it by accident. It has a DVI input but dunno for sure what type of monitor is connected. Probably a cheap screen though since it's mostly used remotely. Thanks for getting back to me so quickly. I guess i'll stop trying to troubleshoot that remotely. I've reinstalled drivers, applications, installed chrome remote deskptop to try an other remote desktop application, same **bleep**. It's too frustrating, i'll wait a few hours until someone's physically in that room and turns the darn monitor on again. SMH.
Cheers.
Typically, monitors or notebooks display shall report their data (such as what resolution they support) to the graphic card once they are connected.
The monitor itself does not need any power, as the HDMI / DVI / VGA cable itself provides enough power.
Unfortunately, there are some monitors that will only pass their data to the graphic card when they are turned on/have power.
In this case, the graphic driver shall decide what it wants to do when the monitor is not detected. There have been 3 cases detected thus far:
TeamViewer grabs the screen as it is currently displayed.
In other words, if Windows did not draw anything, TeamViewer cannot grab the screen, so you will only see a black screen. Unfortunately, we cannot do anything against that.
Hi,
Do you use an integrated graphics chip or are you using stand-alone? --> I use a GTX1080Ti with the newest driver.
Does this only happen on Teamveiwer? --> It only happend with Teamviewer. At the PC the software works without any problems. I did not use any other remote viewing software.
Have you installed the Monitor Driver for the software, if so was that successful? --> No, how to install a monitor driver for a specific software, this is new to me.
Yeah, I got this problem now that I've installed SAMSUNG U28E590D 4K monitor, connected by DP cable, Firefox would whitescreen, I was able to fix this by disabling graphic acceleration but Windows Live Mail still only displays part of the screen, I may have to unplug the cable when I get home to see if it resolves this as I've been at this all night remotely, getting nothing done, I never thought switching a monitor would be such a pain. :-/
I've since found that connecting a HDMI cable to the mb port to monitor seems to fix this, I can still default to using the add on video card to monitor by DP cable when at home but somehow having that second connection resolved this issue.
When using teamviewer to remotely view other computer equipment (a WorkStation) I can not visualize the 3D screens (which have movement and allow you to model and visualize some data in 3D), this did not happen previously, but since I upgraded to the latest version it is not possible for me Visualize these data in 3d dimensions. Has something similar happened to you? How can I configure Teamviewer so that I can visualize those windows as I could before? Thanks in advance.
For me, I get black windows! I am remoting into a laptop media server, which used to work fine. However, as of a couple of days ago, I am starting to see black windows for VLC (I hear audio but see no video), Next PVR, and even Firefox and Edge browsers. It's the same whether I use TeamViewer or **bleep**. However, following the comments above, I have just realized that if I open the laptop lid, all the windows display correctly. If I close it again, they go black. So, yes, it's definitely a rendering issue. I wonder if there was something contained in a recent Microsoft update that caused this behavior?
Hey I have exactly the same problem and a Samsung monitor. When you say 'connecting a HDMI cable to the mb port to monitor' ... what do you mean by mb port to monitor? Just trying to resolve this issue so I can actually use TeamViewer? Thanks
03c5feb9e7