>
> On 8 Mar 2014, at 5:02 pm, Trygve Inda wrote:
>
>> This is slower by about 15%. :(
>
>
> Bummer.
>
> I'm thinking that two seconds to composite 20 x 1920 x 1080 X 32 bits isn't
> too bad actually. That's 165 MB of actual pixel data to iterate over, and at
> each pixel it's going to have
On 8 Mar 2014, at 5:02 pm, Trygve Inda wrote:
> This is slower by about 15%. :(
Bummer.
I'm thinking that two seconds to composite 20 x 1920 x 1080 X 32 bits isn't too
bad actually. That's 165 MB of actual pixel data to iterate over, and at each
pixel it's going to have to perform conside
>
> On Mar 7, 2014, at 8:38 PM, Trygve Inda wrote:
>
>> I'd like it to work with md5, ffmpeg and others. These all work fine, but
>> quit after returning their data.
>
> There’s nothing you can do about that, unless those tools allow multiple input
> files to be passed on the command line. Chec
On Mar 7, 2014, at 8:38 PM, Trygve Inda wrote:
> I'd like it to work with md5, ffmpeg and others. These all work fine, but
> quit after returning their data.
There’s nothing you can do about that, unless those tools allow multiple input
files to be passed on the command line. Check their man p
>
> On 8 Mar 2014, at 4:12 pm, Trygve Inda wrote:
>
>> I get the same times doing it this way, but maybe my color spaces are
>> different. The CGImage returned from my AVAsset is:
>>
>> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB;
>> Composite NTSC)
>>
>> I am not really sure what color spa
On 8 Mar 2014, at 4:12 pm, Trygve Inda wrote:
> I get the same times doing it this way, but maybe my color spaces are
> different. The CGImage returned from my AVAsset is:
>
> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB;
> Composite NTSC)
>
> I am not really sure what color space to pass in
Just a follow up...
I modified the color space with:
[canvasImageRep
bitmapImageRepByConvertingToColorSpace:[[[NSColorSpace alloc]
initWithCGColorSpace:colorSpace] autorelease]
renderingIntent:NSColorRenderingIntentDefault];
I still get the same times to place 20 images in a 4x5 gri
>
> On 8 Mar 2014, at 2:38 pm, Trygve Inda wrote:
>
>> Profiling this shows lots of time (90%) is spent in drawInRect and it takes
>> about 2 seconds to run. Is there a better way to do this that is faster?
>>
>> Maybe keep everything in CG and only convert to NSImage at the end?
>
>
> Sounds
Hi Noah, just a couple of early observations
On 8 Mar 2014, at 3:26 pm, Noah Desch wrote:
> Graham, I’d be glad to see how it performs with your additional test cases.
> Although I spent quite a bit of time handling special cases this is very much
> a work in progress and I appreciate any
>There is, but, first of all, why does this external tool terminate?
> What is it?
I'd like it to work with md5, ffmpeg and others. These all work fine, but
quit after returning their data.
T.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.co
Graham, I’d be glad to see how it performs with your additional test cases.
Although I spent quite a bit of time handling special cases this is very much a
work in progress and I appreciate any help anyone is willing to throw in.
I didn’t follow a specific algorithm, although much of the cubic
On 8 Mar 2014, at 2:38 pm, Trygve Inda wrote:
> Profiling this shows lots of time (90%) is spent in drawInRect and it takes
> about 2 seconds to run. Is there a better way to do this that is faster?
>
> Maybe keep everything in CG and only convert to NSImage at the end?
Sounds like you answer
On 8 Mar 2014, at 2:24 pm, Noah Desch wrote:
> ’ve written a category on NSBezierPath that allows boolean operations on
> paths (union, intersection, subtraction) which preserves curved elements
> throughout the operation and does not require "flattening" paths into line
> segments prior to p
I need to composite/tile about 20 images in a 4x5 grid to one image.
Currently I do:
NSImage* canvas = [[[NSImage alloc] initWithSize:NSMakeSize(canvasWide,
canvasHigh)] autorelease];
[canvas lockFocus];
Loop
{
... Get the CGImage which comes from an AVAssetImageGenerator
frameImage =
On Mar 7, 2014, at 7:24 PM, Noah Desch wrote:
>
> I’ve written a category on NSBezierPath that allows boolean operations on
> paths (union, intersection, subtraction) which preserves curved elements
> throughout the operation and does not require "flattening" paths into line
> segments prior
I’ve written a category on NSBezierPath that allows boolean operations on paths
(union, intersection, subtraction) which preserves curved elements throughout
the operation and does not require "flattening" paths into line segments prior
to processing.
I thought this might be a generally useful
On 2014 Mar 07, at 18:04, Trygve Inda wrote:
> My app sometimes needs to call an external tool that runs via NSTask and
> delivers text output back to my app. I profiled it and most of the time
> (30%) is spent in [NSConcreteTask launchWithDictionary]
>
> Is there any technique I can use to kee
Sixten is correct about -isDeleted. It is rarely useful.
Regarding these two kinds of managed object faults, your “second” kind is
similar to what I described in a message I posted earlier today [1]. In my
case,
-isFault returns NO
-isDeleted returns NO
-retainCount returns +1 or greater
-g
My app sometimes needs to call an external tool that runs via NSTask and
delivers text output back to my app. I profiled it and most of the time
(30%) is spent in [NSConcreteTask launchWithDictionary]
Is there any technique I can use to keep this running and thus not have to
relaunch it the next t
Not as I recall, but it's worth noting that isDeleted only returns YES
between the time that a managed object is marked for deletion, and when
that change is committed. After that, it returns NO (which kind of sucks).
The managedObjectContext will also be nil at that point (though that CAN
happen i
On Mar 7, 2014, at 13:44 , Sixten Otto wrote:
> FWIW: trying to access a managed object that has been deleted, but to which
> something still has a reference, can produce symptoms like the second kind of
> access you describe.
Even the isDeleted property?
>
> Sixten
>
>
> On Fri, Mar 7, 2
FWIW: trying to access a managed object that has been deleted, but to which
something still has a reference, can produce symptoms like the second kind
of access you describe.
Sixten
On Fri, Mar 7, 2014 at 2:21 PM, Rick Mann wrote:
> It seems that objects can be faulted in two ways. In the firs
It seems that objects can be faulted in two ways. In the first, an access will
load the data and things are fine. In the second, an access results in a crash
because the fault could not be fulfilled.
Is there a way to tell these two apart?
--
Rick
signature.asc
Description: Message signed
I have a situation in which -[NSManagedObjectContext save:] is crashing. I
think what's happening is this:
Main MOC creates a "Foo".
Child MOC A gets a copy of that Foo and hangs on to a reference to it, doing
some asynchronous work (uploading it).
Child MOC B gets a copy and deletes it, saving
On Mar 7, 2014, at 8:50 AM, Kyle Sluder wrote:
> On Mar 7, 2014, at 4:54 AM, Bill Cheeseman wrote:
>>
>> My code calls -[NSArray objectAtIndex:]. I compile it with Xcode 5.0.2 on OS
>> X 10.9.x Mavericks in a project with the target's Base SDK set to 10.9 and
>> the OS X Deployment Target set
On Mar 7, 2014, at 4:54 AM, Bill Cheeseman wrote:
> My code calls -[NSArray objectAtIndex:]. I compile it with Xcode 5.0.2 on OS
> X 10.9.x Mavericks in a project with the target's Base SDK set to 10.9 and
> the OS X Deployment Target set to OS X 10.7. It works fine when I run it on
> OS X 10.
On Mar 7, 2014, at 4:54 AM, Bill Cheeseman wrote:
>
> My code calls -[NSArray objectAtIndex:]. I compile it with Xcode 5.0.2 on OS
> X 10.9.x Mavericks in a project with the target's Base SDK set to 10.9 and
> the OS X Deployment Target set to OS X 10.7. It works fine when I run it on
> OS X 1
On Mar 7, 2014, at 3:22 AM, Koen van der Drift
wrote:
>
>
>> On Mar 6, 2014, at 10:02 PM, Kyle Sluder wrote:
>>
>>> On Thu, Mar 6, 2014, at 04:25 PM, Koen van der Drift wrote:
>>> Just changing the name of the VC solved it.
>>
>> Well, the old build compiled nib is still sitting in your buil
This message regards my SQLite NSPersistentDocument-based app, which has
adopted Auto Save and Versions but not Asynchronous Saving, legacy
delete/rollback SQLite journaling, built with OS X 10.9 SDK, manual memory
management. Its document data model has a singular “document options” object,
w
On 7 Mar 2014, at 6:54 AM, Bill Cheeseman wrote:
> My code calls -[NSArray objectAtIndex:]. I compile it with Xcode 5.0.2 on OS
> X 10.9.x Mavericks in a project with the target's Base SDK set to 10.9 and
> the OS X Deployment Target set to OS X 10.7. It works fine when I run it on
> OS X 10.9
On Mar 7, 2014, at 4:54 AM, Bill Cheeseman wrote:
> However, when I run it on Mac OS X 10.7 Lion, I get a runtime error claiming
> it encountered an invalid argument, namely, the unrecognized selector
> -objectAtIndexedSubscript:. The NSArray Class Reference notes that
> -objectAtIndexedSubsc
My code calls -[NSArray objectAtIndex:]. I compile it with Xcode 5.0.2 on OS X
10.9.x Mavericks in a project with the target's Base SDK set to 10.9 and the OS
X Deployment Target set to OS X 10.7. It works fine when I run it on OS X 10.9
or OS X 10.8.
However, when I run it on Mac OS X 10.7 Lio
On Mar 6, 2014, at 10:02 PM, Kyle Sluder wrote:
> On Thu, Mar 6, 2014, at 04:25 PM, Koen van der Drift wrote:
>> Just changing the name of the VC solved it.
>
> Well, the old build compiled nib is still sitting in your build
> products, so it didn't really "solve" anything.
I agree - so is the
33 matches
Mail list logo
