|
#11
|
||||
|
||||
|
I'm curious about "Mobius A" and "Mobius B", are you using two instances of Mobius? You may have problems with that, though I guess if you've been using it they're not that bad. This got better in 2.0 but there are some areas of memory that would be shared by both plugin instances and they may step on each other.
Instead of multiple Mobius instances, we usually have one and route host tracks in and out of the 8 plugin ports. So whether or not you are using multiple instances, I'm curious if Reaper allows access to all 8 Mobius input and output ports. That's kind of rare for DAW hosts. Ableton can do it, but Sonar and Cubase can't. |
|
#12
|
||||
|
||||
|
Quote:
Cakewalk Sonar 8.5.3 and X1 most certainty DOES allow access to all 8 Mobius input and output ports and I would be surprised if cubase can’t.
__________________
Be Lucky In Life... Glynn Cakewalk Sonar Producer 8.5.3, and Sonar X2a, HP pavilion dv6 3031TX, Win7-64-bit, 2x Behringer FCB1010, Edirol UA-25, Edirol Quad UA-55, Edirol PCR-500, Rode NT1A, KRK Rokit 8 Monitors, PODxt, AKG520 Cans, too many guitars to list and a Dog |
|
#13
|
|||
|
|||
|
I created a small tutorial for this since I could not find one and posted in this thread in the first place.
http://anders.rustad.priv.no/?p=9 |
|
#14
|
||||
|
||||
|
Thanks for the tutorial, I have one correction.
The reference to synchronizing by setting Sync Mode to Out and Track Sync Mode to Loop applies to Mobius 1.x. In 2.x we no longer have Sync Mode and Track Sync Mode. Instead you have Sync Source and Track Sync Unit. All of these are in the Setup window. In the Tracks tab of the Setup window make sure Sync Source for all tracks is Default and Track Sync Unit is Default. Then under the Synchronization tab set Default Sync Source to Track and Default Track Sync Unit to Loop. You typically want all tracks to share the same Sync Source, but you might want to override Track Sync Unit. |
|
#15
|
|||
|
|||
|
Quote:
Quote:
|
|
#16
|
||||
|
||||
|
In your tutorial there were two links at the bottom. One to the circularlabs forum and one to the loopers-delight archive. I'd suggest taking the loopers-delight link out and replacing it with a link to the Mobius Synchronization manual.
|
|
#17
|
|||
|
|||
|
Hi everyone, and thanks for all the contributions, especially that tutorial. I am now able to record in Mobius via Reaper!!!
One follow-up question: in standalone mode, I was able to get Mobius to respond to my midi controller for controlling looper functions. I just set up the midi device, then used Configuration > Midi Control to bind the appropriate midi CC# to whatever looper function I wanted. However, as a VST in Reaper, I can't figure out the missing link: my midi controller is "heard" by Reaper, but not by Mobius. Perhaps because Mobius is an insert on a track, and I don't know how to set things up such that the host (Reaper) sends midi events to the VST (Mobius). Does anyone know how to do that? Sorry if this is a newbie question, but I searched the forum and the manuals, but couldn't find it. |
|
#18
|
|||
|
|||
|
@abstract_flight
Had the same problem and just figured it out: It depends on your settings in reaper. Go to options/VST compabilty and choose native (no briding). Then you create a Track and you choose the midi input of the foot controller. Send this midi track to the mobius track or just drag it under the mobius track (as a folder). This worked for me
|
|
#19
|
|||
|
|||
|
Quote:
|
|
#20
|
||||
|
||||
|
There are two ways of sending your controlling MIDI from outside to reach the Mobius plugin:
1) Set up a MIDI routing in the host to pick up MIDI at the system's MIDI In port and have it piped into the Mobius plugin. 2) Set up the Mobius plugin to listen directly to the system's MIDI In port. Over the years I have found that the second method, sidestepping the host's MIDI completely, is less complicated and more reliable. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|