I've noticed this issue with some images on the latest Radiance 4.2 versions as well.
Greg, the length of the file name doesn't seem to have any effect for me -- the errors remain the same. I've been ignoring the problem, so haven't traced the reason as for why it occurs, but it tends to manifest itself with Radiance images generated in certain atypical ways: (1) HDR photographs and (2) renderings using electric lighting via IES2Rad.
fyi in case anyone was trying to pipe falsecolor / gencumulativesky-generated
pics
through pfilt lately, the same error seemed to occur in this scenario - glad
it'll be cleared up
~Max
···
Greg Ward <[email protected]> hat am 20. Oktober 2014 um 15:43
geschrieben:
Well, pfilt hasn't changed in 4 years and pcond hasn't changed in 8, so my
only remaining guess is that the new way we're calling popen() under Windows
is somehow at fault. This call that was hand-written by Georg Mischler was
recently replaced under Microsoft's Visual-C compiler, and I think the issue
is that I'm not explicitly setting the binary file type in pcond. Schorsch's
win_popen() must have done this for me without my realizing it.
I have checked in the new module and it should get recompiled at some point.
My apologies, and I hope this solves the issue.
In the short term, just use the older version of pcond. It's the same,
anyway.
Cheers,
-Greg
> From: Jan Wienold <[email protected]>
> Subject: Re: [Radiance-general] pcond: error reading from pfilt process in
> fovimage
> Date: October 20, 2014 5:02:09 AM CDT
>
> Hi,
> it must be a Windows problem.
> no problems using mac or linux (head-release 3 weeks ago).
>
> Jan
>
>
> Am 10/20/14, 5:06 AM, schrieb Mostapha Sadeghipour:
>> Hi Radiance community,
>>
>> Anybody else has issue running pcond in recent versions of Radiance? Here
>> is the error.
>>
>> pcond: error reading from pfilt process in fovimage
>>
>> I still have the older version of Radiance (4.2..a) also installed which
>> has no problem with the same image.
>>
>> Here is one of the images which fails. Cloudy sky for Denver:
>> Dropbox - Error - Simplify your life
>>
>> Try pcond -h to reproduce the error.
>>
>> Thanks,
>> Mostapha
>>
_______________________________________________
Radiance-general mailing list [email protected] http://www.radiance-online.org/mailman/listinfo/radiance-general
Well, pfilt hasn't changed in 4 years and pcond hasn't changed in 8, so my only remaining guess is that the new way we're calling popen() under Windows is somehow at fault. This call that was hand-written by Georg Mischler was recently replaced under Microsoft's Visual-C compiler, and I think the issue is that I'm not explicitly setting the binary file type in pcond. Schorsch's win_popen() must have done this for me without my realizing it.
I have checked in the new module and it should get recompiled at some point. My apologies, and I hope this solves the issue.
In the short term, just use the older version of pcond. It's the same, anyway.
I'll try to reproduce the error again when in front of the work machine and let
you know- if I recall correctly I just fed a DIVA-generated HDR (from a
rpict+gencumulativesky run) to pfilt, and it wouldn't eat it. Could not figure
that one out.
m
···
Greg Ward <[email protected]> hat am 20. Oktober 2014 um 16:35
geschrieben:
Umm... maybe not. This is specific to pcond -- I didn't find a similar
oversight in any of the other programs. Can you tell me what command(s) are
giving your errors, exactly?
Thanks!
-Greg
> From: Max D <[email protected]>
> Subject: Re: [Radiance-general] pcond: error reading from pfilt process in
> fovimage
> Date: October 20, 2014 9:21:21 AM CDT
>
> fyi in case anyone was trying to pipe falsecolor /
> gencumulativesky-generated
> pics
> through pfilt lately, the same error seemed to occur in this scenario - glad
> it'll be cleared up
>
> ~Max
>
>> Greg Ward <[email protected]> hat am 20. Oktober 2014 um 15:43
>> geschrieben:
>>
>>
>> Well, pfilt hasn't changed in 4 years and pcond hasn't changed in 8, so my
>> only remaining guess is that the new way we're calling popen() under
>> Windows
>> is somehow at fault. This call that was hand-written by Georg Mischler was
>> recently replaced under Microsoft's Visual-C compiler, and I think the
>> issue
>> is that I'm not explicitly setting the binary file type in pcond.
>> Schorsch's
>> win_popen() must have done this for me without my realizing it.
>>
>> I have checked in the new module and it should get recompiled at some
>> point.
>> My apologies, and I hope this solves the issue.
>>
>> In the short term, just use the older version of pcond. It's the same,
>> anyway.
>>
>> Cheers,
>> -Greg
>>
>>> From: Jan Wienold <[email protected]>
>>> Subject: Re: [Radiance-general] pcond: error reading from pfilt process in
>>> fovimage
>>> Date: October 20, 2014 5:02:09 AM CDT
>>>
>>> Hi,
>>> it must be a Windows problem.
>>> no problems using mac or linux (head-release 3 weeks ago).
>>>
>>> Jan
>>>
>>>
>>> Am 10/20/14, 5:06 AM, schrieb Mostapha Sadeghipour:
>>>> Hi Radiance community,
>>>>
>>>> Anybody else has issue running pcond in recent versions of Radiance? Here
>>>> is the error.
>>>>
>>>> pcond: error reading from pfilt process in fovimage
>>>>
>>>> I still have the older version of Radiance (4.2..a) also installed which
>>>> has no problem with the same image.
>>>>
>>>> Here is one of the images which fails. Cloudy sky for Denver:
>>>> Dropbox - Error - Simplify your life
>>>>
>>>> Try pcond -h to reproduce the error.
>>>>
>>>> Thanks,
>>>> Mostapha
>>>>
>> _______________________________________________
>> Radiance-general mailing list
>> [email protected]
>> http://www.radiance-online.org/mailman/listinfo/radiance-general
>
> _______________________________________________
> Radiance-general mailing list
> [email protected]
> http://www.radiance-online.org/mailman/listinfo/radiance-general
