adding markers to a quicktime video
Is there any way to add markers to a quicktime file so when you share a file with someone else you can have markers they can jump to?
iMac, Mac OS X (10.7.2), 3.4 intel core 17, 16gb mem
Is there any way to add markers to a quicktime file so when you share a file with someone else you can have markers they can jump to?
iMac, Mac OS X (10.7.2), 3.4 intel core 17, 16gb mem
I am a visual learner... As I recall (jumpin in the WayBack machine w/ Mr. Peabody), at first rollout, QT was samall window for delivery on the computer display. Apple rightly surmised that the optimum 'apparent resolution' was 3 human fingers at arms length. OK. Further, thru vast amounts of focus group and beta testing, they concluded that the viewer would be completely satisfied with a few dropped frames IF the audio played smoothly. OK. Performance issues on old pooters.
Never really thought about it in terms of "fingers." Believe the May 1991 WDC public demo used a 320x240 display area and since this is equal to 1/16th the area of a VGA monitor (i.e., QQVGA), assumed that was how they initially arrived at these dimensions.
The way I understood they accomplished the latter is 'striping' audio and video segments - perhaps your description of MPEG-2 /AVI? Audio loads into memory first, then video plays like a tape? It would resemble this over time:
Not a technician, so can't really comment on the technical aspects regarding order of loading/playing data and was merely attempting to point out that data was loaded and played sequentially in discrete packages which prevent either the audio or the video running away on its own and that this operation was spatially self-sustaining with respect to the synchronization of the audio and video during playback. I.e., any change in the playback speed automatically speeds up the playback of both the audio and video data, thus, maintaing synchronization of one with respect to the other.
I understand you to say that currently (QT7+X) it is layered like the timeline of Director from earlier. It might resemble this? ::
Not sure I understand your use of the term "layered" here. Since QT can have up to 99 independent data tracks (what I tend the consider 1 dimension) and each track has a duration (what I consider a second dimension) and various forms of data can be "composited" (or "layered") together for playback (what I consider a third dimension), I tend to feel uneasy about your use of the term here.
Did I get it?
Since your visual aid contains tracks of equal width, I would have depicted the individual tracks in your array as having different vertical dimensions denoting differences in individual track data bandwidth. (I.e., to visually denote the measure of data being processed per unit of time over time—or in other words, to better reflect track relationships in terms of the total amount of data contained in each.) If this is what you meant, then yes, you got it.
Jon
To be crystal... My bailiwick is New Media Show Business - client perform it or me really puttin on a real show with client footin the bill! I had one 18-month gig as a personal show thrower for a guy pitching to C-insertInitial-Os of major corporations all over the U.S. When traveling I got paid 24 hours a day! Ridiculous!
QT is a brush in my paintbox. A Very Useful Paintbrush !!
You said:
"Never really thought about it in terms of "fingers." Believe the May 1991 WDC public demo used a 320x240 display area and since this is equal to 1/16th the area of a VGA monitor (i.e., QQVGA), assumed that was how they initially arrived at these dimensions."
The User Experience
San Francisco, an Apple guy held a special breakout session at the MacroMedia Developers Conference in '92. He explained in terms of apparent resolution. 320x240 just ended up being the size that most closely fit that User Experience (Apple wrote the book on UX) specification = Smooth playing video on My Computer . Back then, 15 FPS was adequate performance - 12 FPS was good performance. It just so happened to be 1/4 of a 640x480 resolution 12" display(which was most of installed base of 8-bit/256 color displays) was just an even division of the size - see immediately following. BTW, 240x180 was the REAL PERFORMER in terms of smooth audio AND video. You can experience apparent resolution yourself right now -
Do the same experiment when sitting in your favorite chair in front of your television. I think you will see how close to your computer display experience it likely is. (remember, this was before big-screen TVs) - basically Apple's UX goal was to replicate the normal TV watching experience on the computer display.
FLASH Forward to 2014... What's an iPhone appear to be? Designed and crafted to the UX! A PALM size display that will blot out your Big-Screen TV from your favorite chair. Same deal as early QT!!
----------
Apple Core Values (c. 1992)
1] Darn FINE Design ........................ (maybe I should put white space
everywhere might be an exception) ;-)>
2] Unparalleled Performance
3] ------> Barnum-esque Marketing <-------
----------
You further said:
"Not a technician, so can't really comment on the technical aspects regarding order of loading/playing data... SNIP"
I am no technician - by choice.
You may be able to tell, but in my line of work - " It's All Show Business " just turned out to be a job where you had to know everything about the newest Toy the clients insisted on. Turned out that the hardware was available & darned expensive - from you know who? - to do a SHOW. == Mo' Money! for ME!! Had a pretty good time with new toys on someone else's dime. ALL of the clients insisted on keeping their purchases after seeing the Show we gave 'em. Apple sold a lotta hardware and software products because of my show's tech spec.
Also from the same Apple source at the same breakout session at the MMDC'92. We were all there because Director was the cat's meow software for Rich Media delivery. Clearly Apple had vested interest in the future hardware sales that would generate.
In particular, the user experience part. Focus-grouped, beta-tested thoroughly.
The technology was as I tried to illustrate...
Remember, back then, slow processors and slow drive transfer rates were the norm. It then became imperative to perform those demos, Steve Jobs down to the breakout session Host = ShowBiz!!
These shows were also performed with pre-release hardware - amazing to we unwashed masses.
------
You continued:
"Not sure I understand your use of the term "layered" here. Since QT can have up to 99 independent data tracks (what I tend the consider 1 dimension) and each track has a duration (what I consider a second dimension) and various forms of data can be "composited" (or "layered") together for playback (what I consider a third dimension), I tend to feel uneasy about your use of the term here."
O! Contrare! Methinks you do! 99 tracks is exactly what I was illustrating "ETC. ad infinitum" in the array. Back in the day, best performance was achieved by flattening a movie as a final authoring step - it was a menu choice, maybe. This is where the -- A | VVVV | A | VVVV | A | VVVV was done
-------
lastly, said you:
"SNIP ... differences in individual track data bandwidth. (I.e., to visually denote the measure of data being processed per unit of time over time—or in other words, to better reflect track relationships in terms of the total amount of data contained in each.) If this is what you meant, then yes, you got it."
to be frank, until just above, I had not considered bandwidth at all in the discussion! But I DO see you minds eye analogy clearly.
I pretty much think we both have a clear enough grasp of the inner workings to accomplish our needs. Mine are very low now that my Day Job is Alzheimer's caregiver. While I'm being frank, I really don't much miss the pressure of deadline-driven, client-coddling content authoring!
buenos noches
CCC
Howdy Jon
All that is getting the markers IN the data file. What I see is the OP's problem might be is how to point his audience to specific markers. Easy for Director to playMarker "WoodyGuthrie" of movie "Hootenanny" or waitForCuePoint "Cue01" of movie "LaDeeDa" then go "OnWithTheShow".
I guess I may be reading "share a file with someone else you can have markers they can jump to?" as the important part of his question.
Any suggestions for cheap/quick/down-n-dirty Director substitutes? He needs something to play the movie other than QTPlayer for the "jump to" part, does he not?
CCC
To clarify, my workflow consists of me preparing dailies for my clients. I would like to try and lay each "take" on my timeline, and add chapter markers, so when I export a quicktime for my client, they can easy jump back and forth to earlier or later takes. To add them later on via timecode, would be a little bit of a hassle.
When I use to edit in Final Cut 7, I believe you could make chapter markers right on the edit point so they could be interpreted in Compressor. In premiere, although you can add markers, I don't believe they are recognized when you compress to a quicktime.
HarringtonT......
Could you use Keynote or Powerpoint to deliver these dailies? If so, I could recommend a WortkFlow that seems very easy to me. Requires no "Chapters" at all, just separate 'takes'(clips) put in a folder. Let me know if presentation software is acceptable and I will give you the WorkFlow.
CCC
Jon
You may consider me shamed and contrite. You are the ramrod of this help effort as far as I am concerned.
You of course!, are right about the feature being available in QTpro 7. Being a Director Lingo geek and Premiere user, I never had the inclination to explore the issue internal to QT until you mentioned its existence. Turns out QTpro Player Help is pretty thorough on the subject (not without its errors though)
We both were lulled by the simplicity of the OP. Be interesting to get a complete outline of the complete WorkFlow, shutter-snap to delivery, to best answer the real question "How do I deliver a daily to my clients that is easily reviewable and commented upon?"
The QTpro method is actually a makeshift GUI, a couple of windows in QT - movie and info windows - and one TextEdit window as the third. Actually, very easy to use, even for a non-geek(LingoGeek=ME). Result is effective but not elegant - teeny-weeny menu beside the timeline. I have the QT help page annotated with the errors corrected and clarifications and ready to paste and screenshots of the "interface" if you want me to. Just post "Go for it!" and it shall be done post-haste.
My test took about ten minutes. Tip prep considerably longer 😎
as always, best regards
CCC
Jon
Methinx it's time for you to author a USER TIP !! Your organizational and observational skills are top o' the line.
Unfortunately, looks as if QT's life expectancy as a item for consumer consumption may be short. HTML5 is a comin' - FAST. I am using TenFourFox v31 for my Pismo OS 10.4.11 - NO extensions!! No QT. No Flash. No pure runtime JAVA of any kind. No Nuthin!
BTW, TFFv31 is super fast and handles client-side JavaScript better than Safari.
Back to the game. Go Cowboys! (OSU & Dallas)
CCC
Jon Walker wrote:
SNIP ...consumer consumption ...
Not a specialist in the field and Apple is unlikely to reveal any specifics, but some have speculated the development of the "modernized" version of QuickTime (QT X) will probably take a decade with the current version of the software (QT 7) being gradually phased out over the same period. Still and all, this is a pretty good run for software that has been in development/use in one form or another for more than 23 years already.
I go as far as Darn Good Run. As a very early adopter (presentation creation for corporate clients), I remember having to do the ol' 'Proof of Concept' pitch to 'em! Most couldn't believe it! - Video On My Computer?!?!? What Will They Think Of Next?!?
RE; The Future... View from 30,000 feet - DELIVERY of Content
Whatever Apple does, if QT video is gonna display on a web page, it must comply with the HTML5 standard. This is non-negotiable by content creators (Apple, Flash, WMV, etc. - not the artists). Video, yea! all multimedia content, will be played by the code in the page and the browser's support of same
On the other hand, ProVideo can continue to benefit(?) from Apple's innovation ~😕
best
CCC
PReceding was an further Using ASC experiment with 'Insert" > Table in the advanced editor pane.
I am wholly unsatisfied withe results, much less the headaches involved in even trying to achieve them.
Coulda done it ten times over in PShop in the same time and woulda been perfect
Lesson learned
CCC
Challenge = see if you can spot the error that QTPlayerPro made in the process it described. I have not tried recreate it and tired of trying to debug it on the fly.
CCC
adding markers to a quicktime video