Re: Property synthesis trouble - 32 vs 64 bit builds

> On 6 Jul 2016, at 7:10 AM, Jonathan Taylor > wrote: > > Quicktime. My code has been 32-bit only since I first wrote it, because I > make use of the APIs in QuickTime/ImageCompression.h for encoding movies. Not really quite on-topic, but if you are having to

Re: Prioritize my own app's disk access

> On Jul 5, 2016, at 2:40 PM, Jonathan Taylor > wrote: > > As far as the quality of service goes, I can't see the APIs for that (looking > in the 10.9 SDK, at least). Am I looking in the wrong place? IIRC, QoS was added in 10.10. > I confess that currently I

Re: Prioritize my own app's disk access

Thanks everyone for your replies on this second question of mine. Some responses below: On 5 Jul 2016, at 18:20, Quincey Morris wrote: > What worries me about the Darwin-level (i.e. Unix-level) API suggestions that > others have made is that you don’t

Re: Property synthesis trouble - 32 vs 64 bit builds

On 5 Jul 2016, at 22:22, "Gary L. Wade" wrote: > You might need to write some lower level stuff, but some of the things in > there can be done, albeit differently. Apple knows I've submitted a number of > bugs and incident reports to get codecs supported in later

Re: Property synthesis trouble - 32 vs 64 bit builds

>> Quicktime. > > Oh, you poor thing. That’s one nasty API. (Actually dozens of nasty APIs.) O_o Yep. I rely on code that I worked out years ago, with the help of examples on the internet, and I do my best to leave that code untouched! >> My code has been 32-bit only since I first wrote it,

Re: Property synthesis trouble - 32 vs 64 bit builds

You might need to write some lower level stuff, but some of the things in there can be done, albeit differently. Apple knows I've submitted a number of bugs and incident reports to get codecs supported in later frameworks. Do the same. It may happen. -- Gary L. Wade (Sent from my iPhone)

Re: Property synthesis trouble - 32 vs 64 bit builds

> On Jul 5, 2016, at 2:10 PM, Jonathan Taylor > wrote: > > Quicktime. Oh, you poor thing. That’s one nasty API. (Actually dozens of nasty APIs.) O_o > My code has been 32-bit only since I first wrote it, because I make use of > the APIs in

Re: Property synthesis trouble - 32 vs 64 bit builds

Thanks everyone for your replies - some responses below: On 5 Jul 2016, at 20:55, Greg Parker wrote: > A synthesized property must use one of the following types of storage: > 1. An ivar in that class that @synthesize creates. > 2. An ivar in that class that you defined

Re: Property synthesis trouble - 32 vs 64 bit builds

> On Jul 5, 2016, at 9:27 AM, Jens Alfke wrote: > >> On Jul 5, 2016, at 4:36 AM, Jonathan Taylor >> wrote: >> >> It surprises me that I have to write different synthesis code for 32- or >> 64-bit builds > > It’s because they use different

Re: Prioritize my own app's disk access

If it's a dedicated workstation, it should be OK to require a RAID 0. That won't affect anyone's priority, but all disk I/O will be divided among two or more disks. Alternatively, dedicate a single drive only to video, with your other drive being for everything else. Michael David Crawford,

Re: Prioritize my own app's disk access

On Jul 5, 2016, at 05:36 , Jonathan Taylor wrote: > > suggestions that might be relevant here What worries me about the Darwin-level (i.e. Unix-level) API suggestions that others have made is that you don’t know how these interact with Cocoa apps. You didn’t

Re: Property synthesis trouble - 32 vs 64 bit builds

On Jul 5, 2016, at 04:36 , Jonathan Taylor wrote: > > @interface ImmutableSettings : NSObject > { >BOOL_myFlag; > } > @property (readonly) BOOL myFlag; > @end > > @interface MutableSettings : ImmutableSettings > @property (readwrite) BOOL myFlag; > @end >

Re: Property synthesis trouble - 32 vs 64 bit builds

> On Jul 5, 2016, at 4:36 AM, Jonathan Taylor > wrote: > > It surprises me that I have to write different synthesis code for 32- or > 64-bit builds It’s because they use different Obj-C runtimes. For compatibility reasons, 32-bit Mac apps still use the old

Re: Prioritize my own app's disk access

You might try asking on the darwin-userlevel mailing list. In addition to increasing I/O priority, there may be other ways to make your disk writes more efficient. For example you can preallocate space for the file before writing to it. Writing in larger chunks may also help. (Of course you

Re: Property synthesis trouble - 32 vs 64 bit builds

Thanks for that information - that’s very helpful. It sounds from what you are saying as if there is nothing wrong with me redefining the *property* in the subclass (as read-write), but that it’s just the synthesis itself that is the problem? Assuming that is the case, I can easily(*) rectify

Re: Prioritize my own app's disk access

Thanks Alastair. Mark Allan’s email set me off reading things in that area, and I am indeed reading the man page for setiopolicy_np at this very moment! Certainly sounds like the API I am looking for although, as you say, it’s not clear where the “default” policy fits into the hierarchy. The

Re: Prioritize my own app's disk access

On 5 Jul 2016, at 13:36, Jonathan Taylor wrote: > > This is a long shot, but I thought I would ask in case an API exists to do > what I want. One of the roles of my code is to record video to disk as it is > received from a camera. A magnetic hard disk can

Re: Prioritize my own app's disk access

Have you tried to nice/renice your process ID? I know that works for CPU usage but I'm not sure about other hardware resources. A cursory glance at the man pages for getpriority & setpriority seem to indicate that network and disk IO can be lowered in priority so I would try that first to see

Re: Property synthesis trouble - 32 vs 64 bit builds

> On Jul 5, 2016, at 5:36 AM, Jonathan Taylor > wrote: > > I have a problem with property synthesis in my code, which I hope somebody > can advise on. I find I have to write different property synthesis code for > 32- or 64-bit builds in order to avoid compiler

Prioritize my own app's disk access

This is a long shot, but I thought I would ask in case an API exists to do what I want. One of the roles of my code is to record video to disk as it is received from a camera. A magnetic hard disk can normally keep up with this, but if the user is also doing other things on the computer (e.g.

Cocoa UI preservation - simple example

I’m trying to make usage of Cocoa UI preservation API, but it seems I got stuck at the very beginning and even after almost two hours of trying to figure out what I’m doing wrong, there’s no progress at all. I’m sensing I’m missing something obvious, but I don’t know what that would be.

Property synthesis trouble - 32 vs 64 bit builds

Hi all, I have a problem with property synthesis in my code, which I hope somebody can advise on. I find I have to write different property synthesis code for 32- or 64-bit builds in order to avoid compiler errors. A minimal demonstration of the problem can be found below - build as part of a