Products > Test Equipment
EEVBlog 121GW Discussion thread
JDW:
--- Quote from: JDW on February 22, 2023, 01:10:15 am ---Just to let everyone know, the reason for all this discussion is because I am doing prep work for a YouTube video review of the 121GW. It was not given to me. I purchased it new at the end of January this year, direct from the EEVBlog store.
--- End quote ---
I just made my 121GW review video public here...
https://youtu.be/1iqURp-NsdM
Thanks to Dave and others who kindly offered me feedback in this forum over the last couple weeks, which helped in the video creation.
EEVblog:
--- Quote from: JDW on March 12, 2023, 01:22:44 pm ---I just made my 121GW review video public here...
https://youtu.be/1iqURp-NsdM
--- End quote ---
Took me a minute to realise you didn't have a green screen here!
Your lighting is amazing, what are you using? Do you have a studio tour video?
JDW:
--- Quote from: EEVblog on March 13, 2023, 05:51:30 am ---
--- Quote from: JDW on March 12, 2023, 01:22:44 pm ---I just made my 121GW review video public here...
https://youtu.be/1iqURp-NsdM
--- End quote ---
Took me a minute to realise you didn't have a green screen here!
Your lighting is amazing, what are you using? Do you have a studio tour video?
--- End quote ---
Thanks for taking a look at the video.
Instead of a green-screen, I simply have a black felt sheet hanging on a whiteboard behind me (affixed with magnets so it won't fall down). The scenes with meters used a thinner black felt sheet placed on a table. When editing the video, I crush the blacks to make the background go pretty much pure black. I do it that way because I don't have a lovely scene to put behind me for my videos. The other reason is that a pitch black background isolates me and the items shown in the video. The viewers eyes then focus on the content rather than the background.
No special lighting used. Just overhead, office-length fluorescents shooting straight down on me. I can do that because I shoot at the office after-hours. Fluorescent tubes do produce a rather diffused light though, which is nice.
For the intro and outro sections, I often put a white felt sheet on the table before me (which isn't shown in the camera frame). The white sheet reflects and defuses the overhead lighting up and at me. No other lights or reflectors used.
I shoot with a Panasonic GH5 in 4K HLG(Rec.2020) 10-bit, then convert to Rec.709 in post. (Not everyone has an HDR display, that's why.) Shooting in HLG offers the best dynamic range my camera offers, such that the highlights don't get blown out most of the time.
I don't use autofocus (just half-press to focus and then record a scene). I mostly have my camera on a tripod. I use an iPhone app to stop and start the video during the intro and outro sections. My mic is always a wired LAV with a long cable to the camera. Maybe not as good as wireless, but I never have audio cut out issues with the wired mic.
Any background music I use tends to be the free, no-attribution stuff YouTube gives to creators.
And that's about it. Sounds rather simple, but editing takes hours of time, especially for a long video like this one.
e0ne199:
--- Quote from: JDW on February 27, 2023, 01:14:16 am ---
--- Quote from: J-R on February 26, 2023, 11:19:56 pm ---
Many products have app issues over their lifetime, it is a fact of life now. Best to just move on. The 121GW actually has it pretty good, with the official Android and Windows app still available and working...
--- End quote ---
Once upon a time, most engineering software was exclusive to Windows, and there was a lot of shaming that took place when it came to engineers who preferred Apple hardware, even to the extent that many who embraced Windows called into question the engineering credentials of those who preferred the Mac. But in recent years Apple product adoption has increased to the level that even Microchip decided to make a MacOS version of MPLAB X. People in the engineering world are a tiny bit friendlier to Mac users, which is a nice break from the past. And that has been great for folks like me who are Mac and iOS users exclusively when it comes to machines I used privately at home. Even at work, I've moved my ProMate 3 from an old WinXP machine to my iMac, since MPLAB is on MacOS now.
So when I read something is considered "pretty good" ONLY BECAUSE it has "official Android and Windows apps", I am compelled to chuckle and whisper to myself — that doesn't help me! :-)
But like I said, the Meteor app exists for iOS, and that DOES help me; and I will continue to use it, along with the SD card for data logging. I am merely saying that if Meteor could be improved by way of adding a FREEZE button that freezes the currently logged waveform without frustratingly dimming the screen content, that would be outstanding for iOS users like myself (and I doubt I am the only one). And, if the release of the official iOS app's source code leads to it coming back to the App store AND offering a different set of features than Meteor, all the better!
I wish to humbly that @EEVblog for having investing the time to reply and make source code publicly available, for those (other than myself) who could possibly make productive use of it, for the good of all 121GW users.
--- End quote ---
lol in contrast to me, every single apple products are the last thing i want to touch in the world...but everyone has different preference after all ;D
btw why don't you try using VM for iOs and smuview?? if your iOs is good then it should have no problem running windows or linux VM anyway
JDW:
--- Quote from: e0ne199 on April 11, 2023, 07:20:48 pm ---lol in contrast to me, every single apple products are the last thing i want to touch in the world...but everyone has different preference after all ;D
btw why don't you try using VM for iOs and smuview?? if your iOs is good then it should have no problem running windows or linux VM anyway
--- End quote ---
iOS running Windows... Too funny.
Even if that were possible, and I assure you it is not, most Apple fans tend to share your sentiment regarding Windows: "the last thing I want to touch in the world."
:-)
But the root issue is something I demonstrated in my 121GW video. The only way to get the 200ms logging interval is to log to the 121GW's internal SD card. Sadly, when you log over BlueTooth, for reasons I don't fully understand. The logging interval is fixed, less consistent, and closer to once every half second to 1 second. Sometimes you want to log consistently and quicker than that, which is why the SD card is your only option.
If "BlueTooth logging" could be made more consistent and with the fast interval of once every 200ms like SD card logging, then that would be ideal. That discussion seems to have nothing to do with Android or iOS, because I've not heard any of you Android users say that 121GW BlueTooth logging is a consistent interval of once every 200ms, or that the interval can be changed over BlueTooth.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version