August 2009 - Pro-apps-dev - lists.apple.com

Re: question on refreshing parameter data between instances.
by Steve Christensen 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com On Aug 13, 2009, at 12:38 PM, Brian Gardner wrote: You are correct up to this stage. steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This shouldn't be a problem in practice. When you first create the singleton, it has the values of whichever instance of the plugin asked for it to be created. The next plugin calls the create method, but just gets back the existing instance, so it has the same values and is in synch already. All instances that exist when the document is saved should already be in synch. So when the document is reopened, they'll still be in synch. There is no issue until the user decides to alter a global value by changing a parameter value. That parameter change will in turn update the corresponding global value, stored in the singleton. At this point, all of the other plugin instances set to useGlobalValues will have a parameter value that still is set to the old global value, except the one that the user has just changed. So, the change must be rippled to all of the other instances of the plugin. Normally, I'd expect to do this by having the singleton maintain an array to keep track of the relevant plugin instance id's. Toggling an instance's useGlobalValues parameter, would add/remove it from the singleton's array. The singleton could loop through this array, to send a message to each managed plugin instance to perform a setParameter, to reflect whenever a global value changed. This makes the assumption that a plugin instance is created for each clip that uses your effect and that the instance will hang around in memory until either that clip is removed, the project is closed or the host app quits. I don't know the underlying architecture but it's just as likely that plugin instances are created as needed and then destroyed if you're not currently working with a particular clip. If you create an array and add instances to it, you -could- end up with a bunch of stale items that no longer refer to real clips and/or conflict with the plugin instance that now manages your effect for a particular clip. But... just after an 'open project', the id's are not the same as in the previous session (I think), and the singleton has an empty array anyway (singleton data wasn't seralized). So, this array would need to be reconstructed somehow after the 'project open'. Since the deserialization of the useGlobalValues parameter bypasses ParameterChanged, it never invokes the singleton. So the singleton can't build a list of the relevant plugin instance's new id's. Perhaps, I can replace the toggle with a 'custom parameter' toggle, just so that i can trap the deserialization? Then I could (re)build a new array upon project open. Again, this assumes that effect instances will be created for all clips when the project is opened, and furthermore de-serialization also occurs for each of those instances. That may be the case for the few clips visible in the timeline, but what happens if you have, say, 50 or 100 clips with your effect applied? You can also use the operating system mechanism for saving preferences. See NSUserDefaults for the details. ... ... It also means all instance of your filter, regardless of project, use the same global settings. I don't know if that's what you need or not. Definitely would be an issue -- not what the user wants in this particular case. Actually, the user wants these globals to be scoped to the sequence. Almost like a Sequence Setting (but with easier access, since the globals are changed more often). Unfortunately, I can't figure out how to do that. So, the best I can do is using a singleton ... which is probably Project scoped, which is acceptable. Though, if the user can open multiple projects in one session, then it's probably not even project scoped, it's probably session scoped. (Session scoped is also not very desirable, either.) Plugins are called to perform their effect on some arbitrary clip, thus their scope is the host application, not an individual project or sequence. In other words you can't really tell which project- >sequence->clip is associated with a particular plugin instance. Certainly, somehow, these global settings must be scoped and stored within the Project file. Generally the only plugin-specific data is that which is serialized on a per-clip basis. I have not seen a "global settings" area within a project that can be associated with a particular plugin (vs instance). Thus Darrin's suggestion about using NSUserDefaults makes more sense as a repository for your global settings. Unless your user is going to be moving project(s) from machine to machine, NSUserDefaults is a non-issue. It also gets rid of the hoops you're jumping through to try to manage settings across multiple plugin instances. This email sent to site_archiver(a)lists.apple.com

1 0

Re: adding metadata to a QuickTime file
by Helena Ju 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

adding metadata to a QuickTime file
by Rainer Standke 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Hello, Thanks, Rainer _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I guess that you could use FCP to import an XML containing custom metadata that you'd want to be included in a QT file. In the absence of FCP what can one do programmatically to to read QT metadata out of a file, and to write into it? This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Brian Gardner 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=S9GYwFS7r8o/FGJ37+eH+aPPkf/F+mMzRlHd5ofkaM8TfHwGvHTt5o2HQVIDMJYG; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Thanks, Darrin. Yes. No problem with that case. You are correct up to this stage. There is no issue until the user decides to alter a global value by changing a parameter value. Unfortunately, I can't figure out how to do that. So, the best I can do is using a singleton ... which is probably Project scoped, which is acceptable. -- Brian _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… I think recovering the state should be fairly easy. In the case where "useGlobalValues" is not checked, you don't need to even create the singleton, so that case should work just fine already, right? This shouldn't be a problem in practice. When you first create the singleton, it has the values of whichever instance of the plugin asked for it to be created. The next plugin calls the create method, but just gets back the existing instance, so it has the same values and is in synch already. All instances that exist when the document is saved should already be in synch. So when the document is reopened, they'll still be in synch. That parameter change will in turn update the corresponding global value, stored in the singleton. At this point, all of the other plugin instances set to useGlobalValues will have a parameter value that still is set to the old global value, except the one that the user has just changed. So, the change must be rippled to all of the other instances of the plugin. Normally, I'd expect to do this by having the singleton maintain an array to keep track of the relevant plugin instance id's. Toggling an instance's useGlobalValues parameter, would add/remove it from the singleton's array. The singleton could loop through this array, to send a message to each managed plugin instance to perform a setParameter, to reflect whenever a global value changed. But... just after an 'open project', the id's are not the same as in the previous session (I think), and the singleton has an empty array anyway (singleton data wasn't seralized). So, this array would need to be reconstructed somehow after the 'project open'. Since the deserialization of the useGlobalValues parameter bypasses ParameterChanged, it never invokes the singleton. So the singleton can't build a list of the relevant plugin instance's new id's. Perhaps, I can replace the toggle with a 'custom parameter' toggle, just so that i can trap the deserialization? Then I could (re)build a new array upon project open. You can also use the operating system mechanism for saving preferences. See NSUserDefaults for the details. ... ... It also means all instance of your filter, regardless of project, use the same global settings. I don't know if that's what you need or not. Definitely would be an issue -- not what the user wants in this particular case. Actually, the user wants these globals to be scoped to the sequence. Almost like a Sequence Setting (but with easier access, since the globals are changed more often). Though, if the user can open multiple projects in one session, then it's probably not even project scoped, it's probably session scoped. (Session scoped is also not very desirable, either.) Certainly, somehow, these global settings must be scoped and stored within the Project file. This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Darrin Cardani 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com On Aug 13, 2009, at 10:17 AM, Brian Gardner wrote: Thanks, Darrin. I'm using a singleton object (as you recommended to me a while ago) as a way for the user to set global variables, that are common to all instances of the plugin. Ah, gotcha. That makes a lot more sense. I have two challenges: + (SingletonClass*)createSingletonWithParam1:(int)param1 param2:(float)param2 ... (whatever other parameters you have)... { if (globalSingleton == nil) { globalSingleton = [[SingletonClass alloc] initWithParam1:param1 param2:param2 ...etc...]; } return globalSingleton; } Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… It almost sounds like you're trying to change the value of one parameter based on another parameter between when the user saved a document and reopened it. Is that correct? No, not at all. I'm just trying to save and recover the values that the user set. Since the singleton doesn't get serialized, itself, then I must recreate the singleton, it's state, and it's linkages to the plugins, during project open ... indirectly. 1. I complicated things by giving the plugin a "useGlobalValues" toggle parameter. It is the user's choice whether an instance of the plugin functions independently, (which the user rarely picks) or if the user wants it to be ganged to the global values (which is what they typically choose for this plugin). So, whether the singleton is linked to this plugins' several parameters or not will depend on how the user set this "useGlobalValues" toggle parameter. When the user saves the project, and later reopens the project, the state of the plugins and the singleton need to match the way the user had set it from their previous project save. The challenge is -- how do I save the singleton's state into the project file? And how do I recover that state, later, and re-instate the linkages? I think recovering the state should be fairly easy. In the case where "useGlobalValues" is not checked, you don't need to even create the singleton, so that case should work just fine already, right? When the user does have "useGlobalValues" checked, you need to actually create the singleton (if it doesn't already exist), and set the singleton's values to those of your instance. So the host app creates an instance of your filter and calls its -initWithAPIManager method to initialize it, then calls its -addParameters method to create the parameters. But at this point the parameters still don't have the values that were saved with the document, they're just being created with their default values. The host app will then internally set the keyframes and values of all the parameters from the document. That doesn't involve calling your plugin. So you probably won't get any other messages until your plugin is asked to render the first time. At that point, in -renderOutput:, your plugin will notice that it doesn't have an instance of the singleton, so it will create it and set its values to the values it currently has for its associated parameters. You may have to have a method for creating the singleton that looks something like this: It's a little more cumbersome in that the method which returns the singleton (and possibly creates it, too) has more parameters, so calling it is less pretty. But that seems like a reasonable solution. So what happens is the first time you call +createSingletonWithParam1:param2:etc. it creates the singleton and initializes it with the values you pass in for the parameters. The next time you call it, the singleton already exists, so it ignores the parameters that are passed in. 2. The plugin has its UI parameters, which (depending on the "useGlobalValues" toggle) should reflect either the local settings, or current global settings . When using global, this allows the user to see & change the global value from any plugin instance. So, I need to keep all of those parameters which are linked to the global, in sync. (Possibly, the singleton would need to update the UI parameter for each plugin instance, whenever the global is updated.) When a project is saved, whatever bookkeeping overhead and mechanism is used to manage these linkages, would need to be saved ... and recreated later upon project open. (But, the singleton does not get serialized / deserialized.) This shouldn't be a problem in practice. When you first create the singleton, it has the values of whichever instance of the plugin asked for it to be created. The next plugin calls the create method, but just gets back the existing instance, so it has the same values and is in synch already. All instances that exist when the document is saved should already be in synch. So when the document is reopened, they'll still be in synch. The plugin is mostly completed, and beta user feedback is very positive. But, I still need to solve the problems of how to save the user's settings with the project, and recover them later during the next project open. You can also use the operating system mechanism for saving preferences. See NSUserDefaults for the details. This has the disadvantage that when you move the document to another machine, you have to move the prefs file with it. But that might not be an issue for your users – I don't know. It also means all instance of your filter, regardless of project, use the same global settings. I don't know if that's what you need or not. This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Brian Gardner 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XiGPZionDHQlxJffEgf8IvISlRiWlBFhtSb3Ts4G7Zpto1tk5KZq9uu3VOJ8M0iv; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Thanks, Darrin. I'm using a singleton object (as you recommended to me a while ago) as a way for the user to set global variables, that are common to all instances of the plugin. I have two challenges: -- Brian Darrin On Aug 12, 2009, at 4:28 PM, Brian Gardner wrote: Will the other plugin's parameters exist and be settable during the time when the custom parameter gets called to deserialize? In other words, is the custom parameter deserialization called last? If it were called too soon, some of what we'd need to do wouldn't be available yet to be done. So, I guess I'm really asking... At what point in the plugin's re-instatement is the custom parameter deserialization called? -- Brian On Aug 12, 2009, at 2:42 PM, Darrin Cardani wrote: Darrin On Aug 11, 2009, at 12:58 PM, Brian Gardner wrote: I have a similar situation to Jay. When a saved FCP project is later reopened, I'd like to update some parameter settings. -- Brian On Aug 11, 2009, at 10:53 AM, Jay Boyer wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com -- Darrin Cardani dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… It almost sounds like you're trying to change the value of one parameter based on another parameter between when the user saved a document and reopened it. Is that correct? No, not at all. I'm just trying to save and recover the values that the user set. Since the singleton doesn't get serialized, itself, then I must recreate the singleton, it's state, and it's linkages to the plugins, during project open ... indirectly. 1. I complicated things by giving the plugin a "useGlobalValues" toggle parameter. It is the user's choice whether an instance of the plugin functions independently, (which the user rarely picks) or if the user wants it to be ganged to the global values (which is what they typically choose for this plugin). So, whether the singleton is linked to this plugins' several parameters or not will depend on how the user set this "useGlobalValues" toggle parameter. When the user saves the project, and later reopens the project, the state of the plugins and the singleton need to match the way the user had set it from their previous project save. The challenge is -- how do I save the singleton's state into the project file? And how do I recover that state, later, and re-instate the linkages? 2. The plugin has its UI parameters, which (depending on the "useGlobalValues" toggle) should reflect either the local settings, or current global settings . When using global, this allows the user to see & change the global value from any plugin instance. So, I need to keep all of those parameters which are linked to the global, in sync. (Possibly, the singleton would need to update the UI parameter for each plugin instance, whenever the global is updated.) When a project is saved, whatever bookkeeping overhead and mechanism is used to manage these linkages, would need to be saved ... and recreated later upon project open. (But, the singleton does not get serialized / deserialized.) The plugin is mostly completed, and beta user feedback is very positive. But, I still need to solve the problems of how to save the user's settings with the project, and recover them later during the next project open. If so, you should not do that, and it won't ever be supported. That a) breaks the user's assumptions that the document they saved will be the document they open, and b) could cause problems with other parts of the document, such as keyframes on the parameters you're changing. Not to mention the above problem that we make no guarantees about the order in which things are deserialized. If you're trying to do something else, please explain in more detail what you're trying to do. I believe in Jay's example, he was just trying to save and restore the value of a font menu, and the installed fonts may not be the same between 2 machines (or between closing and reopening the document). Since there's a reasonable fallback of using the default font, you can get away with it in that case. Are you working with a similar type of functionality? There isn't, but if you have a custom parameter, you will get called to deserialize its data. You could do what you need to do at that time. As a plugin is getting re-instated during an "Open Project..." (boot), is there an methods which get called, which we can hook into? Is there a point in the boot sequence that I can detect that the plug-in is from a prior instance so that I can update these lists? This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Darrin Cardani 12 Aug '09

12 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Darrin On Aug 12, 2009, at 4:28 PM, Brian Gardner wrote: Will the other plugin's parameters exist and be settable during the time when the custom parameter gets called to deserialize? In other words, is the custom parameter deserialization called last? If it were called too soon, some of what we'd need to do wouldn't be available yet to be done. So, I guess I'm really asking... At what point in the plugin's re-instatement is the custom parameter deserialization called? -- Brian On Aug 12, 2009, at 2:42 PM, Darrin Cardani wrote: Darrin On Aug 11, 2009, at 12:58 PM, Brian Gardner wrote: I have a similar situation to Jay. When a saved FCP project is later reopened, I'd like to update some parameter settings. -- Brian On Aug 11, 2009, at 10:53 AM, Jay Boyer wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com -- Darrin Cardani dcardani(a)apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… You should not make any assumptions about the order in which parameters being deserialized are instantiated. It almost sounds like you're trying to change the value of one parameter based on another parameter between when the user saved a document and reopened it. Is that correct? If so, you should not do that, and it won't ever be supported. That a) breaks the user's assumptions that the document they saved will be the document they open, and b) could cause problems with other parts of the document, such as keyframes on the parameters you're changing. Not to mention the above problem that we make no guarantees about the order in which things are deserialized. If you're trying to do something else, please explain in more detail what you're trying to do. I believe in Jay's example, he was just trying to save and restore the value of a font menu, and the installed fonts may not be the same between 2 machines (or between closing and reopening the document). Since there's a reasonable fallback of using the default font, you can get away with it in that case. Are you working with a similar type of functionality? There isn't, but if you have a custom parameter, you will get called to deserialize its data. You could do what you need to do at that time. As a plugin is getting re-instated during an "Open Project..." (boot), is there an methods which get called, which we can hook into? Is there a point in the boot sequence that I can detect that the plug-in is from a prior instance so that I can update these lists? This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Brian Gardner 12 Aug '09

12 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=UiYolefpi7wQLiCJFHitELBMazq9EMsFoH1x9/yYXb7ngSp4VggPFF95B9OolWg9; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Will the other plugin's parameters exist and be settable during the time when the custom parameter gets called to deserialize? In other words, is the custom parameter deserialization called last? If it were called too soon, some of what we'd need to do wouldn't be available yet to be done. So, I guess I'm really asking... At what point in the plugin's re-instatement is the custom parameter deserialization called? -- Brian On Aug 12, 2009, at 2:42 PM, Darrin Cardani wrote: Darrin On Aug 11, 2009, at 12:58 PM, Brian Gardner wrote: I have a similar situation to Jay. When a saved FCP project is later reopened, I'd like to update some parameter settings. -- Brian On Aug 11, 2009, at 10:53 AM, Jay Boyer wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… There isn't, but if you have a custom parameter, you will get called to deserialize its data. You could do what you need to do at that time. As a plugin is getting re-instated during an "Open Project..." (boot), is there an methods which get called, which we can hook into? Is there a point in the boot sequence that I can detect that the plug-in is from a prior instance so that I can update these lists? This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: question on refreshing parameter data between instances.
by Darrin Cardani 12 Aug '09

12 Aug '09

site_archiver(a)lists.apple.com Delivered-To: Pro-apps-dev(a)lists.apple.com Darrin On Aug 11, 2009, at 12:58 PM, Brian Gardner wrote: I have a similar situation to Jay. When a saved FCP project is later reopened, I'd like to update some parameter settings. As a plugin is getting re-instated during an "Open Project..." (boot), is there an methods which get called, which we can hook into? -- Brian On Aug 11, 2009, at 10:53 AM, Jay Boyer wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… There isn't, but if you have a custom parameter, you will get called to deserialize its data. You could do what you need to do at that time. Is there a point in the boot sequence that I can detect that the plug-in is from a prior instance so that I can update these lists? This email sent to dcardani(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Testing with lossless codecs
by Darrin Cardani 11 Aug '09

11 Aug '09

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Aug 11, 2009, at 2:04 PM, Dan DiPaola wrote: Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… • Integer or floating-point ('half')? I believe floating point in most cases Really? Does 16-bit TIFF support half float? I wasn't aware of that. I thought it was only integers. This email sent to site_archiver(a)lists.apple.com

1 0