cwilms-loyalist's picture

Chris (@cwilmsloyalist)

Groups

  • Vuo Founder

Compositions

cwilms-loyalist's picture

You can right click on any input that has been previously used for a specific data type and select "Revert to Generic Data Type" to make it able to accept different data types again.

Also if you left click on the input it will tell you in a pop-up window what type of data is currently assigned to it.

cwilms-loyalist's picture

I just found this.

The Logitech C920 only provides 30fps at 1080p with applications that supports H.264 directly, and can pull in the H.264 stream directly from the camera. The C920 does on-board H.264 compression, but most applications don't support pulling the compressed stream straight from the camera; instead, they have to decompress then re-compress the stream, dropping the framerate.

Does that sound right? Does VUO support H.264 camera streams?

cwilms-loyalist's picture

ok, that's still the work around then. I'll continue to do that. I get similar results to you with the frame rate more than doubling when changed in QuickTime Player.

cwilms-loyalist's picture

Barcode Issues (Specifically DataMatrix's getting read incorrectly)

Status: 

Vuo version: 

OS version: 

  • macOS 10.12

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Placed large datamatrix in front of C910 webcam
  2. Partially occlude datamatrix (or sometimes just leave it as it is)
  3. Output from datamatrix node sometimes jumps back and forth between numbers and proper reading of text.

Other notes: 

We had a few instances of the Barcode node incorrectly reading a Datamatrix and ended up displaying numbers momentarily rather than the text that it should have read. Sometimes it was briefly, sometimes it flipped back and forth between numbers and a proper reading and other times numbers were visible for a few seconds before it was read correctly and displayed text. We also had a couple of instances where it displayed numbers when it decided a wood grain was a barcode (The card holder we have the camera mounted to was made of wood). This got me thinking that because the barcode reader can read different types of barcodes perhaps before it read the datamatrix as a datamatrix that it may have incorrectly identified it as a different type of barcode and spit out the results before correctly detecting it as a datamatrix. I think a simple fix might be to add a drop down list of the type of barcode we would like the node to look for. This could prevent incorrect identifications.

I managed to snap a few pictures of two incorrect readings of the same datamatrix (one with a partially occluded datamatrix) along with the correct reading. Because it contains student information I can't post it here but could privately send them to you.

cwilms-loyalist's picture

I still get extremely low frame rates using the exact same composition from my Logitech C920 however my C910 works like a dream. Any idea why this would be?

Pages