My first issue is a very basic how to connect the keyboard to the Mac's USB. One Youtube vid has the keyboard's MIDI IN and OUT ports connected to a USB via a single MIDI cable. Another vid has the keyboard's "Host" connected to a USB (the "Host" is a different type of port to the MIDI IN and OUT and so this would need a different lead). And yet another vid shows this connecting to a computer's USB via what I think is a MIDI hub.
Download Zip https://urlcod.com/2yMP5K
My second issue is, even if I connect this keyboard, will it work with Pro Logic X. I can see a generic Yamaha driver online, but cannot see any posts on specifically connecting this older generation keyboard specifically. Are these things usually plug n play or are there some fairly generic drivers out there?
You better opt for the MIDI-USB interface, connecting your MIDI In and MIDI Out from your PSR keyboard to the MIDI interface and that MIDI interface to your Mac USB port. There are many MIDI interfaces available; no need to go for the one suggested in the PSR user manual. If you don't plan to connect (simultaneously) other MIDI devices to your Mac, a basic MIDI-USB cable interface should suffice and they are less expensive. Drivers installation for the same are most likely required. However, it is recommended to acquire one of reputable quality (such as M-Audio Uno or Roland UM-One, etc...) since there are some on the market that are unreliable, although their very low price make them quite appealing. Troubleshooting is a real pain when faulty cabling is involved...
Besides the (most likely required) drivers to make the (above mentioned) MIDI interface to work, there should be no need for your PSR keyboard to transmit MIDI to Logic (or any other MIDI apt software). MIDI is a protocole that all the softwares that deal with MIDI has to adhere to.
Buy any Logic Pro X compatible MIDI interface and connect to this from the MIDI in and out on the PSR. MIDI interface connects to MAC. MIDI interface should come with it's own driver. No driver needed for PSR. PSR settings as per user manual and with bit of luck the whole thing works out!
Normally, once you had bought your MIDI interface, you would pay a visit to the company web site to look for and download their most recent drivers for that specific MIDI interface model and your computer model. Reading their advice and installation instructions for your specific setup is highly recommended. Installation of the drivers usually are done before connecting the MIDI interface and while Logic (or any other MIDI related software) is not running.
Hi,
I don't know, if I understand you correctly, but if you want to use the keyboard just as a MIDI-Controller, all drivers are already contained in your Linux distribution ("alsa-drivers"). No vendor specific drivers are needed. USB-to-MIDI is class compliant normally.
I'm using a USB-to-Midi cable, as I did before on this machine when I was running Windows XP. The reason I assume I need a driver is that there is no audio or _visual_ response after I hook everything up and load PianoTeq -- by which I mean the graphic in the PianoTeq window that would show the keys on my YPG-235 are being depressed. In other words, it seems as if PianoTeq is not recognizing any connection to the keyboard.
I saw a picture of the Yamaha YPG-235 and it just seems to have an USB-output. It should be possible to connect it directly with an USB-Port of your PC. Sometimes it works better with an USB 3.0 Port, which has a higher current than 1.1/2.0. Wherefore did you use a "USB-to-Midi"-converter?
tango studio, ubuntu studio, kx studio... are just distributions like your ubuntu. An environment around the Linux-kernel. They are just more specialized for audio-purposes an have more audio-relevant Packages preinstalled.
You can watch, what happens in the moment when you plugin the USB-cable. Open a terminal window before that, login as user 'root' or sudo to it. Then type 'tail -f /var/log/syslog' and watch for the new usb-devices appearing.
1. Check whether the usb device is recognized with the command 'lsusb'
If not, then you have a problem with your usb ports or drivers.
If it is recognised, you will get something like this:
Bus 002 Device 002: ID 0a4d:00a0 Evolution Electronics, Ltd
Although with some no-name usb-midi converters the actual device name might be blank. The two numbers xxxx:xxxx uniquely identify your usb device. If all else fails, try searching for them on google.
2. While the cable is plugged in, check whether the appropriate kernel modules are loaded (something like usb_midi or snd_usbmidi_lib or the like. you can check with 'lsmodgrep midi').
If not, try loading them with 'sudo modprobe module_name'
3. Take a look at the ALSA inputs and outputs and connect those where necessary by using 'aconnect -i' to list inputs, 'aconnect -o' to list outputs and 'aconnect in_port out_port' to connect inputs and outputs.
You can also verify that an input gives us the right MIDI messages using 'aseqdump -p in_port'
If you are using an M-audio midisport USB to Midi connector, you may need to install "midisport-firmware." In Ubuntu, you can install it directly from the Ubuntu software center. I don't know if other distributions will allow you to install it directly or not. Alternatively, this website might help: -midi-fw.sourceforge.net/
Connect the output end of a third party MIDI device to the "MIDI In" port on the back of the console. If you are using an external USB MIDI device such as a USB keyboard or an external USB MIDI Widget to receive MIDI then connect the external USB MIDI device to one of the USB ports on your console. Please note that only generic "USB MIDI Class" devices are supported. Any USB MIDI devices that require proprietary drivers may work with Hog 4 PC as long as the specific driver is installed on the Windows machine but these types of USB devices that require specific drivers will not work with Hog 4 OS consoles.
Map a MIDI device to one of the listed indexes by pressing the blue plus button located to the far right of the index, then select a MIDI device from the device drop down menu and press Apply. (On Hog 4, Hog 4-18, and Full Boar 4 consoles the built-in MIDI device will be listed as "LTCMIDI".)
Each entry in the MIDI Map table represents a MIDI input signal and a resulting Hog activity. For example MIDI Note 1 on channel 1 could be assigned to trigger a GM1 comment macro. Please refer to the sections below for details on how to create, rename, edit, and delete MIDI maps as well as information regarding how the different modes utilized for MIDI Controller messages.
Learn Mode provides a quick and easy method for buidling a MIDI Map by simply wiggling physical controls on a MIDI Device and then pressing/moving a Hog 4 feature such as a front panel key, encoder, or fader.
Since control messages are sent is a variety of ways based on the MIDI device, the following modes can be assigned to a MIDI Controller entry. These modes cannot be automatically detected by Hog 4 OS, therefore 7-bit Relative Mode is used by default for all controller type entries in the mapping table until the operator assigns the entry to the most appropriate mode.
14-bit messages are two standard 7-bit MIDI CC messages combined to form a single 14 MIDI CC data point and are always sent as a pair as Course byte , Fine byte. Hog 4 OS cannot detect this based on input from the MIDI controller and therefore you will have to manually configure mappings for 14-bit vs 7-bit based on your knowledge of the MIDI controller product you are using.
b1e95dc632