The MSStyle to WindowBlinds porter manifest.


Recommended Posts

[Dsclaimer: I work for Stardock]

I've been working really hard over the last few months to make your msstyles work with WindowBlinds. As much as you may like or not the idea of your themes being used by WindowBlinds users - the fact is that we've definitely enhanced your audience to users outside Windows XP and those who fear to patch their systems.

Now I do not claim to be undbiassed - should you find more reasons, pro or against porting your skins to WindowBlinds - feel free to leave your comments either on my blog or here.

Now time for the article itself.

Expect the next release of SkinStudio after the New Year improve substantially in accuracy upon the current release - especially the Free one (which is rather old).

[edited] wrong ink!

Edited by SkinStudio
what abt a WBA to MSSTYLES porter ??

I know WB has more functions (shell animation , Toolbar icons etc)

but to make VS`s work u just need to patch uxtheme dll file nothing else

no installation nothing !

585177683[/snapback]

why would they make something to take away the use of their own product...that makes no sense.

what abt a WBA to MSSTYLES porter ??

I know WB has more functions (shell animation , Toolbar icons etc)

but to make VS`s work u just need to patch uxtheme dll file nothing else

no installation nothing !

585177683[/snapback]

Feel free to create your own program if you feel you can do that. They created their own one and do a great job at it. Besides, they worked with Mircosoft to developed the uxtheme and the skinning engine in the 1st place, so it should only make sense that they create a program that takes it to the next level.

I never really liked window blinds, i probably never will. The only theme I actually liked was celia (sp?) by bant. It was a complete theme that wasn't too gaudy or underdone. It was perfect. KoL is another good themer and all of his theme's were useable, because he puts a lot of effort into his work, but since most of his theme's are msstyles i have no use for windowblinds. I just hate the fact that it doesn't skin EVERYTHING as do msstyles.

WindowBlinds does skin a lot more elements of the Windows GUI than msstyles do so there are advantages. The disadvantage (obviously) is that it's not free.

On the otheer hand, msstyles to WindowBlinds have a key importance - Longhorn. When Longhorn comes out, the .msstyles format of today will be history replaced by something completely different so the only way all those msstyles will exist on Longhorn that I can think of is by converting them to a different format.

I never really liked window blinds, i probably never will. The only theme I actually liked was celia (sp?) by bant. It was a complete theme that wasn't too gaudy or underdone. It was perfect. KoL is another good themer and all of his theme's were useable, because he puts a lot of effort into his work, but since most of his theme's are msstyles i have no use for windowblinds. I just hate the fact that it doesn't skin EVERYTHING as do msstyles.

585179975[/snapback]

Actually WB skins more than msstlyes such as the logon/shutdown boxes, animations, toolbars, etc... It does a lot more then msstyles could ever hope to do.

The thing that i found is that with Windows Blinds it is another thing to load at StartUp, which my PC already has trouble with :/

Another reason why i stopped using it was the quality of the themers. I am not into theming, but looking at the quality of themes for WB (on WinCustomize) and them a MSSTYLES site, such as Studio 28 - there is a rather large difference in quality, and useability.

I thought the GUI Olympic's would be a good venture, sorting the useable themes from the ones created by people who look like they never have done it before. BUT, i went on and saw the same sorts of skins. Even some of the premium skins I wouldn't ever use - i would have thought these would be better? :/

If i see more skins like on Studio 28 and GFXOasis (using their Blue one now - its a beaut!) then I would most likely convert back.

I am an object desktop user. Of all the OD apps available, I only use iconpackager. I also use CursorXP and ObjectDock, which are also Stardock products, but not part of OD. I used to use Desktop X, but now I rarely touch it and if I use it at all it's in the form of widgets. Stardock makes some good apps. I won't use windowblinds. Every time there is a new version I try it out, and within minutes I uninstall it. It does skin more things than native visual styles do, but it's glitchy. Windows flicker, sometimes things don't display correctly. Most windowblinds skins suck (I've only ever used 5 of them so far for any limited amount of time, but I've tried hundreds). Ever play a game in windowed mode using windowblinds? Most likely your game window will be using a classic windows border and titlebar. And these problems have been around since Windows XP came out, they should have had them fixed a long time ago, before they started adding other "useless" features like skinning the toolbar buttons and shutdown prompts, etc., which are cool but unnecessary when the software is not already 100% perfect before adding those features. Also, regardless of what anybody at Stardock claims, Windowblinds skins seem to run slower. I have an Athlon 64 3400 and 2 GB of PC3200 RAM, plus a GeForce FX 5700. I shouldn't notice any difference, especially if I have no programs running, yet I do. Should Stardock create a Windowblinds to MSStyles conversion feature in SkinStudio? I think so. They have a better understanding of how the Windowblinds works than any of us ever will, plus they own the format. Who's to say they wouldn't sue somebody if they created such a program? Stardock, at least to me, has always seemed to be about freedom of choice. The truest test of that would be to give us that option. Additionally, even if they didn't add a converter, the ability to create MSStyles as well as Windowblinds skins in Skinstudio would be nice. Sure, TGTSoft has their own little tool for that, but I'd rather be able to use Skinstudio. Now...

