![]() If you can stick to this format, I think you’d be a great candidate for a Steinberg tester considering how many issues you found in such a short period of time. Every single beta I’ve been involved with has requested basically the same type of format for reporting bugs to make it easy to identify the issue and reproduce. All of my tech is up to date.Īllegro, echoing what Steve just said, try to post your bugs in the following format. I am using an Alienware Aurora R7 that was purchased in January of 2019. In the years I’ve used Cubase I’ve changed computers, controllers and audio interfaces. But in retrospect, I think I’ve veered away from midi productions because of this very frustrating issue that seems to be constant. It’s really impeding upon production.Īnother note: I’ve been using Cubase for mostly audio for the last several years so the midi thing really hasn’t been an issue. I love Cubase and Steinberg has always treated me AWESOME! No complaints about the company but the early midi recordings and crashes are coming to a head. I think I’m just going to go back to version 10.0 or maybe just bite the bullet and learn a whole new DAW. This was all discovered in about 1 hour of usage. I can’t say this is NI’s software because it wasn’t an issue with Cubase 10 My Midi controller (Native Instruments Kontrol S61) is sending modulation data even when nothing has moved. Turns out that battery was still playing when I’d stop and restart playback quickly. I’ve been sitting here for 30 minutes trying to figure out why the hell it sounds all funky. It keeps on playing even after the track is stopped. Native Instrument’s Battery is performing in some really weird manner that I’ve never seen before. I had to move some audio around after a performance. I believe audio recordings are also off sync too but I am not 100% certain. I’ve tried to switch to another DAW but I’ve been using Cubase for so long that I’ve found myself weighing what is more frustrating: learning to do simple tasks with another DAW or just moving my midi performances. This has been an ongoing frustration since Cubase 3.0. Midi notes are STILL being recorded about 1/16th note early. I did manage to get tracks imported via the “import tracks from another project” so not all was lost. No tail.įirst project I did gave a “Serious error”. It didn’t work when I needed it to work though NOTE: I just tested it again and it worked. I tried to retrospectively import a midi track that I just did and it just came out blank. ![]() Retrospective recording simply doesn’t work.I have to admit, I am a little upset because I just paid $70 for an update that doesn’t seem like much of an update in regard to features. I figure it was a good time to just start fresh. Completely cleaned out my computer too and reorganized. Fresh install of Windows 10 - Formatted SSDs and tested for health (all top notch). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |