AmpGUI DP Themes (now at AMPGUIMODS.NET)

[jimagine]

Poifect thanks, I'm impressed you got the whole supplemental folder thing happening so quick. And thanks for the additional features.

[amplidood]

Fixed the InfoBar mixer strip color mismatch. Updated files on site.

[amplidood]

I'm updating these in order loosely based on requests. If you've got a version you want updated soon, speak up!!

[jimagine]

I don't tend to get all gushy over this stuff but I've got to throw a little praise around re the Amplimods, even if It's preaching to the choir on this thread.

I'm probably not unique in that I'm on of those who skipped the 6 upgrade, mostly because of too many ongoing projects and too many other changes to deal with when everything was working perfectly in the studio.

We just finished a new room and installed all new everything, so I finally leapfrogged to DP7. I was aware of the GUI discussion but honestly was surprised at how much it didn't work for me...especially on a big, bright new 2560x1440 monitor.

Well, the new 7.1 Amplidood tweaks are really nice. I happened to settle on Overcast as my look, but by adding things like the green lit faders from Sleek, the blue reveal pan knobs from Night, and some little color tweaks and stuff, I've created kind of an ideal personalized space...it's really the best GUI i've seen from Logic to Pro Tools.

That's something, given what it looks like if I flash back the original GUI.

Part of my biz is a design firm and I learned early on there's no such thing as a perfect look - especially with something as personal and intensely used as a GUI like this. What the Dood did is create a number of superior looks. But I would look at one and say, too bad he didn't use the green light behind these faders, or I like the blue reveal on the pan pots but not such a dark background.

So I created a best of Amplidood melange, a Goldilocks just right GUI porridge if you will.

So I say to the Dood, "sometimes you eat the baar and sometimes the baar eats you"...no, no, that's the other dude.

I say, keep developing and refining, and make a modular system so people can easily do what I did. That would be invaluable to a lot of folks, and I think unique in the biz. Most importantly there should be a way to make it a successful biz model for him...you...whoever I'm talking to here. Maybe make the next upgrades a separate release

Anyway, you have a great concept and product and those things should be encouraged and rewarded in 'merca (subcontinent, Asia etc.) so you can keep developing them.

Man that was strong coffee.

[Shooshie]

Suggestion, Amplidood (after a heartfelt thank you for the work -- another donation coming soon): might you consider renumbering your output with matching numbers of MOTU products? Thus, gold 3.2 for 7.1 could be "GOLD 7.1/3.2." It would eliminate a lot of "for version 7.1 only," and similar qualifications. You might even think of a more streamlined approach after you begin with the DP version number.

It would completely eliminate all questions like "does Jade 1.1 work with 7.02?"

Just a thought. It won't matter to me which way you do it, but I thought I'd share the idea.


Shoosh

[amplidood]

Suggestion, Amplidood (after a heartfelt thank you for the work -- another donation coming soon): might you consider renumbering your output with matching numbers of MOTU products? Thus, gold 3.2 for 7.1 could be "GOLD 7.1/3.2." It would eliminate a lot of "for version 7.1 only," and similar qualifications. You might even think of a more streamlined approach after you begin with the DP version number.
It would completely eliminate all questions like "does Jade 1.1 work with 7.02?"
Just a thought. It won't matter to me which way you do it, but I thought I'd share the idea.
Shoosh

It's a good idea. I think basically the simplest thing to do is start over at 1 for every version of DP that comes out. AmpGUI Simple 7.1 v1, v2, v3 and so on, as high as it needs to go.

[KEVORKIAN]

It's a good idea. I think basically the simplest thing to do is start over at 1 for every version of DP that comes out. AmpGUI Simple 7.1 v1, v2, v3 and so on, as high as it needs to go.

I like this idea.

[KEVORKIAN]

I say, keep developing and refining, and make a modular system so people can easily do what I did. That would be invaluable to a lot of folks, and I think unique in the biz.

This is a cool idea. I like the mods however you make them, but I wonder... now that you can group the image files to a sub-folder... would it be possible to further group them within that sub-folder? So say you have "Mixer" and "Track Overview" etc. and people will have an easier time mixing and matching? Just an idea.

[amplidood]

