Computing desk
< April 15	<< Mar \| April \| May >>	Current desk >

Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is a transcluded archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.

April 16

Pertaining to CUDA/NVCUVENC and NVENC

While looking through pages on different media encoding software, I noticed that one of the articles appeared to use CUDA interchangeably with/in place of NVENC:

https://en.wikipedia.org/wiki/XMedia_Recode#System_requirements

The snippet in question is this one: "Nvidia CUDA: Nvidia GPU driver 347.09 or higher"

If I remember correctly, CUDA H.264/NVCUVENC was deprecated in 2014, in favor of NVENC - a hardware encoding ASIC that's available for GPUs with Kepler (GTX 600/700) and above. This is a snippet from Bandicam's website: "NVIDIA doesn't support the CUDA H.264 encoder from the GeForce 340.43 beta driver."

I'll get to why that's important in a second. While I do see the benefit of CUDA/NVCUVENC, for people who still have access to older GPUs (like Fermi - GTX 500), I also find it necessary to make sure that the terms are not being used interchangeably. CUDA H.264 is a version of software encoding that offloads some of the work to the GPU. But on some websites, I see it referred to as "hardware" encoding. I simply want to make sure that this community does not fall into the same practice.

Here are a few sources that I have found to be helpful in the matter:

The Bandicam page is linked because I used to own a GTX 550 Ti, which had no NVENC hardware. But was able to use the CUDA H.264 encoder linked on that page to record and upload 720p,60fps videos to YouTube. This makes the CUDA encoder viable for situations where NVENC is either incapable or non-existent. I was able to verify the functionality of this encoding technology. I am not sure if XMedia is using the same encoding technology, due to the System Requirements. In addition to this, I also am forced to consider the possibility that this isn't the only page where such has happened (using CUDA interchangeably with NVENC).

I apologize if this concern is misplaced. I simply want to help ensure the accuracy of information on this platform. Thanks for reading this.

HEIF samples

can anyone provide HEIF sample images for download? thanks!

https://nokiatech.github.io/heif/examples.html

I'm not able to download the images. do you have a direct URL by any chance?

How did e-editions start? And how did e-editions start to replace actual print editions on some days?

I added a red link E-edition to at least one article but don't know where that red link should redirect to. It's even possible an article could be written, but I wouldn't know how to create it. I'd have to start with the above questions. Google is of little help since the results are all e-editions of newspapers. Some results show the description, which is an online replica of what the actual newspaper looks like, or in the case of the articles I edited, what it would look like if there was one for that date. Some newspapers aren't printing, for example, an actual Saturday edition, but there is an e-edition.— Vchimpanzee • talk • contributions • 22:49, 16 April 2020 (UTC)[reply]

Any answers provided here would probably be content added to one or more Wikipedia articles, but which ones?— Vchimpanzee • talk • contributions • 23:03, 16 April 2020 (UTC)[reply]

See digital edition

That will work. Now all I need to do is figure out what information to add to that and where to get it.— Vchimpanzee • talk • contributions • 16:11, 17 April 2020 (UTC)[reply]

E-book has a history section that might help. 2601:648:8202:96B0:E0CB:579B:1F5:84ED (talk) 00:35, 18 April 2020 (UTC)[reply]

I didn't see anything there. I did do a search on ProQuest that showed the e-edition existed in 2000 and I could probably go back further. Why I was getting documents from the 18th century I don't know.— Vchimpanzee • talk • contributions • 16:38, 18 April 2020 (UTC)[reply]