Upgrades within a major version (1.0, 1.1, 1.2, ...) are free for Kineme products, and we offer discounts to upgrade from one major version to another (see our License page).
To upgrade from QuartzCrystal 1.4 (or earlier) to QuartzCrystal 2.0, it's $5. The 2.0 release adds significant functionality, so we thought it was fair to increase the purchase price from $18 to $26. If you're upgrading, you can think of it as an $8 upgrade for the price of $5 ;-]
Thanks. Is the license key the same as the serial number? Because entering the serial as a coupon code tells me it's expired. I paid $10 for the original QuartzCrystal -- could it be that it is expired, considering what you explained about the upgrade price?
It's really okay -- the new price is fine and I am happy to support kineme. I'd just like to move forward here.... :)
@jersmi and I got this resolved over e-mail. For the record, the license key / serial number for any QuartzCrystal 1.x version is supposed to work as a coupon code. If you got a "coupon expired" message earlier, just try again-- we had a problem with our database for a few hours after QuartzCrystal 2.0 was released, but it's been fixed.
I was hoping it would come in handy to catch live data -- which was a real hassle with Value Historian, as I just cant get it to work properly. I just noticed that it only captures mouse movements and input, and not other data going into the comp. Bummer.
Doing a record data session on it was nice and everything was saved temporarily, but then it wasn't saved. Since I chose a huge codec to begin with, I needed to re-record. I went to just "play" back the data on a new codec, and it was all gone. So, yeah. Bummer.
If I am missing something, please let me know, but a quick glance at the data file it creates (.QCRecording) shows that the data is long gone, or maybe was never there.
the contents of which look much like the excerpt shown above taken from the visualization I posted recently to http://vimeo.com/24485424 .
Strikes me you've suffered a loss of data whilst recording, due to a crash, though that might be simply an educated guess on my part. I was using H.264 codec. What codec were you using?
BTW, the particulars of the codec employed aren't recorded into that file , the recorded input isn't shown in the Preview window & in my experience to date, swapping codecs doesn't seem to nullify the use of the recorded input for me at all.
I'd try running the composition without recorded input for a short while just to see if it would render OK, then see if the use of adding recorded events fouls up your composition for you. I'm just thinking that there may be something in your composition's structure that is causing such a failure. I must admit that I've found one sort of composition & thus far only one, fails to render anything for me at all via Quartz Crystal 2.0.
@ginsu777-- Can you say more about what was happening when your .QCRecording file was lost? Was it a crash like @cybero was guessing? When you say "saved temporarily", do you mean that you could play back the recording in the Record Input window but it was gone when you got back to the main QuartzCrystal window?
The .QCRecording file does get overwritten (intentionally) if you make a recording in Replace Events mode. And the file doesn't get written if you crash while in the Record Input window. Was it one of those cases or something else?
Maybe we could help you with the Value Historian patch. What problem are you having? (Might be appropriate to start a separate thread.)
cybero wrote: Strikes me you've suffered a loss of data whilst recording, due to a crash
Hmmm... I dont think so. I think the 2.0 only records mouse and menu input, where I am feeding realtime data from a port on localhost via IP. I see it is an XML file, but that prvides further evidence that it doesnt record data that is fed through the comp. Just mouse and menu input.
I got it to render fine with the H.264 codec, but I had to ride (to provide data) in real-time while it was rendering, and I know the data was jumpy, and not recorded and rendered smoothly.
(value historian release version doesn't catch key/up down stuff reliably, and sometimes just boolean stuff in general - you can't use it with particle paint.qtz reliably for example.)
QuartzCrystal 2.0 records (only) mouse, keyboard, and scroll wheel events.
Quartz Composer does not provide a method to record and regenerate data provided to the composition via other means (network, camera, audio, MIDI, smoke signals, etc.), but this is definitely something we're thinking about. For now, Value Historian is the way to handle recording and regenerating most other types of realtime input data.
Upgrades within a major version (1.0, 1.1, 1.2, ...) are free for Kineme products, and we offer discounts to upgrade from one major version to another (see our License page).
To upgrade from QuartzCrystal 1.4 (or earlier) to QuartzCrystal 2.0, it's $5. The 2.0 release adds significant functionality, so we thought it was fair to increase the purchase price from $18 to $26. If you're upgrading, you can think of it as an $8 upgrade for the price of $5 ;-]
Okay, no problem, good work. :) But, sorry, I don't see how to upgrade....
Oh, I didn't explain very well in the release notes. Added to FAQ-- hopefully that's more clear.
Thanks. Is the license key the same as the serial number? Because entering the serial as a coupon code tells me it's expired. I paid $10 for the original QuartzCrystal -- could it be that it is expired, considering what you explained about the upgrade price?
It's really okay -- the new price is fine and I am happy to support kineme. I'd just like to move forward here.... :)
@jersmi and I got this resolved over e-mail. For the record, the license key / serial number for any QuartzCrystal 1.x version is supposed to work as a coupon code. If you got a "coupon expired" message earlier, just try again-- we had a problem with our database for a few hours after QuartzCrystal 2.0 was released, but it's been fixed.
This upgrade is not as useful as I would like.
I was hoping it would come in handy to catch live data -- which was a real hassle with Value Historian, as I just cant get it to work properly. I just noticed that it only captures mouse movements and input, and not other data going into the comp. Bummer.
Doing a record data session on it was nice and everything was saved temporarily, but then it wasn't saved. Since I chose a huge codec to begin with, I needed to re-record. I went to just "play" back the data on a new codec, and it was all gone. So, yeah. Bummer.
If I am missing something, please let me know, but a quick glance at the data file it creates (.QCRecording) shows that the data is long gone, or maybe was never there.
@ginsue, in point of fact the QC recording is an XML file.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>takes</key> <dict> <key>default</key> <dict> <key>0</key> <dict> <key>QCRuntimeMouseLocationKey</key> <string>{0.13913746, -0.080310106}</string> <key>locationInWindow</key> <string>{92.804688, 23.078125}</string> <key>type</key> <string>NSMouseMoved</string> </dict> <key>0.1366810202598572</key>the contents of which look much like the excerpt shown above taken from the visualization I posted recently to http://vimeo.com/24485424 .
Strikes me you've suffered a loss of data whilst recording, due to a crash, though that might be simply an educated guess on my part. I was using H.264 codec. What codec were you using?
BTW, the particulars of the codec employed aren't recorded into that file , the recorded input isn't shown in the Preview window & in my experience to date, swapping codecs doesn't seem to nullify the use of the recorded input for me at all.
I'd try running the composition without recorded input for a short while just to see if it would render OK, then see if the use of adding recorded events fouls up your composition for you. I'm just thinking that there may be something in your composition's structure that is causing such a failure. I must admit that I've found one sort of composition & thus far only one, fails to render anything for me at all via Quartz Crystal 2.0.
@ginsu777-- Can you say more about what was happening when your .QCRecording file was lost? Was it a crash like @cybero was guessing? When you say "saved temporarily", do you mean that you could play back the recording in the Record Input window but it was gone when you got back to the main QuartzCrystal window?
The .QCRecording file does get overwritten (intentionally) if you make a recording in Replace Events mode. And the file doesn't get written if you crash while in the Record Input window. Was it one of those cases or something else?
Maybe we could help you with the Value Historian patch. What problem are you having? (Might be appropriate to start a separate thread.)
Thanks for the reply.
Hmmm... I dont think so. I think the 2.0 only records mouse and menu input, where I am feeding realtime data from a port on localhost via IP. I see it is an XML file, but that prvides further evidence that it doesnt record data that is fed through the comp. Just mouse and menu input.
I got it to render fine with the H.264 codec, but I had to ride (to provide data) in real-time while it was rendering, and I know the data was jumpy, and not recorded and rendered smoothly.
(value historian release version doesn't catch key/up down stuff reliably, and sometimes just boolean stuff in general - you can't use it with particle paint.qtz reliably for example.)
QuartzCrystal 2.0 records (only) mouse, keyboard, and scroll wheel events.
Quartz Composer does not provide a method to record and regenerate data provided to the composition via other means (network, camera, audio, MIDI, smoke signals, etc.), but this is definitely something we're thinking about. For now, Value Historian is the way to handle recording and regenerating most other types of realtime input data.
Not sure what you mean by "menu input".
Thanks George, I wont bother trying for recording Key inputs then, back to Quartz Crystal 2.0.