Micomsoft XCAPTURE-1 USB 3.0 Capture Unit

[NightSprinter]

Akumajou: I would be extremely wary of the new driver. I posted on the SC500 thread about the 160 driver for the PCIe cards. So the XCAPTURE-1 may also have its ability to do RGB capture below 480i hosed. I would suggest someone do like I did with my PEXHDCAP, and test first to confirm.

Last I wanna see is a wave of owners complaining about how retro RGB capture no longer works, becaus Micomsoft didn't report that feature was removed.

[STG]

Akumajou: I would be extremely wary of the new driver. I posted on the SC500 thread about the 160 driver for the PCIe cards. So the XCAPTURE-1 may also have its ability to do RGB capture below 480i hosed. I would suggest someone do like I did with my PEXHDCAP, and test first to confirm.

Last I wanna see is a wave of owners complaining about how retro RGB capture no longer works, becaus Micomsoft didn't report that feature was removed.

You're definitely right NightSprinter, just tried the latest drivers myself with the XCapture-1 (running Windows 7) and it is indeed borked for 240p! Weird... Got the same results in both Videokeeper2 and Amarec, all I get is an unstable stretched picture. Even trying to configure the settings in the driver didn't work right.

At least it's easy to reinstall 1.1.0.140.1 and then install 1.1.0.141.5 (for the XCapture-1 driver) for recording of low res RGB until Micomsoft sorts out that latest update.

[Smashbro29]

new driver : http://www.micomsoft.co.jp/xcapture-1_V ... .160.5.zip
Japanese patch notes.

Translation incoming?

[NightSprinter]

STG, it's not Micomsoft that's at fault. All they do is add their vendor ID to the drivers. So if anything, it's the fault of the OEM of the device for ruining the functionality. As for Smashbro29 (I'm redoing what Google Translate kinda did) :

■ Now supports Windows 10
● Video Keeper 2, due to dropped support from nVidia of CUDA encoding, now uses NVENC.

● We added a "special adjustment setting" to the setting function of VideoKeeper2.
• The display position of the analog RGB input can be fine-tuned.
-Further screen adjustments, such as Tint, can now be made.
※ If you re-display the special adjustment setting TAB after the adjustment, the set value does not remain in effect.

● When you play a video that was made from recording for a long time (6 hours or more), or playback that was unstable in Windows Media Player, it has been improved and now also not a problem when opened in PEGASYS Inc. TMPEG Enc.

<Problems and symptoms dependent on software and drivers that have been identified.>

● When you capture an image of the HD image quality in analog RGB (720p, etc.), level of red and blue is low.

● On some analog screens (such as a 70Hz 720x400 BIOS or MS-DOS screen), the capture settings may show the displayable image as "640x448" or "640x449".

Auto-adjust for the screen's black level may not work properly.

