More GPU actors are coming. This is being worked on heavily.
I will enter a new feature request for the extended speed range for QT.
NOTE: I have gotten around this limitation by scrubbing the position dynamically (using some calculations to figure out speed settings), requires testing since not all codecs respond well to scrubbing.
I am using Edge Blend. I usually do it this kind of effect with add Alpha Channel, GaussianBlur & Shapes.
However, some of my patches are using 40-50 projector actors, so it just takes time. Also this way makes my computer slow.
I do not use the mapper.(I do not know how to make edge softer with it...)
I know that a new version of Isadora is under the hood.
I need to say another time to everybody involved in the Isadora development that outside english speaking countries, we NEED to output letters outside the ASCII range (like é,è,à,ç,ô in France ü, ö in Germany etc.).
I experimented all the way to go around this limitation:
– QuickTime text worked well, but not implemented in AV foundation
– Quartz Composer worked well but QC patch no more efficient with GPU
– Parsing in Max/Msp not possible because OSC accept only ASCII
– Parsing in Processing not possible because Syphon doesn't accept text (I don't know why)
Here in France, Isadora is concurrenced by Millumin, less possibilities but easier to use. One of my argument to "sale" Isadora (as video creator and teacher) is the flexibility but without proper text handling, it's more difficult to do.
So please, a way to output UTF-8 (and perhaps UTF-16 for asiatic language) is a necessity.
All the best,
Just stepping in here as 'moderator' for a moment....
We are happy forum here and we will do everything we can to keep it that way.
We have users from all over the globe, English is not often their first, or even second language, not only this; writing, emails, and other virtual forms of communication are often very different. It's very easy to misinterpret text on a screen too.
I don't think @[Mikhail](http://troikatronix.com/troikatronixforum/profile/8038/Mikhail) meant any harm by using bold and underlinings things. Some people do use bold to represent shouting - but I don't think this is the case. He was just trying to highlight the key areas in the discussion. But I can see how this may have come across to some.
Anyway, It looks like you have moved on from this now anyway, so I will say no more. I just wanted to make it clear that the team here had spotted the discussion and I had been keeping an eye on it.
No need for anyone to reply to this or apologise any further - it's all cool :)
@j[hoepffner](/troikatronixforum/profile/15/jhoepffner) - not disputing any of that, it’s just (imo) a weigh-up of how much should be done in Isadora, and what should be kept out... where does Izzy specialise. A balance needs keeping to prevent it spiralling into a fully-fledged IDE rather than a visual construction kit (so-to-speak). Seen this with rFactor / ISI development - when you’re talking a small team of devs it can be easy for them to be stretched too thinly, and quality can suffer... that’s my only concern.
Ask and ye shall receive. (Well, sometimes, when I've got a quiet morning and the request only requires a couple of hours to invent.)
See here: http://troikatronix.com/troikatronixforum/discussion/2601/new-get-scene-name-actors#latest
Not doubting your issues chuck - just reassuring you that it’s doable on your hardware, so doubtful switching from Mac to Mac will make any real difference, and that the issue must be software-based somewhere along the line.
Am not sure of difference regarding Syphon sending video vs generated graphics - a frame from the frame buffer is a frame from the frame buffer (?) - beyond my knowledge there! Airbeam is firing over 4x streams of H264-encoded video from iPhone cameras live, and I also tend to have a HDMI Camera hooked up via Black Magic Intensity Shuttle, but don’t really ferry it’s signal around by Syphon.
I _do_ know there are differences in the Syphon output of different apps. e.g.: If I use native Syphon receivers I occasionally have issues receiving streams from processing (just show up all white), and end up resorting to the FFGL Syphon Receiver plugin from http://syphon.v002.info - could be worth a try to see if there’s a difference for you between running the Isadora native Syphon receiver and FFGL Syphon receiver... both co-exist happily in Isadora and can be used simultaneously in a patch for comparisons.
MagicMusicVisuals = https://magicmusicvisuals.com, which I mainly use for running custom GLSL shaders into Isadora patches, with the shaders’ animated properties triggered via frequency-gated multi-audio input channels coming from MOTU 828MkII & 8PRE (firewire) & Leap/Kinect motion data via OSC.