I say, keep developing and refining, and make a modular system so people can easily do what I did. That would be invaluable to a lot of folks, and I think unique in the biz.

This is a cool idea. I like the mods however you make them, but I wonder... now that you can group the image files to a sub-folder... would it be possible to further group them within that sub-folder? So say you have "Mixer" and "Track Overview" etc. and people will have an easier time mixing and matching? Just an idea.

It already is sort of a modular system. You just have to look and see what .png's are used where. Perhaps I will create another guide similar to the .xml guide. Available by donation, of course I'm not sure about putting more folders in the Supplemental one. That would be purely dependent on the code DP uses to link to those files in the first place. There is one direction I could go in, however, that would make the whole thing pretty flexible...

A while ago I experimented with giving folks layered files they could load up in Gimp, Photoshop, whatever. That way you could change hues, remove layers you didn't want, and so on. It quickly became hugely cumbersome as I developed more and more versions, however. I decided to scrap it and just continue making different looks. I tend to do my best trying to make everything work as a whole. The more I make, the more individual elements are available for users to mix and match as they see fit, with a lot less fuss.

A big thanks to Shoosh for helping me get clarity on the version system. It had been bothering me and I just didn't seem to have the brain cycles available to fix it. His suggestions got me going in the right direction. Thanks again, man.

[amplidood]

New version system in place for all updated mods... will implement it on the others as I create 7.1 versions.

[sayatnova]

I'm updating these in order loosely based on requests. If you've got a version you want updated soon, speak up!!

Hello,

Any chance for "Nostalgia" for 7.1?...

Thank you very much,

Sayat Nova

[bdr]

Andy, I don't really understand how to use the Default Style Reference that you sent me. For example, I see 'editor content background' listed in the folder, but where in the mod do I go to change that?

If you have mentioned this somewhere else in this post, I must have missed it.

[jimagine]

It already is sort of a modular system. You just have to look and see what .png's are used where. Perhaps I will create another guide similar to the .xml guide. Available by donation, of course I'm not sure about putting more folders in the Supplemental one. That would be purely dependent on the code DP uses to link to those files in the first place. There is one direction I could go in, however, that would make the whole thing pretty flexible...

So far there's no problem. What I do to try different elements is rename the original pngs with a .orig in the supplemental folder and then just option drag from another folder of "Nice GUI" elements that I created. Assuming that it's drawing from the root folder like a standard XTML app then it's just ignoring what isn't in it's code. I've even created sizably larger files in Fireworks and PS (say 200k vs 20k original) that have worked fine.

Anyway, my simple point was going back to when I first found and followed this thread before I upgraded. When people were asking about one subtle change or another, you're response was (paraphrasing) "unfortunately you can't please everyone".

My suggestion of a mod-mod release (with future releases of new design elements) would give you a way to make money, er, ah, donations, doing something really valuable while solving the "you can't please everyone" issue. A good business model.

Hey as a new business consultant, I'd normally be billing you right now <g>.

[jimagine]

For anyone interested here's an image of my Overcast Hybrid. It's a look I evolved through a simple series of changes and restarts.

http://farm5.static.flickr.com/4004/430 ... 6323_b.jpg

I changed the faders, pan pots and elements, control panel and controls and gave muted color to the the Mute/Solo static states as well as a differentiating color to the tab headers and bar. Just subtle things that I liked. It was easy enough for me but the average non-design oriented DP user would probably dig the idea of a simple customizable interface...who wouldn't really?

I don't think it would need to be as complex as layered PS files that grow exponentially Andy. You don't need EVERY option in the world and you've already got nice design elements going.

I'd start with a collection of the core design elements in sub folders separate from the Supp. folder. They could be easily previewed in Finder and swapped in and out to customize your look. Simple things like the Mixer Background could also be a series of choices easily swapped. I know it's not all that simple with the XML files but that could be done pretty simply too.

Again you could make it into a nice business model while offering something really unique - not that what you've already done isn't great, I just want to make you some real money <g>.

[delcosmos]

Andy, the picture of your "Sleek mod" looks with a nice grey background overview, I downloaded the Sleek 7.1 version and the background overview is still white.

BTW, any chance to have the Gold 1.1 for 7.1? that's my favorite!

Best regards.

delcosmos.