wolfstudios53 Posted July 30, 2019 Share Posted July 30, 2019 Everything fine here! Windows 10 build 17134.885 Thanks Bakers! Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 30, 2019 Share Posted July 30, 2019 Do any of you with the issue have any control surfaces set up? If so does disabling it resolve it for you? Link to comment Share on other sites More sharing options...
Promidi Posted July 30, 2019 Share Posted July 30, 2019 1 hour ago, Noel Borthwick said: @Promidithe project file you sent loads fine for me - without all your plugins. Can you please send a Minidump so we can investigate the source of the crash? Unfortunately this issue does not generate a minidump Link to comment Share on other sites More sharing options...
HIBI Posted July 30, 2019 Share Posted July 30, 2019 So... in short, does this issue happen with specific MIDI device is set as MIDI inputs? Seems no problem here. (FYI: there is only UA-101 as MIDI inputs on my system) Link to comment Share on other sites More sharing options...
Elena Kolpakova Posted July 30, 2019 Share Posted July 30, 2019 Maybe it's one of those bugs that were observed in earlier versions for users of NI keyboards, when Omni is selected as MIDI IN on an instrument track for the instance of the Komplete Kontrol VST Plugin. It would somehow turn into several MIDI ports selected at the same time: * Komplete Kontrol - 1 (first physical MIDI out over USB that contains the keybed data - notes and controllers) * Komplete Kontrol 1 (MIDI Out of the first instance of the Komplete Kontrol VST plugin loaded in the instrument track) * Komplete Kontrol DAW (second physical MIDI out over USB that contains transport control buttons) This would cause notes to be recorded twice (one from keyboard, another from MIDI through of the KK VST plugin instance) and other annoying inconsistencies until one manually set the MIDI IN to Komplete Kontrol - 1. So maybe some had projects where those Omni inputs were never manually fixed, and the new version just dies when it faces such tracks. That's a lot of guessing on my end though considering I haven't tried 2019.7 yet ? Link to comment Share on other sites More sharing options...
pax-eterna Posted July 30, 2019 Author Share Posted July 30, 2019 Thx Noel - I have replied. @Promidi thx for posting that but it made no difference. FWIW when I checked the MIDI devices, none were selected even though I know before the update they were. So I tried re-enabling it and that made no difference either. going on most of the replies it seems it is a local issue so it could be a bitch to try and sort out Link to comment Share on other sites More sharing options...
pax-eterna Posted July 30, 2019 Author Share Posted July 30, 2019 I think I found the issue. So far so good - narrowed it down to the Allow Only One Open Project tab. Turned it off and projects now load. I will advise if it happens again. 3 Link to comment Share on other sites More sharing options...
chuckebaby Posted July 30, 2019 Share Posted July 30, 2019 5 hours ago, Promidi said: I have actually lodged a support ticket with Cakewalk Support. I included a copy of a complete project file where this issue manifest for them to have a look at. I also exported an MSinfo32 report and sent that as well. I've known you for a long time on these forums. Im not doubting you P-Mid. Just trying to help narrow down weather it might be specific builds, set ups, soundcards, exc. I applaud your follow up with Cakewalk, it helps when users submit stuff like you did. Helps us all 1 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 30, 2019 Share Posted July 30, 2019 @pax-eterna thanks for your report. We were able to repro it and I have a fix. The problem only occured when "Allow Only One Open Project" was enabled which is why it wasn't spotted. We'll send out a build with this soon for you to try out. 3 1 Link to comment Share on other sites More sharing options...
Jim Fogle Posted July 30, 2019 Share Posted July 30, 2019 8 hours ago, Promidi said: Unfortunately this issue does not generate a minidump @Promidi and others, Noel Borthwick wrote a pretty concise post about minidumps. The post includes information about how to collect a minidump report when one is not automatically generated. Here is a link: https://discuss.cakewalk.com/index.php?/topic/3865-better-problem-reporting-how-to-capture-a-crash-dump/ I also have a link to the article in my signature. 1 1 Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted July 31, 2019 Share Posted July 31, 2019 For those experiencing the problem with project load in 2019.07, please go ahead and try the new Hotfix Early Access build here: 1 Link to comment Share on other sites More sharing options...
pax-eterna Posted August 1, 2019 Author Share Posted August 1, 2019 Cool, thanks all at Cakewalk for the hotfix - opening projects issue has gone (related to one project only button) - with the Allow Only One Open Project checked! Link to comment Share on other sites More sharing options...
John Nelson Posted August 1, 2019 Share Posted August 1, 2019 Working great here. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now