Blulite
ive searched but cant find it other then on a video on youtube that points me back to the vdj site for download.
ive checked out some of the photoscape videos but those seem to just be for adding your own personalisation to a premade skin. i need the ability of creating a skin from scratch. ive tried using the v7 skin creator tool but there seems to be no clear guide on how to use it correctly, the videos are all either overlayed with a hardcore track or by silence. so its not exactly easy for follow when your having to watch the video and try to follow at the same time in skin creator.
can any skinners please give me a starting point as i want to build a new skin.
ive checked out some of the photoscape videos but those seem to just be for adding your own personalisation to a premade skin. i need the ability of creating a skin from scratch. ive tried using the v7 skin creator tool but there seems to be no clear guide on how to use it correctly, the videos are all either overlayed with a hardcore track or by silence. so its not exactly easy for follow when your having to watch the video and try to follow at the same time in skin creator.
can any skinners please give me a starting point as i want to build a new skin.
Posté Thu 20 Apr 17 @ 7:30 pm
groovindj
Posté Thu 20 Apr 17 @ 7:39 pm
Blulite
Thanks, Gdj, i was using an early version called "skin creator" as i couldnt for some reason locate the newer versions.
am i correct in thinking i can create the skin in mack but if i want to extract if for use once its complete i have to use skin extractor?
am i correct in thinking i can create the skin in mack but if i want to extract if for use once its complete i have to use skin extractor?
Posté Thu 20 Apr 17 @ 7:55 pm
Blulite
looking at SB v3, am i limited to the elements provided for building skins? or can i use custom elements? im building a skin for the sb2.
Posté Thu 20 Apr 17 @ 7:59 pm
locoDog
Correct you can prototype with the mac but to have a finished skin you'll have to extract with a m$ machine.
Posté Thu 20 Apr 17 @ 8:01 pm
Blulite
locodog wrote :
Correct you can prototype with the mac but to have a finished skin you'll have to extract with a m$ machine.
thats fine as long as i can complete the build from start to finish without having to constantly swap OS.
so about custom elements? can i use them with the v3 skin builder?
Posté Thu 20 Apr 17 @ 8:05 pm
Blulite
eg. this is one of my pads
so how would i incorporate that into my new skin?
so how would i incorporate that into my new skin?
Posté Thu 20 Apr 17 @ 8:08 pm
groovindj
You can't really add your own stuff with (or to) the builder as it stands, but once you've got your end result, of course you can add your own stuff to the graphics and the XML (provided you have the necessary knowledge).
I recently created a skin using the builder, and am gradually customising it as I go along. The fact that the extractor uses the resolution of the screen it's running on was useful, as I wanted a 1366x768 starting point for a laptop skin.
It's a good way of getting something started quickly.
I recently created a skin using the builder, and am gradually customising it as I go along. The fact that the extractor uses the resolution of the screen it's running on was useful, as I wanted a 1366x768 starting point for a laptop skin.
It's a good way of getting something started quickly.
Posté Thu 20 Apr 17 @ 8:13 pm
locoDog
Custom elements will probably have to go in after extraction, (traditional skinning)
On release I was pondering about vdj hosting a user created elements library, although I am completely unaware as to the practicality
On release I was pondering about vdj hosting a user created elements library, although I am completely unaware as to the practicality
Posté Thu 20 Apr 17 @ 8:23 pm
groovindj
One technique I've used before is Frankensteining. Basically pilfering bits from other skins. Skeuomorphism takes time.
Posté Thu 20 Apr 17 @ 8:33 pm
Blulite
ive extracted the files from the virtually pioneer skin so i can get an idea of the element breakdown.
as the skin files has two pictures, one of the separated elements and one of the completed skin preview.
am i right in assuming my skin is built by using the separated elements, written into position by xml, and the preview is the finished product once the unicode is read by the software?
so for example my pad would be scripted into the skin by pointing the builder to the correct element and telling it where it should be placed?
as the skin files has two pictures, one of the separated elements and one of the completed skin preview.
am i right in assuming my skin is built by using the separated elements, written into position by xml, and the preview is the finished product once the unicode is read by the software?
so for example my pad would be scripted into the skin by pointing the builder to the correct element and telling it where it should be placed?
Posté Thu 20 Apr 17 @ 8:36 pm
Blulite
groovindj wrote :
One technique I've used before is Frankensteining. Basically pilfering bits from other skins. Skeuomorphism takes time.
yeah i considered that but the elements i need aren't readily available and i want the skin to look and feel just like the controller, well as best as it can. once i get the basic layout built and the basic functions, ill spend some time tweaking it for a better feel. .
Posté Thu 20 Apr 17 @ 8:39 pm
Blulite
am i also correct in thinking that the wave forms are generic elements that can be resized and repositioned into any skin?
Posté Thu 20 Apr 17 @ 8:45 pm
groovindj
Well if you want your controller duplicated on screen (you won't be able to use the skin builder) then I'd suggest the best method to use is the old skinning technique (VDJ 7 and earlier) rather than the new (VDJ 8) one.
Basically the old method used images of the complete skin. The new method lays the individual pieces over a blank background.
Contrast and compare the BMP in an old skin to the PNG of a new one.
I say go with the old method because you can easily find a high res picture of your controller online, as your starting point.
Basically the old method used images of the complete skin. The new method lays the individual pieces over a blank background.
Contrast and compare the BMP in an old skin to the PNG of a new one.
I say go with the old method because you can easily find a high res picture of your controller online, as your starting point.
Posté Thu 20 Apr 17 @ 8:53 pm
Blulite
groovindj wrote :
Well if you want your controller duplicated on screen then I'd suggest the best method to use is the old skinning technique (VDJ 7 and earlier) rather than the new (VDJ 8) one.
Basically the old method used images of the complete skin. The new method lays the individual pieces over a blank background.
Contrast and compare the BMP in an old skin to the PNG of a new one.
I say go with the old method because you can easily find a high res picture of your controller online, as your starting point.
Basically the old method used images of the complete skin. The new method lays the individual pieces over a blank background.
Contrast and compare the BMP in an old skin to the PNG of a new one.
I say go with the old method because you can easily find a high res picture of your controller online, as your starting point.
thats precisely what i have started with, i have found a high res image, and im extracting elements from it and saving them individually, i will then recompile them into a single image that contains all relevant images, including those i will have to recolour in photoshop so they appear lit up when elements are active or not. i have an older skin creator but im finding it pretty difficult to work out, it appears to only be a selection tool that will give basic xml code determined by the relative position on the picture.
Posté Thu 20 Apr 17 @ 8:57 pm
groovindj
Yeah, if you've got this far then I'd suggest you carry on without the 'tool'.
Just use a good text editor (on PC that's Notepad++) and graphics software, and do it all manually.
You'll learn a lot and be proud that you created a whole skin yourself!
The skin forum is there for any questions.
Just use a good text editor (on PC that's Notepad++) and graphics software, and do it all manually.
You'll learn a lot and be proud that you created a whole skin yourself!
The skin forum is there for any questions.
Posté Thu 20 Apr 17 @ 9:07 pm
Blulite
once i figure out how this tool works i should be ok, as stated earlier, it appears atm to be more of an xml helper than and actual skin builder. but then ive only been using if for about half hour, so what would i know lol
Posté Thu 20 Apr 17 @ 9:34 pm