[Rwp] Determining Input (Recording) Peaks

[Matej Golian]

James, that sounds fantastic. I took a look at Osara and the feature
list is pretty impressive. I guess I'll wait for the key map file to
arrive, before I start using it though, because at the moment I'm only
familiarizing myself with Reaper and so the functionality ReaAccess
provides is more than enough for me. I hope, however, that I won't
have to wait too long for it. :D

2015-02-08 23:24 GMT+01:00, Scott Chesworth via RWP <rwp at bluegrasspals.com>:
> Now you're just showing off :P
>
> On 2/8/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
>> OSARA supports timed or indefinite peak hold.
>>
>>
>> Sent from a mobile device
>>
>>> On 9 Feb 2015, at 5:01 am, Scott Chesworth via RWP
>>> <rwp at bluegrasspals.com>
>>> wrote:
>>>
>>> Hi Matej,
>>>
>>> Sure, you could use the Peak Inspector for this. Most of the time here
>>> though I just use J and K to check the left and right channels of the
>>> armed track. The main advantage of Peak Inspector so far as I can tell
>>> is that it can alert you when a defined threshold has been reached,
>>> but it's kind of a dangerous game to be recording so close to 0 DB
>>> that those alerts would be necessary on the way in. There's plenty of
>>> articles on the web about the optimum level to aim for if you like to
>>> read that stuff. Here, I generally aim for somewhere around -10 DB
>>> unless it's a particularly dynamic signal, in which case I'll leave
>>> some extra head room. Unfortunately, Reaper doesn't seem to have a
>>> function where the meter will hold indefinitely at the loudest point
>>> like some other DAWs do, so you'll need to practice catching a reading
>>> that's close to the attack of the signal. Again, if in any doubt,
>>> leave yourself some extra room for error.
>>>
>>> Hth a bit. Yeah, there are quite a few keystrokes dedicated to
>>> metering with ReaAccess, but many of them essentially do the same
>>> thing.
>>>
>>> Scott
>>>
>>>> On 2/8/15, Matej Golian via RWP <rwp at bluegrasspals.com> wrote:
>>>> Sorry, but any suggestions, anyone? :D
>>>>
>>>> 2015-02-06 14:39 GMT+01:00, Matej Golian <matej.golian at gmail.com>:
>>>>> Hi,
>>>>> sorry for yet another basic question, but I just can't figure it out
>>>>> on my own. I'll get straight to the point.
>>>>> Let's say that I want to record a musical keyboard. I create a new
>>>>> track, select the 2 inputs of my audio interface into which my
>>>>> keyboard is plugged in as the recording source for that track. So far
>>>>> so good, but how do I know whether the input volume isn't too loud or
>>>>> too low? Is this what the peak inspector is for or is the peak
>>>>> inspector only usable in case of imported/already recorded audio?
>>>>> If it is the peak inspector, is the process of detecting input volume
>>>>> as simple as turning on the peak inspector, selecting the appropriate
>>>>> options in the dialogue that appears and than pressing alt + F9
>>>>> through F12 while playing the keyboard? I ask because in addition to
>>>>> the ones I already mentioned quite a few shortcuts related to peak
>>>>> detection seem to exist (j, k shift + j, shift + k).
>>>>> Many thanks.
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
>