trying to jump into mid on reason

  • warzone round 1 voting begins in...
T

The Bastard

Guest
yeah i play the keyboard and im trying to jump over from recording my synth and looping it to using midi,until know i always recording my samples and drums and looped them in acid then carried over that project into a 4 track sequencer and added vocal from there,well i was convinced that midi was the way to go for music production so i bought the program reason and in attempting to connect my keyboard which has midi outputs and input ive come to relize i have no damn clue why its not working i set up everything right in the prefrences diaolog, i think ,it says once the keyboard is installed properlly that when a key is pressed a certain sound will play,i have the midi wire going from the output of my keyboard to the input of my soundcard,my soundcard is selected in the midi prefrences dialog the only thing i wasnt to sure about was the appropriate channel to select,i have a basic concept of how midi works im just having trouble setting this up i has a yamaha psr 292 and im using reason 1, any input would help :confused:
 

Architect

ILLIEN
ill o.g.
Battle Points: 3
What up Inspectah Wu! You should probably go over some guides on the power of Midi recording to really get a good understanding, but check the link out below for some helpful instructions on using Midi with Reason. Here is my take on Midi.

Musical Instrument Device Interface (MIDI)
Basically a standardized means of talking (communicating) to other devices (musical instruments whether software or hardware). Midi is all digital based, it can exchanges information between devices such as tempo, pitch, velocity, and more allowing you to edit those attributes very easily from one device and/or midi controller. You could have three or four or however many midi devices connect them all up using midi cables to each other or to a midi hub and you can be a one man band (controlling sounds from each device simultaneously). I'm sure you may already understand this but I just figured I would give you my short rundown of the knowledge I have of midi.

http://www.midiman.net/support/how_to/phmainmac/reason2.php
 

vitaminman

IllMuzik Staff
ill o.g.
Battle Points: 1
Hey,

Great link, Architect!

On top of that:

1. When you hit a key on the PSR, does Reason give you any indication that it is receiving MIDI, like little lights flashing on and off?
2. Have you tried changing the Sequencer Channel in Reason? It is possible that your PSR is set to transmit on channel 5, and Reason is set to receive on channel 1...they both need to be the same for it to work.
3. I've never used the PSR, but maybe you have to turn MIDI transmission on? This isn't normal, but you never know...

What MIDI interface are you using?

Take care,

Nick
 

Freakwncy

IllMuzik Moderator
ill o.g.
Battle Points: 17
ok... here it is...I have the PSR-410....run your midi out[keybrd]>midi In[soundcard]midi Out[soundcard]>midi In[keybrd].....selected your proper port...make sure [here's the biggie] that your Oct. is -1 and that you have a sound loaded into the NN-19 or whatever you choose and that the little midi icon is present to the left of the device name in the sequencer....now try playing something.... if nothing... try downloading my tutorial and playing the devices using my tutorial....let us know what happens....
 
T

The Bastard

Guest
yeah so i went through the directions real closely from what i read here i have no midi out on my soundcard and from what was in the manual i guess my soundcard wasnt compatible ,i ended up getting a midiman oxygen 8 i love how it works only thing thats gettin to me is theres a lag from when i hit the key to when the sound comes out,it kind of messes me up ,any ideas how tx it, and thanks for all yur input before it really helped i kinda know what im doing now
 

bigdmakintrax

BeatKreatoR
ill o.g.
Battle Points: 123
you have to make sure that the latency on your card is set right....if you use Fruity loops its under preference but reason I oun know....but you can get the board working just like a keyboard...then you'll see what I was talking about....I had that same problem and I could never figure it out until within the last few months....once you get that fixed you can make beats till your eyes fall out...I set the latency as low as possible then experiment until I get it just right....making sure that the keyboard response matches and my sample doesn't get truncated...there is an art to this little piece of getting the midi controller set...
 

Freakwncy

IllMuzik Moderator
ill o.g.
Battle Points: 17
About Latency
At the bottom of the audio page in the Preferences dialog, you will find an indication
of the current Output Latency.
This is the delay between when audio is “sent” from the program and when
you actually hear it. The latency in an audio system depends on the audio
hardware, its drivers and their settings.
If the latency is large, you will notice that the sound is delayed when you play
a device from a MIDI keyboard. You may also notice that reactions are delayed
when adjusting controls on the device panels (for example, if you lower
the volume of a device, you will not hear this immediately but after the latency
time). Therefore, you want to get as low a latency value as possible.
Adjusting the latency
When you select a driver, its latency value is automatically reported and displayed
in the lower left corner of the Preferences-Audio dialog. Depending
on the audio hardware and the driver, you may be able to adjust this value:

If you are running Reason under Windows using a Direct Sound or
MME driver, you can adjust the latency value by using the slider or
the up/down arrow buttons.
The highest and lowest possible values depend on the driver.

If you are using an ASIO driver specifically written for the audio
hardware, you can in most cases make settings for the hardware by
clicking the Control Panel button.
This opens the hardware’s ASIO Device Control Panel, which may or
may not contain parameters for adjusting the latency. Usually this is done
by changing the number and/or size of the audio buffers - the fewer and
smaller the audio buffers, the lower the latency. Please consult the documentation
of your audio hardware and its ASIO drivers for details!

If you are running Reason on a Mac using the Sound Manager Default
Output driver, you cannot change the latency.
OK, so why not just set the latency to the lowest possible value? The problem
is that selecting too low a latency is likely to result in playback problems
(clicks, pops, dropouts, etc.). There are several technical reasons for this,
the main one being that with smaller buffers (lower latency), the average
strain on the CPU will be higher. This also means that the more CPU-intensive
your Reason song (i.e. the more devices you use), the higher the minimum
latency required for avoiding playback difficulties.
For this reason, you should adjust the latency while playing back a test song:
!
If you are using audio hardware with an ASIO driver, and thus need
to adjust the buffers in the ASIO Device Control Panel, you should
make a note of the original settings before changing anything!
1. Pull down the File menu and select Open.
The Reason Song Browser dialog appears.
2. Navigate to the Reason program folder and open one of the songs
in the Demo Songs folder.
The song appears in a new Reason document window.
3. Click the play button on the transport panel at the bottom of the
song window.
Playback starts, and you should hear the song being played back (provided
that you have connected your audio equipment properly).
4. While listening closely for pops and clicks, try lowering the latency
in the Preferences dialog or the ASIO Control Panel.
5. When you get pops and clicks, raise the latency value a bit.
6. Stop playback by clicking the stop button on the transport panel.
Now you have adjusted the latency so that
this song
plays back OK on your
computer. However, you may create more demanding songs, that require
you to raise the latency further.
!
The connection between “demanding songs” (CPU usage) and latency
is especially noticeable if you are using Direct Sound or MME
drivers on the PC. If you are using a specific ASIO driver for the audio
hardware, it may be possible to get very low latency values
(down to a few ms), regardless of the CPU usage. See the electronic
documentation for details about this and general information
 
T

The Bastard

Guest
good look fellas shits proper now,i apreciate that shit a lot, im bustin out with better better beats on reason in 15 minutes then ive ever done the previous setup i had ,

j/w how do i get more samples for the subtractor and redrum?
 
Top