MartinusMagneson's picture

Magneson (@MartinusMagneson)


MartinusMagneson's picture

try removing the last item in the list

MartinusMagneson's picture

Time from both display refresh and timestamp from video cause thread-split


Vuo version: 

OS version: 

  • macOS 10.15

How severely does this bug affect you?: 

●○○○ — Not much; I'm just letting you know about it.

Steps causing the bug to occur: 

This is a fun one!

  1. Use timestamp from receive live video to trigger storing frames/images to video
  2. Use smoothing timed by display refresh to trigger a finalize event based on nonzero condition (became false)
  3. Nonprofit. (or thread-split and confused computer)

Have you found a workaround?: 

Use same time-source for both smoothing and storing frames/images to video.

Other notes: 

I can e-mail you the composition if needed. Probably a fringe case, and also probably a pita to code a prevention for (although maybe something like the loop error when you don't use a hold node could work?).

MartinusMagneson's picture
Magneson commented on jersmi's Discussion, “3D audio file display

jersmi Yup, and by having 16 sequential sine waves you should have 16 upwards pointing peaks, and 16 pointing downwards. From your image it seems like you have 32 peaks pointing upwards with something in between. As this is also repeating, it will be beneficial to "zoom" in on just one half-cycle of the main sine which would be 1/32 of the full image. By the looks of the wave it seems like the frequency of the part I'd expect to be at the negative range is quite a bit higher. Can you also try with a sine wave from the link I posted with the parameters I provided? Then you can check if the composition works as intended with the expected source material to see if it is the input that differs or if it is the composition that does something funky.

MartinusMagneson's picture

I'm afraid the questions have to be answered by VDMX, and I don't think they hang much around in the Vuo forums. I would try contacting them at instead to get a response through their official support line. Facebook groups and forums can often be hard to get a response through since it's mostly community driven, and the companies won't have the time to follow every thread there scanning for- and replying to issues. I suspect you will have better luck via email :)

MartinusMagneson's picture
Magneson commented on jersmi's Discussion, “3D audio file display

Jean Marie Yup, I don't think my thoughts around how such a node should/could work is complete or backed by enough knowledge about how to deal with it yet either. I've read a bit more on the RIFF format/spec, and it gets even worse. The WAVE spec does not specify a distinct order of the chunks, meaning that you can stumble across something that place the DATA chunk before the FORMAT/FMT chunk. Not good practice, but not disallowed either.

The official spec is here: (starting on page 56 for WAVE) I however found a more informational explanation here: which is where it's mentioned that chunks doesn't need to be ordered in a specific way. It also lists a bunch of chunks to consider, which can be pretty cool for creating WAVE files from data with included cues, playlists and MIDI information.

jersmi can you cut the length of your data down to one cycle to see what's happening and post the pic of that? You have 32 sine-like peaks in there with something in between (might be because of the scaling). Dividing your data byte count by 32 should place you somewhere around one cycle depending on the stuff at the end.