gecko zzed
Grumpy Mod
The system:
Firepod through firepod into Logic 5.1 on XP
The story:
I've been successful and blissfully happy using Logic for many years, and its partnership with Presonus Firepod has been untroubled.
In recent times I've become interested in Reaper, and have been experimenting. I used Rearoute to route Logic's outputs directly into Reaper: sixteen tracks popped in without a whimper of protest. However, what got left behind was a tempo map. I thought the answer might lie in Midi Yoke which I downloaded and installed. Silly me!
Midi yoke is good for Reaper as master and something else as slave, but I couldn't get it to work the other way. Not only that, it left Logic without its clock when running as a stand-alone. Not good!
Simple problem really . . . just uninstall Midiyoke, which I did. Which caused Logic to crash altogether. That was an unexpected and unpleasant surprise.
So . . . quickest and most painless way to get things up was to do a system restore, which I did. No worries . . . Reaper ok, Logic ok . . . no midiyoke . . . everything was fine.
But . . . it wasn't really, because when running Logic, I discovered it had lost the Firepod midi device, and midi was being directed to the Microsoft GS wavetable . . . nasty sounds and nasty latency.
So . . . I uninstalled and re-installed Logic, with fingers crossed. But crossed fingers didn't work . . . still no midi output to the Firepod.
But . . . here is the interesting thing:
1 Reaper still fires Midi out to the Firepod ok, and so does Sibelius. So does Cubase that came with it.
2 Windows' Sound and Audio devices all recognise Firepod for midi and audio.
So it does not appear that the Firepod is the problem (and in fact Logic still records via the Firepod just dandy).
But I didn't want to uninstall and re-install the Firepod just yet, though I did turn it off and restart it. Naturally, this had no effect.
I've since done another system restore to an even earlier time, and a re-install of Logic . . . no luck.
Maybe I've somehow distured Logic's environment, but re-installing should have fixed that.
If anyone has a solution, I'm prepared to grovel obsequiously for it.
Help!
anyone?
anyone?
Firepod through firepod into Logic 5.1 on XP
The story:
I've been successful and blissfully happy using Logic for many years, and its partnership with Presonus Firepod has been untroubled.
In recent times I've become interested in Reaper, and have been experimenting. I used Rearoute to route Logic's outputs directly into Reaper: sixteen tracks popped in without a whimper of protest. However, what got left behind was a tempo map. I thought the answer might lie in Midi Yoke which I downloaded and installed. Silly me!
Midi yoke is good for Reaper as master and something else as slave, but I couldn't get it to work the other way. Not only that, it left Logic without its clock when running as a stand-alone. Not good!
Simple problem really . . . just uninstall Midiyoke, which I did. Which caused Logic to crash altogether. That was an unexpected and unpleasant surprise.
So . . . quickest and most painless way to get things up was to do a system restore, which I did. No worries . . . Reaper ok, Logic ok . . . no midiyoke . . . everything was fine.
But . . . it wasn't really, because when running Logic, I discovered it had lost the Firepod midi device, and midi was being directed to the Microsoft GS wavetable . . . nasty sounds and nasty latency.
So . . . I uninstalled and re-installed Logic, with fingers crossed. But crossed fingers didn't work . . . still no midi output to the Firepod.
But . . . here is the interesting thing:
1 Reaper still fires Midi out to the Firepod ok, and so does Sibelius. So does Cubase that came with it.
2 Windows' Sound and Audio devices all recognise Firepod for midi and audio.
So it does not appear that the Firepod is the problem (and in fact Logic still records via the Firepod just dandy).
But I didn't want to uninstall and re-install the Firepod just yet, though I did turn it off and restart it. Naturally, this had no effect.
I've since done another system restore to an even earlier time, and a re-install of Logic . . . no luck.
Maybe I've somehow distured Logic's environment, but re-installing should have fixed that.
If anyone has a solution, I'm prepared to grovel obsequiously for it.
Help!
anyone?
anyone?