Strange MIDI behavior

  • Thread starter Thread starter famous beagle
  • Start date Start date
famous beagle

famous beagle

Well-known member
So, I recorded a bit with five MIDI tracks, using plugs on each track. And everything worked great. Saved it, lights out. The next day, I brought up the project. I went to add to the keyboard track. For some reason, I get a latency of literally about half a second (when normally the latency is not noticeable at all). Then I realize that three of the tracks are giving me this same problem. But the bass and the drum tracks are working fine -- no noticeable latency.

I'm using the same controller, same configuration, etc. from day 1 to day 2.

Any clue?

And tonight, another similar issue has come up. I tracked another tune with 3 MIDI tracks, each using a different plug, again with no problems (same controller and everything as the first tune). Saved it. Tonight, when I pull it up, two of the tracks are working fine, but one track has decided not to play at all. The data is still there, and the meters show movement, but there's no sound from the track. I've checked and double-checked all the plug settings, track volume, mute, etc.

Any ideas?

Thanks
 
Well, I've figured out what was causing the first problem.

I hadn't experienced this issue with my main rig, but I'm using my laptop rig, which I set up as a portable thing I could use for just doing MIDI demos in bed or something. As I just set it up, I don't have a ton of plugs yet. So I was just using the ReaVerb plug to add verb to my MIDI tracks.

After some trial and error, I discovered that when I removed that plug, the latency went away. So I tried adding the ReaVerberate plug instead. And bingo ... no latency. So I don't know what the deal was with the ReaVerb plug. I tried messing with the parameters in it, but nothing seemed to do the trick.

Anyway, I'm happy to have figured it out. Hopefully I don't run into that problem with a bunch of other plugs.

I don't know what's causing the second problem yet, but I have discovered that if I delete the plug and add it again, it seems to fix it.
 
You haven't got enough RAM to handle all the processing. Reverb eats up a ton of resources - if you're happy with a MIDI track , stem render it, then disable and mute the original, this will cut way down on the CPU usage, then you can add your plug-ins to the rendered stem.
 
mjbphotos said:
You haven't got enough RAM to handle all the processing. Reverb eats up a ton of resources - if you're happy with a MIDI track , stem render it, then disable and mute the original, this will cut way down on the CPU usage, then you can add your plug-ins to the rendered stem.
Click to expand...

Thanks for the tip. It's true that I don't have as much RAM on this system as I do my main one. It's weird though that I didn't have the problem at all with the ReaVerberate plug.
 
famous beagle said:
Thanks for the tip. It's true that I don't have as much RAM on this system as I do my main one. It's weird though that I didn't have the problem at all with the ReaVerberate plug.
Click to expand...

Look at your CPU usage view - ReVerbate doesn't use as much CPU as ReaVerb
 
You must log in or register to reply here.
Back
Top