Because their internal engineering documents would not be hindered by anything you did.
Starting from scratch when you know where everything is at already isn't so hard.
Hello,
got an HD60S basically for free and have been reading up on the issues on Github as well as the chat here. Can some of you perhaps pinpoint me into the right direction where to get started for making drivers / the process of doing so? Haven't digged into the code yet and want to get myself comfortable with the material in general
got an HD60S basically for free and have been reading up on the issues on Github as well as the chat here. Can some of you perhaps pinpoint me into the right direction where to get started for making drivers / the process of doing so? Haven't digged into the code yet and want to get myself comfortable with the material in general
hi, i'm following the wiki on how to get the firmware from the mac drivers. has elgato removed the mac os 2.0.3 drivers? https://www.elgato.com/en/video-capture/support
im using hdmi input with a game capture hd. i have seen output with vlc in the past, but not as of recently
after opening the .ts vlc, the orange bar bounces around forever, and i get "Initializing device. Hardware revision is V1100090 HDMI input forced."
and i never get any vlc output
Hi, what if we make a request to corsair for support?, I contact them in support and they send me a Feature request form
https://app.smartsheet.com/b/form/19f2943b645c401b9ecb96a3eae9be94
https://app.smartsheet.com/b/form/19f2943b645c401b9ecb96a3eae9be94
maybe https://github.com/stoth68000/sc0710 can be leveraged eventually, depending on how similar the different cards are
Hello @3mj4y79_twitter , I believe the HD60S+ should "just work" as it uses a UVC driver common to multiple stream capture devices. See https://www.youtube.com/watch?v=XCQrcY0PiSE
( @hopperpl Feb 26 2017 15:24 )
I notice my HD60S board features the ITE branding of the 6612 chip, but I seem to be running into a similar problem as the CAT chip regarding another chip on the board, a Mstar MST3363CNK-170. As far as I am aware, Mstar merged with MediaTek in 2012
I notice my HD60S board features the ITE branding of the 6612 chip, but I seem to be running into a similar problem as the CAT chip regarding another chip on the board, a Mstar MST3363CNK-170. As far as I am aware, Mstar merged with MediaTek in 2012
Also, I definitely agree with this youtuber when he says "Don't do what I'm doing": https://www.youtube.com/watch?v=yQ3KzlXPkhU
I opened up my HD60S with my thumbnails. The top and bottom of the case are joined with a small amount of adhesive
I'm not sure if the case design in the video I linked is the same as the one on my HD60S. Mine came apart in two large flat pieces. The clip-in end pieces appear to be the same from what I can tell, at least. I was not able to see if there was a revision identifier on the board in the video, but mine lists the unit as a 2GC309901004 rev 3.3 on the corner of the side of the board labeled R
I see, he doesn't show the backside of the board. Hmm. No matter, I have my own HD60S, it's the HD60S+ that I am seeking high-resolution scans from. It would be interesting and possibly fruitful to see if the HD60S+ uses similar hardware to the HD60S, as the S+ is supported under Linux via UVC
Hello all. I was watching the "Linux HDMI Capture & Streaming using Elgato Game Capture HD" from 4 years ago and noticed in the description that it does not work with the Elgato HD60 Pro, witch I currently have, so now I'm here to cross my fingers and pray to all the gods while I ask this question... Was a driver ever developed for the HD60 Pro?
@martmists-gh I would probably suggest starting by reading the contents of this chat from as far back as you think may be relevant. That should get you up to speed on the development of this particular package, which if I'm not mistaken did intend to support the HD60 Pro at least at one point. After that, you can probably choose an avenue of development that appears the most approachable to you.
Hi all, I'm interested in adding support for the HD60S. I see a long line of people in this chat announcing similar intentions and are never heard from again. I fear I may be one of them O_O Anyway, if anyone is interested in joining me please let me know.
Current status is I've been able to build and run the code to have it create a /tmp/gchd.ts file. It dies when initializing the device. I'm basically running through the debugger and stepping through to understand what is going on.
brief update, during initialization there's a function called read_config() that in turn calls libusb_control_transfer(). it seems that that this should return a certain amount of data but instead gives a -9 or "pipe error". i'm not familiar with libusb so i'll have to look into this function later. it's getting a bit late here so i'll take a break, haha
in commands.cpp there is this little piece
void GCHD::readVersion( std::vector<unsigned char> &version )
{
uint32_t value0=read_config<uint32_t>(HDNEW_VERSION_REGISTER0);
uint32_t value1=read_config<uint32_t>(HDNEW_VERSION_REGISTER1);
...where the version registers are defined as:
#define HDNEW_VERSION_REGISTER0 0xbc, 0x0800, 0x0094 //4 byte read
#define HDNEW_VERSION_REGISTER1 0xbc, 0x0800, 0x0098 //4 byte readDoes anyone know where these numbers came from? I assume they are unique to each device so the HD60S registers will need to be added.
I think they were found by USB traffic captures, but I'm not 100% sure anymore. What I'd like to drop here though, is hopperpl's https://drive.google.com/file/d/0Bz5O5xWCIELacU84VTdTbWViT2c and usbparse by seveirein under https://github.com/tolga9009/usbparse. At the time of writing elgato-gchd, hopperpl's documentation was not available and once it was available, we didn't use it due to legal considerations. For adding HD60S support, I think you have 2 options: option 1 is the quick and dirty approach we used, by capturing USB traffic and putting everything into a parser (usbparse), which filters out the unnecessary parts, but leads to a impossible-to-maintain, 10s of thousands lines of code output. The usbparser probably needs a few touches though. Or option 2: using hopperpl's information to unscramble the USB traffic and use Elgato's own script files, which were included in old driver versions of the macOS driver. Shrinking the 10s of thousands lines of code to a few hundred and a much more readable and easier to understand codebase. But more work is involved than option 1 and I'm not sure, if Elgato's script files were ever "leaked" for the HD60S. Good luck!