You need to login to view this content

You can join Blender Studio for €11.50/month and get access to all of our training & film content instantly!

Join Blender Studio

Videos

Data Types

16th August 2017

info License: CC-BY
flag Report Problem

Published by

Sybren A. Stüvel

As discussed before, names refer to objects. Those objects have properties and functionality; what those are and what they can do are determined by the object's type.

  • All Python objects have a type
  • Type determines behaviour
  • Numbers, strings, lists
  • Vectors

Links from the video

The Slides

Slides are only visible to Blender Cloud susbcribers

6 Comments

Join to comment publicly.

Amin Chouana

14th November 2017 - 12:23

Hello ! I love your videos and can't wait to finish this instructive series. Thank you Dr. Sybren ! There's a minor mistake at 5:31: words[1:3] should result ['slicing', 'bread']

Roelant Rijs

10th May 2018 - 18:23

@Amin Chouana: He purposely put that in there to see if we're paying attention :)

Julian Darley

8th November 2020 - 13:19

re 4K resolution mentioned at 4.27: to clarify (citing https://en.wikipedia.org/wiki/4K_resolution), 4K has two general meanings depending on whether delivery is for TV or cinema.

  1. for TV, it is 3840 × 2160 (known as 4K UHD);
  2. for movie projection it 4096 × 2160 (known as DCI 4K; DCI = Digital Cinema Initiatives, which is 'a consortium of major motion picture studios, formed to establish specifications for a common systems architecture for digital cinema systems').

regarding aspect ratios, only 4K UHD is 16:9. the movie version is more complicated, because it can be either 1.9:1 (256:135) for DCI 4K full frame or other ratios depending on how it is cropped. when working with live action (eg blender is used for the scene backplates), it is important to be absolutely sure what resolution the camera is shooting.

Ejnar Brendsdal

28th September 2017 - 09:59

Hey Dr. Sybren. (I just had to use your awesome title) Using these small math snippets in the UI input fields is pure magic. How about keeping the math when pressing enter instead of substituting it with the evaluated result? It would be very useful and go a long way to make inputs behave parametrically.

Sybren A. Stüvel

28th September 2017 - 13:45

@ejnaren: then you get into the domain of drivers, which do exactly that. It's not like that by default, just to keep things simple and performing well. Imagine evaluating these math expressions every time they're needed...

Julian Darley

8th November 2020 - 13:54

at 7.39: delta_location is mentioned. the current entry for this in the API docs is: https://docs.blender.org/api/current/bpy.types.Object.html

the info is the same as shown in the slide. the trouble is, i am none the wiser. if someone can explain what the point of delta_location is and point to some use cases, i would be most grateful.

side note:  if you are looking for info on API matters, make sure you search in https://docs.blender.org/api/current/index.html not the general Blender manual: https://docs.blender.org/manual/en/latest/ - the latter gives no useful results.