alexmitchellmus's picture

@alexmitchellmus

I made a donation to Vuo.

Compositions

3 years ago
3 years ago
4 years ago
4 years ago
alexmitchellmus's picture
alexmitchellmus commented on Paul's Discussion, “Equirectangular camera

Paul, the reason for forcing 2:1 is that that is the official format aspect ratio.

Personally I don't mind either way, as it can be changed to a degree afterwards. Also, equirectangular isn't really the best format for storage of 360°. As you would be aware the poles become distorted, and have excessive resolution, with heavy antialiasing.

alexmitchellmus's picture

IIRC dual fisheye will always have errors around the perimeter. Hence the need to go with a 90° cubemap rendering.

I think this is what the current Vuo2 code does, but I haven't had time to check.

alexmitchellmus's picture

Ardour is a GPL DAW that has ability to split buffers. Hence why all LV2 plugins always need to know the buffer size (not the sample rate, that's set).

This allows as you said, a buffer to work with timming that are between buffers.

I don't know how this would work in a live context, as Vuo would need to know in advanced where when to split the buffer. Which would mean that all incoming data (MIDI/OSC/controll) would need to be delayed by one buffer cycle.

I think that would be ok, given the benefit it would bring.

alexmitchellmus's picture

Yes it is. It may also be interesting to instead of having a buffer size per node, to allow audio nodes to split their buffer when a new event occurs.

This would mean there would be a Vuo buffer preference, (where we set the value), and internally the buffer can't go longer than that value.

IIRC both VST & LV2 pass the buffer size to the audio function. Thus allowing those plugins to compute different buffer sizes on the fly.

Pages