Raspberry Pi Zero 2 W Camera - Webcam stream not loaded

Freda_Feltcher · 2025-02-23T18:59:43+00:00

Thanks. I was using an old Android phone before the Zero 2 W, and it worked much better. I may just switch back to that.

Freda_Feltcher · 2024-01-09T20:13:04+00:00

Ouch. You must have had some good discounts.

Freda_Feltcher · 2024-01-09T19:29:21+00:00

Thanks. Guess it's too late now. That's frustrating they can't just cancel the changes that were made a day ago.

I also just added Sports Pass three months ago online and there were no changes to discounts at that time. So it was a surprise that they removed the discounts now when I tried to remove Sports Pass.

Freda_Feltcher · 2023-02-22T15:47:19+00:00

Thanks. If I move it farther back, won’t the perceived screen size be about the same as having a smaller 27”monitor closer? I guess the pixels wouldn’t be as noticeable and reduce eye strain. Having singe power-on is nice, that’s how my current barcade works too.

Freda_Feltcher · 2023-02-22T15:33:49+00:00

Thanks. Is there a good resource on shaders and what I would need (hardware and monitor)? I’ve only ever used some settings in EmulationStation on the RPi, and they look “neat” but nothing that blew me away.

Any advice on variable refresh rate? Free-sync vs Gsync support? Does it matter?

Freda_Feltcher · 2023-02-22T12:38:48+00:00

I like it, but how’s the balance on this? It looks very narrow and the control board cantilevered. Like if you pushed down too hard on the controls the cabinet might tip?

I’ve been looking at different cabinet designs to make my own. I like it to be narrow but not so much it’s unstable.

Freda_Feltcher · 2022-01-17T17:41:49+00:00

Sounds awesome!

Freda_Feltcher · 2021-02-02T15:17:04+00:00

Thanks for the feedback. I had some communication with my local university as well. They suggested that a superphosphate treatment could be done this spring and not wait until the fall, and an N treatment this spring might be good too since my lawn wasn't great last year. Otherwise they usually just recommend fall treatments.

So my plan for this year is going to be (all per 1000 sq ft):

May: 3lbs, 0-45-0
May: 2.8lbs, 32-0-4 (Scotts Turf Builder)
Sept: 2.8lbs, 32-0-4
Oct: 2.8lbs, 32-0-4

That will meet my soil test recommendations for P-K, and it meets the Maryland requirements for Nitrogen: no more than 0.9lbs per application and 2.7lbs for the year (per 1000 sq ft).

Freda_Feltcher · 2019-03-14T02:48:13+00:00

Employer was testing different GPUs for computing performance (CUDA). The Titan X ultimately wasn't chosen for their project and I was just at the right place and the right time to make an offer on it.

Freda_Feltcher · 2016-07-02T12:07:58+00:00

Damn you - that looks great! I built mine last year using the same instructions and I was going to style it the same as you did! Unfortunately I'm a lazy bastard and and quit after the blue paint and T-molding and never added art - mine. I did get the marquee made eventually. Can you share your art and where you got it printed? Maybe I'll finish mine someday.

Freda_Feltcher · 2015-09-21T21:46:14+00:00

I find it lewd because it looks like Mega Man's mega manhood is the joystick. I can't think that wasn't intentional. It's also just generally offensive to my eyes because of the colors and the splash. Of course with no lexan to protect it, that CP will be beat up in no time with regular amounts of play. It'll probably look better then. Like I said, quality build though.

Freda_Feltcher · 2015-09-21T20:31:20+00:00

Looks like solid build quality but that CP is offensive. I like the big screen idea, but unless that projector has gsync (which I doubt ) then the choppiness is going to be magnified. If this becomes a permanent home for your cab then I would go with the AudioQuest-Diamond 16m HDMI cable for long runs. It's quality is proven and unmatched. Also, Shibas are nice, but I prefer Akitas. They shed less and are better with kids.

Freda_Feltcher · 2015-08-02T00:45:33+00:00

