MIDI

Smooth Switching to my iSight?

joshuarule's picture

First day with QC and it's already 4:40am!

I am trying to make something that triggers video clips and switches to my isight triggered by midi. The problem I have is that when the midi note enables the isight to capture it takes a second for the camera to turn on.

Can anyone point me in a direction of where to learn about keeping the isight camera always on/capturing and then only displaying it on screen when it's triggered via midi.

right now I have a simple midi note to billboard enable to turn on...with the video input sending to the billboard image.

Thanks Josh

MIDITools Global Input Midi Note Follower off by one issue

Summary: Provide a descriptive summary of the issue.

Steps to Reproduce: I'm only seeing this when using Ableton's Feedback midi notes, so I'm afraid this will be hard to reproduce if you don't have Ableton.

When using MIDI feedback feature, Ableton sends the same note with three different velocities to show the state of the clip that is playing: 0 126, and 127.

Global Input MIDI note Follower is not catching the 127 velocity. It just skips from 0 to 126 and back and forth. MIDI Monitor is displaying the 127 velocity as expected, and I can see the 127 when using the regular MIDI Note receiver.

What's odd is when I send a standard MIDI note from ableton with velocity of 127, the Global Follower is working.

Expected Results: I expect to see Velocity of 127 coming out when played.

Actual Results:

Global Input MIDI note Follower is not catching the 127 velocity. It just skips from 0 to 126 and back and forth.

Regression: I'm using Snow Leopard 64 bit, and I've tried a few different versions of MIDI tools all with the same result.

Notes: Provide additional information, such as references to related problems, workarounds and relevant attachments.

Right now I'm using the Built In MIDI note reciever, but it's a pain because I have to route each individual note. It'd be swell to get this working properly.

Internal case: https://b33p.net/kosada/node/3066

OSC receiver not working

djfil's picture

quartz composer OSC receiver has stopped working. It worked before. With OSCulator everything is fine. I get no error messages from QC. In console i get:

3/16/10 4:16:38 PM Finder[231] *** Patch class "QCOSCReceiver" is not allowed in safe mode 3/16/10 4:16:38 PM Finder[231] *** : Failed instantiating patch with name "QCOSCReceiver" 3/16/10 4:16:38 PM Finder[231] *** Message from : Cannot create node of class "QCOSCReceiver" and identifier "(null)" 3/16/10 4:16:38 PM Finder[231] *** Message from : Cannot create connection from ["outputSignal" @ "OSCReceiver_2"] to ["tap" @ "Patch_1"] 3/16/10 4:16:38 PM Finder[231] *** State restoration failed on

But this is from finder, something about safe mode. I've tryed to set this options to allow OSC receiver. But without success. Also tryed qcOSC from somewhere arround here. Again unsucceess. Changed the communication port to several different. No success. Also tryed to send from within the mac from pure data and no succeess either. I have spent the last day trying to find anyone with this kind of error but no luck. Can't understand why or what.

On debug mode QC is able to receive something but i still get no reaction on screen. it prints this:

3/16/10 5:18:45 AM Quartz Composer[1756] *** Message from : Packet received on port 11000: { }

I've not done much, kineme has something to detect bad installation of packages but apparently they are all fine.I just installed camcamx and manycam. Whome weren't working but suddenly they started working. (fixed something to broke another)

From my understanding of QC i believe that the problem is on the socket read from QC. But i own a mac less than a year, and only started working with QC last month.

Can anyone help? Please! The objective was to syncronize Traktor(running on a windows machine) to Coge(running on this mac).

BTW platform: OSX 10.5.8 QC Version 3.0 (63) Framework Version 2.1 (106.13)

Midi Clock Sender

.lov.'s picture

Hi,

i just trying to build a midi clock signal plugin, which basically works, but not accurate. Think i missed some basic stuff about how QC works. Looks like a plugin executed only 1/60 sec intervals, and UI changes (dragging something for example) blocks the rendering.

Am i true?