norichan

2011-10-16 01:09:56 am

Stand: Devil's Call in your Heart

now with the second beta, i could test the program sucessfully.

it worked good. all i had to do was install the program, plug the easy cap, wait for it to install, open the program, set the capture file and the video input (s-video) and start capturing.
the captured footage looks good so far. i made a sample after fiddling around with some stuff.

the program also hanged for a bit when i closed it but i bet that has more to do with me having many things open at the same time lol.

Attachment:

sample.mp4

nate

2011-10-16 01:56:47 am

awesome. thanks for the feedback.

DJS

2011-10-16 02:14:36 am

torch slug since 2006

nate's avatars fit so good to his posts Smiley

also, is it possible for you to program an driver that lets you record pal-60, even though the device does not support it? I was thinking because NTSC got the correct resolution and framerate, and pal-50 has the correct colors. Is it possible to merge them together?

nate

2011-10-16 02:20:36 am

yeah, i may already have. i just need someone to test it.

Tranquilite

Edit history:

Tranquilite: 2011-10-16 03:17:28 am

Tranquilite: 2011-10-16 03:09:49 am

Tranquilite: 2011-10-16 03:09:23 am

2011-10-16 03:08:20 am

All right, so nori chan seems to be working for me now. After I changed the driver, I had to unplug and then replug the easycap before norichan started working properly... I probably should have done so earlier, but I was in a bit of a rush.

Also, In order to try testing pal-60, I forced my Wii to boot Super Mario Galaxy in PAL60 mode, and while the picture (minus color) showed up fine in NTSC capture mode, I was unable to get any kind of picture whatsoever in PAL mode. My LCD monitor seems to view said PAL60 signal just fine. While it would be nice to get somebody else to verify this, I'm pretty sure nori is not handling PAL60 right.

In case this matters, I was using composite inputs, I haven't tried svideo yet, because I seem to have misplaced my svideo cables.

Mute Audio Preview still crashes the program though.

nate

2011-10-16 03:35:25 am

bleh ... that crash is going to be hard to debug. the cause may be further up inside the os. if you want to you can pm me the contents of the crash report the os generates.

thanks for testing pal-60. it sounds like i will need to make a dedicated pal-60 mode since autodetect is apparently either not very good or based on the framerate/number of lines and not the actual color signal. it'll just be a clone of the ntsc mode except with forced pal color. that along with disabling the crappy easycap audio will be beta 3. hopefully i can finish it tomorrow but hard to say right now.

DJS

Edit history:

DJS: 2011-10-16 03:54:20 am

DJS: 2011-10-16 03:52:44 am

2011-10-16 03:50:27 am

torch slug since 2006

Quote from nate:

yeah, i may already have. i just need someone to test it.

I would test it, unfortunately your program does not support my trident vc500... If you get some good easycaps for sale later; ill might buy one. I would want pal-60 support though, whether its software or hardware based.

Tranquilite: I just want to say that pal on s-video cables (for the wii) just gives black/flashing image. The wii wont output pal correctly to s-video. I think its the same thing about ntsc + rgb/scart. Something silly in nintendos programming.

DJGrenola

Edit history:

DJGrenola: 2011-10-16 05:03:52 am

2011-10-16 05:03:26 am

guffaw

Quote from DJS:

Tranquilite: I just want to say that pal on s-video cables (for the wii) just gives black/flashing image. The wii wont output pal correctly to s-video. I think its the same thing about ntsc + rgb/scart. Something silly in nintendos programming.

It's nothing to do with programming. It's because the A/V connector uses the same pins for s-video in NTSC regions as it does for RGB in PAL regions. Whether your wii has RGB out or s-video out depends on its region. http://pinouts.ru/Game/nintendo_wii_av_pinout.shtml

DJS

2011-10-16 05:51:37 am

torch slug since 2006

Quote from DJGrenola:

Quote from DJS:

Tranquilite: I just want to say that pal on s-video cables (for the wii) just gives black/flashing image. The wii wont output pal correctly to s-video. I think its the same thing about ntsc + rgb/scart. Something silly in nintendos programming.