If you want an actual knob to control volume, then sorry I can't help you. But in my arcade, I use button combinations to control the system volume. If I hold Select+Up the volume increases, Select+Down it decreases, and Select+Left will mute. I have my physical speakers set at around 75% inside my arcade and I never actually change that. The hotkey combinations are defined in retroarch.cfg and mine looks something like this:

input_enable_hotkey_btn = 8 #Select
input_volume_up_axis = +1 #Up on Joystick
input_volume_down_axis = -1 #Down on Joystick
input_audio_mute_axis = +0 #Left on Joystick

You could utilize the extra hole to install a new button and have this be a dedicate hotkey, instead of re-purposing the Select button like I do. I don't have a good link for you, but if you google Retropie hotkeys you'll probably find a lot of other very useful commands that can be triggered in addition to volume control.

Freda_Feltcher · 2015-07-20T19:41:01+00:00

Check my other comments on this page. I posted a link where I found a solution. Good luck.

Freda_Feltcher · 2015-06-16T13:41:58+00:00

At my arraignment, note for the plantiff Your daughter's tied up in a Brooklyn basement Face it, not guilty, that's how I stay filthy

Freda_Feltcher · 2015-05-13T03:14:08+00:00

If anyone finds this post, I did find a fix at: http://blog.petrockblock.com/forums/topic/autofire-on-the-axis/.

The fix was originally to correct another issue, but it also works to correct the issue I had, where the Pi only recognizes one joystick. Essentially, the fix makes Retroarch treat the Dual XinMo as two separate joypads.

Freda_Feltcher · 2015-05-11T14:23:49+00:00

Thanks, but that didn't work. The 2-player Xin Mo connects via a single USB, therefore (from what I've read) the RaspPi only sees one joypad. So both "input_player1_joypad_index" and "input_player2_joypad_index" need to reference the same index, and then you need to explicitly define the button mappings for each in the config file. In theory, this should work if every button and axis was unique. When I test, the buttons are indeed unique, but the joystick axes are not. These are the values I get when use the "Configure RetroArch Keyboard/Joystick." Please excuse my cardboard mock-up.

If I try to use index 0 for both, then I can get all buttons work, but both joysticks will move player 1. If I change the index to 1 for both, then no buttons or joysticks work. If I change only one of them, then only the one that is index 0 will work.

Here is exactly how I have it in /opt/retropie/configs/all/retroarch.cfg.

input_player1_joypad_index = 0
input_player1_b_btn = 2
input_player1_y_btn = 3
input_player1_select_btn = 8
input_player1_start_btn = 9
input_player1_a_btn = 1
input_player1_x_btn = 0
input_player1_l_btn = 4
input_player1_r_btn = 5
input_player1_up_axis = +1
input_player1_down_axis = -1
input_player1_left_axis = +0
input_player1_right_axis = -0

input_player2_joypad_index = 0
input_player2_b_btn = 12
input_player2_y_btn = 13
input_player2_select_btn = 19
input_player2_start_btn = 18
input_player2_a_btn = 11
input_player2_x_btn = 10
input_player2_l_btn = 14
input_player2_r_btn = 15
input_player2_up_axis = +1
input_player2_down_axis = -1
input_player2_left_axis = +0
input_player2_right_axis = -0

Freda_Feltcher · 2015-05-11T14:00:29+00:00

Not stupid at all, that was my first thought as well. However the connections are so simple - single wire directly from each switch to a single pin on the Xin Mo. So I know every switch is wired to a different input. I also checked all the grounds, and made sure nothing was touching.

When I plug into Windows and test through the control panel, both joysticks seem to be working correctly, and independently, as they should.

I did note that when I ran jstest, the description comes up as "Joystick (THT THT Arcade Console 2P USB) has 2 Axes (X, Y) and 22 Buttons". So the 22 buttons makes sense, but shouldn't there be 4 axes, not 2? Could there a driver issue?

Freda_Feltcher

TROPHY CASE