Posts by mollydyer

    . I get it that Windows 7 will be out of support from Microsoft soon

    Windows 7 End Of *Extended* support is January 14. It was End Of Life five years ago. FYI. It's not soon as in 'maybe sometime this year or next',


    While it's still possible to have your toolchain target windows 7, the costs associated with supporting an unsupported operating system do not math. I'm not surprised at all that Win 7 is not supported.

    FWIW, Win 10 is quite stable. I have it running on a tablet and it drives my whole show.

    Really... that's interesting. I routinely send those CC#s to change to the performance, and then slots within over MIDI. Mind you, I'm either using QLAB or my uTrack 24.

    It's a lot easier from a workflow perspective when I'm laying out the backtracks - I set the performance, and then set the slots as needed.

    Is there a technical reason to go the way you mentioned over the CC#s? Is this an Ableton specific thing?

    Lol... Anyone else see the irony of the mis-edited quote in 7string's post up there?

    For anyone who thinks Software Development is easy- I'd love to see what you can do. Hell, assemble a team if you want. Make it even bigger than the Software team at Kemper too.

    Also bring in a product manager, ux designer, qa testing team, release manager in addition to the development team. Then you'll set the product goals & design, write out the epic, create the user stories for the engineering team to execute on. Then, after each sprint they'll review what they've done, and make sure the direction is set properly for the next sprint.

    Finally, as the project nears completion - you'll engage the QA resources to start testing. All while reading some of these frankly childish and toxic posts.

    Lather, rinse, repeat until QA says it's ready to go, then you pass it along to the release manager.

    And that's just the editor. The same thing is happening for the OS update that will pair with it.

    This is a LOT of coordination.

    I find it absolutely laughably entitled that some of you people are complaining about something - no matter how cool it is - will be delivered to you *at no extra charge*. So, the next time those of you who are so inclined to complain about this feel the urge- I want you to do the same within your own field- music - write, produce, record, mix, master and release a song- for free - while your fans bitch about it not being out soon enough. At the same time you're doing this, rewire the studio.

    Give them some slack. This isn't easy.

    Quote

    I don't mean to hijack this thread,


    But ya did, didntya?

    You really should start a new thread for that. I don't think your points are invalid - they're just quite OT from the Editor, even if this is just chit-chat now.

    Well - as much as I'd love the editor to be out...


    By now, experienced Kemper users have a workflow sorted out for building performances. I do. The editor is candy, not soup.


    D

    It does help.


    Of course I realize that they have internal betas before the public ones. So a RC in Kemper fashion would be first released as a public beta once they decide it, and if everything goes well they would elevate it to a Release version.


    So, in real world out of Kemper offices it means that we are close to a beta release.

    They way I do software releases is like this:

    Alpha: Developer only code. Guaranteed to break. Might even catch fire. Not for public consumption. May or may not be feature complete.

    Beta: Developer and Testing code: May or may not be feature complete, but it's more stable than Alpha. For testing purposes. Not for the general public, although open public betas are possible (Kemper does this with the OS, but I don't think they do it with Rig Manager)


    Release Candidate: Testing code. This is the version that will go to the quality assurance team. It is feature complete, code reviewed and typically an indication that the product is ready for release, but additional testing is warranted. For big projects (developer tools, operating systems etc) this is released to partners and developers- but the general public is often not involved in RCs.

    Kemper may do things differently though.

    The fact that GString has called this a RC is very very good news. It tells me three things:

    (1) They're being incredibly diligent with what will become mission critical software. I truly appreciate this.
    (2) They've completed the herculean task of building the editor and are happy with the result.
    (3) They're very close to being finished.

    I'm following this thread because it's incredibly funny now. Kemper users are a better sort than some of their competition's customers, but there's a level of entitlement in this thread that entertains me. Those who don't develop software often grossly underestimate the time, effort, energy and skill it takes to do so. It's not easy - and the Kemper's software is complex.

    we are running test. i cannot predict the future, so i cannot know what we will find next. I thought the word "release candidate" give you a good indication of what state the product is in. when i'd read this, I'd think "that's good news". but if you want to know if it's 2 weeks or 4 weeks - the answer is simple: i could only guess and that does't help anybody.

    GString  

    You can 100% tell the software engineers from other profession by reading the replies, eh? Thanks for the update. This is very good news.

    Maybe a RC means something to the many software developers that use the forum. But for the rest of us it doesn't mean much. We are only used to the typical beta versions that you release. But we are not aware of the internal process you have before they really get released.


    Anyway, what I get from your message is that we still are weeks away from a beta.


    Thanks for the update.

    Atlantic


    A RC - Release Candidate - is a bit beyond beta. It's the step software takes between beta and production. Typically, it's a code complete version of the product that's gone for rigorous internal testing. It is not uncommon for software to go through multiple release candidate versions - but as the name implies, it's so close to ready that they have a version they're considering releasing.


    It means the project is feature / code complete. The developers are happy with it. The product manager is happy with it. It's just being vetted.


    Does that help?

    round and round and round we go.


    it's amazing to me that people will make the same posts that 30 others have already made.

    What's probably ironic is that even this post has likely been made bef...


    oh. sorry.

    See, that's some good feedback there everyone. I ditched ALL of my pedals - even the ones I thought I'd keep to fill voids - including my wah and my talk box - because I can get the tones I need out of the Kemper.

    Now there's something I've been thinking about - a synth pedal and perhaps an outboard looper - we don't have a keyboard player, but I'm not quite in need of these yet.