It's nothing to do with programming. It's because the A/V connector uses the same pins for s-video in NTSC regions as it does for RGB in PAL regions. Whether your wii has RGB out or s-video out depends on its region. http://pinouts.ru/Game/nintendo_wii_av_pinout.shtml

Eh? I have a pal wii, that I tried using S-video cables on, when it was running in pal mode. The s-video didnt work, it was just black, and sometimes it flickered. (composite was fine). Then i softmodded my wii and changed region of it to NTSC, so it runs in NTSC, and now the S-video works excellent.
I havent tried rgb/scart yet though.

DJGrenola

2011-10-16 05:53:13 am

guffaw

Quote from DJS:

Eh? I have a pal wii, that I tried using S-video cables on, when it was running in pal mode. The s-video didnt work, it was just black, and sometimes it flickered. (composite was fine). Then i softmodded my wii and changed region of it to NTSC, so it runs in NTSC, and now the S-video works excellent.
I havent tried rgb/scart yet though.

really? never mind then.

ExtremeYoshiFan

Edit history:

ExtremeYoshiFan: 2011-10-16 11:45:59 am

2011-10-16 09:00:57 am

Hmm, I've played around with the Wii Menu before, If I could get a good PAL config file and an NTSC config file I could take a look, I'm sure it is just some stupid setting in the config file.

I don't remember what all is in it, so I would find it wise that anyone that could grab one for me would skim through it to make sure there is no MAC address or other important or sensitive information.

If S-Video out truly isn't an option due to something lower level, I know for a fact that Neogamma can force a graphics settings, so maybe if you forced NTSC mode you could use S-Video(this will not affect gameplay, can somebody with a softmodded PAL wii test this for me?).

The only issue with this however, is that you'd need a TV that accepts NTSC to output to, as well as an S-Video splitter.

nate

2011-10-16 02:42:37 pm

ok, updated the first post with beta 3. there is now a pal-60 menu option. please give it a try. i didn't have time yet to look at the audio crash unfortunately.

Tranquilite

Edit history:

Tranquilite: 2011-10-16 05:34:38 pm

2011-10-16 05:20:58 pm

Nori is now has color when I force PAL60 on Super Mario Galaxy 2. I guess that means it's working properly.

Also, as for the discussion about Wii's. On the hardware side of things, all Wii's are exactly the same. All region related things are determined purely by which system menu is installed. As for the issues with video mode, I'm certain that it is because of the way the video hardware works. According to the pinout listed earlier, pins 7, 9 and 11 are used for svideo, rgb, and component YPbPr outputs. While component YPbPr output is determined based on whether pin 8/10 is shorted with the other pins, there is no physical way to determine if svideo or RGB should be output, which probably means that the video hardware automatically selects what kind of output is being used based on the video signal, so when you are running PAL formats RGB will be used, and when you are using NTSC formats, svideo will be outputted.

Since the easycap only has composite and svideo inputs, I guess this means that at least for the case of the Wii, you will only be able to capture PAL60 using composite.

Nori is now has color when I force PAL60 on Super Mario Galaxy 2. I guess that means it's working properly.

Also, as for the discussion about Wii's. On the hardware side of things, all Wii's are exactly the same. All region related things are determined purely by which system menu is installed. As for the issues with video mode, I'm certain that it is because of the way the video hardware works. According to the pinout listed earlier, pins 7, 9 and 11 are used for svideo, rgb, and component YPbPr outputs. While component YPbPr output is determined based on whether pin 8/10 is shorted with the other pins, there is no physical way to determine if svideo or RGB should be output, which probably means that the video hardware automatically selects what kind of output is being used based on the video signal, so when you are running PAL formats RGB will be used, and when you are using NTSC formats, svideo will be outputted.

Since the easycap only has composite and svideo inputs, I guess this means that at least for the case of the Wii, you will only be able to capture PAL60 using composite.

nate

Edit history:

nate: 2011-10-16 05:39:50 pm

2011-10-16 05:39:32 pm

svideo is worthless for pal anyway afaik. the problem it was meant to solve does not exist.

i'm curious to see some test video of pal60.

Tranquilite

2011-10-16 05:53:10 pm

Allright, I captured some PAL60 footage, do you want the raw huffyuv, or is it fine if i send it through anri first? I have a pretty bad upload speed, and the 36 second capture is 351 megs.

