On Wed, 8 Jan 2014 20:10:28 +0400
parafin wrote:
> On Fri, 27 Dec 2013 18:27:45 +0100
> Moritz Moeller wrote:
>
> > > I don't have observed issues here. I can change the zoom level and the
> > > center view immediately gets updated. Same if I pan the small rectangle
> > > to change the region o
On Fri, 27 Dec 2013 18:27:45 +0100
Moritz Moeller wrote:
> > I don't have observed issues here. I can change the zoom level and the
> > center view immediately gets updated. Same if I pan the small rectangle
> > to change the region of interest.
>
> Yes, the ROI update is instant on OS X too. Bu
I have not complained earlier but I have had a number of mask problems
which I feel now may have resulted from using reentrants that caused an
overlap of the fade boundary.
David
On 27/12/13 06:32 AM, Ulrich Pegelow wrote:
Can you offer a recipe of how to reproduce the crash? From the backtrac
On 27/12/13 6:20 pm, Ulrich Pegelow wrote:
> No, these are totally independent.
That would be very nice though. This is a common workflow for roto:
start with base shape, then add CVs to match the actual shape better.
For this, it would be so nice if DT finally had context menus (i.e. RMB
on a pa
Am 27.12.2013 18:12, schrieb Moritz Moeller:
> On 27/12/13 6:04 pm, Ulrich Pegelow wrote:
>> Guess I found the cause. Too bad this got only discovered just after the
>> release :/
>
> Well, I think it's not such an issue to do 1.4.1, innit? :D
>
> Btw, is there a way to convert an ellipse path into
On 27/12/13 6:04 pm, Ulrich Pegelow wrote:
> Guess I found the cause. Too bad this got only discovered just after the
> release :/
Well, I think it's not such an issue to do 1.4.1, innit? :D
Btw, is there a way to convert an ellipse path into one consisting of
editable CVs?
Also, there still is
Am 27.12.2013 17:56, schrieb Moritz Moeller:
> On 27/12/13 5:52 pm, Ulrich Pegelow wrote:
>> Some info on the size of the image (w * h) and the rough percentage of
>> area covered by the path would be fine.
>
> The images come from my GH2, so they're RAWs 4752x3168 in size.
>
> I'd say the path I w
On 27/12/13 5:52 pm, Ulrich Pegelow wrote:
> Some info on the size of the image (w * h) and the rough percentage of
> area covered by the path would be fine.
The images come from my GH2, so they're RAWs 4752x3168 in size.
I'd say the path I was trying to edit covered less that 10% of the
image's
Am 27.12.2013 17:35, schrieb Moritz Moeller:
> On 27/12/13 3:32 pm, Ulrich Pegelow wrote:
>> Can you offer a recipe of how to reproduce the crash? From the backtrace
>> I would guess that this happens if the path has a significant portion of
>> self-intersections.
>
> This path had max. 1 self inte
On 27/12/13 3:32 pm, Ulrich Pegelow wrote:
> Can you offer a recipe of how to reproduce the crash? From the backtrace
> I would guess that this happens if the path has a significant portion of
> self-intersections.
This path had max. 1 self intersections (and 4 CVs, I believe to
recall). So far
Can you offer a recipe of how to reproduce the crash? From the backtrace
I would guess that this happens if the path has a significant portion of
self-intersections.
Ulrich
Am 25.12.2013 20:43, schrieb Moritz Moeller:
> I get this crash regularly, when editing path-based masks in 1.4 on OS X
>
Another one. Basically, editing path-based masks on DT 1.4 on OS X is
close to impossible atm, its simply too unstable:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000134825000
VM Regions Near
On 25/12/13 8:43 pm, Moritz Moeller wrote:
> I get this crash regularly, when editing path-based masks in 1.4 on OS X
> 10.9.1:
>
> Thread 7 Crashed:
> 0 libsystem_kernel.dylib0x7fff8a3f9866 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x7fff890c235c pthread_ki
I get this crash regularly, when editing path-based masks in 1.4 on OS X
10.9.1:
Thread 7 Crashed:
0 libsystem_kernel.dylib 0x7fff8a3f9866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7fff890c235c pthread_kill + 92
2 libsystem_c.dylib 0x0
14 matches
Mail list logo
