Automated Preset/Scene midi changes using DAW (Lag)

I made a new track and started from scratch. I made sure that I aligned the CC message to the beat. In this case 42.1.00. The scene won't change until about 42.2.5.

1676843455642.png
 
Hmm. MIDI automation is basically instantaneous through Reaper with my Axe III using MIDI over USB directly and using my old M-Audio interface and MIDI cables. Your settings seem to be correct. One thing you can try is to create a portable install of Reaper (there an option for that when you run the installer). That will let you reset everything back to defaults without messing up your current install. Maybe there's some setting that is making it lag. I'd also try again from a new empty project just in case it's something specific to that project as well.
 
So interesting enough, I was troubleshooting as well with Jon from Reaper.Blog (what a great guy). He suggested to try another machine, I have a laptop. I did a factory reset for Reaper to get default all my settings on my laptop. There's a bigger "lag". I'm also experiencing weird behavior, such as I can't skip more than 1 prest, if I go to "presets page" it auto scrolls
 
It does, also it took a minute for it to "work" when using my laptop. Then it started doing what I wrote
 
Sounds like something is sending a bunch of MIDI traffic from your system. Do you have anything else connected to your MIDI interface? Maybe download a MIDI monitor app see what traffic is being sent. Is the MIDI In light on the front panel on solid or blinking a bunch when you have the cable connected to your interface and the Fractal editor closed?
 
Last edited:
mr_fender said:
Sounds like something is sending a bunch of MIDI traffic from your system. Do you have anything else connected to your MIDI interface? Maybe download a MIDI monitor app see what traffic is being sent. Is the MIDI In light on the front panel on solid or blinking a bunch when you have the cable connected to your interface and the Fractal editor closed?
Click to expand...
I downloaded MidiView and I'm not sure if I'm using it correctly. I picked my Scarlett since that's what I'm using for midi, pressed play on Reaper to see the changes, I don't get any info. Then I picked my arturia keyboard, pressed a key and got information.

As far as the midi light, it seems to light up only when I press play (spacebar) or click somewhere in the Reaper timeline before another change comes up. There's one that it skipped for some reason.

 
Last edited:
Edrod said:
I downloaded MidiView and I'm not sure if I'm using it correctly. I picked my Scarlett since that's what I'm using for midi, pressed play on Reaper to see the changes, I don't get any info. Then I picked my arturia keyboard, pressed a key and got information.

As far as the midi light, it seems to light up only when I press play (spacebar) or click somewhere in the Reaper timeline before another change comes up. There's one that it skipped for some reason.

Click to expand...

https://forum.cockos.com/showthread.php?t=175007 - might be worth taking a look at this. You can watch the midi track fire in reaper (the note shows on the channel meeter) and then watch the unit to see when the midi comes in. Maybe the gap is related to latency on the system, maybe the asio driver thing (as mentioned in the linked forum post), etc. I use reaper all the time for midi changes and don't have any issues, but I only ever send CCs with it.
 
KevinP said:
https://forum.cockos.com/showthread.php?t=175007 - might be worth taking a look at this. You can watch the midi track fire in reaper (the note shows on the channel meeter) and then watch the unit to see when the midi comes in. Maybe the gap is related to latency on the system, maybe the asio driver thing (as mentioned in the linked forum post), etc. I use reaper all the time for midi changes and don't have any issues, but I only ever send CCs with it.
Click to expand...
I used a different method that I think Jon from Reaper.blog suggested yesterday, I had forgotten about it.

The last change, in Chorus, it does not even make the change.
(video may be processing)

 
Edrod said:
There's a bigger "lag".
Click to expand...
Do you mean the midi activity light on the FM3 is flashing later than you expect? If so, KevinP is probably right and this is a Reaper problem. Try a different DAW and see if that has the same problem.
 
Four things...

A) Properly config a MIDI Viewer and confirm you're only sending what you want, when you want, and nothing additional.

B) If your Preset is much over 80% CPU that can slow the FM3 down as it puts audio threads ahead of others.

C) "B" is worse if you're sending MIDI Beat Clock. Better to configure a CC for Tempo and average 1/4 or 1/8 notes to set Tempo IME.

D) Reaper might have a MIDI Offset parameter that you'll need to confirm as configured properly?

My show is automated via Ableton LIVE, and with my presets under 80% CPU, without MBC, the FM3 handles Scene Changes perfectly, so it's likely not the FM3.
 