You really want me to use SkinStudio? Give me the option to make Trillian skins with it! That feature had been planned for a while now, what happened to it? Was it dropped? Why? There isn't any program yet that will allow us to make Trillian skins, that option alone could very well sell SkinStudio. Additionally, who gives a rat's ass about Windows Media Player? How bout Winamp skins?

I will continue to subscribe to and support Object Desktop, and I will probably continue to ignore Windowblinds. Since SkinStudio is part of Object Desktop, Stardock won't be able to sell me SkinStudio as a separate product, since I already have it. Add some additional features in, though, particularly Trillian 3 skinning, and it could very well become an invaluable app, not just a curiosity to anybody who isn't a windowblinds skinner.

<edit>Windowblinds was invaluable for making Windows 2000 look nice, however, and I used it religiously until XP came out. It's a shame that it can't work as seamlessly on a more modern OS as it did then.</edit>

gud points there darrian !

i used windowblinds for 1 year .

the guiolympics skins were damn cool (atleast for me) specially the vectorcell and minios and such other skins ...that is why i wanted a wba to visual style porter !

i know skinstudio wudnt want that feature because then noone would use WB ...

but i was just thinking that if there was a wba to msstyles porter some of the coolest skins in WB wud be ported quite easily !

The thing that i found is that with Windows Blinds it is another thing to load at StartUp, which my PC already has trouble with :/

Another reason why i stopped using it was the quality of the themers. I am not into theming, but looking at the quality of themes for WB (on WinCustomize) and them a MSSTYLES site, such as Studio 28 - there is a rather large difference in quality, and useability.

I thought the GUI Olympic's would be a good venture, sorting the useable themes from the ones created by people who look like they never have done it before. BUT, i went on and saw the same sorts of skins. Even some of the premium skins I wouldn't ever use - i would have thought these would be better? :/

If i see more skins like on Studio 28 and GFXOasis (using their Blue one now - its a beaut!) then I would most likely convert back.

585181894[/snapback]

Except you forget that the default windows theme service has to load at startup also. It runs under an svchost as the uxtheme and can take any from 5-20 MB of ram to run where as WB runs approx 512 ~2 MB ram depending on the skin.

I am an object desktop user.  Of all the OD apps available, I only use iconpackager.  I also use CursorXP and ObjectDock, which are also Stardock products, but not part of OD.  I used to use Desktop X, but now I rarely touch it and if I use it at all it's in the form of widgets.  Stardock makes some good apps.  I won't use windowblinds.  Every time there is a new version I try it out, and within minutes I uninstall it.  It does skin more things than native visual styles do, but it's glitchy.  Windows flicker, sometimes things don't display correctly.  Most windowblinds skins suck (I've only ever used 5 of them so far for any limited amount of time, but I've tried hundreds).  Ever play a game in windowed mode using windowblinds?  Most likely your game window will be using a classic windows border and titlebar.  And these problems have been around since Windows XP came out, they should have had them fixed a long time ago, before they started adding other "useless" features like skinning the toolbar buttons and shutdown prompts, etc., which are cool but unnecessary when the software is not already 100% perfect before adding those features.  Also, regardless of what anybody at Stardock claims, Windowblinds skins seem to run slower.  I have an Athlon 64 3400 and 2 GB of PC3200 RAM, plus a GeForce FX 5700.  I shouldn't notice any difference, especially if I have no programs running, yet I do.  Should Stardock create a Windowblinds to MSStyles conversion feature in SkinStudio?  I think so.  They have a better understanding of how the Windowblinds works than any of us ever will, plus they own the format.  Who's to say they wouldn't sue somebody if they created such a program?  Stardock, at least to me, has always seemed to be about freedom of choice.  The truest test of that would be to give us that option.  Additionally, even if they didn't add a converter, the ability to create MSStyles as well as Windowblinds skins in Skinstudio would be nice.  Sure, TGTSoft has their own little tool for that, but I'd rather be able to use Skinstudio.  Now...

You really want me to use SkinStudio?  Give me the option to make Trillian skins with it!  That feature had been planned for a while now, what happened to it?  Was it dropped?  Why?  There isn't any program yet that will allow us to make Trillian skins, that option alone could very well sell SkinStudio.  Additionally, who gives a rat's ass about Windows Media Player?  How bout Winamp skins?

