Go Back   Cockos Incorporated Forums > REAPER Forums > newbieland

Reply
 
Thread Tools Display Modes
Old 09-24-2017, 12:41 PM   #1
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default Not again - no Keyboard input

If you want to sort through my previous thread "aahhh ...Oh boy" be my guest.

I have no idea why this is not working (again). It worked great for three days of testing, so I carefully wrote out instructions for me to use (see attachment, plus a little extra) - I wanted to make sure I did the same thing every time.

Now my keyboard and Reaper are not talking to each other. I've been tinkering with things but no luck.

Any help is greatly appreciated.

Thanks in advance
Attached Files
File Type: zip Reaper forum verbiage 3.zip (25.0 KB, 155 views)
Wino Bob is offline   Reply With Quote
Old 09-25-2017, 01:41 AM   #2
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

The steps in your attachment look OK.

First thing which comes to mind: are the notes played on the Casio inside the playable note range (indicated by the colored keys in Kontakt's virtual keyboard) of the loaded Kontakt instrument?

When you load the "Band / Classic Bass" instrument mentioned in your attachment, you can see that not all keys in Kontakt's virtual keyboard are colored.
So when you try to play, as example, a C1 MIDI note on the Casio, it won't trigger any sound samples from "Band / Classic Bass" because C1 is outside the playable instrument range (which is in this case: B1-G5 and C6-A#6).

The playable note range can vary depending on the loaded Kontakt instrument.

---------------------------

In general, you can use this to check if any MIDI messages/notes from the Casio are coming into the Reaper Track (see 0:40 - 0:50 in the video): www.youtube.com/watch?v=P5mL2OSTrNc

1) Insert ReaControlMIDI before the Kontakt Plugin in the FX Chain of the Track (you can change the order of the plugins in a FX chain via drag and drop)
2) In ReaControlMIDI: click on the [Show Log] button
3) See if any MIDI messages are displayed in the MIDI activity log window on the right when pressing keys on the Casio

Last edited by solger; 09-25-2017 at 02:18 AM.
solger is offline   Reply With Quote
Old 09-25-2017, 06:17 PM   #3
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default

Quote:
Originally Posted by solger View Post
The steps in your attachment look OK.

First thing which comes to mind: are the notes played on the Casio inside the playable note range (indicated by the colored keys in Kontakt's virtual keyboard) of the loaded Kontakt instrument?


---------------------------

In general, you can use this to check if any MIDI messages/notes from the Casio are coming into the Reaper Track (see 0:40 - 0:50 in the video): www.youtube.com/watch?v=P5mL2OSTrNc

1) Insert ReaControlMIDI before the Kontakt Plugin in the FX Chain of the Track (you can change the order of the plugins in a FX chain via drag and drop)
2) In ReaControlMIDI: click on the [Show Log] button
3) See if any MIDI messages are displayed in the MIDI activity log window on the right when pressing keys on the Casio
_________

1) Yes, I'm staying within the playable range regardless of the sample I'm playing.
2) Added the ReaControlMIDI before the Kontakt Plugin and played keyboard - no midi messages were displayed in the log
Wino Bob is offline   Reply With Quote
Old 09-25-2017, 08:18 PM   #4
Fergler
Human being with feelings
 
Fergler's Avatar
 
Join Date: Jan 2014
Posts: 5,220
Default

Have you tried a different USB cable? Also make sure the device is fully enabled in the MIDI devices part of preferences.
Fergler is offline   Reply With Quote
Old 09-26-2017, 10:59 AM   #5
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

Quote:
Originally Posted by Wino Bob View Post
1) Yes, I'm staying within the playable range regardless of the sample I'm playing.
2) Added the ReaControlMIDI before the Kontakt Plugin and played keyboard - no midi mess(ages were displayed in the log
If you haven't already, try using a different MIDI cable for connecting the Casio to the Focusrite (to rule out a faulty cable/connection).

And also try using the Focusrite with a different USB cable, as Fergler mentioned.
In addition, check if connecting the Focusrite to another USB port makes any difference.


Quote:
Originally Posted by Wino Bob
When I play my keyboard, my Focusrite pre-amp lights up, however
Just to clarify (since you mentioned this in the attachment):

- Is the Casio only connected via MIDI cable to the Focusrite? Or is it connected via Audio cable, as well?
- And in case you have both cables (MIDI + Audio) connected: is this led (which lights up) on the Focusrite a MIDI activity led? Or a led for the Audio Input?

Last edited by solger; 09-27-2017 at 01:56 AM. Reason: typo
solger is offline   Reply With Quote
Old 09-27-2017, 06:20 PM   #6
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default

Quote:
Originally Posted by solger View Post
If you haven't already, try using a different MIDI cable for connecting the Casio to the Focusrite (to rule out a faulty cable/connection).

And also try using the Focusrite with a different USB cable, as Fergler mentioned.
In addition, check if connecting the Focusrite to another USB port makes any difference.



Just to clarify (since you mentioned this in the attachment):

- Is the Casio only connected via MIDI cable to the Focusrite? Or is it connected via Audio cable, as well?
- And in case you have both cables (MIDI + Audio) connected: is this led (which lights up) on the Focusrite a MIDI activity led? Or a led for the Audio Input?
____________
I do not have another pair of midi cables but if this latest round points to that, I will get some. I have switched out a different USB cable and put it in a different USB port. The only connections to the Focusrite are the two midi cables which light up the midi LED.
I’m testing two tracks.
Track one includes ReaControlMIDI and ReaSynth (in that order).
1) When the track is armed and I play the keyboard, I get the appropriate sound from the monitor speakers and midi messages in the log – all good
Track two includes ReaControlMIDI and Kontakt 5 (in that order).
1) When the track is armed and I play the keyboard, I get no sound from the monitor speakers but I do get midi messages in the log.
2) When I reverse the order, Kontakt 5 then ReaControlMIDI, arm the track, and play the keyboard, I get no sound from the monitor speakers. However, I do get sound from the monitors if I use the virtual keyboard.
3) I just noticed, in the upper right-hand corner of the Kontakt Player screen is “tune and 0.00”. The meters move when I play the virtual keyboard, and when I play my keyboard . . . what does that mean?
Wino Bob is offline   Reply With Quote
Old 09-28-2017, 12:38 AM   #7
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

