Hi I just picked up a slim phatty, love it but have a few issues.
first off, i'm using logic 9, with local control off and 14bit mode set on there is noticeable lag with fast pot tweaks. The light and setting doesn't keep up and carries on after i've stopped moving the pot. In 7bit mode this is not an issue at all. Is this a bug?
another possible bug, using the same setup above, but with the pots set to track mode. Sometimes say if the pot is quite high one way (we'll say to the right for this example) and the parameter is low (to the left). Turning the knob to the left runs faster as expected but if it doesn't pass the led marker and you turn it right it carries on moving fast. So its possible to have the parameter at max even though the pot is say only halfway. Again this doesn't happen if the knob catches up with the led when turning to the left and then turning to the right it behaves as expected. I can only assume this is also a bug.
Finally is it possible to change the cc assignments? i only ask since in logic if you have an audio track selected some of the slim cc's are the same as the logic mixer, for example volume adsr corresponds to mixer sends 1 thru 4. So if you happen to move a knob when on an audio track you can mess up your sends settings. This may be a logic thing, but i've tried to filter them but i jsut cant seem to stop this behaviour.
any help anyone can give me or suggestions would be welcomed
Paul
slim phatty bugs/questions
Re: slim phatty bugs/questions
that last issue is also an issue for me, I usually just select a different channel in logic (one I don't use), this way it won't affect the channel, unless for one thing, one function of the LP seems to solo tracks..hehe
This should be possible to handle in the logic environment, but as I use different midi interfaces at different times it can be a pain.
I don't think this option will be available for the LP though, as it seems that the memory for the OS is pretty much full now.
This should be possible to handle in the logic environment, but as I use different midi interfaces at different times it can be a pain.
I don't think this option will be available for the LP though, as it seems that the memory for the OS is pretty much full now.
Re: slim phatty bugs/questions
i found a small work around for the logic cc problems, this is far from a perfect solution though.
open the ENV then select the clicks and ports page.
add a new transformer, connect slim midi in to the transformer, set the transformer to split the cc (top connection true) and connect the top cable to sequencer input and connect the bottom one to the midi out (you need to open a second env window with the midi isntruments page)
repeat for each cc you want to add to seq input for recording.
This way im able to send the cutoff and resonance pots (which dont interfere with logic) direct to the seq input for recording and everything else goes direct to the slim (with local off) and does not interfere with the logic seq.
Its a pain, but it works with a little effort.
The best solution would be the ability to change the cc numbers on the slim itself, then the offending ones could be changed manually (even by sysex would be nice)
Now if someone can answer the question about the lag with the 14bit mode and the tracking bug i would be greatful
Paul
open the ENV then select the clicks and ports page.
add a new transformer, connect slim midi in to the transformer, set the transformer to split the cc (top connection true) and connect the top cable to sequencer input and connect the bottom one to the midi out (you need to open a second env window with the midi isntruments page)
repeat for each cc you want to add to seq input for recording.
This way im able to send the cutoff and resonance pots (which dont interfere with logic) direct to the seq input for recording and everything else goes direct to the slim (with local off) and does not interfere with the logic seq.
Its a pain, but it works with a little effort.
The best solution would be the ability to change the cc numbers on the slim itself, then the offending ones could be changed manually (even by sysex would be nice)
Now if someone can answer the question about the lag with the 14bit mode and the tracking bug i would be greatful
Paul
-
pipwilliams
- Posts: 2
- Joined: Sat Mar 19, 2011 4:35 pm
Re: slim phatty bugs/questions
I bought the SP last week and also noticed some really weird bugs when using it with Logic 9. For example, rotating the oscillator knob with freq selected will pan the tracks left and right. Also I get a solo'd track at random points with other controls (I could probably figure what is doing this but got too many other problems right now that need resolving!)
I can check off the midi input filters for control changes under project settings which stops a lot of the weirdness but obviously is a terrible solution as, just for starters, it leaves me without use of the modwheel.
I also purchased the Library Editor. The Moog SE virtual Input Port they advise to use with Logic is so temperamental. Loading and saving is flakey beyond belief and it refuses to allow use of the pitchwheel when selected!
Frankly I'm disgusted with all this. Don't get me wrong, I love the sounds from the Phatty but why all these bugs? It seems I'm not alone. I've got other (considerably cheaper!) kit and these work like a dream. I contacted Soundtower 4 days ago too and still have no reply.
Any solution that doesn't involve dipping into the environment would be greatly appreciated
I can check off the midi input filters for control changes under project settings which stops a lot of the weirdness but obviously is a terrible solution as, just for starters, it leaves me without use of the modwheel.
I also purchased the Library Editor. The Moog SE virtual Input Port they advise to use with Logic is so temperamental. Loading and saving is flakey beyond belief and it refuses to allow use of the pitchwheel when selected!
Frankly I'm disgusted with all this. Don't get me wrong, I love the sounds from the Phatty but why all these bugs? It seems I'm not alone. I've got other (considerably cheaper!) kit and these work like a dream. I contacted Soundtower 4 days ago too and still have no reply.
Any solution that doesn't involve dipping into the environment would be greatly appreciated
Re: slim phatty bugs/questions
the track mode bug is a bug which I've fixed in a firmware update coming very soon. I could use some beta testers for it as I am only one person and I don't want to propagate any additional bugs due to lack of testing. Any volunteers?
If you have time for some thorough and careful usage it would be a big help to me.
Email amos at moogmusic dot com and let me know if you'll be using Mac OS or Windows to update your Slim Phatty.
The business with the Logic environment CC conflicts is an old one that goes back to the Moog Voyager. The Little Phatty was required to have the same CC mapping as the Voyager, so it inherited the same conflicts. The Slim Phatty of course must be 100% compatible with the Little Phatty, so there's no freedom to change the CC assignment.
All these years I've been hoping Logic would allow users to re-define what MIDI CCs control Logic's own functions... but alas no joy there either, it seems. The workarounds suggested earlier (select a different track to monitor so that the CCs aren't applied to Logic's own windows and panning etc.) seem to work fairly well.
As for the lag with 14bit mode I'm not sure... there's no lag at all when sending 14-bit data directly from one Slim to another or from an LP to a Slim (or vice versa) so I assume the lagginess has to do with how Logic handles/passes 14bit data rather than how the Slim sends or receives it.
All the best, and my sincere apologies for the inconvenience...
-Amos
If you have time for some thorough and careful usage it would be a big help to me.
Email amos at moogmusic dot com and let me know if you'll be using Mac OS or Windows to update your Slim Phatty.
The business with the Logic environment CC conflicts is an old one that goes back to the Moog Voyager. The Little Phatty was required to have the same CC mapping as the Voyager, so it inherited the same conflicts. The Slim Phatty of course must be 100% compatible with the Little Phatty, so there's no freedom to change the CC assignment.
All these years I've been hoping Logic would allow users to re-define what MIDI CCs control Logic's own functions... but alas no joy there either, it seems. The workarounds suggested earlier (select a different track to monitor so that the CCs aren't applied to Logic's own windows and panning etc.) seem to work fairly well.
As for the lag with 14bit mode I'm not sure... there's no lag at all when sending 14-bit data directly from one Slim to another or from an LP to a Slim (or vice versa) so I assume the lagginess has to do with how Logic handles/passes 14bit data rather than how the Slim sends or receives it.
All the best, and my sincere apologies for the inconvenience...
-Amos