Hi, i mapped a large array of 6 layers x 48 columns with some midi note on" provided by IAC bus and also controllers. when clicking on any clip, just a solid color, the cpu go from 40% to 150% Is it normal that midi mapping is so Cpu hungry ??? Avenue 7.0.5 MacBook Pro (Retina, 15-inch, Mid 2015) AM...

Ahah thanks for your post.

That's OK, I made a openframework app to generate all the midi mapping in XML on all clips columns and all what I needed to map in some plugins.

Sure i am the only one to need this feature.

Midi over network timing is much more efficient and accurate than osc

Hi all,
Should be nice if during the midi mapping process, we could select the item target thru osc command.
It will allow to quickly automate the midi mapping of a bunch of clips, faders (and so on) very fast.

Arvol wrote: ↑

Wed Nov 20, 2019 06:58

Good catch

What plugins have you made? Just for OSX?

I made a serie of plugins, quite simple, 2d transform, smoothers and particles customized for my needs in visualsystem.org, yes just os x

Thank you very much.
In my case, the problem came from the double uniqueid used in two different custom plugins.
during the composition being opened, it seemed that avenue stop the "open process" when first occurence of another plugin with same uniqueid appeared.

thanks

Great ! really, thanks for the advice.

For Avenue 7, i rewrote all my ffgl plugins for 64 bits in xcode.

And yes, you're right, i did a mistake, and one of my plugins had the same uniqueid than another.

it is working well now. I retrieve all the columns of my compositions.

thanks

Hi all, i tried importing my version 6.1.3 compositions to Avenue 7 demo version. I have 31 columns in one deck. When i use the function in the menu to import avenue 6 compositions, i can only see 8 columns no more. I read in a text editor the .avc renamed as .xml, and i can see that the composition...

Anyone knows how to load a picture from disk via a file path, and load it into a texture.
Or any ffgl filling a texture from cpu generated image ?

Ok, but is it still possible to simply load an image (or fill an array in cpu side) and fill a texture with it, like a generator does?

Hi all !

I couldn't figure out how to write to a texture using the current FFGL 2.0 sdk for resolume.

Anybody has an example of cpu generated picture sent to "pGL->inputTextures[ 0 ]" in the processOpenGl method ?

all the best