Recommended Posts

Just to let everyone know there is a update for dreamscene on windows update for all us ultimate users.

untitledmr3.png

yeah just installed it, and the option to show dreamscenes is still greyed out on my system - I use Nvida drivers on Geforce 6600 card. has anyone worked how to get it to work?

Gawd, those Dreamscenes look really crappy...the quality is really bad compared to others.

Using DeskScapes I am using this one http://lotherius.wincustomize.com/skins.as...17&libid=50 and it has been the best one so far for me

Yea, I have to say I've been really surprised at how good some of the After Effects type Dreams have come out. My favorite one I think is this one http://www.wincustomize.com/skins.aspx?ski...04&libid=50

The Microsoft ones I think are pretty good. The new Plasma one that they released was done by Stardock Design.

After installing this I'm noticing rundll32.exe errors every time I open the DreamScene content in Personalization, I think it has something to do with the thumbnails that aren't being displayed for these .mpegs it also happens when I browse to the folder. Any know about this?

LOL, WTF spanish users with the 32bits ultimate version can't download it :angry: :angry:

36325387te4.png

Are we :alien: ?

I guess DreamScene requires localization before it's made available, although I don't understand why, as it's just a multimedia thing.

After installing this I'm noticing rundll32.exe errors every time I open the DreamScene content in Personalization, I think it has something to do with the thumbnails that aren't being displayed for these .mpegs it also happens when I browse to the folder. Any know about this?

Hye there try google it i already fix mine, i think there is an issue with nero , here is the fix.

under c:\program files\common files\ahead\dsfilter\

rename the following two items as follows:

nevideo.ax - rename this (for example 1nevideo.ax)

nerovideoproc.ax - also rename this one (for example 1nerovideoproc.ax )

reboot. that should fix it. it's not a vista issue but a nero issue.

Anyone else getting something like 20% cpu usage with dreamscene on, just idle? I thought it was supposed to be purely gpu driven?

Only uses up 2% here, it heavely depends on the media type and if the VDDM drivers are optimized enough (video drivers in vista)... WMV files use up a lot more processor usage because of the compression type, MPEG files seem to run more smooth processor speed wise

Anyone else getting something like 20% cpu usage with dreamscene on, just idle? I thought it was supposed to be purely gpu driven?

I'm having the same problem with x86 Vista, DreamScene take 15-25% of CPU juice. And I also found that when using Media Player in full screen, I get some background flicker of my dreamscene... Weird thing is, even if I turn OFF DS, I still get the flicker. If I uninstall DS, everything is OK.

I'm using the latest nVidia driver on my 7900GT.

But current DS is only in "preview" so I'm hoping it's going to be better when it's Gold.

Hye there try google it i already fix mine, i think there is an issue with nero , here is the fix.

under c:\program files\common files\ahead\dsfilter\

rename the following two items as follows:

nevideo.ax - rename this (for example 1nevideo.ax)

nerovideoproc.ax - also rename this one (for example 1nerovideoproc.ax )

reboot. that should fix it. it's not a vista issue but a nero issue.

Thanks a lot, I reinstalled and updated nero and it fixed it, but I would never have guess it was nero :)

.wmv uses a lot more cpu power and most of the work is CPU based right now, so wait for the final to get the good performance for both wmv and mpeg hopfullly

yeah just installed it, and the option to show dreamscenes is still greyed out on my system - I use Nvida drivers on Geforce 6600 card. has anyone worked how to get it to work?

What do you mean greyed out?

Do you mean when you're on the desktop with a normal wallpaper and you right click?

Or do you mean when you in the actual desktop backgrounds menu selecting it?

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

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!