Last edited:
GlennO said:
Do you mean the midi activity light on the FM3 is flashing later than you expect? If so, KevinP is probably right and this is a Reaper problem. Try a different DAW and see if that has the same problem.
Click to expand...
I should have used a more proper term, there's latency during my patch changes.
These are the behaviors I'm noticing.

The midi light blinks when I press spacebar to play the track
The midi light blinks when it changes presets/scenes
The midi light at times stays on


I have a copy of Ableton Live, I installed and tested this. Unfortunately there's latency there as well.
 
DJD100 said:
Four things...

A) Properly config a MIDI Viewer and confirm you're only sending what you want, when you want, and nothing additional.

B) If your Preset is much over 80% CPU that can slow the FM3 down as it puts audio threads ahead of others.

C) "B" is worse if you're sending MIDI Beat Clock. Better to configure a CC for Tempo and average 1/4 or 1/8 notes to set Tempo IME.

D) Reaper might have a MIDI Offset parameter that you'll need to confirm as configured properly?

My show is automated via Ableton LIVE, and with my presets under 80% CPU, without MBC, the FM3 handles Scene Changes perfectly, so it's likely not the FM3.
Click to expand...
A. I believe it configured midi viewer correctly. I followed a video from their website. I was getting messages only when pressing my arturia keyboard. When I picked Focusrite midi through the select device, I was not getting any messages.

B. My "don't stop B.." preset is at around 57% CPU

C. Not sure if this is what you mean. I also have the track properties set for Item Timebase: Time.

1676990332003.png

1676990412731.png

D. The only thing on midi offset I found was an option for media playback offset in the midi track. I guess this can be used to offset to compensate what's off.

Also, my fm3 froze once while working on this
 
There's a section in a different song where if I click before the solo should be CC - 1 from the previous item change, it changes to CC - 3 which is nowhere programmed. Then it skips the solo section CC - 2.
 
Edrod said:
A. I believe it configured midi viewer correctly. I followed a video from their website. I was getting messages only when pressing my arturia keyboard. When I picked Focusrite midi through the select device, I was not getting any messages.

B. My "don't stop B.." preset is at around 57% CPU

C. Not sure if this is what you mean. I also have the track properties set for Item Timebase: Time.

View attachment 116511

View attachment 116512

D. The only thing on midi offset I found was an option for media playback offset in the midi track. I guess this can be used to offset to compensate what's off.

Also, my fm3 froze once while working on this
Click to expand...
"A", if you're not seeing any MIDI output via your MIDI Viewing program when running, then it's not conf'd correctly.

1) Assign DAW MIDI track out to a MIDI Out on your MIDI Interface.
2) Assign MIDI IN on your MIDI Viewer app to a MIDI IN on your MIDI Interface.
3) Use a MIDI Cable to Loop between MIDI In and Out: "1" and "2" above.
4) Enable MIDI Viewer to record/view MIDI.
5) Play DAW MIDI track.
6) View MIDI Data Stream. Many here believe you're sending additional MIDI aside from the Scene change CC's, and that's likely your problem, though you will not know until you config your MIDI Viewer correctly.

Good luck...
 
Last edited:
I automate everything in my band - I send all MIDI data to two FM3's a bit before it should be triggered.
In Ableton, I think a 1/32 before the actual switch.
Nothing "serious", but to be really on point, I have to send it a bit early.

Your video shows, that you don't hit the right scene directly - instead, you "scroll" through your scenes.
I wouldn't to that - I directly set my scenes via MIDI CC.

ALSO: I think the change is actually before the FM3 is displaying the new scene.
Play along your MIDI automation and listen to your sounds - I think it's already fine, try not to focus on when the FM3 highlights the new scene ..
 
Last edited:
MrPond said:
I automate everything in my band - I send all MIDI data to two FM3's a bit before it should be triggered.
In Ableton, I think a 1/32 before the actual switch.
Nothing "serious", but to be really on point, I have to send it a bit early.

Your video shows, that you don't hit the right scene directly - instead, you "scroll" through your scenes.
I wouldn't to that - I directly set my scenes via MIDI CC.

ALSO: I think the change is actually before the FM3 is displaying the new scene.
Play along your MIDI automation and listen to your sounds - I think it's already fine, try not to focus on when the FM3 highlights the new scene ..
Click to expand...
I don't think it's "scrolling". I think it's doing a PC followed by a CC and you're seeing the default scene (not scene 1) get loaded in between.
 
You must log in or register to reply here.
Back
Top Bottom