Quote:
Originally Posted by Wino Bob View Post
The only connections to the Focusrite are the two midi cables which light up the midi LED.
OK. An active MIDI led on the Focusrite indicates that MIDI from the Casio reaches the Focusrite.

As a side note: for sending MIDI from the Casio into Reaper, it's enough to just use one MIDI connection: CASIO [MIDI OUT] ---> [MIDI IN] Focusrite. You don't need to connect the second MIDI cable in this case.

Quote:
Originally Posted by Wino Bob View Post
3) I just noticed, in the upper right-hand corner of the Kontakt Player screen is “tune and 0.00”...
- The tune knob (by default set to 0.00) allows you to globally change the pitch up/down: https://support.native-instruments.c...ds-Out-of-Tune
- The L/R slider below the tune knob is for globally panning the output audio signal.
- The level meters in the right corner show the current output level of the instrument. The volume slider below is for adjusting the output volume.

You can find more info in the 'Instrument Header' chapter in the Kontakt Application Reference Manual.

Quote:
...The meters move when I play the virtual keyboard, and when I play my keyboard . . . what does that mean?
Moving level meters in the Kontakt instrument header mean that there's audio output from the played Kontakt instrument. So at this point we know that MIDI from the Casio reaches/triggers the Kontakt instrument and generates audio output (indicated by the level meters). But according to your description it looks like that the audio output from Kontakt doesn't get back into the Reaper Track (for whatever reason) and therefore audio doesn't get through to your Monitor Speakers, as well.

-------

Although I don't think that this might be the issue here, the next thing to check is the assigned audio output channel in the Kontakt instrument header. The default setting [Output: st. 1] should be fine: https://support.native-instruments.c.../OutputSt1.png

Another thing to try in general is loading Kontakt into 2 or more Tracks and see if the problem (getting no audio output from Kontakt) is the same on all Tracks.

If the problem persists, try doing a [Clear cache/rescan] of the plugins via Preferences > Plug-ins > VST, just in case.

Last edited by solger; 09-28-2017 at 08:58 AM.
solger is offline   Reply With Quote
Old 10-01-2017, 09:06 AM   #8
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default

- The level meters in the right corner show the current output level of the instrument. The volume slider below is for adjusting the output volume.

Moving level meters in the Kontakt instrument header mean that there's audio output from the played Kontakt instrument. So at this point we know that MIDI from the Casio reaches/triggers the Kontakt instrument and generates audio output (indicated by the level meters). But according to your description it looks like that the audio output from Kontakt doesn't get back into the Reaper Track (for whatever reason) and therefore audio doesn't get through to your Monitor Speakers, as well.

Another thing to try in general is loading Kontakt into 2 or more Tracks and see if the problem (getting no audio output from Kontakt) is the same on all Tracks.

If the problem persists, try doing a [Clear cache/rescan] of the plugins via Preferences > Plug-ins > VST, just in case.[/QUOTE]
Attached Files
File Type: zip Reaper forum verbiage 4.zip (10.9 KB, 110 views)
Wino Bob is offline   Reply With Quote
Old 10-01-2017, 09:47 AM   #9
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

I had a look at your attachment (verbiage 4.zip) and I'm starting to wonder if this might be a bug of the Kontakt plugin (since it seems to work fine with other virtual instruments like Reasynth) ...

In the Kontakt Player when you click on the NI icon at the top right corner: which version number (5.x) is shown?
And can you please also attach the current .RPP project file (with the 6 Tracks) to a post so I can check if something else comes into mind.

Last edited by solger; 10-01-2017 at 09:53 AM.
solger is offline   Reply With Quote
Old 10-01-2017, 11:39 AM   #10
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default

