Bug Report Amarec Screen Cap - Blank Screen

Ive managed to work out what the problem was!! In the device settings for AmaRec, for the capture card i usually have to have the Video standard option set to 'PAL 60' i think by default its set to 'PAL B', if i leave it at 'Pal B' i get this message when starting AmaRec....

i61xZ3iNPIuWs.jpg


If i change it to 'PAL 60' AmaRec shows the xbox 360 display or whatever i have hooked up to the HDMI port on the capture card.

BUT, for using the capture card with OBS if i change it back to 'PAL B' i get a display, so it must be 'PAL 60' causing the red display in OBS, i wonder if this can be fixed so it works with PAL 60hz mode??
 

paibox

heros in an halfshel
I'm not quite sure why the color format would matter, as all of the capture methods the card supports use either some form of RGB or YPbPr. Mine has always been set to NTSC_M, and works with both PAL and NTSC console input, I would suggest changing it to that and see if that fixes it.
 

entr0py

New Member
I've been using Amarec 2.31 with screen region capture from a Xbox 360. Video capture card is the SA7160. Works perfectly fine with the Micomsoft and StarTech drivers.

I can't get embedded sound (from HDMI) using Video Capture device as a source, which is unfortunate.

Video works perfectly fine using screen region as I mentioned above, or using Video Capture device as a source at 720p resolution. I think the issue BlockAboots (?) may be experiencing is that the card does not support 1080p60. You have to capture at 1080i or 720p. I had the same problem (red screen) until I realized that the card didn't support 1080p60, so I changed the output resolution of the 360 to 720p and now it works perfectly fine.

Looking forward to a stable release that supports embedded audio from this card. Do any of the experimental builds support it currently?
 

paibox

heros in an halfshel
The latest test version (and a few of the previous ones, 0.48.X) support the card's audio input directly in OBS, as well as point filtering (non-blurry pixel scaling) for upscaling/downscaling of the progressive RGB sources the card offers.

That's weird though, 1080p60 input should work fine, as long as you make sure to set the capture frame rate to either 24 or 30. I unfortunately don't have a 1080p HDMI source to test this with at the moment, only component.
 

entr0py

New Member
paibox said:
The latest test version (and a few of the previous ones, 0.48.X) support the card's audio input directly in OBS, as well as point filtering (non-blurry pixel scaling) for upscaling/downscaling of the progressive RGB sources the card offers.

That's weird though, 1080p60 input should work fine, as long as you make sure to set the capture frame rate to either 24 or 30. I unfortunately don't have a 1080p HDMI source to test this with at the moment, only component.

I just tried build 0.48.012b. Embedded audio seems to be working perfectly. 1080p video does not work regardless of what frame rate you set for capture. I tried setting the frame rate to 24, 25 & 30, none worked.

The card doesn't support 1080p60 input, so I'm not sure how changing the frame rate in software would make it work. Perhaps I am missing something.
 

defhvk

New Member
I know this is an old thread, and you've probably fixed it already. Anyway, disabling Aero at startup should fix your problem.
 
Top