holy shit I watched one Trump front page ad and now YouTube is showing Breitbart in recommended channels
Updates from October, 2020 Toggle Comment Threads | Keyboard Shortcuts
-
-
installed the Homies app. Oh my god.. this app’s technology is shit, and it seems to be teeming with ring winger latin american immigrants… i’ll check around the mood of the users a little longer
-
Can we reenact the Rose Garden event and this time bring special guest Elon Musk? He made amazing contributions to space and to the technology of electricity, or something. He needs to share a few words on the podium about Artificial Intelligence, after Hope’s remarks.
-
Adobe Media Encoder was acting up, I restarted, and now after a system restart it’s working.. but it told the GT710 card to do the encoding work, and left the RTX 2070 idle. What the heck…_
-
Yongho Kim 김용호
and after 15 minutes, the main video sequence ends up all black in the encoded file. amazing.
-
Yongho Kim 김용호
I can’t seem to find information online. My search only triggers people complaining about Media Encoder picking up on the Integrated GPU, and I don’t see anyone with two discrete graphics cards.
-
Yongho Kim 김용호
interesting.
Today, I added an After Effects sequence into the Premiere project, to show audio spectrum waves synced to audio.
1. having premiere load up media encoder upon queue makes encoder crash
2. if I launch media encoder first before telling premiere to queue the encode, then it works. it takes a very long time to do some prep, however, and then all video scenes after the AE portion, mid-video, comes out black. the video (and also some scenes where I had a photo as a background are also gone) is black, but the audio is there, and also the text layers also made it. So it’s normal video, then the AE portion (which comes out normal) and then the remainder is just a very long 30 minute continuous black, interrupted by some moments of text layers. the video scenes before the AE portion are fine. Another problem is that the hardware encoder is using the GT710 card (maxed at 100%, and really slow, of course) instead of RTX2070 like it did before.
3. I tried using Premiere’s in-house encoder (“export” instead of “queue”) and it was just stuck for a long time at 0%
4. I disabled GT710 in Device Manager. Still, all the above problems persist.
5. I removed the AE portion and then the video encoded fine. Since I still have the GT710 disabled, it encoded fast using the RTX2070
6. Finally, I created a new sequence just for the AE portion, and exported it into a MP4. I then imported that MP4 back into the video project, and swapped it in place of the original AE portion. So there’s no AE in the project to be exported. now it works!I also downloaded Nvidia Studio drivers 456.38 from September 2020, but haven’t installed it yet. I bought the RTX2070 in early August and installed the August game-focused driver release. I ‘m going to install the new driver now. Maybe it will help with the dual GPU problem
-
Yongho Kim 김용호
plot thickens – installed NVIDIA STUDIO DRIVER : 456.38 – Release Date: Thu Sep 17, 2020 and it made my GT710 unable to work anymore. Device Manager error message: “This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect.”
Did this happen because I disabled GT710, restarted computer, made the encoder do the encode, and then enabled GT710, and without restarting installed the drivers? Not sure.
I’m gonna install the GEFORCE GAME READY DRIVER – WHQL 456.55 – Release Date: Mon Sep 28, 2020 and hope that this fixes things.
-
Yongho Kim 김용호
the second update automatically restored the five monitors. I also tried to do the encoding, and this time the Media Encoder is using the RTX2070 even though I have both GPUs enabled. I’m not gonna touch that AE sequence for a while – will stick to the two-step export trick instead.
-
Yongho Kim 김용호
Media Encoder is again using the GT710 card! Aaaaaaaaaaaaaaaahhhhh
-
Yongho Kim 김용호
-
Yongho Kim 김용호
today, it uses the RTX2070. One difference is this time I had OBS turned off. Did encoder skip RTX 2070 seeing that it was being moderately used by OBS?
-
Yongho Kim
Seems to be solved. So it’s possible to specify the GPU to be used from OBS when there are multiple GPUs. So maybe if I assign OBS to the slower GPU, maybe Encoder will automatically pick up the “less busy” and faster GPU?
I reinstalled the GT710 card. On first boot, Windows didn’t detect it. I changed it PCI slot location to the one underneath the main GPU and restarted, and this time it picked it up as GPU 0. Upon another restart, it was picked up as GPU 1 (I see the GPU number in Task Manager). I configured OBS to use GPU 1’s NVENC for streaming (also changed Preset from Quality to Performance and Profile from High to main.. just in case the GT710 would choke on the workload. These are downgrades in image quality, I think. Also, hopefully what OBS means by “GPU 1” is what the Task Manager means by GPU 1), then started a livestream, and opened Premiere and encoded a video. This time the encoder is using the GT710. This is the third boot – we’ll see whether Windows continues to assign GPU 1 to the GT710 on future bootups or whether this allotment is somehow arbitrary (which would mean that OBS settings would need to be changed for each restart)
After doing this, and quitting Encoder, I see that the RTX2070’s load is at 35%-40% even though the only graphically intensive thing running is OBS.
-
Yongho Kim
It seems that the setting to specify the GPU is gone in the current version of OBS. (At this point, I don’t remember well if there was the option back in December of last year)
-
Reply