KVR Audio

brok landers · Post by **brok landers** » Tue Mar 10, 2009 11:44 pm

i'm starting to worry here ... g200kg, are you all good? alive? no trouble?
say something so we know!

g200kg · Post by **g200kg** » Fri Mar 13, 2009 3:47 pm

brok landers wrote:i'm starting to worry here ... g200kg, are you all good? alive? no trouble?
say something so we know!

Thank you for your concern.
Sorry but I'm currently shocked and busy due to a bereavement.
Anyway I'm fine.

brok landers · Post by **brok landers** » Fri Mar 13, 2009 3:55 pm

hi g200kg,

ahhh, what can i say ... i feel sorry for you, my condolences towards you and whomever it deserves ... it's always hard if some beloved person dies ...

hope to see you back recovered asap ...
wish you all the best!

Leslie Sanford · Post by **Leslie Sanford** » Fri Mar 13, 2009 9:14 pm

g200kg wrote:Sorry but I'm currently shocked and busy due to a bereavement.
Anyway I'm fine.

I'm sorry to hear that, g200kg. My thoughts and best wishes are with you.

brok landers · Post by **brok landers** » Sat Apr 04, 2009 2:31 pm

a master bump for this thread to stay up ...
are you ok, g200kg?

brok landers · Post by **brok landers** » Wed Apr 29, 2009 8:04 pm

come on, g200kg, make some noise so we know you're allright ...
don't let this die ...

grimtraveller · Post by **grimtraveller** » Wed May 13, 2009 6:06 am

ok, I've seen the app and it looks interesting.
But How exactly can this be used in VST development? It doesn't seem to export the skin to a readily usable format - or did I miss something?

-It seems that I need to write my own .skin file format reader function for my VST. Or am I mistaken?
-Does it export to a readily usable format (C++ code... or other) like knobman?
-How does it simply workflow for VST gui creation other than design mockups?
-Can I do anything tangible aside from mock-ups and bitmap re-export... ?

I'm confused how VST programmers are currently using skinman in its current form. Is it simply a vector drawing tool that can export bitmaps? Or is it more than that?

grim.

bvesco · Post by **bvesco** » Wed May 13, 2009 6:37 am

Typical workflow would be to export a .bmp or .png background and use that as the background texture of your plugin. All the knobs, switches, meters, etc. are separate graphics that are added on their own over top of the background. You don't have to write a .skin reader.

grimtraveller · Post by **grimtraveller** » Wed May 13, 2009 6:51 am

bvesco wrote:Typical workflow would be to export a .bmp or .png background and use that as the background texture of your plugin. All the knobs, switches, meters, etc. are separate graphics that are added on their own over top of the background. You don't have to write a .skin reader.

I understand that it exports bitmaps. but what about all positioning & property data?

brok landers · Post by **brok landers** » Wed May 13, 2009 9:45 am

grimtraveller wrote:
bvesco wrote:Typical workflow would be to export a .bmp or .png background and use that as the background texture of your plugin. All the knobs, switches, meters, etc. are separate graphics that are added on their own over top of the background. You don't have to write a .skin reader.
I understand that it exports bitmaps. but what about all positioning & property data?

skinman provides an insaneley easy way of doing the graphics, that's what it's for. it's not intended to provide the implementation into a plugin.

Hlis93 · Post by **Hlis93** » Wed May 13, 2009 2:24 pm

After using Skinman for a week and assembling several skins. I feel that there are a few things that would like to request that would make working with Skinman much easier…for me at least. It would be very helpful if I could create a swatch menu that can stay visible. It would really help me to keep the colors I want to use organized and consistent. It would also be very useful if I was able to save collections of object so that I could load and re-use them in other projects. I designed a keyboard for use in a plug but I would have to remake the entire keyboard for every project or export it as .png, I would prefer to have it so that I can edit it per project. I might also help if there is a function similar to photoshop's layer styles; I can save the beveling, light setting and direction etc and apply that to another object without changing it position or size. It would also be helpful is I can set up the export to image to only capture a portion of the GUI, not like a crop tool it would be non-destructive. This would help me to export areas that might change per a menu selection but allow me to edit it and view it in terms of the whole GUI in place.

duncanparsons · Post by **duncanparsons** » Wed May 13, 2009 2:37 pm

Don't know if it helps you much, but you can edit the .skin file - it's plaintext in an ini-file format.

If you use something like Notepad++ and tell it to read it as an ini file, you can navigate using the function list.. with this you could then fudge a collection of 'inserts' for which you would need to update the [ObjXXXXX] to the IDs you need (integer padded with leading zeroes)

In due course g200kg may implement something, but in the mean time you could put something together.. if you can use a scripting language you may be able to automate it a bit

HTH
DSP

bvesco · Post by **bvesco** » Thu May 14, 2009 6:58 am

grimtraveller wrote:I understand that it exports bitmaps. but what about all positioning & property data?

There is no property or positioning to export. Skinman is for making a skin which is only the background of your plugin. Everything you export is "burned in" which means it is part of the image. There's nothing to position. If you're talking about the knobs then that is a different story. Knobs are not part of the background. Those are a separate thing entirely. While skinman does provide some convenience features so you can see how the knobs will look, it does not provide any implementation for inserting the knobs to your plugin. You have to do that part yourself. All the text and panels and whatnot become part of the image you export.

GaryG · Post by **GaryG** » Thu May 14, 2009 1:31 pm

How do you merge two shapes in Skinman? I'd like to have two overlapping rectangles treated as one object for lighting purposes etc.

I gather it's something to do with Shape+ etc. but selecting that just causes the rectangle to disappear...

Is the Parent functionality involved? I played with that but couldn't see any point to it, I guess I'm missing something.

cheers,
.g

SKINMAN, the new strike by g200kg (early early alpha)