● In an analog RGB image captured from a 24KHz 400 line signal (such as from a PC-8801mkⅡSR where there's a color graphics screen and both color and black "scanlines"), the displayed image may shown in black and white.

● While it may be the same resolution, changing the sync polarity in a "CVT" generated resolution or changing "CVT-RB" or "GTF" generated resolutions like "DMT" (analog resolutions or digital resolutions) are not available. In addition, some of these four types of resolution might not be supported.

● are not reflected in the operation panel settings when you re-display the settings TAB in "special adjustment setting" (numerical value and adjustment bar becomes the default setting)

● Game development board for a particular business (pachinko board) due to the aspect ratio the display may look abnormal due to a shifted image (There's no plan for this currently).

<Hardware compatibility information (specific cases I can't resolve)>

The following PC or motherboard, and chip sets are equipped with hardware specifications available this machine, but it does not work properly due to compatibility, or it is not supported.
In · HP Company models equipped with the Intel C226 chipset in the workstation (Z230, such as Z420), to be connected, the personal computer can not recognize this unit.
For this reason, HP's models were equipped with the Intel C226 chip set in the workstation I will consider it as unsupported.

• When this capture device is used in a computer with a motherboard equipped with an Intel P67, X79, or X99 chipset, it may not work properly.
For this reason, stable operation with an Intel P67/X79/X99 platform-based computer can't be guaranteed.

• Usage with AMD CPUs (such as the FX Series) and compatible motherboards may not be stable. I can't guarantee compatibility with such hardware.

Please feel free to improve even further on that. Google Translate isn't the best at times.

[DanAdamKOF]

Has anyone used the XCapture-1 with a USB 3.0 Expresscard?

I did for a short while, it worked but because it was an older laptop running XP I didn't get great performance with Amarec or Videokeeper. Certainly wasn't because of the card. I upgraded my laptop to the latest and greatest with multiple 3.0 ports shortly after that.

Thanks! Do you know which card you used? Have things changed regarding Xcapture-1 only working with certain USB 3.0 chipsets or is it still only compatible with particular ones?

[STG]

STG, it's not Micomsoft that's at fault. All they do is add their vendor ID to the drivers. So if anything, it's the fault of the OEM of the device for ruining the functionality.

I see. Well, it's odd that they would release this driver into the wild and miss something so obviously broken like 240p capturing, especially since they're advertising that these devices can handle that...

Thanks! Do you know which card you used? Have things changed regarding Xcapture-1 only working with certain USB 3.0 chipsets or is it still only compatible with particular ones?

No problem, the card I used was this one:

http://www.newegg.com/Product/Product.a ... 6839158046

[NightSprinter]

Yeah, I think really all that is done is the OEM drivers are repackaged with their company info. I doubt it'd do anything, but I let StarTech know the low-res capture functionality over analog RGB is very reduced in the new driver. Mostly because I know some of us went with their cards from a price standpoint

[akumajo]

240p is still broken for me in Windows 10

[NightSprinter]

Not just Windows 10, but ALL versions supported by the driver.

[nachos]

Hi all, first post... regarding the half-screen problem with composite/S-video. I have a new USB3HDCAP and I installed the latest StarTech drivers (1.1.0.160.5) in 64-bit Windows 10. I was having the half-screen issue and found this thread. I messed around with settings, and unchecking "Auto Resolution Scaling & RGB24/32 Output (Pls Reboot)" under "Driver Property" in the device settings seems to have done the trick:



Now the resolution settings in both AmaRecTV and OBS work as I would expect and I can see the full image from N64 on S-Video and Composite. I haven't done much testing with other systems yet, but I hope this is helpful for others.

[lettuce]

Does anyone know what the latest version of the AmaRec Software is??. As i have looked on the English download page (http://www.amarectv.com/english/amarectv_e.htm) and that seem to only have vers 2.31 but looking on the AmaRec Blog (http://amalabo.blog35.fc2.com/page-1.html) there seems to be a ver 3.24 if you scroll down the page a bit and you'll see a picture showing ver 3.24!!?

[blizzz]

3.10 is the current version on the normal (non-english) website: http://www.amarectv.com/download_amarectv.htm

I think 3.24 is still not publicly available.

[Coestar]

I updated to the latest driver (160.5) today as I've been tearing my hair out trying to resolve gradual audio de-sync with my XCAP. The new problem I've been experiencing after updating is video signal loss. I have two consoles connected to my setup at the moment, here's the arrangement:

SNES -> RGB -> XRGB-mini (HDMI out) -> 8x2 HDMI Splitter/Switcher -> XCAPTURE-1 (HDMI in)
Neo Geo -> Composite -> [ditto above]

The composite signal from the Neo Geo is lost intermittently, but the RGB signal from the SNES is solid. This is a new problem, as both video signals were fine on the previous driver (141.5). I haven't experienced a total loss of sub-480i support (yet), no idea why that is (I'm on Win7, maybe that's it?). EDIT: I realized later the reason is clearly because I'm not sending 240p direct to the XCAPTURE-1, but instead everything is upscaled to 720p by the XRGB-mini. Duh!

At any rate, things only got worse and the gradual audio de-sync remains. Gonna have to begrudgingly go back to my Live Gamer HD with its popping audio.

[lettuce]

3.10 is the current version on the normal (non-english) website: http://www.amarectv.com/download_amarectv.htm

I think 3.24 is still not publicly available.

I wonder what changes have been made, i would like the ability to save capture files in .flv or .mp4 format and also the ability to delay/bring forward audio for sync issues

[Guspaz]

Wait, what? Why FLV? It's a dead file format. Even people using Flash for video stopped using it, and Flash is getting increasingly rare for video in the first place.

[lettuce]

Wait, what? Why FLV? It's a dead file format. Even people using Flash for video stopped using it, and Flash is getting increasingly rare for video in the first place.

Well with .flv if for what ever reason your PC, Capture Device or Capture software crashes the .flv file is still salvageable (it will save the file up to that point) and you'll have something to work with, with formats like .avi and .mp4 if it crashes you lose everything and the file is useless! Also .flv is less intensive in the encoding process and cpu usage

[Guspaz]

That's not true with either AVI or MP4: just because you can't stick the file into a video player and have it work perfectly doesn't mean that the file is "useless". It just means you need to run a tool on it.

FLV would be less CPU intensive to encode because it typically uses codecs that are very old and inefficient: we're talking stuff like Sorenson Spark, which was an incomplete implementation of H.263, a standard developed twenty years ago. Encoding in modern non-proprietary formats is really not very CPU intensive, and pretty much any computer made for years and years has supported hardware encoding of some kind.

[lettuce]

That's not true with either AVI or MP4: just because you can't stick the file into a video player and have it work perfectly doesn't mean that the file is "useless". It just means you need to run a tool on it.

FLV would be less CPU intensive to encode because it typically uses codecs that are very old and inefficient: we're talking stuff like Sorenson Spark, which was an incomplete implementation of H.263, a standard developed twenty years ago. Encoding in modern non-proprietary formats is really not very CPU intensive, and pretty much any computer made for years and years has supported hardware encoding of some kind.

The file as it stands on its own would be useless!

If you had a 18GB file it would take far too long for a 'tool' to try and fix the file only to find after the 8 or so hours that the 'tool' hasn't managed to fix the file . With FLV file no such time wasting measures is needed as you'll only lose the last 2-3 seconds of the capture!, why would you waste time trying to fix a file when you dont need to if using .flv!. There is no disadvantages to using flv over mp4

[Guspaz]

You can configure mp4 muxers to fragment appropriately to achieve the same thing (only lose the last few seconds), but the major disadvantage of flv is poor compatibility with other things, and a large drop in quality (or large increase in file size) if it's using the typical FLV codecs.

[NightSprinter]

Nachos: can you go back to "device properties" and show us what the resolution is via RGB? I need to see confirmation it has input at 720x240p. Big reason I ask, is because this surprisingly also affects those who may also have bought the USB3 capture devices by VeloCap or Magewell (which also use the CY3014).

[nachos]

I'm working on building a sync splitter soon for my SNES and a couple other consoles I have SCART cables for, but at the moment I don't think I have any compatible 240p RGB sources to test with. As I understand, I need to split CSYNC to vertical/horizontal for the VGA input?

It shows my N64 via S-Video as 1440 x 240P @ 59.94FPS in device properties. No idea why it says 1440, but it has been working fine for recording 240p via composite and S-Video after changing the setting I mentioned before (no more half-screen glitch).

[NightSprinter]

If connecting directly to the HD15 input, it is an option. Otherwise, connect the raw csync to the hsync pin. It is important that you make sure the sync signal is stripped of composite/luma.

The new drivers (at least my experience on the PCIe side) shows 240p still works fine via comppnent. Just baffled as to why it was ruined via RGB.

[kardus]

Will the Xcapture record/passthrough component YPbPr via the VGA/HD15 port? I was planning on getting the component -> VGA cables from monoprice.

[Plasia]

I just got my xcapture unit as a christmas present to myself.

I've come up with a curious and infuriating problem when trying it out.
(testing on z77, i5 3570, 8GB RAM PC)

-> I downloaded the latest 1.1.0.160 drivers from Micomsoft.
-> Tried plugging in my PS2 via component, constant cutouts
-> Tried different USB3.0 ports, same result
-> Tried HDMI from another PC, works flawlessly
-> Tried different component to dterminal adapter, still constant cutouts
-> Tried GC via component, same constant cutouts
-> Tried GC via composite, works flawlessly

^^ All these were tested in both OBS and Videokeeper2, multiple PC restarts

So I have HDMI and composite working perfectly but not component. Has anyone come across this before? Anyone have any ideas?

[Coestar]

I just got my xcapture unit as a christmas present to myself.

I've come up with a curious and infuriating problem when trying it out.
(testing on z77, i5 3570, 8GB RAM PC)

-> I downloaded the latest 1.1.0.160 drivers from Micomsoft.
-> Tried plugging in my PS2 via component, constant cutouts
-> Tried different USB3.0 ports, same result
-> Tried HDMI from another PC, works flawlessly
-> Tried different component to dterminal adapter, still constant cutouts
-> Tried GC via component, same constant cutouts
-> Tried GC via composite, works flawlessly

^^ All these were tested in both OBS and Videokeeper2, multiple PC restarts

So I have HDMI and composite working perfectly but not component. Has anyone come across this before? Anyone have any ideas?

Try an earlier driver. The latest driver has given me the same problems you are describing, but it was working fine before. Honestly, you may want to return it and get something else. I've been extremely disappointed with it.

[Whitesnake]

Has anyone tried capturing a 3DO with the XCAPTURE-1 or USB3HDCAP?

I'm having trouble getting AmaRecTV to give me 60fps in the viewscreen, any ideas?



Other sources tell me the 3DO outputs 480i if that is the case does that mean the capture card is incorrectly picking up the video signal?

[system11]

So I'm confused, which of these devices supports standard RGB + composite sync (not sync over composite video) - all of them? None of them?

I'm trying to put together stuff to capture from PCBs, so there's no composite within a mile, it's RGBS.

[Fudoh]

all of them.

[FinalBaton]

So, I just got my USB3HDCAP.

I've made my homework by reading a lot in this thread, but I still have some interrogations.
So I'll start by listing what I think I understood right (so that you guys correct me if I'm wrong), followed by some questions.




What I've gathered so far :

- I need to chose the 720x240 or 640x240 @ 60fps resolutions and check the "line-doubling" option for 240p games.

- "Lanczos" or whatever the name of that codec is should be avoided because even though it offers the best quality(lossless), it makes for gigantic files. I should instead go for the "x264" codec (please give me that exact codec's name under AmarecTV), wich should give great quality still, and much smaller-sized files.




Now for the questions :


- Should I bother installing the CDrom's (that comes with the USB3HDCAP) content? Or should I skip that and download a particular driver?

- If so : wich driver should I download (I have Windows 7)? I've seen many drivers versions mentionned, but I don't think I saw a clear consensus

- AmarecTV Color space : Should I capture in RGB, or should I use YUV to reduce the files' sizes (does YUV even reduce files sizes by that much?) And what about 24-bit vs 32-bit color depth? What do you recommend?

- Does AmarecTV gives better quality recordings (for files relatively decently compressed) than OBS? or is this aspect only a result of the driver and codec, and not related at all to the program?

- Wich file format should I chose?

- I saw someone on another forum reccommend to , under ''Settings > Output > Recording'' select a lossy encoder (say x264), then 'CPU Usage : Ultra Fast', and a high bitrate. what do you guys think of that?



Feel free to also give me any n00b-friendly tips that you feel will make it easier for me to set this up and get started recording. Note that I only have a little bit of experience recording game footage (with OBS, recording fightcade with the 'window capture' function).
I should also mention that I plan to record, not live-stream. And input-lag is not a concern since I'm plugged into my crt first, and then use the crt's passthrough to feed the USB3HDCAP.



EDIT : In the meantime I went ahead with the included CD and OBS. With these settings I get a squished image. Anybody know where is the line doubling option in OBS? I can't find it.
I selected 720x480, as 720x240 just didn't make sense, the image appeared just as squished but took the whole height of the frame, leaving no room for the missing bottom half of the image.
Note that I am using a 15kHz RGB signal through the VGA to DVI adapter

[FinalBaton]

Any idea why my capture above takes only half the space?