1. Forum
  2. USENET
  3. rec.audio.pro

  • Re: Is there anybody =?UTF-8?B?aGVyZT8=?=

    From Tim Sprout@timsprout@yahoo.com to rec.audio.pro on Fri Dec 13 19:08:05 2024
    From Newsgroup: rec.audio.pro

    I use Reaper because of its ability to record midi tracks of my
    electronic tom tomrCOs. What I donrCOt like is that for sessions longer than two hours Reaper begins a new 2nd wav file so I have to stitch the two consecutive tracks together in Audition where I do my editing.

    (Still lurking amateur, these days using NovaBBS, free browser based
    Usenet)
    --
    Tim Sprout
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Nil@rednoise9@rednoise9.invalid to rec.audio.pro on Tue Dec 17 17:24:17 2024
    From Newsgroup: rec.audio.pro

    On 13 Dec 2024, Tim Sprout <timsprout@yahoo.com> wrote in
    rec.audio.pro:

    I use Reaper because of its ability to record midi tracks of my
    electronic tom tom's. What I don't like is that for sessions
    longer than two hours Reaper begins a new 2nd wav file so I have
    to stitch the two consecutive tracks together in Audition where I
    do my editing.

    As someone pointed out, recording MIDI doesn't create WAV files. Sounds
    like you may be recording the output of a software synth to a file, but
    that's probably not necessary.

    There is a setting to control how Reaper will create multiple files
    during a long recording (Options | Preferences | Recording | Start new
    files every (x) megabytes.) You can disable it, but it's a good safety measure. You shouldn't have to manually stitch the files together -
    when you render the track the system will do that for you seamlessly.
    --- Synchronet 3.21a-Linux NewsLink 1.2