keyboard/mouse is supported (along with tablets, though that functionality is untested on our end).
Published parameters are not currently supported in 1.0, and aren't likely to be supported in 1.1 (due any day now...). 1.2 or later is the target for that functionality.
I had an issue with mouse keyboard input not working when a path for an external quicktime movie was absolute. changing it to a relative path (with ~) fixed that. But the movie still does not show up.
if I refer to the movie with ~video.mov in the Movie Loader, where do I put the actual file within the Quartz Builder application package?
I'm 100% certain that mouse/keyboard interaction is unrelated to movie paths. Sounds more like the movie wasn't getting loaded at all, so the interaction didn't visually do anything.
As for the movie path, I've seen 2 common ways to handle this:
First, you can put all the media in the same folder as the composition, and then use just the file name ("composition-relative path" stuff, like "video.mov" (no /, no ~, etc)).
Second, you can have a folder with you composition, and a folder in that folder called "Media", then put your videos/images/whatever in there. In the composition, you'll still do composition-relative addressing, but using "Media/video.mov" or "Media/image.jpg". This keeps clutter down.
In both of the above, QB will generally autodetect the media in use, and include the Media folder (or the individual files, in option 1) inside the app.
QB Cannot bundle in ~-relative or absolute path files, because there's no way to keep those paths working while keeping the files bundled into the app.
Thanks chris.
The problem seems to be with the movie loader in general. the QB application does not update anymore if a movie is loaded. i only get an update if i move the QB application window across the desktop.
This is a quicktime bug (the movie loader doesn't check to make sure it's working on the main thread before it does some main-thread-only QT stuff, and then it fails randomly). That's why sometimes you get a grey box, sometimes you get no box, sometimes you get a few frames of video, and then a grey box or no box.
There's not really a good way to solve this problem, since it's on apple end (Both the movie loader patch not checking threads, and QT's overall absence of thread support at all...)
[note: check console.app, it contains notes when most QC stuff doesn't work as expected.]
oh, quicktime bug, i see...
but, it seems to work in QB with vades V002 Movie Player. the problem here, it does not support a relative path to the movie.
I think vade included the necessary thread sanity stuff (unlike apple :/.. go figure). Is his movie player open source? if so, making it support relative paths probably isn't too difficult. If it's no open source, it's probably not too difficult to ask him to add that (it's only a few lines of code, maybe a dozen or so).
keyboard/mouse is supported (along with tablets, though that functionality is untested on our end).
Published parameters are not currently supported in 1.0, and aren't likely to be supported in 1.1 (due any day now...). 1.2 or later is the target for that functionality.
I had an issue with mouse keyboard input not working when a path for an external quicktime movie was absolute. changing it to a relative path (with ~) fixed that. But the movie still does not show up. if I refer to the movie with ~video.mov in the Movie Loader, where do I put the actual file within the Quartz Builder application package?
I'm 100% certain that mouse/keyboard interaction is unrelated to movie paths. Sounds more like the movie wasn't getting loaded at all, so the interaction didn't visually do anything.
As for the movie path, I've seen 2 common ways to handle this:
First, you can put all the media in the same folder as the composition, and then use just the file name ("composition-relative path" stuff, like "video.mov" (no /, no ~, etc)).
Second, you can have a folder with you composition, and a folder in that folder called "Media", then put your videos/images/whatever in there. In the composition, you'll still do composition-relative addressing, but using "Media/video.mov" or "Media/image.jpg". This keeps clutter down.
In both of the above, QB will generally autodetect the media in use, and include the Media folder (or the individual files, in option 1) inside the app.
QB Cannot bundle in ~-relative or absolute path files, because there's no way to keep those paths working while keeping the files bundled into the app.
Thanks chris. The problem seems to be with the movie loader in general. the QB application does not update anymore if a movie is loaded. i only get an update if i move the QB application window across the desktop.
please have a look at the attached example.
This is a quicktime bug (the movie loader doesn't check to make sure it's working on the main thread before it does some main-thread-only QT stuff, and then it fails randomly). That's why sometimes you get a grey box, sometimes you get no box, sometimes you get a few frames of video, and then a grey box or no box.
There's not really a good way to solve this problem, since it's on apple end (Both the movie loader patch not checking threads, and QT's overall absence of thread support at all...)
[note: check console.app, it contains notes when most QC stuff doesn't work as expected.]
oh, quicktime bug, i see... but, it seems to work in QB with vades V002 Movie Player. the problem here, it does not support a relative path to the movie.
I think vade included the necessary thread sanity stuff (unlike apple :/.. go figure). Is his movie player open source? if so, making it support relative paths probably isn't too difficult. If it's no open source, it's probably not too difficult to ask him to add that (it's only a few lines of code, maybe a dozen or so).
yes, he published the source
a workaround is using V002 movie player and getting the file path through Directory Scanner patch.