Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    Please note that Odroid-Show features a very slow USB protocol, and it takes several seconds (!) to perform a single frame update. It's not really suitable for the AIDA64 LCD module. The only reason we've implemented support for Odroid-Show is because a passionate AIDA64 user requested support for it. It is possible to handle multiple LCD screens from a different vendor, without limitations on the number of simultaneous screens connected. It is also possible to handle multiple screens from the same vendor, but not for all screen types. The Odroid-Show LCD module supports only a single screen in AIDA64 for example, but you can use up to three picoLCD screens, up to three Trefon screens, up to two AlphaCool screens, up to two Logitech G15/G19 screens, etc. DisplayLink monitors are connected via USB, but they act like classic monitors. So you can define a Windows desktop for it, and you can use the SensorPanel on it. Please note that you can only use a single SensorPanel right now, so having multiple DisplayLink screens may not work out well in your case. DisplayLink performance should be just fine for the SensorPanel (that uses cca. 1 or 2 FPS update rate), but I'm not sure how it works with video playback. It should work smoothly too, but we never had a chance to try it out.
  2. Fiery
    Thank you for the feedback. I'm afraid we have no information on how to handle the frame buttons. There's a good chance that they cannot be handled via the USB connection, but only the frame's built-in software can handle them.
  3. Fiery
    Please let me know what keyboard and mouse you've got. It's most likely due to a bug in the DirectX driver of one of your input devices. Thanks, Fiery
  4. Fiery
    Thank you for the feedback. I've updated the opening post.
  5. Fiery
    For that purpose the AIDA64 PhotoWorxx benchmark may be the solution we can offer at this time. It is heavily multi-threaded, it uses integer code, and it utilizes all cache levels.
  6. Fiery
    That is normal, and it's much better than the first generation eDRAM solution. Core i7-4770R: L4 cache latency = 76.2 ns. Our ZLib data compression benchmark uses the "best" compression method, so it's more CPU bound than memory/cache interface bound. It is not designed to show off the underlying cache architecture performance. Our PhotoWorxx image manipulation benchmarks should be better to reflect the performance gains you can get from the L4 cache, but you may need to limit the number of used CPU cores to 3 or 4 if you really want to see a big difference between Haswell and Broadwell-H. I'm afraid we have no plans about implementing a sorting benchmark. AIDA64 benchmarks are not designed to show off the performance gain coming from a particular hardware feature. So we will not develop a new benchmark method just to show off how great 128MB or 256MB L4 is. And actually, in general (non-gaming) use the L4 cache doesn't provide huge gains. BTW, some rumours state that with Skylake and Cannonlake the eDRAM will no longer act as a L4 cache, but more as a dedicated buffer (cache) for the iGPU. I'm not sure if that's true, it would be surprising if Intel made such a move.
  7. Fiery
    You can find the mentioned new beta update to AIDA64 Extreme at: http://www.aida64.com/downloads/latesta64xebeta If you have a disconnection issue after a few seconds, make sure to enable the new keep-alive option, and then restart AIDA64.
  8. Fiery
    Thank you for the info. As I've mentioned above, we'll get around that by adding one more option to enable/disable the latest "Keep alive" workaround. A new AIDA64 beta update including that fix will be rolled out in an hour or so.
  9. Fiery
    Please cut us some slack. Samsung never provided a SDK or other programming manual for their picture frames. What AIDA64 does may not work with all SPF variants. Samsung made a lot of variants of those SPF frames, they offer multiple models with the same (e.g. "SPF-87H") designation, so it's a big mess. And since it's not documented (at least not publicly documented), for us it's a big headache to sort things out and find out what tricks do we have to use to support all the different SPF models out there. As you can see, a certain bug fix could help to get around issues with a particular SPF model, but in the same time the fix ruins it for others. It's not easy to go blindly, without documentation, but we're doing our best to sort out every single issue you guys are facing. It would be much easier for us to pull the plug and remove SPF support from AIDA64... As for your issue, if possible, please uninstall Samsung Frame Manager and install our libusb driver: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip It should help, as long as you wouldn't bump into the issue Xixou is having now with the latest beta. But we'll get around that by adding one more option to enable/disable the latest "Keep alive" workaround.
  10. Fiery
    Did previous betas work before? Do you use the libusb driver?
  11. Fiery
    Do you use the libusb driver? What SPF model do you have?
  12. Fiery
    As far as I know, on Kepler/Maxwell GeForce GPUs it's not possible to measure the power draw in Watts. Regards, Fiery
  13. Fiery

    Happy 20th

    Fiery replied to Dutch's topic in General Discussion

    Thank you http://www.aida64.com/news/aida64-turns-20-windows-phone-ios-mobile-apps AIDA64 for iOS Download: http://www.aida64.com/goto/?p=iosapp AIDA64 for Windows Phone Download: http://www.aida64.com/goto/?p=winapp
  14. Fiery
    Your post came at just the right time to squeeze a new single line into the code before we rolled out the new beta update Thanks again
  15. Fiery
    That seems like a very useful information, thanks a lot! We've already implemented it in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let us know if it helps to fix the disconnection issue.
  16. Fiery
    In case you want to push your reports into a SQL database, then you need to remove /CSV from your command-line, and add /DATABASE instead.
  17. Fiery
    AIDA64 cannot measure drive activity, so you cannot put it on the SensorPanel either.
  18. Fiery
    I don't think I can follow that If by Frame manager you mean Samsung Frame Manager software, then you have to uninstall all SPF-related Samsung software and driver before installing our LibUsb driver. Otherwise Samsung's software and driver may collide with our driver. But, in case you've figured it out and now things are stable, then it's great
  19. Fiery
    Does the every 500ms there are "Device Vendor_Device" command - two zero bytes anomaly happen with both drivers?
  20. Fiery
    No, it's not possible to monitor the uncore load level. Yes, you can use the Logitech Arx Control LCD module or the RemoteSensor LCD module of AIDA64: http://forums.aida64.com/topic/2610-logitech-arx-control-lcd-for-smartphones-and-tablets/ http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/
  21. Fiery
    Thank you. Do you use our LibUsb driver?
  22. Fiery
    We've extended the update frequency down to 100 msec in the latest beta update to AIDA64 Extreme: http://www.aida64.com/downloads/latesta64xebeta But, I don't think it would help. Please let me know how it works.
  23. Fiery
    I cannot recommend you a method to stabilize your current configuration, since every configuration has its own "dirty little secrets". You have to try various settings and see which one works out. BTW, I wouldn't consider a system stable if it is stable only for a few hours and then it throws a hardware failure. But I completely understand if you find that acceptable for your everyday use. Regards, Fiery
  24. Fiery
    I'm afraid that wouldn't help, since on their high-end products Asus tend to use custom chips that no other manufacturers use
  25. Fiery
    Asus Matrix cards usually feature a custom Asus sensor chip that is not publicly documented, and so cannot be supported by 3rd party monitoring applications like AIDA64
×
×
  • Create New...