I use Arch Linux. OpenEXR and OpenImageIO is provided by the system, so I
don't understand why the script compiles them on your machine. It
shouldn't.
When libraries are updated via system update, it is not always enough to
run 'make clean; make' but instead remove your build_linux dir, and run
to set some things up (disable
fstop in the camera and set up comp nodes). The scene is build to scale and
camera matches my real one.
http://www.pasteall.org/blend/35139
Best regards
Ejner Fergo
On Sun, May 17, 2015 at 9:57 AM, Jeroen Bakker j.bak...@atmind.nl wrote:
Hi all,
just a small
As I see it, the f-stop value in the defocus node has nothing to do with
what f-stop is in Cycles (and in reality). This value in the defocus node
is a purely creative tool, and as such should stay, but the name should
change to focal blur so it is not confused with the concept and mechanism
of
? Is that correct?
It is because the normal camera presets and tracking camera presets are
different. Both dimensions are present in the normal camera, while the
tracking camera only uses the width. It would be cool if the two presets
could be consolidated though, if possible.
/Ejner Fergo
On Mon
I don't think the tracking algorithm uses the sensor height, but as I
mentioned, the normal camera presets in the properties editor does show
both sensor width and height (horizontal/vertical sensor fit), for
calculating the horizontal and vertical FOV.
Here's the presets for the original BMCC:
Hola all,
I know the plan is to eventually do the script in python, but in the
meanwhile I touched up on the install_deps script.
Main things done is posted on the patch tracker:
http://projects.blender.org/tracker/index.php?func=detailaid=34680group_id=9atid=127
but quickly the main things are
Sorry I forgot to mention that building OIIO 1.1.7 fails to build on 32bit
distros! Didn't know what to do about that.. :-/
The script is tested and works on 64bit distros though.
/Ejner
On Mon, Mar 18, 2013 at 8:28 PM, Ejner Fergo ejner...@gmail.com wrote:
Hola all,
I know the plan
Hi again,
I got RPM to compile with scons, by adding 'rt' in this scons config option:
LLIBS = ['util', 'c', 'm', 'dl', 'pthread', 'stdc++', 'rt' ]
I also forgot to mention yesterday another caveat compiling with scons: No
OSL or OpenCOLLADA... couldn't get them to work :-/ Compiling with cmake
, 2013 at 11:21 AM, Ejner Fergo ejner...@gmail.com wrote:
Ok, so you are saying numpy build and opencollada option should be removed
again?
Numpy is RC because that is the only thing that can build using python 3.3
In any case, it seems Bastien will port the script to python, so if you
feel like
for
this script..
Bastien, look fine for me. If you could do quick tests guess patch could be
commited.
On Thu, Jan 10, 2013 at 4:23 PM, Ejner Fergo ejner...@gmail.com wrote:
Hi again Sergey and Bastien!
Well I kept hacking and testing the script, even if it will be replaced
eventually
Ok, so you are saying numpy build and opencollada option should be removed
again?
Numpy is RC because that is the only thing that can build using python 3.3
In any case, it seems Bastien will port the script to python, so if you
feel like reverting be my guest...
On Fri, Jan 4, 2013 at 8:02
to activate something (panel, dropdown) to get my info.
It need to be seen with a quick glance, and this patch helps with that, IMO.
Best regards and happy holidays,
Ejner Fergo
On Sun, Dec 23, 2012 at 7:30 PM, Tobias Oelgarte
tobias.oelga...@googlemail.com wrote:
Hi,
As long icons aren't
Hola,
Spend some time fighting with PNG textures not working in Cycles using
Blender-SVN under Fedora 17, getting this error:
libpng warning: Application built with libpng-1.2.27 but running with 1.5.10
and think I know the problem now. Found this update from DingTo:
easier compilable than
continuing maintaining pre-compiled libraries from our side.
On Mon, Sep 24, 2012 at 1:45 AM, Ejner Fergo ejner...@gmail.com wrote:
Hola,
Spend some time fighting with PNG textures not working in Cycles using
Blender-SVN under Fedora 17, getting this error:
libpng
Nice and useful, thanks!
nice, however feels a bit stepped
Maybe a tiny bit, but much better than using scroll!
On Wed, Mar 7, 2012 at 7:45 PM, Daniel Salazar - 3Developer.com
zan...@gmail.com wrote:
nice, however feels a bit stepped
Daniel Salazar
patazstudio.com
On Wed, Mar 7, 2012 at
lens that is very fast (F/1.4) and
will make new test images that will hopefully be a bit more
scientific and useful for documentation.
Hope you will find this as useful as I do!
Best regards,
Ejner Fergo
___
Bf-committers mailing list
Bf-committers
Hola,
I have updated the io_import_fbx.py script in addons_contrib. Diff here:
http://projects.blender.org/tracker/?group_id=9atid=127func=detailaid=27317
This imports the correct camera properties from FBX: Focal length,
Sensor sizes and Film offset.
Tested with FBX 2010 files from Maya and
Hi Campbell,
Thank you for committing the patch!
I've been looking more into the (local) rotation problem in Nuke
Houdini. Turns out a small change is needed on line 404, but the
change is also needed for lamps, so posted the changes here:
http://www.pasteall.org/26478
Basically Vector((0.0,
) works
with these mp4's, so I'm wondering if the official Blender ffmpeg will
be updated before 2.61?
Thanks!
Best regards,
Ejner
On Thu, Oct 20, 2011 at 6:25 PM, Ejner Fergo ejner...@gmail.com wrote:
Hi Dalai,
First of all I'm sorry for my lack of action, and only now replying.
I updated my
, Campbell Barton ideasma...@gmail.com wrote:
On Thu, Nov 17, 2011 at 4:28 AM, Ejner Fergo ejner...@gmail.com wrote:
Hi Campbell,
Thank you for committing the patch!
I've been looking more into the (local) rotation problem in Nuke
Houdini. Turns out a small change is needed on line 404
no not all of them start at 1. starting at zero makes as much sense IMO
Fair enough, I don't have access to every FBX aware app. I just
assumed that frame 1 is standard in DCC apps, especially since Maya
has changed to 1 (only app I know that used to start at 0). Just out
of curiosity what app
On Thu, Nov 17, 2011 at 12:55 AM, François T.
francoistarl...@gmail.com wrote: Maya is not locked to 1, if you
set a background sequence, it will sync up to the frame number (if
started at zero Maya will start there as well)
The version of Maya I have access to (2011) does not change frame
range
Hola,
Despite some recent changes to the FBX exporter, it still didn't
export the correct focal length. I fixed this and also worked out how
to export the film offset (shift_x/shift_y) correctly.
Tested on Maya, Nuke and Houdini. Patch is here:
Instead of being in the N panel couldn't the reconstruction display
options be moved to the camera properties display options? This seems
a more natural place for accessing this.
I don't mind the terminology in general, but can see how some may
think it's complex. I definitely don't need to know
- try the patch showed here:
http://projects.blender.org/tracker/index.php?func=detailaid=25634group_id=9atid=498
- cross your fingers and hope ffmpeg devs fix that any soon (not sure how to
report bugs for them though).
--
Dalai
2011/9/2 Ejner Fergo ejner...@gmail.com
Hola,
I'm having
Pretty cool :)
I know this is early but shouldn't it be called View Frustum Culling
or something like that?
Also could the darkened area be a display option for the camera (could
be called Field of View) since the cameras clipping distance is
used, and not the 3D Views. The option in View3D
Hi François,
It is like a backdrop node. See here (last point):
http://wiki.blender.org/index.php/User:Phonybone/Particles2010
Also a +1 here for the Reroute node. Btw what does This sub-menu will
not be visible on screen mean? The Frame node could also live in this
Helper sub-menu.
Best
On my Ubuntu 11.04 laptop I use FFMPEG 0.8.2 so same as you, and on my
Gentoo system it is version 0.7.3 (don't know how long the 0.7 series
will work still, or when 0.8.x will be a hard dependency).
I can't tell from your output what the problem is. Do you use Scons
and have you tried a 'scons
Hi Matt,
I'm really happy that you have the time to look at this. Thank you.
As far as I can see right now from a cursory glance, all that's
needed is to make blender's internal camera respect the vertical/horizontal
FOV settings
Is this the viewport camera User Perspective, or will this
Hola,
I have updated the patch to rev. 37468
I have also made some simple example .blend files to those of you who
want to see how it works:
http://dl.dropbox.com/u/11299813/cam_match_examples.zip
@Lars
Hi again!
Yes, it does: The sensor size that is currently fixed at 32 units. Otherwise
far made
good progress on FBX and .chan and will do my best to make every
script having to do with cameras work with this new code.
Best regards,
Ejner
On Wed, Apr 27, 2011 at 9:08 AM, Martin Bürbaum
martin.buerb...@gmx.at wrote:
Ejner Fergo ejner...@gmail.com wrote:
I am of course hopeful to see
not actully areas of code i've been working before so
patch should be reviewed by somebody more familiar with this areas.
I could only say that functionality looks useful for me (due to my
camera-tracking related job atm) and i haven't noticed serious issues
with code style.
Ejner Fergo wrote:
Hola
five years and never had problems. Just enter the
correct scale for the calibration object and you're done.
Original-Nachricht
Datum: Mon, 30 May 2011 17:48:05 +0200
Von: Ejner Fergo ejner...@gmail.com
An: bf-blender developers bf-committers@blender.org
Betreff: Re: [Bf
Hi Peter,
It fixed the previous error, but then this happened:
Compiling == 'VideoFFmpeg.cpp'
source/gameengine/VideoTexture/VideoFFmpeg.cpp: In member function
‘int VideoFFmpeg::openStream(const char*, AVInputFormat*,
AVFormatParameters*)’:
source/gameengine/VideoTexture/VideoFFmpeg.cpp:181:24:
I get this error in scons on Ubuntu 11.04 64bit and Fedora 13 32bit
with revision 36941:
Compiling == 'writeffmpeg.c'
source/blender/blenkernel/intern/writeffmpeg.c: In function ‘start_ffmpeg_impl’:
source/blender/blenkernel/intern/writeffmpeg.c:758:2: error: implicit
declaration of function
Really nice to see this finally in Blender, many thanks Campbell!
During my short testing I only found a bug with Auto Perspective
enabled, then it doesn't work. But you are probably aware of this
already.
Best regards,
Ejner
On Sat, May 14, 2011 at 10:01 PM, Damir Prebeg
from Ejner Fergo I'm
wondering what the percentage chance we can see this appear in trunk?
http://projects.blender.org/tracker/?func=detailatid=127aid=24427group_id=9
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org
Hi,
I loaded up my last camera projection scene, taken with an EOS 50D
(APS-C sensor). Before, I found the correct hfov using the BLenses
script in Blender 2.4x, which I then matched geometry against in 2.5x.
But this would give me a focal length based on the default Blender
sensor size (32x18),
Hola all,
I have updated Matt Ebb's patch for adjustable camera sensor sizes.
There's also a few changes of my own, so now it is possible to get/set
the vertical FOV (mostly important for import/export).
Link:
http://projects.blender.org/tracker/?func=detailatid=127aid=24427group_id=9
With this
39 matches
Mail list logo