nate

Edit history:

nate: 2011-10-16 05:54:53 pm

2011-10-16 05:53:57 pm

anri-encoded is fine.

i'm just trying to make sure i didn't accidentally turn on any weird filters along with the 4.43 or whatever mhz chrominance subcarrier setting in that register.

Tranquilite

2011-10-16 06:11:09 pm

Ok, here you go, things looks pretty good to me.

Attachment:

smg2pal60test_HQ.mp4

nate

2011-10-16 06:12:17 pm

yeah looks fantastic. thanks.

Kryal

2011-10-19 12:25:57 pm

from red to blue

inb4i'mdumb

Tranquilite

Edit history:

Tranquilite: 2011-10-19 12:34:23 pm

2011-10-19 12:34:14 pm

Your problem should fall somewhere in here:

Quote from nate:

note that the driver norichan installs under windows (which comes from my day job - that's why it's not called norichan) is incompatible with the common "stk1150" and "stk1160" easycap drivers. you will need to uninstall those before you install norichan. unfortunately the uninstaller doesn't uninstall the driver and afaik it's not possible under xp to get rid of it without hacking the registry. under vista and 7 you should be able to go into device manager, right click on the easycap, go to uninstall, and check "delete the driver". alternatively, you can try plugging the easycap into a new/different usb port than you've plugged it into in the past. windows will prompt to install the driver and you should have a choice at that point if you've installed norichan. also note that uninstalling norichan does not yet uninstall its driver (i'm working on that), so you will need to repeat the same procedure if you wish to switch back to the 1150 or 1160 driver for that particular usb port.

If you have done that already, try unplugging/replugging your easycap, or try plugging it into a different port.

Your problem should fall somewhere in here:

[quote="nate"]note that the driver norichan installs under windows (which comes from my day job - that's why it's not called norichan) is incompatible with the common "stk1150" and "stk1160" easycap drivers. you will need to uninstall those before you install norichan. unfortunately the uninstaller doesn't uninstall the driver and afaik it's not possible under xp to get rid of it without hacking the registry. under vista and 7 you should be able to go into device manager, right click on the easycap, go to uninstall, and check "delete the driver". alternatively, you can try plugging the easycap into a new/different usb port than you've plugged it into in the past. windows will prompt to install the driver and you should have a choice at that point if you've installed norichan. also note that uninstalling norichan does not yet uninstall its driver (i'm working on that), so you will need to repeat the same procedure if you wish to switch back to the 1150 or 1160 driver for that particular usb port.[/quote]

If you have done that already, try unplugging/replugging your easycap, or try plugging it into a different port.

Kryal

Edit history:

Kryal: 2011-10-19 01:44:07 pm

2011-10-19 12:54:07 pm

from red to blue

still getting the same error :l

edit: ok my ezcap isn't supported, lol

Reaif

Edit history:

Reaif: 2011-10-19 08:14:15 pm

Reaif: 2011-10-19 08:11:39 pm

2011-10-19 07:07:11 pm

This idea is awesome, Nate! I went ahead and downloaded and installed Norichan. So far, it looks like an amazing program. As far as that "Mute audio preview" error goes, the same one that Tranquilite experienced is happening to me as well. On the plus side however, I grabbed a bunch of debug information!

Not sure if this will be useful or not, but I went ahead and attached the files here. Also, I am using Windows 7 Professional 64-bit with SP1.

Files:
Event Viewer - Error.txt | This is the error text that was given by the event viewer.
Event Viewer - Information.txt | This is the information text that was given by the event viewer.
WER9090.tmp.appcompat.txt | A complimentary file that was mentioned in some of the dialogue.
WER7C34.tmp.WERInternalMetadata.xml | Another complimentary file that was mentioned in some of the dialogue.
Also, there was a dump file that was generated. It was a little large as a forum attachment, so I uploaded it to my Googledocs. Enjoy! https://docs.google.com/leaf?id=0B_icQZOMhj2-MjYwNzJmZDUtMDY4Zi00YTdiLTk1ZmEtODVmNzI2MzJlZTFi&hl=en_US

EDIT: I suppose I should post some test video. Here are two files for a retrospect comparison:
Norichan with svideo: https://docs.google.com/leaf?id=0B_icQZOMhj2-M2JjMDc3YWEtOGE2NC00ZDZlLThmYTItZGUyNzNkMmRkZWY0&hl=en_US
Old driver with composite: https://docs.google.com/leaf?id=0B_icQZOMhj2-MmM2MzIyYWQtYzM2Ny00NTllLWJjODgtNWQ3ODQ4YjU2M2Zj&hl=en_US

Aren't the differences so stark? You do great things, Nate. Can't wait for version 1.0

This idea is awesome, Nate! I went ahead and downloaded and installed Norichan. So far, it looks like an amazing program. As far as that "Mute audio preview" error goes, the same one that Tranquilite experienced is happening to me as well. On the plus side however, I grabbed a bunch of debug information!

Not sure if this will be useful or not, but I went ahead and attached the files here. Also, I am using Windows 7 Professional 64-bit with SP1.

Files:
Event Viewer - Error.txt | This is the error text that was given by the event viewer.
Event Viewer - Information.txt | This is the information text that was given by the event viewer.
WER9090.tmp.appcompat.txt | A complimentary file that was mentioned in some of the dialogue.
WER7C34.tmp.WERInternalMetadata.xml | Another complimentary file that was mentioned in some of the dialogue.
Also, there was a dump file that was generated. It was a little large as a forum attachment, so I uploaded it to my Googledocs. Enjoy! https://docs.google.com/leaf?id=0B_icQZOMhj2-MjYwNzJmZDUtMDY4Zi00YTdiLTk1ZmEtODVmNzI2MzJlZTFi&hl=en_US

EDIT: I suppose I should post some test video. Here are two files for a retrospect comparison:
Norichan with svideo: https://docs.google.com/leaf?id=0B_icQZOMhj2-M2JjMDc3YWEtOGE2NC00ZDZlLThmYTItZGUyNzNkMmRkZWY0&hl=en_US
Old driver with composite: https://docs.google.com/leaf?id=0B_icQZOMhj2-MmM2MzIyYWQtYzM2Ny00NTllLWJjODgtNWQ3ODQ4YjU2M2Zj&hl=en_US

Aren't the differences so stark? You do great things, Nate. Can't wait for version 1.0

Attachments:

Event Viewer - Error.txt

Event Viewer - Information.txt

WER7C34.tmp.WERInternalMetadata.xml

WER9090.tmp.appcompat.txt

nate

2011-10-19 08:33:54 pm

ok well now i feel bad for not checking this earlier ... i just totally changed how mute audio works so give beta 4 in the first post a try and let me know if it fixes it. if not i will have to try yet another thing.

also new in this version is a display menu to pick between opengl (the default) and an unaccelerated display. theoretically this should be better for certain screen capture programs to lock onto (but it will use more cpu). let me know. thanks.

Reaif

Edit history:

Reaif: 2011-10-19 09:18:27 pm

Reaif: 2011-10-19 09:12:07 pm

Reaif: 2011-10-19 09:10:36 pm

2011-10-19 09:03:38 pm

Lol. It isn't a big deal. It wasn't any trouble to get that info.

Anyway, after installing beta 4, this is what I have noticed...

I haven't been able to tell a difference between using opengl vs no acceleration when it comes to using scfh. When locking on to the window, it still shows the white background behind the video. Just using an area selection there works, same as it used to.

The mute option works quite well. I tested capturing with the audio preview muted and the resulting recording has great sound.

Edit: I checked the CPU usage with OpenGL and unaccelerated and here are the results:
OpenGL: Averages 25-30% cpu usage while not capturing
Unaccelerated: Averages 35-40% cpu usage while not capturing

I'm not sure if this matters, but this was done with an Intel E8400 Core2Duo @3.0ghz

EDIT 2: I know people have mentioned this before, but it truly is amazing how well those avatar graphics match up with what your posts are about.

nate

2011-10-19 09:11:53 pm

bleh ... ok. sounds like i will have to do something different with the graphicsview, maybe tearing it down and rebuilding it or something. anyway i'll download scfh so i can test this myself.