I will continue to subscribe to and support Object Desktop, and I will probably continue to ignore Windowblinds.  Since SkinStudio is part of Object Desktop, Stardock won't be able to sell me SkinStudio as a separate product, since I already have it.  Add some additional features in, though, particularly Trillian 3 skinning, and it could very well become an invaluable app, not just a curiosity to anybody who isn't a windowblinds skinner.

<edit>Windowblinds was invaluable for making Windows 2000 look nice, however, and I used it religiously until XP came out.  It's a shame that it can't work as seamlessly on a more modern OS as it did then.</edit>

585181913[/snapback]

Ever heard of doing per application skinning? If a game if giving you trouble then tell WB not to skin it or only skin the titlebar. There are over over 3 thousand skins on wincustomize today, your telling me you can't find one skin you like?

gud points there darrian !

i used windowblinds for 1 year .

the guiolympics skins were damn cool (atleast for me) specially the vectorcell and minios and such other skins ...that is why i wanted a wba to visual style porter !

i know skinstudio wudnt want that feature because then noone would use WB ...

but i was just thinking that if there was a wba to msstyles porter some of the coolest skins in WB wud be ported quite easily !

585182023[/snapback]

And I tell this to everyone else, WB is far superior to uxtheme. Consider uxtheme to be a stripped down version of WB considering Stardock helped Microsoft develop it. And you know what, until you design a program that converts from WB to msstyles stop whinning.

I get so sick to death of people saying that WB is so eye candy and that it never has any good skins, but when you take a look at any of the recently released msstyles here or soon to be released ones, they are ALL mods on luna or longhorn. Absoultly no creativity or originality but yet when a WB skin does get released here that breaks the mold such as the unorthodox skins thread, the 1st few pages are filled with rants of they are unuseable, yet they show the potential of WB.

Edited by AthleticTrainer1981
Ever heard of doing per application skinning? If a game if giving you trouble then tell WB not to skin it or only skin the titlebar. There are over over 3 thousand skins on wincustomize today, your telling me you can't find one skin you like?

Been there, done that, no workey. I've fiddled with about every control imaginable to get WB to function the way I want. Telling WB NOT to skin it is exactly what I DON'T want it to do. What I want is for it TO SKIN it. And if you had a higher reading comprehension you would have caught the part where I stated that there are approximately 5 windowblinds skins that I will use regularly when running windowblinds. Actually, there are about 15, the other 10 are outdated skins that do not support things like the xp start menu, and so I won't use them.

Stardock may have helped MS develop uxtheme, but either MS ensured that non-native skinning apps won't work 100% correctly, or Stardock can't seem to figure out how to get windowblinds to work the way they intend it. Either way, it's glitchy. Stardock's biggest argument against using MSStyles is that it requires patching your uxtheme.dll, thus making your system "unsecure." Pretty much an invalid argument, since most people who patch their system are well aware and willing to accept any risk. Furthermore, when was the last time you heard of a virus coming from a MSStyles file? I can't think of any such incident, thus far, so it's pretty much marketing propoganda. And that's fine. This isn't a msstyle vs windowblinds discussion, and if you want to be a fanboy go find yourself such a thread and flame away. Personally, I don't like to use windowblinds for reasons that I feel are very solid and sound, which I've backed up with examples that you have only feebly and unsucessfully contested. My argument in THIS thread is very simple, and related to skinstudio, not WB. Any discussion on my part of WB is simply used to illustrate WHY SkinStudio, at this point in time, is virtually useless to me, not to proclaim superiority of one format over another. It's truly a matter of preference in most cases, anyway.

Skinstudio is not a very attractive product to me as its primary use is to create windowblinds skins, which I'm highly unlikely to use. If Stardock wants to expand their user base they need to add in more features and make the features they already have more useful. I've already given examples on how they could do that, as well, so I'm not going to repeat myself any further.

I get so sick to death of people saying that WB is so eye candy and that it never has any good skins, but when you take a look at any of the recently released msstyles here or soon to be released ones, they are ALL mods on luna or longhorn. Absoultly no creativity or originality but yet when a WB skin does get released here that breaks the mold such as the unorthodox skins thread, the 1st few pages are filled with rants of they are unuseable, yet they show the potential of WB.

