i am having this problem today and had it before. I have a project open with a halion sonic piano. No recorded notes just using it for the sound so I can l can learn boogie woogie piano from a youtube video. It is playing back the notes i played (silently) when I switch back from the YouTube window.
I’m using Cubase 14 pro with a Nektar Impact LX49 midi keyboard.
Not a major issue as I don’t think it happens when I’m only using the Cubase window but annoying. Just tried momentarily switching monitor off the track when switching to YouTube and think that’s stopping it. Does anyone know why this happens and is it a bug?
Hi Martin my only remote is the Nektar Impact 49 midi keyboard/controller. I can’t see a column labelled All Midi Inputs inb midi port setup - see screen shot. But there is one labelled ‘IN All Mic’ and that is checked. Although I’ve used cubase for years I’m still a beginner in some aspects.
I can see that you are using Nektar Impact LX49+ and LX61+ as a MIDI Remote, but also as a Remote Device (Legacy). Please double-check these devices in the Remote Device (Legacy). What kind of Input/Output MIDI Ports do they use? They should be set to None, or even deleted in the best case.
Yes, this way the MIDI Remote will work, so you can remove the Remote Devices. But first, you can just set the Remote Device Input and Output Ports to None, to test it.
Sorry for the delay in implementing what you said. I think I did that. In the legacy remote part of studio set up I set the midi in and out for LX49+ and LX61+ to none. (as an aside I wonder if running the Impact_GX_LX+_SE49_Steinberg_Support_WIN_1.1.26.exe ‘script’ may have set that up using an entry for LX61 to get around the fact that the 49+ has 2 ports one for keyboard and the other for the other hardware controls. One port is named ‘MIDIN2 (Impact LX49+)’ the other just ‘Impact LX49+’. I b
I went to youtube, played some (silent) notes on the LX49+ and on returning to the cubase screen the same notes played by themselves via Halion Sonic. Below are the relevent screen captures. The new lower zone Midi Remote manager has only one input port - but then I created that ‘script’ so may be my error. Apart from the ghost notes issue I’d like the factory script to work as intended with the addition of my custom assignment of knobs to say quick controls and for the midi keyboard to continue to work.
OK, so it’s not involved. Is it the same for the LX61+?
Could you add the MIDI Monitor, MIDI Insert and observe the MIDI data? Then you can select the MIDI Input Ports one by one (instead of the All MIDI Inputs, which you are using, probably), to see if any MIDI Input Port is responsible.
Hi Martin, I set up midi monitor then disconnected all items in the studio set up remote legacy section incl VST and track QC’s then I changed the midi input on the track inspector from all midi inputs to Impact LX49+ (the only other option other than plugins). I then played a single G note with cubase in focus then a single G with YouTube in focus and switched back to cubase and the 2nd note played after a couple of seconds. Setting the midi input to blank in the inspector stopped all notes as did switching of the track’s monitor function.
I set it up for quick controls and other things but so far only used it as a midi keyboard. Can the lower zone remote access cater for 2 midi in’s? I think it’s quite common for multipurpose interfaces like mine with keys knobs faders. I’ve probably not set it up right. There wasn’t a ready made script in the lower zone pull down.
re ghost notes, could it be an artifact of the (v useful) unsollicited midi prerecord function?
Hi Martin, for the midi monitor test above I had disconnected the track vst and quick controls in the legacy section. They remain disconnected. Here’s the screen shot
Apart from the midi keyboard of LX49+ for note input I’ve not really used much it as a midi controller. A couple of years back I ran a Nektar official factory .exe and settup the old style ports within Studio Settup according to Nektar’s instructions. This gave 2 input ports one called ‘Impact LN48+’ the other ‘MIDIN2(Impact 49+)’ A couple of months back I heard about the new midi remote tab and manually created the controller layout and used the midi learn in the new tab to set a few things up like quick controls.
I thought I’d read somewhere that 2 ports are needed , one for the keyboard and one for the surface’s other controls so that there isn’t any conflict between the 2 lots of messages.
What i would like to achieve is a midi keyboard for notes and for the knobs/faders/pads to use most of the close cubase integration Nektar has developed but with some customisation for the likes of VST and Track quick controls and key commands I’d like to trigger.
I can see only the Impact 49+ MIDI Port in your system. If the device is using 2 MIDI Ports (which is quite common to distinguish the MIDI Keyboard and the controllers), then you have to set it up properly.
Any hints on how to set it up properly would be greatly appreciated. Clearly I’m a novice to using a remote. I’m reluctant to do this but if I totally delete the controller
can I setup the 2 midi in ports in the new remote tab
how do I implement Nektars .exe as a starting point. this is a sort of script it seems but without the usual extension scripts have.
thanks for your dedication to sorting me. I expect there are a load of others who are iin the same boat and will learn from this post. Other folk have had the ghost notes thing.
thanks Martin I’ll give that a try. From another forum message i saw that there’s been collaboration between Nektar to sort some bugs so may be worth me waiting till I get V15. Have fired a message to their help desk to see what the latest recommendation is for installing the LX49+. I’ll post here any info useful to other folk.
