KnobMan/SkinMan Examples

[Hlis93]

My latest design of my upcoming dual phaser:


(Took me more than one complete day )

I like that font.

question, do you get blurs on the horz line on the fader when you slide it. I've found that when I do such things with knobman there is a bluring, the lines do not stay consistant, even when I re-import as a static image and animate that. I'm sure there are a dozen reason just something I noticed and thought I'd ask others if they've encountered the same issue.

not about how long it takes...just that you like it when it's done

[WOK]

I like that font.

Just the font?

question, do you get blurs on the horz line on the fader when you slide it. I've found that when I do such things with knobman there is a bluring, the lines do not stay consistant, even when I re-import as a static image and animate that. I'm sure there are a dozen reason just something I noticed and thought I'd ask others if they've encountered the same issue.

Yes, I can see it at the thin lines. If I make the slider bigger, it disappears (until I make the steps smaller to increase the number of lines, then it comes back)
Seems to have to do with the antialiasing that is not constant when the lines are thin and too close, so that one pixel moving on the screen make the lines jump exactly to the next (dif. antialiased) gap.

[Branis]

If the step number equals the fader path length in pixels there should be no blurring. I guess also if the path size in pixels can be divided by the number of steps no blurring will occur.

[WOK]

If the step number equals the fader path length in pixels there should be no blurring. I guess also if the path size in pixels can be divided by the number of steps no blurring will occur.

I just tried setting position from 1 to 60 and rendering 60 frames, but the lines still change their look when moving, until I set zoom of this element to 100% !

[Branis]

I succeded in animating a pixel perfect fader, but only after I imported an image.
Here is the knob file
Here is the exported png

[Hlis93]

I like that font.

Just the font?

question, do you get blurs on the horz line on the fader when you slide it. I've found that when I do such things with knobman there is a bluring, the lines do not stay consistant, even when I re-import as a static image and animate that. I'm sure there are a dozen reason just something I noticed and thought I'd ask others if they've encountered the same issue.

Yes, I can see it at the thin lines. If I make the slider bigger, it disappears (until I make the steps smaller to increase the number of lines, then it comes back)
Seems to have to do with the antialiasing that is not constant when the lines are thin and too close, so that one pixel moving on the screen make the lines jump exactly to the next (dif. antialiased) gap.

not just the font.

I've tried making sure they only move one pixel as best I can but I still found the blurring as well. I guess I could do it in psd by hand but I rather not.

[chuck death]

If the step number equals the fader path length in pixels there should be no blurring. I guess also if the path size in pixels can be divided by the number of steps no blurring will occur.

I just tried setting position from 1 to 60 and rendering 60 frames, but the lines still change their look when moving, until I set zoom of this element to 100% !

Think about it, that's exactly what should happen. To get non blurred lines you have to set your number of frames to the same number as the difference between the the lines origin and destination. So, if you want a slider to move 25 pixels you have to set the number of frames to 25 (or 26, depending on whether or not you included your original frame in your line movement count). That way the line falls exactly within one pixel on each frame. If you change the zoom, the distance between origin and destination changes. At 80% the line is now only moving 20 pixels meaning that the line will no longer fall exactly within one pixel.

The important factor is that no matter what size you are working with the number of frames must be set to exactly the same as the number of pixels the line moves on screen at your final resolution.

[WOK]

Think about it, that's exactly what should happen. To get non blurred lines you have to set your number of frames to the same number as the difference between the the lines origin and destination. So, if you want a slider to move 25 pixels you have to set the number of frames to 25 (or 26, depending on whether or not you included your original frame in your line movement count). That way the line falls exactly within one pixel on each frame. If you change the zoom, the distance between origin and destination changes. At 80% the line is now only moving 20 pixels meaning that the line will no longer fall exactly within one pixel.
The important factor is that no matter what size you are working with the number of frames must be set to exactly the same as the number of pixels the line moves on screen at your final resolution.

I doubt the zoom is the reason, because I am just talking about the zoom % of the element. This is independend from position and movement in Knobman. If I make a circle and set it to move from Y -20 to Y +20 it will move this distance, regardless I set it to 50% or 20% size (that's the % in relation to the size of the whole graphic in knobman).
But I realized something else: I forgot that the movement position is set in % not pixel. So when I set the movement to 0% > 100% and set the number of frames the same than the size of the whole graphic, the slider moves one pixel per step and thus there's no blur. If it's set to 0% > 50% than the number of frames must be half of the size in pixel and so on.
My slider has a vert. size of 118, the knob moves from Y -31 to +29 (%), so 60% of 118 is 70.8 , and with 71 frames there is no blur any more (hurray!)

[Hlis93]

good.

[WOK]

[chuck death]

Think about it, that's exactly what should happen. To get non blurred lines you have to set your number of frames to the same number as the difference between the the lines origin and destination. So, if you want a slider to move 25 pixels you have to set the number of frames to 25 (or 26, depending on whether or not you included your original frame in your line movement count). That way the line falls exactly within one pixel on each frame. If you change the zoom, the distance between origin and destination changes. At 80% the line is now only moving 20 pixels meaning that the line will no longer fall exactly within one pixel.
The important factor is that no matter what size you are working with the number of frames must be set to exactly the same as the number of pixels the line moves on screen at your final resolution.

I doubt the zoom is the reason, because I am just talking about the zoom % of the element. This is independend from position and movement in Knobman. If I make a circle and set it to move from Y -20 to Y +20 it will move this distance, regardless I set it to 50% or 20% size (that's the % in relation to the size of the whole graphic in knobman).
But I realized something else: I forgot that the movement position is set in % not pixel. So when I set the movement to 0% > 100% and set the number of frames the same than the size of the whole graphic, the slider moves one pixel per step and thus there's no blur. If it's set to 0% > 50% than the number of frames must be half of the size in pixel and so on.
My slider has a vert. size of 118, the knob moves from Y -31 to +29 (%), so 60% of 118 is 70.8 , and with 71 frames there is no blur any more (hurray!)

Ah, I misunderstood what you meant with the zoom but I was at least correct about what was causing your blurring i.e. number of frames must exactly equal number of pixels moved.

[WOK]

My latest plugin (info here )



(Knobs inspired as usual by HLIS )

[Hlis93]

The look pretty good WOK, did you do those is knobman only?


Anyway, if one has reaktor they can dl the the ens that I stalled those graphic seen in the pic or read some of my rather uncharming ranting here: http://www.native-instruments.com/forum ... p?t=107583

I'll take a look to see if I can find the source files for those for anyone that might be interested. Did the knobs and background in Silo and the renders/editing in psd because I just upgraded to CS4 and wanted to see what it could do with the 3D which wasn't all that impressive...should have waited a month and upgraded to CS5...oh, well.

[WOK]

The look pretty good WOK, did you do those is knobman only?

Yes, that's all skinman/knobman (with some textures).
Took the knobs for it I made before after seeing your 3D-try at your page (thought it would be from a rendering software; does Photoshop 3D - I didn't know ?) - wanted to try wether it's possible in knobman, but knobman has difficulties to get these "shiny effects" - it always becomes too "silky".

[Hlis93]

Photoshop extended has 3D in so far as you can import things like .obj file, or use some privative shapes they provide, add in textures, etc and do some lighting. It appears they are spending a bit more time with it in CS5 update. As far as CS4 extended my impression is to get a serious render you still need to work it out in something that does 3D like Blender, but it does make for nice testing and it doesn't suck being able to drop .obj into a project. But I am no expert not even a decent novice with 3D.