Skins can show as much potential as they want, but that doesn't make them useable. To me, a skin MUST be useable and functional, not just eye candy. I wouldn't even mind your argument so much if there actually were a lot of windowblinds skins out there with eye candy, but most of them look as if a young child with no experience created them. There are very few truly great skinners in the WB community (and here I'm talking about WB artists, not people who port msstyles over to WB, usually somewhat imperfectly, and then get praised at how good a job they did and how great "their" skin is) who actually make skins that I would consider professional, useable, functional, whatever. Of those skins, only a small fraction of them actually suite my tastes, and I'm extremely picky. Point of fact, I'm currently running the Luna Element msstyle. Yes, it's a Luna mod. And so what? Luna isn't as bad as everybody makes it out to be. Element takes almost everything people hate about Luna and fixes it. Now if only a black substyle would be made, as I prefer dark skins, I might actually be happy with it. As it is, I'm simply content, because when it comes down to it, I have yet to see a skin in either format that I'm 100% happy with, hence the neverending search to find a new visual style. I'm the same way with wallpapers. Something better is always going to come out, people are always going to be searching for that something, and everybody is going to have a different opion on what that something is and what makes it "better." That's what makes this community thrive. I think the majority of the Neowin community prefers msstyles, and there's a good reason for that. I'm sorry that you're disappointed with our reasons and the skins that seem to be popular around here, but preaching isn't going to get you anywhere. Perhaps try being beneficial to the thread by offering suggestions and CONSTRUCTIVE criticism rather than just assuming everybody here is a moron and throwing biased opinions around. I understand your frustrations, but you're essentially making the same accusations you're upset about, simply from the other side of the fence. I apologize if I've been inflamatory with this response, but I felt assaulted and obligated to defend myself.

Edited by Darrian
Why dont most people use SkinStudio then ????

Why are there more 'good' skins for stylexp than for windowblinds ??

585181863[/snapback]

There aren't. There are a lot more WindowBlinds skins than msstyles. And as for "good" that's a matter of taste. If you look here at Neowin the best of the best on msstyles gets shown and there are indeed dozens of good msstyles made each year. But the typical msstyle is just as, if not more, gaudy than the worst of the WB skins (visit themexp sometime and compare).

And there are no skins "for Style XP". It's just a program that patches uxtheme.dll so that you can use unsigned msstyles.

There are some really good discussions here.

Let me add my 2 cents. I'm biased but that doesn't change the facts of the matter from here:

I'm running WindowBlinds 4.4. I also run PC games all the time. I'm a game developer (lead designer on The Political Machine, Galactic Civilizations - both won editor's choice awards from Computer Gaming World).

I am currently playing World of Warcraft, Half-Life 2, and Pirates. I have never seen any of the problems you describe, Darian. I don't run into "flaky" behavior with WindowBlinds. My windows are skinned. When we develop our games, they are always running in a window (for debugging purposes) and they are always skinned fine with WindowBlinds.

I don't know of any apps that are "glitchy" with WindowBlinds. I do, however, find that some skins are glitchy or buggy. Is this WindowBlinds fault? No. There are plenty of msstyles that are glitchy and buggy too.

You guys do these apples and oranges comparisons. You go and compare the elite msstyles made on Studio 28 or posted here on Neowin with the rank and file WB skins on WinCustomize. That's ridiculous. And I could do the same thing saying look at Pixtudio, The Skins Factory, SkinPlant, Essorant's Page, etc.

If you want an apples and apples comparison, go look at ThemeXP.org and then compare those skins to what's on WinCustomize.

In fact let's do that now:

Here are the newest 3 skins on ThemeXP:

http://www.themexp.org/preview.php?mid=844...e=EQUALIZER.zip

http://www.themexp.org/preview.php?mid=843...Liquid+Blue.zip

http://www.themexp.org/preview.php?mid=843...me=CANDIDva.zip

Now the newest 3 on WinCustomize:

http://www.wincustomize.com/ViewSkin.aspx?...ID=4357&LibID=1

http://www.wincustomize.com/ViewSkin.aspx?...ID=4752&LibID=1

http://www.wincustomize.com/ViewSkin.aspx?...ID=4750&LibID=1

Now if you guys think the 3 newest on Themexp look better than the 3 newest on WC we can just end this discussion now and I can write you off as someone with crappy taste. ;)

I run skins on multiple configurations all the time and they work fine. Glitchy skins are glitchy but that's the same for msstyles where the author has some out of control element (like a 6000 pixel long title bar or a button that is only 2 pixels tall or whatever). That's not uxtheme's fault nor is it WindowBlinds' fault. But in both cases, that's pretty rare.

And WindowBlinds 4.4 is so much faster than msstyles at this point that it's pretty undeniable. And if you are running some strange apps where compatibility is a concern, you can click an option and set WindowBlinds to only skin theme aware programs just like uxtheme does.

But let's cut to the chase - the msstyles life expectancy is almost over. Msstyles, as you know them, die with Longhorn. And given how difficult it has been to get WindowBlinds to run msstyles fluidly in 2 years of work, SkinStudio is your best bet for whathever future format is in Longhorn (if there is a format with the name .msstyles or .lhstyles or whatever).

This is for Brad:

You're absolutely right, in many cases the fault is with the skin. What I'm specifically referring to is flickering of WB elements for no apparent reason, objects not being refreshed after initially drawn (say when moving a window or something, where the "skin" should be there is just a white blankness that takes a moment or so to redraw where a msstyles skin would remain constant--and this is a glitch that I have not seen consistantly for quite some time, but it does still occur occasionally under some circumstances), and as far as games go, well, specifically I see that bug consistantly on any game based on the Quake III engine. I have not attempted it with a game with a more modern engine yet, say Half-Life 2, but the majority of FPS games use Q3, and when it comes to online play chances are I'll be running a Q3 game (usually JK2 or JK3). I have not played any Stardock games. They're just not my genre. I may just load WB back up sometime today and test it with the games I'm currently playing and see how it holds up. However...

The biggest reason I don't use WB is because it doesn't have many skins I like, and the skins that I use regularly are msstyles. Additionally, even if there is a WB port, why use the port when I can easily use the original? If WB allowed you to use msstyles as well as WB (without being forced to convert the msstyles format to wba, which is pretty much the only way I've seen to do this, and I think that's crap, since it's difficult for most skins to be converted 100% perfectly, which in turn forces you to fiddle with the skin in skinstudio, possibly for hours, before it's usable--and I'm aware that improvements in this area are what started this thread and sincerely hope that it can indeed be improved) then I would keep it installed all the time and simply disable it when I was using msstyles, but it doesn't, and the installation/uninstallion process is a pain in the ass (on this note, after you uninstall WB it would be great if windows was returned to its original functionality and cease loading WB elements, which it seems to do until you manually delete the windowblinds folder, something I'd rather not do since skins are kept there--of course, you can rename the folder, too, say add a .bak to it or whatever, but it makes a frequent uninstall/reinstall tedious, which makes switching back and forth undesirable). Because of this I only use WB when I see a new skin that looks so great I just have to try it. I monitor wincustomize.com regularly for updated skins for several Stardock apps, including WB. The last time I saw a skin I couldn't live without I think it was called Metal X. A great skin, but I had to recolor it to get it to where I wanted it. Now, recoloring a skin is a great feature. It also slows down WB considerably. A better way to do that, I would think, would be to allow WB to recreate the bitmaps for the skin in a temp folder after it's been recolored, and essentially rebuild the skin with the new bitmaps. Recoloring it in real time, constantly, is too much of a bog. But I do like the feature and hope that it gets developed further. What it comes down to is my own taste. It isn't that all WB skins suck by default simply because they're WB skins. More skins that I would actually use are created either exclusively or first for msstyles. Because of this, I more or less exclusively use msstyles, which are just as easy to install with none of the headache, plus the interface to change skins is already built into xp, so I don't need to bother with additional WB interfaces. I appreciate simplicity and ease of use (not that I don't appreciate advanced options, in fact I would demand them from such an app, but they should be hidden away until I specifically desire to access them, probably the control panel would be the best place, and not the system tray or in the appearance tab in display properties, and wherever else it shows up, even if I tell it not to in the case of the system tray). Anyway, I'm sure I've been rambling and I'm short on sleep. I just wanted to make it clear that I don't hate windowblinds. I've always thought it showed promise, and I still do. I just don't think that it's as compatible with XP as it was with 2000, I think there are more bugs now than there used to be, and this may very well be simply because it skins more elements now than it used to. I really don't know why, I'm not the programmer :)

As an aside, I tend to stay the hell away from themexp.org and would never recommend it to anybody; I despise spyware and/or whatever crap they put in their installers these days. Gimme a good old fashioned zip or rar any day.

If WB allowed you to use msstyles as well as WB (without being forced to convert the msstyles format to wba, which is pretty much the only way I've seen to do this, and I think that's crap, since it's difficult for most skins to be converted 100% perfectly, which in turn forces you to fiddle with the skin in skinstudio, possibly for hours, before it's usable--and I'm aware that improvements in this area are what started this thread and sincerely hope that it can indeed be improved)  then I would keep it installed all the time and simply disable it when I was using msstyles, but it doesn't...

actually it does - unload WB and press the Ctrl key while loading Display Properties dialog. Also should you have any problems with an msstyle, please mail me: adam AT stardock DOT com and I will gladly fix the glitch for you. I always try to fix them instantaneously, but i cannot fix it if I'm not aware of it. Please, please, please report all faulty msstyles.

The last time I saw a skin I couldn't live without I think it was called Metal X.  A great skin, but I had to recolor it to get it to where I wanted it.  Now, recoloring a skin is a great feature.  It also slows down WB considerably.  A better way to do that, I would think, would be to allow WB to recreate the bitmaps for the skin in a temp folder after it's been recolored, and essentially rebuild the skin with the new bitmaps.  Recoloring it in real time, constantly, is too much of a bog.  But I do like the feature and hope that it gets developed further. 

You can recolor the skin in skinstudio as described in this article and it will run as fast as the original. Also as far as I know the skin is recolored by WB on load NOT on paint, so the loading of the skin may be a bit slower, but not the painting.

Darrian: what type of computer are you running that you experence these glitches? I run a athlon XP at 2 ghz with 64 mb geforce 4 and it works great.

Try the newest versions of WB 4.4 and give skins like dogmax a try, they will blow your mind away at how complex yet professional and minimal they are.

You want to now why the skins you use are all msstyles because they are all the same. They are all basic mods of luna/panther/longhorn. Nobody has any creativty left in them anymore and nobody can create anything radical anymore. Take a look at any recently released msstyle on this board and you will see a mod of luna or longhorn.

KoL's newest theme is a perfect example. While it is a great theme with graphics that are handcrafted, it has the fisher price look of luna. A true lack of originality. And yet look at the thread in the WB forum of the unorthodox skins. Those show what true skinning can achieve. Something radical, something original. It may not be something you use day in and day out, but it is different and that is what counts. It is also something that cannot be done with msstyles.

You talk about how you don't like how windowblinds handles itself when it comes to unloading the themes and uninstalling, etc.... Well, I hate to say it but no program is perfect but this one is definately improving. Even Microsoft isn't perfect, that's why they stopped with only 3 variations on the themes.

I have done a lot of recoloring of skins using skinstudio and I haven't expeienced this slowdown you have talked about, can you explain it more??

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Movavi Video Editor Plus 26.18.0 by Razvan Serea With Movavi Video Editor Plus, you can either enhance your video files with two or three simple steps, or turn them into something completely new. Create your own movies using multiple filters, transitions, and special effects: show multiple videos on one screen with the Picture in picture effect or change the background with the Chroma Key effect, imitate the camera zoom or make your video look like an old-style movie. Adjust video parameters such as brightness, contrast and colors. Stabilize shaky footage, improve video quality and remove defects. Create video presentations, tutorials or educational videos: add titles and record your own narration to create a video with voiceover. Import video from any source: TV-tuner, webcam, camcorder, or VHS. Drop multiple media files onto a timeline and let your imagination do the rest! Features at a glance: Video and audio editing on a timeline Edit, enhance videos Add background music Apply titles and effects Image quality improvement Hollywood-worthy effects High-grade titles and fades Digitize VHS tapes, record video from TV tuners Stabilize any shaky sections Support for a wide range of formats Prepare your videos for uploading to YouTube, Facebook, Vimeo, or any other website New in Movavi Video Editor 2026: 30+ fresh subtitle styles. Upgrade your automatic captions with new designs. Customize your text in the Styles tab with a single click. Optional advanced settings are also available in the dedicated Design tab. Subtitles in English – instantly! Translate auto-subtitles into English with a click – no dictionaries or online services needed. Once translated, configure and fine-tune the subtitles using the standard editing tools. 40+ adjustable effects. Enhance your videos in a click with new realistic effects – from dust particles and light leaks to retro-style and VHS. Every effect is fully customizable – so it will fit any clip perfectly and bring an extra spark to your edits. Ultra-fast playback. Show more in less time with video speed control of up to 100x. Perfect for epic time-lapses, long process recaps, or whenever you want to add some extra energy to your content. Magnetic zones are marked with dots, and the 1x value is indicated by a vertical line. Silence removal – in a click. Cut out unwanted pauses automatically or fine-tune the pause length and volume threshold yourself. Skip the tedious cleanup and make your videos more dynamic. Fast effect copying. Effortlessly duplicate any effect from one video to another: click Clip effects in the dropdown menu and proceed to copy or paste. Movavi Video Editor Plus 26.18.0 changes: This version includes small improvements for better editing. Download: Movavi Video Editor Plus 26.18.0 | 2.7 MB (Shareware) View: Movavi Video Editor Plus Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • JBL BAR 800 5.1.2 Dolby Atmos soundbar is an amazing deal today by Sayan Sen This Amazon Prime Day 2026 sales so far we have had a couple of nice deals related to sound and audio. First we have the Sennheiser HD 600 at its lowest ever price of just $225. Next we also have the Beats Studio Pro at its lowest price ever at just $150. However perhaps you prefer your gear to sound great on a larger scale, like throughout the room. In that case an all-in-one soundbar system can help and currently JBL's BAR 800 is a great deal for sure as it's up for grabs at just $600 (purchase link under the specs table down below). One thing that should be appreciated a lot about these JBL soundbars is their spec sheet and the frequency response data it provides. The firm is honest about it as JBL confirms the subwoofer is able to go down to 35 Hz at -6dB or F6. This means it should be covering 40Hz and up very well, where most of the bass lies. You miss out on a lot of sub-bass but that is to be expected given the price point and the subwoofer driver size. Speaking of which, it is a 10-inch driver and promises a max output power of 300 watts at 1% THD (total harmonic distortion). JBL also claims the system will provide you with a "True Dolby Atmos" experience. The surround speakers are wireless and battery-powered which means setting them up should be really convenient. The technical specs of the JBL BAR 800 are given in the table below: Specification Value Channel Configuration 5.1.2-channel soundbar system Dolby Atmos Yes, with 2 up-firing drivers Total System Power Output 720 W Soundbar Power Output 340 W Surround Speaker Power Output 2 × 40 W Subwoofer Power Output 300 W Soundbar Drivers 3 × 46×90 mm racetrack drivers, 3 × 20 mm tweeters, 2 × 70 mm up-firing full-range drivers Surround Speaker Drivers 1 × 46×90 mm racetrack driver (each speaker) Subwoofer Driver 10-inch (260 mm) wireless subwoofer Frequency Response 35 Hz – 20 kHz (-6 dB) Audio Inputs Optical, Bluetooth, Chromecast built-in, AirPlay, Alexa Multi-Room Music (MRM), USB* HDMI Inputs 1 HDMI video input HDMI Output 1 HDMI eARC output HDCP Version 2.3 HDR Pass-Through HDR10, Dolby Vision Bluetooth Version 5.0 Wi-Fi Version 6, 6E Streaming Services Chromecast built-in, Apple AirPlay, Alexa MRM Get it at the link below: JBL Bar 800-5.1.2-Channel Dolby Atmos soundbar with Detachable Surround Speakers (Black): $599.85 (Sold and Shipped by Amazon US with Prime) Prime subscription can be cancelled within three business days. Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Microsoft releases PowerToys v0.100.1, fixes a bug that made remapped keys misbehave by Ivan Jenic Microsoft just released PowerToys v0.100.1, a patch update that addresses several stability and behavior issues found in v0.100.0. The v0.100.0 patch was a significant update for PowerToys, as it introduced all sorts of new features and additions, such as a rebuilt Shortcut Guide, a Command Palette Extension Gallery, webcam overlay support in ZoomIt, and more. However, the v0.100.0 version also introduced some bugs and stability issues. And now, Microsoft is addressing these issues in the new patch. The most impactful fix in this release perhaps is in Keyboard Manager, where remapped modifier keys were being delivered as system-key events, causing unexpected behavior in apps. The clearest example of this was Alt-to-Backspace remaps, deleting whole words instead of a single character. So, if you thought there was an issue with your keyboard, Microsoft just confirmed that it was PowerToys. Beyond the Keyboard Manager fix, v0.100.1 also addresses several other issues. It fixes a bug with Power Display that was preventing monitors from waking from standby correctly. Additionally, the new update patches Quick Access crashes on launch, and resolves a Shortcut Guide crash that occurred when switching between sidebar sections. Here’s the full changelog: Color Picker Fixed a bug where the main Color Picker window could appear inside the zoomed-in picker view Command Palette Fixed Run history initialization in AOT builds Fixed a bug where the Performance Monitor dock item could show ??? after restart Fixed the Hibernate command using the Sleep icon Limited the "pin to dock" dialog to displays where the dock is enabled Keyboard Manager Fixed modifier keys remapped to non-modifier keys being delivered as system-key events, which caused unexpected behavior in apps such as Alt-to-Backspace deleting whole words Power Display Fixed a bug where selecting On in the monitor power-state control did not wake a monitor from standby Fixed built-in display detection and brightness control on dual-GPU laptops where the internal panel is driven by the discrete GPU PowerToys Run Fixed VS Code Workspaces discovery after VS Code moved recently opened workspace data to shared storage Quick Access Fixed Quick Access flyout crashes caused by unhandled XAML exceptions during launch or page navigation Shortcut Guide Fixed a crash when navigating between Shortcut Guide sidebar sections Fixed number-key rendering in shortcut manifests and added a Postman shortcut manifest Updated bundled shortcut manifests to use the literal number-key token so number keys render correctly across apps ZoomIt Fixed a race condition in audio initialization for ZoomIt video recording You can download PowerToys v0.100.1 from the official GitHub releases page.
    • OBS Studio 32.2.0 Beta 2 by Razvan Serea OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content, efficiently. It is the re-write of the widely used Open Broadcaster Software, to allow even more features and multi-platform support. OBS Studio supports multiple sources, including media files, games, web pages, application windows, webcams, your desktop, microphone and more. OBS Studio Features: High performance real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions. Live streaming to Twitch, YouTube, Periscope, Mixer, GoodGame, DailyMotion, Hitbox, VK and any other RTMP server Filters for video sources such as image masking, color correction, chroma/color keying, and more. x264, H.264 and AAC for your live streams and video recordings Intel Quick Sync Video (QSV) and NVIDIA NVENC support Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. GPU-based game capture for high performance game streaming Unlimited number of scenes and sources Number of different and customizable transitions for when you switch between scenes Hotkeys for almost any action such as start or stop your stream or recording, push-to-talk, fast mute of any audio source, show or hide any video source, switch between scenes,and much more Live preview of any changes on your scenes and sources using Studio Mode before pushing them to your stream where your viewers will see those changes DirectShow capture device support (webcams, capture cards, etc) Powerful and easy to use configuration options. Add new Sources, duplicate existing ones, and adjust their properties effortlessly. Streamlined Settings panel for quickly configuring your broadcasts and recordings. Switch between different profiles with ease. Light and dark themes available to fit your environment. …and many other features. For free. At all. OBS Studio 32.2.0 Beta 2 changelog: Beta 2 Changes Fixed a CI deployment issue. There are no application changes since Beta 1. 32.2 New Features Replaced add source dropdown with new dialog [Warchamp7] Improved FPS selector UX [jcm93] Added missing file support for filters [exeldro] Added ability for plugins to set custom icons for new source types [cg2121] Included .webp files when adding a directory to Image Slide Show source [TarunCore] Added copy paste functions to frontend API [exeldro] Added filter to compose SDR into HDR [jpark37] Added delete as a hotkey to delete sources on macOS [PatTheMav] Added dynamic bitrate support to multitrack video [lexano-ivs] 32.2 Changes Forced Intel-based installations to update to Apple Silicon version on macOS [PatTheMav] This change means that OBS Studio versions built for Intel-based Macs but running on Apple Silicon Macs will automatically update to OBS Studio built for Apple Silicon Macs. If an installation was using third-party plugins, those plugins will no longer load until replaced with Apple Silicon versions. Fixed audio mixer state getting out of sync when changing settings via websockets or plugins [Warchamp7] Added theming for checked QToolButtons [glikely] Improved OpenGL performance slightly on low-end machines [kkartaltepe] Set minimum size for color source to 1 pixel [exeldro] Added minimum width to spinboxes [Warchamp7] Disallowed overwriting the crash handler [sebastian-s-beckmann] Applied process mitigation policies for Windows [notr1ch] Adjusted description of multitrack video [jhnbwrs] Changed new capture devices to use fallback frame rate by default [PatTheMav] Improved DLL loading behavior on Windows [notr1ch] Limited multitrack video config to Custom service [PatTheMav] 32.2 Bug Fixes Fixed OAuth and dock state save corruption [PatTheMav] Fixed group bounds not resizing when removing items [howellrl] Fixed canvas mixes not being restored after video reset [dsaedtler] Fixed some erroneous crashes during shutdown [Warchamp7] Fixed display capture sometimes capturing black after a duplicator failure [ThrowTop] Fixed color of controls dock output buttons in System theme [shiina424] Fixed virtual camera reset failures [stephematician] Fixed potential crash when user discards changes in the settings window [suogesi] Fixed incorrect return value in virtualcam filter [xtfo] Fixed source toolbar buttons not working after dragging a source into a group [Warchamp7] Fixed properties hint icon spacing [Warchamp7] Fixed potential crash when a video device reconnects on macOS [jcm93] Fixed an issue where PipeWire could fail on NVIDIA GPUs [hoshinolina] Fixed obs_canvas_get_video_info returning incorrect framerate [dsaedtler] 32.2 Deprecations Deprecated obs_properties_add_button [sebastian-s-beckmann] Download: OBS Studio 32.2.0 Beta 2 | Portable | ARM64 | ~200.0 MB (Open Source) View: OBS Studio Homepage | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Is a fast food restaurant a good metric to compare against?
  • Recent Achievements

    • One Year In
      OHI Accounting earned a badge
      One Year In
    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      122
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      72
  • Tell a friend

    Love Neowin? Tell a friend!