Speaking of driver updates, because my wifi speed seemed slower than normal on this tablet, I thought to force an update for its wifi adapter, and suddenly the speed is got about 10x faster.

Argh! I guess this must have gotten slower after upgrading to Windows 10 but I didn't realize how bad it was until recently. I'm guessing the driver update was mainly optimizations for Windows 10.

I'll still use the ethernet adapter for batch transferring final mocap data (my new wifi boost isn't anywhere near gigabit ethernet fast,) but at least it's reasonably fast enough for checking calibration data and other short recordings.

Since I upgraded almost all of our computers to Windows 10, I better check the hardware drivers for everything now. This could be a game changer.

G.

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

...

Yes, I was having windows lag issues too on iPi Studio and found I had to manually update my network adapter driver from the location on my computer, I guess Win 10 downloaded it, but it was not installed properly and yes my issues went away also and my processing speeds picked up considerably.

I meant to post that in the forum and forgot.

If anyone is experiencing Windows opening lag in iPi, try updating your network adapter driver to the latest version, manually if needed by searching the location of the drivers on your comp.

...

After a few forced driver updates, I finally managed to get one of the render boxes to run a Kinect v2! We're not out of the woods yet though because it was recording well below 30fps. I have some ideas for improving and stabilizing the frame rate but that may have to wait till tomorrow evening or perhaps later this weekend.

If I can get this render box fully operational with the v2, I should be able to make at least one other render box working with it too--although at this stage, I only need one more computer to test the quad-Kinect capture configuration. (And, TBH, I'm not sure we even have the space for four Kinect v2 devices.)

In any case, I'm all set to test the triple-Kinect v2 configuration this weekend.

G.

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

...

Good news, I hope everything can get up to proper functioning for you.

BTW.. you can try to minimize the window(s) on the slave machines after all configured and connected to the master, may help your frame rate, worth a shot.

...

Good idea! Thanks for the tip. I'm not exactly sure why the frame rate on the render box was slow yet. I may still need to update a driver or two for full Win 10 support. But a smaller window should certainly help regardless. Actually, now that I'm thinking about it, lowering the screen res for the graphics card might help too. Since these are just render boxes, I really don't need a very high display resolution.

There was a major Win 10 update last night that seemed like it was taking a couple of hours to complete, and I let it run on three of our machines. It was finished by this morning and all systems seemed to be running fine. Hopefully, that will have fixed something as well.

I did notice that the Windows Bluetooth panel was online again after the update. I'm not sure if this means I'll have to re-install the MotioninJoy drivers. I'll check on that tonight. I'm also looking into Better DS3 in case I ever need to re-pair my PS3 Move controllers. Better DS3 is meant to replace the MotioninJoy Tool for pairing and it doesn't require internet connection. (I think you still need MotioninJoy for the initial driver installation though; but after the installation, you only need Better DS3 for pairing. I'll know if it's applicable to what we're doing tonight.)

G.

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

...

Ok, Thanks

You can just minimize the recorder window on the slave all the way to the task bar after it's set up, it will connect through the master even if it is, no real need to see it, or watch it during recording, as long as you see the slave is recording on the master at 30 fps.

I didn't have the slow frame rate issue, and I don't know how much drop those allow before it throws an error and stops recording from the slave.

...

A few quick questions: With MiJ, are the alternative bluetooth drivers loaded only temporarily? Is the idea that you would use the DS3 Tool or Better DS3 to reload the drivers when you need them? I was wondering this when I noticed the Windows Bluetooth panel being available again this morning.

Based on comments from MiJ users on various gaming forums, I'm guessing this is the case but I wanted to confirm it here with iPi Soft users. It's not a big deal, I just want to understand the new workflow.

When poking around the MiJ tool, I thought I saw an option to permanently replace the drivers. But I guess if the drivers are loaded only temporarily, that might be the safer option.

G.

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

...

You don't even need to load the CD drivers for the ASUS BT211 dongle, the DS3 Tool will load the MiJ drivers and they will remain loaded and paired once successfully done, until you remove the dongle or switch ports, then may need to re-pair the Moves, or may not.

In Win 10, my MiJ drivers show up under xbox 360 peripherals in the device manager, very bottom.

Moves only appear in connected devices when turned on and connected properly though using the Win 10 Connected Devices window, if using the Control Panel/Devices and Printers Window like Win 7, they will only appear when connected also, not grayed out like saw in Win 7.

I don't have a listing at all in my device manager for Blue Tooth device and no icon appears in the task bar either, like you saw on Win 7.

I just plugged my USB 2.0 extension cable into a USB 3.0 port and the dongle and the Moves both stayed paired and connected fine in iPi Recorder, but the drivers wouldn't load correctly unless it was plugged into a 2.0 port, threw an error saying it was a USB 2.0 device, to plug it into a 2.0 port, so I did and they loaded.

...

Thanks for the reply! I don't think I installed the BT drivers from a CD...I was using the native Windows 10 BT drivers, but obviously that's not working for the PS3 Move controllers anyway. I was just wondering if the MiJ load was temporary since it looked like the native drivers were back, but that may have happened because of the Windows update last night. Or not. For all I know at this moment, the MiJ drivers might still be active and I simply misread what I saw this morning. Will know for sure tonight.



That's what was weird. Before I installed the MiJ drivers, the Move Controllers did show up as paired and connected in the Bluetooth panel when I turned them on, but they weren't available to Recorder. I think Win 10 was blocking access for some reason. After successfully loading the MiJ drivers, all was good though--never even had to re-pair the controllers, which I thought was odd too but I'm not complaining. :)



Thanks for this info. I had the device icon before MiJ and it went away after I installed MiJ, but then it reappeared this morning. Okay, now I'm certain this is because of the big Win update from last night. I swear, it was such a long process, you would think this latest update replaced the entire OS. Anyway, I suspect I'll need to reload the MiJ drivers now. (No biggie.)

BTW, I think I may be wrong about my BT being connected to USB 3.0 under windows 7. I had two USB 3.0 controllers and a total of four USB 3.0 ports, which I used for the three Kinect v1 devices, but it's more likely that I had the BT adapter running of one of the USB 2.0 ports and not the fourth USB 3.0 port so as to minimize interference with the Kinect capture. Never mind. :)

G

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

...

On Win 7, I was using the IOGear 4.0 adapter and the drivers from its CD, I had the IOGear 4.0 plugged into the front USB 3.0 port, but was getting sporadic drops showing up when I applied the Moves data in iPi studio, I didn't try the extension cable at that time.

I did also experience this a bit with the Asus 211 plugged directly into the rear USB 2.0 port, that's why I now use the cable to get it away from the machine and closer to the performance area, now I don't get that issue, good tip.

Also, I don't think you can have another device plugged into any other 3.0 port while running the Kinect 2, it will interfere with the bandwidth the camera needs and won't load properly, so using the BT 211 in the 2.0 port is best, I just plugged the BT211 into the front 3.0 port just to see if it connected while in this thread, but not while the Kv2 was running.

The Kv2 draws just about every ounce of the bandwidth when started up and stores it, so no other device can draw much, and if the cam can't draw enough, it will cause drop out freezing. (My experience).

...