Posts by Chris Duncan

    After using for a while, I would be very grateful for a "light mode" for the Location, List, and Inspector. The current color scheme is causing me eye fatigue.

    Yeah, I know all the cool kids are into "darkness" these days, but dark color schemes make my eyes bleed. Fine on a mobile phone at night, pretty brutal on a desktop for prolonged use.

    That said, I'm reserving requests like this for RM 3.1. Right now I'm sure their priority is to just Make It Work. Since I'm waiting for RM and the OS to come out of beta before I give it a play, I heartily endorse that priority.

    Just like that :D

    I too enjoy plain solid modern C++ on a desktop app with no 3rd party frameworks (or 3rd party developers, as I have read in some rumors :P ).. It took a while but regarding the Editor part of the new Rig Manager, it seems to really pay off in stability, size and performance.

    Hey there monkey_man, glad you are still here :)

    Man, I haven't done C++ since the air traffic control days, i.e. MFC. The C# stuff can be productive, and with websites you don't have all the install hassles, but it's just not the same.

    I bought my Kemper right at a year ago and honestly, I was already impressed with RM as it was. A nice, solid app that's easy to use and has been quite stable for me. Just got through moving all the boxes on the network to Windows 10, so when it's out of beta I can't wait to fire it up and have some fun with it.

    If you're ever in Atlanta, pizza's on me. :)

    Programmers usually prefer to just stay in their cubes coding. Management throws raw meat over the walls once a day because they frequently forget to eat, but other than that it's usually best to leave them be. :)

    Nice work on the editor, guys. It's always fun to see people doing cool stuff. After the last decade of doing mostly web / Sql Server stuff, I envy you guys who get to work on native apps.

    I've been trying for days to install on 2 different Windows 10 laptops (updated from 7). Each and every time I get: "There is a problem with this Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor"...….I have tried every suggestion/workaround on the internet.

    That sounds a lot like the problem some folks were having installing RM on Windows 8, where the source of the problem was the state of the OS before beginning the install process. So, the first thing I'd try (painful though it may be) is to run Windows Update on your 7 install and make sure it's 100% up to date, do the requisite reboots, then try again.

    Of the boxes I've upgraded thus far, one laptop crashed in the middle with an obscure error message. I had been selecting "keep everything," i.e. installed apps and files, so I decided to try keep nothing and the second time around it worked without issue. Of course, I'll have to reinstall apps on that box, but at least it's now running 10.

    It took me 2 days to instal Windows 10 as it kept installing until around 85-90% then crashing. It turned out to be the network wifi drivers. I uninstalled them and it finally worked.

    Hope this helps someone.

    The weirdest I've encountered thus far was an HP box that simply wouldn't boot from the DVD. I'd already formatted the hard drive during the first installation attempt, so obviously there was no OS to boot from. Figured it out today when I happened to notice that the boot menu as well as the post message to select a boot option both referred to the cd-rom, not the dvd drive. I looked at the tray and it was in fact a dvd (got the box from a friend).

    It also had the option to boot from usb, so I went that path and got it installed. Once 10 was running, I stuck the Windows 10 dvd back into the drive and it read it just fine. So, there was obviously some sort of driver voodoo that had hidden drivers or something that would make it known as a dvd drive at boot time. Certainly not the weirdest thing I've ever seen.

    That honor would go to Finally:

    It came built with 32 bit, but had the capability to do 64.

    I thought all architecture was either 32 or 64 bit, base on cpu, motherboard, etc. Never heard of such a thing. Wow, that's gotta be some serious hardware voodoo. Always something new to learn!

    There are lots of Win 7 era machines that just don't run Windows 10 properly. If you're going to persist with it I recommend ensuring you have at least 8GB of RAM. I've got an old laptop from around 2008 that's been Win 10 for years and no issues. On the other hand we have older graphics workstations at work that just won't cope with it, even though they've got decent specs.

    I've upgraded half a dozen 7 boxes thus far, but I put the details in the Other gear - Windows 10 thread to keep from distracting from the RM discussion in this thread.

    TL;DR - so far, so good.

    This is a reply from the Rig Manager 3.0 Beta Release Discussion Thread - I'm putting it here in the 10 thread to keep from distracting from the RM discussion, but I thought it might be encouraging to 7 users considering making the move to 10 with their current hardware.

    There are lots of Win 7 era machines that just don't run Windows 10 properly. If you're going to persist with it I recommend ensuring you have at least 8GB of RAM. I've got an old laptop from around 2008 that's been Win 10 for years and no issues. On the other hand we have older graphics workstations at work that just won't cope with it, even though they've got decent specs.

    At the shallow end of the pool, I've just upgraded a handful of 32 bit desktops and laptops from 7 to 10. 32 bit architecture limits max memory to 4GB (3, really), and while 2Ghz processors, none of them are exactly blazing. Performance is a bit slower since 10, but that's an old story with any new operating system. That said, the desktop and three laptops all took the upgrade and are functioning normally as best I can tell thus far.

    I've also upgraded a desktop and laptop that were both 64 bit, with 24GB of memory and decent CPUs. Cubase is running on the laptop, and no perceived hit in performance on either of these.

    All upgrades have been in place, i.e. running the install from within Windows 7 as an upgrade and keeping my programs rather than a clean install from a DVD.

    Obviously there's always a chance of some bit of hardware or software not playing nice, but in general it seems to be handling these older boxes okay. Hope this is helpful to any of you doing your own upgrades.

    ... or use a virtual machine, if you have RAM enough, and leave it online all the time :p

    I'm in the process of migrating my non-critical boxes to 10 so I can see what squeaks before getting into the important ones.

    Until I update the studio box (which may be quite some time), my plan is to install RM on one of my spare 10 boxes, USB that to the Kemper, and just remote desktop into it from my studio box. A bit clumsy perhaps, but until I migrate the studio to 10 it gives me a path forward. Since there will be some work to do anyway, I plan on waiting until both RM and the OS have most of the kinks worked out before I get into it.

    That said, if I didn't have the spare computers lying around the virtual machine is an excellent idea, and would be my approach.

    That looks like it is an error in your window system files not the installer but maybe one of your library files is missing.

    I am no expert though!

    A number of people have reported this error. Since the error message doesn't specify the name of the missing dll, you might check the event viewer to see if an error was logged naming the offending dll.

    Knowing exactly what dll is not being found would be an important step toward finding and resolving the problem.


    I’m running it on DOS but thinking of upgrading to Win 3.1 once I’m sure its stable.

    The flat UI on Windows 10 looks suspiciously familiar. :/

    I've heard rumors that they just filed off the serial numbers on Win 3.1 and re-released it as 10. They're a west coast company after all, and recycling is all the rage these days.

    I won't go into every detail of your post (some I agree, some I disagree) ... but regarding the above statement: This isn't true. Windows 10 still costs money. Buy a new Windows laptop/computer/tablet and be sure that the manufacturer will have paid an OEM price ... and you pay for getting the product being equipped with Windows 10. My rough guess would be around 32 billion US$ revenue from Windows 10 per year (about 25% of their revenue). So it's far from free. ;)

    You're right, of course. My thinking was influenced by the long term giveaway program when they were first promoting it, but I would imagine OEMs have always accounted for far more revenue than individuals buying an upgrade.

    In the current state if you try to load the DLL on Windows 7 you instantly get an error because unknown Windows 8 things are static linked.

    Ah, the joys of DLL Hell. I think dynamic link libraries are probably responsible for more grief than all other Windows issues combined over the years. When I was writing air traffic control software (back in the C++ / MFC days), we used to statically link all libs to try to minimize that hassle as much as possible. I'd gladly buy more disk space to get rid of dlls, but that's not going to happen without a time machine or some dimensional shifting to a more reasonable universe. Oh, well...

    Great work on the editor, man. I'm sure you guys have been burning the midnight oil for quite some time.

    They said from outset they would not be making any editor Win 7 compliant so I wouldn’t hold your breath.

    I don't think adding W7 compatibility to even be an option: I am certain the code would need to be different, and you have to draw a borderline somewhere in terms of back-compatibility, since supporting both Win 7 and 10 means a lot more effort for a developer.

    I'm probably one of the most vocal opponents there is of Windows 10 in general. Nonetheless, I agree that there's a better chance of an asteroid wiping out humanity than there is a Windows 7 version of the editor. Even the small, furry creatures who benefit from our demise would probably still be running Windows 10 (SFC Edition).

    I've typically used Microsoft Security Essentials, as many antivirus companies are as sketchy as the viruses they protect against. Recently I've been getting failures on definition updates. MSE is Windows 7 only, and my guess is that they're reducing the number of servers that handle these connections, but that's just a guess. In any event, it's an indication that I've ridden this pony about as far as it'll go before things start getting weird.

    So, I've been slowly migrating some non-critical boxes from 7 to 10 the past few months. Older 32 bit laptops that ran fine with 7 are significantly slower with 10. That may be the 4 gig memory cap in a 32 bit OS, hard to say for sure. The 64 bit laptop for my keyboard station running Cubase 10 seems to work fine. I'm still reluctant to change my studio or dev boxes as I depend on these, and there's always some bit of hardware or software you depend on that doesn't play nice in the new world. Since 10 doesn't do anything for me that 7 didn't do, I have little enthusiasm for fighting that battle before I have to. In fact, I'm only doing these upgrades at all because ultimately, I just don't have a choice. There is absolutely zero value to me in moving to 10, but I have to do it anyway.

    My livelihood has been dependent on Microsoft operating systems and dev tools since DOS 3.1, so I'm used to change and am far from a technology Luddite. In fact, I've typically been excited about each new release since, like music gear, it's a new toy to play with. Some versions of Windows I've loved, some I haven't been terribly impressed with (e.g. Vista was a bit of a clumsy transition). Windows 10 is the first version that I actively, passionately hate, and that's because it's a paradigm shift that's not at all in favor of the paying public.

    Microsoft doesn't pay for my computers or software. I do. But with the advent of 10, I have now lost control of the systems that I (allegedly) own. There are tricks to disable automatic updates. And they work. Until they don't. And even the briefest foray into the "privacy" settings reveals an avalanche of phone home activities that are on by default, coupled with the message that there's some stuff you simply can't turn off. MS, not I, now controls the vertical and the horizontal (for all you Outer Limits fans). On a computer that I paid for.

    In addition to the privacy implications and the fact that MS can now install updates at will (and that will become even more relevant in the future), there's another thing that the general public won't see coming until it's too late. From the earliest days of Bill Gates' reign, he complained about piracy and wanted to move to Software as a Service (SAAS) since it's easier to prevent theft that way. MS has always charged for Windows (and it's been a significant profit center), but suddenly, with the advent of the always-connected Windows 10, they decided to give it away for free. Am I really to believe that MS has now become a philanthropic non-profit organization?

    The simple fact of the matter is that once the world has converted to 10 and there's no going back, and they can push updates at will without your consent (I'm sure it'll be in the 1000 page terms of service that we never read), there's nothing to stop them from flipping a few switches and starting a new subscription service for Windows. Instead of purchasing an OS license as we have in the past, Microsoft will now be a monthly utility bill, an added expense that you simply have to live with. Your cost of living / doing business will go up whether your income does or not. And they can raise prices whenever they want. After all, what are you going to do about it?

    When Adobe was in transition and introducing their Creative Cloud (CC) platform I was active on the forums and expressed concern that perpetual licenses (the ones where you "buy" the software instead of renting it every month) would go away. Adobe employees swore up and down that would never happen. That's exactly what happened.

    However, that's not the most chilling thing about their change. I love subscription services and paid for Microsoft's MSDN for many years. At the end of the year if you didn't renew, you still owned the licenses you got during that period. With Adobe CC, as soon as you stop paying, every Adobe app is bricked. You can no longer work on any of your projects. Their apps phone home (sound familiar?) and if you're not paying rent, they simply won't run. So, either pay the Adobe Tax for the rest of your life, or completely lose the software, no matter how long you've been paying.

    Now imagine this happening with your computer's operating system. I promise you, the only reason MS hasn't already flipped the SAAS switch for Windows is the fear of a massive beat down by federal regulators. They're a for-profit company that's always charged for Windows. To think they suddenly no longer want to make money off of it is naive. Most likely the SAAS change will come incrementally, to raise fewer flags. First splashy new features (if there are any left) will only be available by subscription, and it will creep from there. And if you depend on Windows, there's not a thing you can do about it.

    Lest you think that I just bought a fresh, new tinfoil hat, I would offer that those who fail to learn from history are doomed to repeat it. Adobe got away with their forced conversion to the Adobe Tax because they hold the creative community at gunpoint. But they got away with it nonetheless. More and more software companies are moving to SAAS, and some have tried doing way with perpetual licenses to varying degrees of success, mostly based on whether or not people had options. The software world really wants to move to the Monthly Tax model, and they will if they can. And if you think Adobe had people by the short and curlies, consider Windows.

    And yes, I do realize that I'm just barking at the moon. There's absolutely nothing I can do to avoid this future short of installing a different operating system. And if Microsoft gets away with it and sets the precedent, you can be sure that Apple won't be far behind. Perhaps it's time to look at Linux. Oh, wait. The Editor won't run on Linux. Like most everything else in the world.

    So, I've delayed my move from Windows 7 for as long as possible because I simply don't want to hand over the keys to my computer to someone else. Call me old fashioned, call me a control freak, but this ain't your grandfather's Windows update. I suppose my protest is little more than holding up the social finger to Microsoft, but if I'm going to be held at gunpoint, I'm not going quietly.

    Hey, Chu.

    I would recommend getting in touch with Kemper and including the specifics on the version of Windows that you're currently running, i.e. the build, etc. rather than just "Windows 10". It'll help them with debugging.

    You might have uncovered something in the installer that they can address, solving your problem and keeping others from experiencing it.

    Is there some sort of manual for the editor controls? I have seen the posts about shift and ctrl keys so far

    There's a beta manual on the same page as the editor download. It's got a couple of pages about keyboard shortcuts.

    It seems a bit thin but I don't know if that's because a) it's a beta manual or b) it's just not that complicated since the knobs are already documented for the profiler itself. Could be either.

    I've got a Windows 10 tablet which throws up a dll missing warning whenever I try to install RM3 so I'm not able to give it a go.

    It's likely that it's due to it being a cheapo thing but thought I'd bring it up.

    Thanks anyway and I look forward trying to get it to work :):):):)

    I don't think it's about cheapo hardware, so it's a cat you can probably skin (if you're into hairless felines, of course). If you're getting an error about a missing dll, there's a good chance that there are Windows updates that you haven't installed. Usually these updates are automatic but sometimes installations don't happen properly (Stuff Happens).

    If it were me, I would Google the name of the dll. You'll have to wade through a lot of "is this a virus?" results but if you keep going you'll probably find a reference to a Microsoft Knowledge Base (KB) article or update referring to that dll.

    It may also be related to a device driver, which can be it's own thing, but again it's a problem that can probably be solved.

    If you'll post the name of it, I don't mind doing a little poking around to see what I can learn. There are guys here who work on the IT / support side of the fence who would be even better resources and some of them may chime in as well.