Pierre Jasmin
75
COW Coins
2
Premiere Pro Coins
2
VEGAS Pro Coins
18
RE:Vision Effects Coins
Forum Replies Created
-
Not just to blame Microsoft, Nvidia, AMD, motherboard manufacturers, Adobe, Apple,… let’s add Intel here.
This is sort of “adaptive” overclocking and will generate CPU variations.
There is some controls for that in Advanced Power Settings panel (and I think it can be turned off to see in the bios, however this should result in stable performance between runs but by slowing it down sometimes).
-
I see someone else on the thread you refer has the issue even with Power Management on
– Try the same with the nVidia Power Settings (in 3D settings)
Other things to try to see for trouble shooting:
– start a long render and disconnect the monitor cable from the computer (then windows won’t think the screen has not been refreshed for some amount of time…) and see if it makes a difference in time it took to render.
– other troubleshoot idea: set the fan to manual so it’s always on. Run test, any differences… actually this test only works if you can have a previous install to compare against (to see if this slows down the previous version).
– overclocking will require a larger power block
– note: depending on how things are internally implemented you do loose CPU compute power when processing with GPU as there is some thread management involved in controlling the gfx card. It’s much more significative on a quad core then on a 12 cores say I noticed.
– I haven’t tried recently (don’t have dot 0.2 installed) but try to see if there is a difference setting the memory Preferences in Premiere to Favor Memory. This sometimes helped in the past to go faster.
Pierre
-
Did you try just setting Power Options to High performance?
Control PanelAll Control Panel ItemsPower Options
I have seen this on another app with an ASUS motherboard and Sandy Bridge chips and AMD 7970 gfz running some other app, over 30% slowdown using Balanced Plan…
Pierre
-
It looks like it as per this description. You can always use the version of RSMB for now that works without motion vectors, that is works by estimating the pixel motion from the video itself. Although RSMB+Vectors for flat/low-textured graphics works sometimes more accurately from vectors rendered from the 3D system, many people are happy with just good old regular RSMB.
I remember that earlier this year I did file on the blender developer list an offer to help out someone who knows blender code base, but no one has answered.
Pierre
-
It looks like it as per this description. You can always use the version of RSMB for now that works without motion vectors, that is works by estimating the pixel motion from the video itself. Although RSMB+Vectors for flat/low-textured graphics works sometimes more accurately from vectors rendered from the 3D system, many people are happy with just good old regular RSMB.
I remember that earlier this year I did file on the blender developer list an offer to help out someone who knows blender code base, but no one has answered.
Pierre
-
This is definitely not XY raster space motion as RSMB expects.
I cannot find the explanation anymore about what these channels are. I see some vague reference about orientation and speed but looking at your example file, that does not look like that.
I cannot quite tell which of the 3 channels is speed and which is orientation as if you look at it, they all have large areas of black in them, perhaps it’s being clipped by the 8 bit image. If you can render the vec image in floating point and the color image with an alpha channel, and see in an app like AE in a 32b float project that the 0 are under 0.0… if 2 of them are speed x and y, there might be a way, else feel free to play with SmoothKit Directional Per Pixel with Dir Source Interp to Orientation or Direction (if spread over two channels) and Len Mode would be like Speed. But again that you have full on white or black large areas is an indication that it’s not motion that is encoded here.Pierre
-
This is definitely not XY raster space motion as RSMB expects.
I cannot find the explanation anymore about what these channels are. I see some vague reference about orientation and speed but looking at your example file, that does not look like that.
I cannot quite tell which of the 3 channels is speed and which is orientation as if you look at it, they all have large areas of black in them, perhaps it’s being clipped by the 8 bit image. If you can render the vec image in floating point and the color image with an alpha channel, and see in an app like AE in a 32b float project that the 0 are under 0.0… if 2 of them are speed x and y, there might be a way, else feel free to play with SmoothKit Directional Per Pixel with Dir Source Interp to Orientation or Direction (if spread over two channels) and Len Mode would be like Speed. But again that you have full on white or black large areas is an indication that it’s not motion that is encoded here.Pierre
-
It’s better you contact techsupport at revisionfx.com
If you hit the support button at the top of our website and then the contact form, it will send you a way to ship to us a project to see.
I am unclear if you mean the whole screen (then memory issue?) or the viewer. If the viewer there might be an issue with the MV themselves. For example if there is no alpha channel in the MV it could throw pixels off the screen… Hard to say blindly.
Pierre
-
It’s better you contact techsupport at revisionfx.com
If you hit the support button at the top of our website and then the contact form, it will send you a way to ship to us a project to see.
I am unclear if you mean the whole screen (then memory issue?) or the viewer. If the viewer there might be an issue with the MV themselves. For example if there is no alpha channel in the MV it could throw pixels off the screen… Hard to say blindly.
Pierre
-
It’s not listed right now (same with Combustion, also delisted) but should/might still work.
Pierre