I have the core version.
I tried with CI movie player and CI projector, movie is smoother, but there are still some drops, often where there are a lot of movements in the image... Compression settings problem? But in proRes the bit rate is constant...
Maybe you can try the lower ProRes 422 (LT) this uses 100Mbit/s instead of 147 Mbit/s. Or try PhotoJPEG between 50% and 75%. It's often dificult to say why does this codec work on the one computer and not on the other with similar specs.
craigw last edited by
Hi,Isadora isn't the only program that does this. QT 7pro is bad also. QT 10 is better but still has the problem. I've been trying to get to the bottom of this for a while because I would love to useIsadora for video playback, but I still haven't solved this problem. I've tried many different codecs even lowering the resolution all the way down to 480x320\. And still stutters in different spots of the video.I'm using a Macbook pro with a USB 3.0 SSD hard drive that I've clocked at over 200MB/s which helps the read. So with a video file that has such a small resolution and fast drive speeds I've pretty much ruled out the hard drive. So next part of the chain would move to data to processor. Is something getting dropped there with buffers or look ahead? Or possible the graphics cards?I'm still testing on different computers with different hardware setups because I love the power and ease of this program.
For best results, make sure your video footage has a fps that relates directly to both your projector/monitors refrash rate, and the target rate in isadora.
For example.. video at 30fps, Isadora target 30fps, projector refresh 60hz
or video at 30fps, Isadora target 15fps, projector refresh 60hz
or video at 25fps, Isadora target 25fps, projector refresh 75hz
this way the system won't have to double/drop any frames to compensate.
I checked every parameters : 25 fps projector set to 1080p PAL 50hz. I noticed that when export a full hd (1920x1080) instead of 1920x640 performances are better, but always some drops appears. I start to think the problem is from qt side.
I'm in the same situation as you :
I have tried several players to have perfect smooth movements in my movies.
QTPlayer, QLab, VPT5, Max/MSPJitter, Resolume, GrandVJ... And the winner is ... Modul8 : extremely fast and smooth VJ software. But no triggers, sequential actions...
Too bad that Isadora's play engine isn't as good.
But I still love it..
vanakaru last edited by
I use M8 too for the good video performance reasons and since I have 2 licenses anyway. Often conjuction with Isadora doing all triggering/interactivity and sending over MIDI to M8. If ever Modul8 would implement good MIDI control it would be great, but it does not seems to happen. So the MIDI is piece of job to set up in Modul8, but doable with the help of Isadora.I would gues however that Resolume actually will beat M8 if you use DXV encoded video.And I think CoGe would beat them all with Hap supported video codec. CoGe is very interesting app with fantastic Quartz implementations.Look at this work is rather impressive.http://www.cogevj.hu/blog/I do not have workable(expired trials) CoGe or Resolume to run tests, but I would be most interested in results.Millumin supposed to be very good timeline based player too with excellent MIDI, OSC support and to my knowledge is supporting Hap as well.
For Isadora(master)->Md8(slave) users like you, i've written an user actor to control layers of Md8 via OSC.
It's more accurate than Midi and you don't have to configure midi links.
Just leave the OSC(global) module in md8 running (the GarageCube's Library one, not the others !) on port 8002.
This actor controls one layer of md8 : movie n°, speed, position, loop, volume, opacity, X,Y position, zoom, X,Y,Z, rotation, Sat, Lum, contrast controls with auto off to spare cpu...
You can use several actors to drive several layers.
The only problem, there's no feedback from md8 about movie running or not, (not end trigger) no timecode return... So this actor only sends data.
Hope you'll find it usefull
vanakaru last edited by
Very nice. I like it a lot. Thanks!
An update of my Modul8 Layer OSC remote control Actor.
Some bug fixes, but still not perfect.
When you copy or add this actor inside a patch, you have to change the layer n° (to update osc message inside the actor).