Quote:
Originally Posted by solger View Post
I had a look at your attachment (verbiage 4.zip) and I'm starting to wonder if this might be a bug of the Kontakt plugin (since it seems to work fine with other virtual instruments like Reasynth) ...

In the Kontakt Player when you click on the NI icon at the top right corner: which version number (5.x) is shown?
And can you please also attach the current .RPP project file (with the 6 Tracks) to a post so I can check if something else comes into mind.
The version is 5.7.0 (R32),License Type-Player, Processor-x64 (SSE, SSE2, SSE3)
Does the "(R32) " mean the 32 bit version, and I have a 64 bit Processor?
Let me know if you can get into the attached - I wasn't sure if I was supposed to use a zip file.

Many thanks solger
Attached Files
File Type: zip midi test.zip (378.6 KB, 115 views)
Wino Bob is offline   Reply With Quote
Old 10-02-2017, 02:21 AM   #11
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

Quote:
Originally Posted by Wino Bob View Post
The version is 5.7.0 (R32),License Type-Player, Processor-x64 (SSE, SSE2, SSE3)
Does the "(R32) " mean the 32 bit version, and I have a 64 bit Processor?
The Kontakt version looks OK, so far:

- 5.7.0 (R32) is the latest available update version (if I remember correctly R32 is just NI's internal Revision number).
- And 'Processor-x64 (SSE, SSE2, SSE3)' indicates that it's the 64-bit version of the plugin (a 32-bit NI plugin would show Processor: IA32 (SSE, SSE2, SSE3))

Quote:
Let me know if you can get into the attached - I wasn't sure if I was supposed to use a zip file.
Yeah, thanks. In general, you can attach .RPP files directly or put them in a .zip file. It's fine either way
I'll report back when I had time to take a closer look at the .RPP file ...

Last edited by solger; 10-02-2017 at 02:46 AM.
solger is offline   Reply With Quote
Old 10-08-2017, 02:12 PM   #12
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

OK, looks like the problem in the 'midi test.rpp' file in post #10 is that there are some things loaded as Input FX in all Tracks - indicated by the little green <IN|FX] button in the second row on the left in the screenshot - which are basically blocking the incoming MIDI from going through the rest of the Signal Chain in the Kontakt Tracks:




So for all (ReaSynth and Kontakt) Tracks in the Project: click on the little <IN|FX] button (shown in the second row in the screenshot) to open the Input FX chain and remove all FX entries from there.

And in general, make sure that virtual instruments like ReaSynth, Kontakt Player, etc. are added (manually) only as Track FX (which is the [FX] button in the first row in the screenshot).

I hope this solves the problem.
Attached Images
File Type: jpg TrackFX.jpg (15.9 KB, 3317 views)

Last edited by solger; 10-09-2017 at 08:43 AM.
solger is offline   Reply With Quote
Old 10-10-2017, 05:51 PM   #13
Wino Bob
Human being with feelings
 
Join Date: Aug 2017
Posts: 33
Default

Quote:
Originally Posted by solger View Post
OK, looks like the problem in the 'midi test.rpp' file in post #10 is that there are some things loaded as Input FX in all Tracks - indicated by the little green <IN|FX] button in the second row on the left in the screenshot - which are basically blocking the incoming MIDI from going through the rest of the Signal Chain in the Kontakt Tracks:




So for all (ReaSynth and Kontakt) Tracks in the Project: click on the little <IN|FX] button (shown in the second row in the screenshot) to open the Input FX chain and remove all FX entries from there.

And in general, make sure that virtual instruments like ReaSynth, Kontakt Player, etc. are added (manually) only as Track FX (which is the [FX] button in the first row in the screenshot).

I hope this solves the problem.
_____

All Input FX entries have been removed (no green lights). For the four Kontakt tracks (regardless of whether the track is armed or not) I get correct sample sounds and meter readings using Kontakt's virtual keyboard.

At first, (also regardless of whether the track is armed or not) I had no sounds or track meter levels (or level meters in the right corner) showing any activity when playing my keyboard.

However, I then restarted my computer. Everything now seems to work!! We were here once before and I swear I will try not to mess anything up (and will pray to the voodoo god of restart).

Thanks again solger - truly appreciate it.

I swear I'm not making this stuff up
Wino Bob is offline   Reply With Quote
Old 10-11-2017, 10:18 AM   #14
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 5,859
Default

Quote:
Originally Posted by Wino Bob View Post
... However, I then restarted my computer. Everything now seems to work!! ...
OK, great


Just as a side note: using ReaControlMIDI's Log function or using a different virtual instrument plugin like ReaSynth as Track FX is a good strategy in general to check if incoming MIDI notes/messages are getting through to the Track FX chain. Or to narrow down if a problem might only be with a certain instrument plugin (if other instrument plugins are working fine with the same setup).

Last edited by solger; 10-11-2017 at 11:05 AM.
solger is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 04:39 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.