Cream and Logic Pro X

[Mark R]

Just a quick note to say that I have found that Cream also works in Logic Pro X but currently (late July 2013) requires an extra step involving rescanning Cream in the 'Audio Units Manager'.

• Find the 'Audio Units Manager' (under the top left preferences menu).
  
  Select 'Cream' and click on 'Reset & Rescan Selection' (takes less than 15 seconds on my mac mini)
  
  Click on 'Done' (wait a few more seconds for a quick progress bar)
  
  Go to the environment and (re)cable Cream's virtual output to the instrument you want to control.

I have to currently do the "rescan" each time I open Logic Pro X (and every time I load a project that uses Cream).

[Kirnu]

Thanks for the info.

I wonder what's the reason for Apple to reimplement this behavior.

I have to dig into this Logic X stuff also.

-Arto

[jimmyfredriksson]

Hi,

I just can't find Creams virtual output in the environment. I hate to think I'm slow haha.

/Jimmy

[jimmyfredriksson]

Weird, now it pops up in the physical input object

[jimmyfredriksson]

Mark,

As you wrote I needed to rescan Cream for it to appear in the physical input.


Arto,

Have you found anything why it has to be rescanned for it to come up in the physical input?


Regards
/Jimmy

[Mark R]

Mark,

As you wrote I needed to rescan Cream for it to appear in the physical input.

Hi Jimmy (and Arto),

I may have found an alternative (slightly shorter) work around for my system with Logic 10.0.2 right now.

Say I'm loading a project that contains an instance of Cream.
If I turn my USB keyboard (Axiom Pro) OFF then back ON, then click on the 'Physical Input', Cream will appear therein (without doing a rescan).

I still usually have to re-cable Cream in the environment and my Axiom Pro has temporarily lost it's 'HyperControl' communication with Logic. But I found that I can reestablish communications by hitting my 'Bypass All Control Surfaces' key command twice.

Curious if this might get better with more Logic updates around the corner and the new Mavericks operating system this fall?

[jimmyfredriksson]

Hi Mark,

First I thought so aswell. I have the Novation Impulse 61 key kontroller with Automap 4.7ish or something. When Logic validates the plugins they end up as 2 different AU's. One with automapping and one without. I unchecked the Kirnu automap instance in AU validator but is seems no luck there too. But it's not that I rule out the midikontrollers fault or the driver that may prevent this from not working as normally.

Thanks for your post Mark.

Any idea what the problem might be Arto?

/Jimmy

[Kirnu]

Mark,

As you wrote I needed to rescan Cream for it to appear in the physical input.


Arto,

Have you found anything why it has to be rescanned for it to come up in the physical input?


Regards
/Jimmy

Sorry, I don't have a clue why Cream has to be rescanned in order it to appear in the physical input.

-Arto

[Mark R]

Sorry, I don't have a clue why Cream has to be rescanned in order it to appear in the physical input.
-Arto

Just noticed that another developer (DSP Trigger) posted a similar problem with Logic X and has also found that...
"simply disconnecting a USB MIDI device causes Logic to refresh it's MIDI device list and the virtual MIDI port created by my plugin magically shows up...".

Then Kirnu is mentioned as having the same issue.
http://www.logicprohelp.com/forum/viewt ... 42&t=98656

Arto,
Have you submitted a bug report to Apple? It can be done here:
http://www.apple.com/feedback/logic-pro.html


I'm so glad that your plugin works with Logic X but it would be so much better if these extra setup steps were no longer needed.

[popskull]

A beta exists that puts Cthulhu from xfer records in the MIDI FX section of Logic X - Would be great if Cream is coded that way as well.

[Kirnu]

A beta exists that puts Cthulhu from xfer records in the MIDI FX section of Logic X - Would be great if Cream is coded that way as well.

Indeed

[Mark R]

A beta exists that puts Cthulhu from xfer records in the MIDI FX section of Logic X - Would be great if Cream is coded that way as well.

Indeed

Kirnu Cream as a MIDI FX in Logic.
A great development, Indeed!!!

First tests with 1.0.8 - looks like no more environment patching and difficult latency issue work arounds.
Wow - and now we might even be able to easily pre-process MIDI before it gets to Kirnu!

One problem noticed while trying to record.
Recording with Logic's Cycle mode OFF - record timing works as expected.
Recording with Logic's Cycle mode ON, I can't get my arpeggiation to play on the beat.

[Mark R]

Ah - just remembered an old Logic trick. And this gets around the timing difficulty I was having in my previous post.
(see above)

In Logic - after pressing record - sometimes you need to "wake up" a midi instrument with a little bit of MIDI. If you don't, the first note/s will pop out late as processor power is suddenly switched over to a "live playing' mode.
So - During the "record count in" move the mod wheel, tap on the sustain pedal, or play one note. - This will activate the track's instrument.

I think we can probably disregard my previous post's caution about recording in 'Cycle' mode.

[Kirnu]

Thanks for the info Mark

-Arto