View Full Version : AU Teaser #1
Just a little sneak peek....
shamburglar
08-13-2009, 02:23 PM
Well if thats not enough to convince current numerology owners not to pull the trigger on Sugarbytes Eloquence, I don't know what is. I hold a grudge against those folks anyways because supposedly that is what Consequence was supposed to do, they promised midi and it was wildy requested for Consequence but instead they go and release another plugin... BOOO!
Per Boysen
08-13-2009, 05:16 PM
Wow , can't wait for teaser #2!
blurk
08-13-2009, 06:55 PM
I don't know what I'm looking at (i.e. from the context I can guess, but I don't know what the host is).
twoandtwo
08-13-2009, 07:55 PM
this looks very promising!
i hope this works in ableton live, too. because all the plugins that i used so far(also consequence), could only output midi within live as an VSTI. while the AU plugins couldnīt.
I don't know what I'm looking at (i.e. from the context I can guess, but I don't know what the host is).
That was Logic, this is Ableton Live:
twoandtwo
08-13-2009, 08:06 PM
this screenshot makes me veeeeery happy.
canīt wait to try this out!
Well, I could put up a beta now, but there's no AUPreset support yet, so there's no way to save your work....
Jim
lut lei
08-14-2009, 01:24 AM
Well, will it work in my favourite host - Numerology?
koalaboy
08-14-2009, 02:54 AM
Very nice :D
Will there be a way to save 'patterns' for transfer to/from Numerology standalone ?
(Perhaps Numerology could import AUPresets into the modules ?)
Something like that, I'm not sure yet what will make the most sense. This is all about taking it step by step, er, so to speak....
Jim
koalaboy
08-16-2009, 03:31 AM
Another quick question on this, Jim.
Does it require using the IAC 'workaround' or have you managed something else ? The only reason I ask, and I assume you're just thinking a bit more about the task, is that it seems to show in Live quite fine.
I've just loaded the demo of 'Eloquence' into various hosts, and unless I go and set up the IAC loopback, I get no MIDI. What's curious about this though, is it doesn't even seem to support MIDI out, even outside Logic, as Numerology doesn't show a MIDI out port, and Live doesn't seem to receive anything.
Looking at your Live screenshot, it suggests that you have normal MIDI out, so that Live, Numerology, etc. would work as normal - and perhaps something different for Logic ?
Thanks,
Michael.
vanhaze
08-16-2009, 05:30 AM
Guess what ?!
Yesterday i took the plunge and bought Eloquence.
Cause they were heavily promoting the fact that it's AU could output MIDI.(via IAC bus).
Well, it can indeed (with rocksolid timing) BUT : only if you cable the IAC bus DIRECTLY to an software instrument track.
But what i really wanted is to RECORD the generated midi from eloquence.
So i thought : let's cable the IAC bus to the sequencer input object in logic.
And then , when in play , indeed i could record the midi but timing is WAY OFF !
(and i checked if i had an midi feedbackloop in logic but NO, wasn't the case)
So this is awfully disappointing for me !
I later tried it in Live 8 and (offcourse !) worked like a charm cause Live can directly output it's VST midi output to an midi input , with rock solid timing , so recording Eloquence's output was a breeze in live !
Side note : Eloquence is a pretty neat plugin in it's capabilities but i think Numerology has far better user interface and WAY MORE possibilities.
So bottom line for me : if Numerology as an audio unit can output it's midi with rock solid timing to the sequencer input with Logic , then i will sing Hallelujaah !!!
(the screenshot looks promising indeed , can't wait jim !!!)
Kind regards,
Rob
Another quick question on this, Jim.
Does it require using the IAC 'workaround' or have you managed something else ? The only reason I ask, and I assume you're just thinking a bit more about the task, is that it seems to show in Live quite fine.
I've just loaded the demo of 'Eloquence' into various hosts, and unless I go and set up the IAC loopback, I get no MIDI. What's curious about this though, is it doesn't even seem to support MIDI out, even outside Logic, as Numerology doesn't show a MIDI out port, and Live doesn't seem to receive anything.
Looking at your Live screenshot, it suggests that you have normal MIDI out, so that Live, Numerology, etc. would work as normal - and perhaps something different for Logic ?
Thanks,
Michael.
The MonoNote AU creates a virtual output port, so you can route that wherever you like. I will also add a MIDI out menu so you can switch to a hardware port if you prefer, or even an IAC bus.
Cheers,
Jim
Well, it can indeed (with rocksolid timing) BUT : only if you cable the IAC bus DIRECTLY to an software instrument track.
But what i really wanted is to RECORD the generated midi from eloquence.
So i thought : let's cable the IAC bus to the sequencer input object in logic.
And then , when in play , indeed i could record the midi but timing is WAY OFF !
Can you be more specific about "way off", as in "the timing was stable, but there was a lot of delay" or "the delay was short, but there was a lot of jitter in the recorded notes", or some combination of both...
Cheers,
Jim
Also, the plugin will have AU hosting, so you can sequence latency-free.
Cheers,
Jim
vanhaze
08-17-2009, 03:27 AM
Hi Jim,
Sorry for being abit vague in my previous post.
This is more detailed :
I get a NEGATIVE delay of the generated midi notes from Eloquence of about 150 ms.
So for example : i put on Logic's metronome and then hit play and listen to the generated midi data from Eloquence that is arriving at logic's input object.(and going to another software instrument, just to hear it)
Then i hear that the midi data is running about 150 ms AHEAD of the metronome.
That is problem 1.
Problem 2 is that the generated midi data from eloquence has an amount of jitter : i can hear the timing isn't tight at all.
I got a response from Sugarbytes about this problem , they did test it and experienced the same results.
They said that the problem lies in Logic , not cooping well with midi data coming from the IAC bus.
So there is nothing they can do about this problem ; it is in Apple hands :( (so THEY said).
Now you stated that the AU version of Numerology will use a virtual midi out port (not being neccesarily the IAC bus) ?
Very anxious to hear if your solution is gonna work better in Logic !
I so very hope so ; for me it will be like i am in heaven when it works tight !
Kind regards,
Rob van Hees
shamburglar
08-17-2009, 09:56 AM
I am not fond of being negative on forums or anywhere but I must say that I had a terrible experience with Sugarbytes Consequence. I was very excited about it when it was announced and all the PR led one to believe that it had some serious midi out capabilities. I bought it on day one and the midi out didn't work at all. The KVR message boards exploded, I emailed them (as I'm sure many people did) and honestly they seemed kind of frustrated at the users. Then they released an update which somehow enabled midi in a very rudimentary manner (as in all 4 voices generated by the plugin were funneled to one single channel) and didn't even announce the update nor change the version number. I thought consequence was very promising but very limited in its initial release and I was expecting a few updates to it which would allow for better midi and also the ability for one to add their own sounds to its banks instead of being stuck with its default sound bank. A year later and the plugin sits right at version 1.0 as it did the day it was released. I realize that I am at fault for purchasing the plugin day one and really regret it... I got hyped about it, it looked really cool and I thought I'd be buying into a product that was going to mature.
Point being.... it's a competitive market out there and Sugarbytes lost at least one customer. I understand why Jim is putting the time in to stay competitive and develop the plugin functionality. He already has many loyal customers who appreciate his fantastic communication. I would love to see the Pro version sooner but I fully understand the necessity to come up with solutions to these plugin problems now because as the Numerology user base expands the demand for a simple plugin mononote step sequencer will not go away... and what a bargain that is when it is cheaper than Eloquence and comes with Numerology 2 as well!
koalaboy
08-17-2009, 02:07 PM
The MonoNote AU creates a virtual output port, so you can route that wherever you like. I will also add a MIDI out menu so you can switch to a hardware port if you prefer, or even an IAC bus.
That's a great solution :D Does this mean that if multiple MonoNote AU are added, there's a virtual out created for each ?
Also, the plugin will have AU hosting, so you can sequence latency-free.
Superb !! :cool:
(I know I'd decided I didn't need an AU, but this 'solution' you seem to have come to is great, and I'd feel stupid if I didn't encourage it ;) )
vanhaze
08-17-2009, 02:16 PM
Hi mate,
I have the same negative experience with SB Eloquence.
Bought it right at day 1 (last sunday) and now i am disappointed.
Their promotion about the workaround for getting midi data into logic was misleading imho.
Cause they have ignored the fact that people (like me) also want the capability to RECORD the midi data into logic without a hassle.
Or is this too much too ask for ? i think not !
Nowhere in the manual (which is very basic and short) you can read about the ability to record the midi data and how to do it and if it works.
Offcourse in ableton Live this goes without a hassle (my own experience) and i assume Cubase is the right partner for that too.
But even for these apps there is no explanation on how to record the midi data from eloquence.
I hope Jim wil crush Eloquence and Consequence with his pro version !
(and as a matter a fact : i do believe he will (or did already haha!);)
Kind regards,
Rob
Per Boysen
08-17-2009, 02:40 PM
I think this AU will sell like shit! Every damn Logic user will just love it, since "MIDI plug-ins" and "step sequencing" have been standing wishes in the Logic User Community for... DECADES!!!
vanhaze
08-17-2009, 02:49 PM
so totally true !
sbaishya
08-17-2009, 03:04 PM
Also, the plugin will have AU hosting, so you can sequence latency-free.
Can't wait for this :)
Numerology just gets better and better!
I get a NEGATIVE delay of the generated midi notes from Eloquence of about 150 ms.
So for example : i put on Logic's metronome and then hit play and listen to the generated midi data from Eloquence that is arriving at logic's input object.(and going to another software instrument, just to hear it)
Then i hear that the midi data is running about 150 ms AHEAD of the metronome.
weird...
That is problem 1.
Problem 2 is that the generated midi data from eloquence has an amount of jitter : i can hear the timing isn't tight at all.
I got a response from Sugarbytes about this problem , they did test it and experienced the same results.
They said that the problem lies in Logic , not cooping well with midi data coming from the IAC bus.
So there is nothing they can do about this problem ; it is in Apple hands :( (so THEY said).
Well, I will say that it is not easy to generate MIDI accurately out of an AU, but I think I can do quite a bit better than what you describe...
Best,
Jim
That's a great solution :D Does this mean that if multiple MonoNote AU are added, there's a virtual out created for each ?
Yup.
Jim
vanhaze
08-18-2009, 07:40 AM
Jim, maybe i overlooked something in your posts about AU version.
Is it true that only mono note module goes AU or all the other modules as well ?
Lemme clear things up :
I would imagine that, when opening numerology as an audio unit, it opens normally as if numerology was openend stand alone.
In the audio unit window you can then make your own stack and then sent midi stuff via the virtual port to logic.
Or am i totally wrong in my assumption that it will work this way ?
Kind regards,
Rob van Hees
Per Boysen
08-18-2009, 08:34 AM
I get a NEGATIVE delay of the generated midi notes from Eloquence of about 150 ms.
I got a response from Sugarbytes about this problem , they did test it and experienced the same results.
They said that the problem lies in Logic , not cooping well with midi data coming from the IAC bus.
So there is nothing they can do about this problem ; it is in Apple hands (so THEY said).
This sounds more like Sugarbytes having missed out on some homework :-)
Have you tried different settings for latency compensation for software plug-ins (instruments)?
Logic Pro > Preferences > Audio >
You can turn off latency compensation for software instruments or you can use latency compensation for the entire system (audio, instruments, aux, outputs, bus, ReWire).
The "negative delay" you notice in Eloquence may be due to some other component on the system that induces latency. For mixing and playback latency issues in Logic is normally transparent and this is made possible since the system is fully self diagnostic and compensates either by delaying audio streams or by shifting instrument- and audio tracks forwards in time.
So what may happen is that the Instrument Track Eloquence is inserted on, as an effect plug-in, is being time shifted forwards by 150 ms to compensate for the summed latency of 150 ms in other plug-ins. Not saying this is the case, but it seems like something worth checking out. Simply turn off latency compensation in order to do that check.
You may also try activating Low Latency mode to see if it helps.
Sjoerd
08-18-2009, 11:28 AM
Well, I could put up a beta now, but there's no AUPreset support yet, so there's no way to save your work....
Saving is for wimps. :p
Can I haz AU nau? :D
Sjoerd
08-18-2009, 12:53 PM
Btw, fwiw, a little tip for playing with plugins that have step/pattern sequencers that output MIDI:
I've been doing this a lot with AudioRealism's Bass Line 2 (ABL2, a TB-303 bisimulation), Bass Line Pro (aka ASM, semi-modular), and Drum Machine (ADM, a bisimulation of TR-606, TR-808, TR-909, simple sample player), and also with SonicCharge's ĩTonic. Even in quite complex modular ways, with many instances that trigger patterns in each other. Oh what a joy... :) Piano-rolls suck. :p
I have been using the VSTi versions for MIDI output since they're not problematic at all. I'm not at my DAW now, but I do remember for a fact though that the AUi version of at least ABL2 also (attempts to) create(s) a MIDI output on the fly.
I really *love* seeing Numerology (also) moving in this direction, since no doubt it is going to be even more powerful and flexible. Biggup Jim!
vanhaze
08-18-2009, 01:32 PM
Per , fyi :
I played around with the latency compensation settings in Logic : no difference at all. :(:(:(
Per Boysen
08-18-2009, 03:20 PM
Oh, I'm sorry my guess wasn't correct. Wonder what that could be then? Does the MIDI come out tight under other host applications?
Jim, maybe i overlooked something in your posts about AU version.
Is it true that only mono note module goes AU or all the other modules as well ?
Lemme clear things up :
I would imagine that, when opening numerology as an audio unit, it opens normally as if numerology was openend stand alone.
In the audio unit window you can then make your own stack and then sent midi stuff via the virtual port to logic.
Or am i totally wrong in my assumption that it will work this way ?
Kind regards,
Rob van Hees
For now, the plugin is just hosting the MonoNote. The idea was to spend a few days to see how far I could get, with the assumption that doing just a single Note Sequencer would be easier than the whole app. The assumption turned out to be correct, as it only took about 4 days to get running reasonably well. However, I will say I got very lucky with some potentially difficult technical issues.
In addition, focusing on just the MonoNote has helped clarify what makes sense from a user's perspective for Numerology-style sequencing within another host. In particular, it seems to be very nice to start with something very simple (pick a sequencer), then move on from there. That approach also mirrors how I plan to proceed on a programming level:
I will next add enough stack functionality to enable presets, then audio unit hosting, and so on. Eventually I think you will be able to at least load in or create a full Numerology stack, but rather than dump that all in at once, I think it makes more sense to approach it step by step.
I don't know what the final product plan will be yet, but I am currently thinking that I will finish this plugin as just the MonoNote and release that as a new introductory product at a very competitive price. Anyone with a full Numerology license could use it for free, and new users could pick it up real
cheap (less than $50 US).
Following that, I am thinking that there will be more plugins, probably as part of a package whose functions will steadily grow over time.
Cheers,
Jim
Saving is for wimps. :p
Can I haz AU nau? :D
Send me a short email (info at five12 dot com) and I'll put you on the private testers list. That goes for anyone else interested also. I'll have a more formal announcement on this later today.
Cheers,
Jim
earthlinger
08-19-2009, 09:47 AM
plugin version is great news. thanks jim!
the only thing I wish for now is using Numerology directly inside AudioMulch. since AM is VST only, NM plugin is AU only for now, I'm sure it will happen one day....
vanhaze
08-19-2009, 01:50 PM
To Jim : I am very anxious to test the mono note AU version.
Could you please put me on the testers list ?
Also anxious to know if it has a tight midi output for recording in Logic 9 ...
(So hopefully no "eloquence - alike " problems :cool:
Kind regards,
Rob
You just need to send me an email.... :)
I have not tested the timing yet.
Cheers,
Jim
blurk
09-01-2009, 03:36 AM
I don't know what the final product plan will be yet, but I am currently thinking that I will finish this plugin as just the MonoNote and release that as a new introductory product at a very competitive price. Anyone with a full Numerology license could use it for free, and new users could pick it up real
cheap (less than $50 US).
Following that, I am thinking that there will be more plugins, probably as part of a package whose functions will steadily grow over time.
Sorry about the late reply, I have been looking in for a bit. This is all sounding really promising, and all I'd like to add is that even if you add more plugins, it'd be really good if you kept each one small and lightweight. I can see myself instantiating a bunch of these smaller plugins within a Bidule layout. Anything needing a more heavyweight setup would probably be better served by all those alternatives you were outlining in the original plugin vs rewire thread.
And keeping the plugins lightweight would make a great point of distinction between the plugins and the core product.
All I need to do now is send that email to belatedly join the test list.
necho
09-11-2009, 10:09 AM
plugin version is great news. thanks jim!
the only thing I wish for now is using Numerology directly inside AudioMulch. since AM is VST only, NM plugin is AU only for now, I'm sure it will happen one day....
my thoughts exactly...
I'll evaluate the VST (on mac) options after the AU is shipping and the pro version is released.
Cheers,
Jim
shamburglar
09-17-2009, 08:15 AM
It's been real quiet around here......
Yup. Lots going on behind the scenes though. I'll have some updates shortly...
Jim
Is the AU version ready for sale as of yet?
And can it be controlled by the Launchpad?
Is the AU version ready for sale as of yet?
Not yet. I'm making several internal changes to the plugin so it is not ready for public consumption yet.
And can it be controlled by the Launchpad?
That is the plan (and one of the reasons for the delay).
Cheers,
Jim
ignatius
04-20-2010, 11:57 PM
wow. can't wait for this. it's gonna blow audiomulch wide open in new ways once the next update of mulch comes out for the mac (AU Support!!!) i'm gonna need a 2nd monitor.
narosis
04-27-2010, 12:23 PM
how does it look in Digital performer 6?
how does it look in Digital performer 6?
Exactly the same -- just the 'wrapper' part of the window is different.
Cheers,
Jim
Gnuus
05-02-2010, 07:14 AM
I can't wait for this plugin to use in Live!
Logos Lover
05-17-2010, 08:46 AM
Two questions.....
Will the Mononote AU have a resizable GUI?
And how will this work with the AU? Say I have a sequence in the MN AU running for 8 bars, but on bar 9 i'd like the sequence to transpose by a 5th upwards. Will this type of thing be easy to do when running the AU in Logic?
Will the Mononote AU have a resizable GUI?
Probably not, but the full Numerology AU probably will.
And how will this work with the AU? Say I have a sequence in the MN AU running for 8 bars, but on bar 9 i'd like the sequence to transpose by a 5th upwards. Will this type of thing be easy to do when running the AU in Logic?
Pretty easy: just setup a 2nd preset with the transposition, and use the preset playlist function to make the change. Another option would be to use automation in in a Logic track.
Cheers,
Jim
vanhaze
05-19-2010, 11:17 AM
Just awesome Jim !
Logos Lover
07-02-2010, 06:54 PM
Any news on a possible release date for the AU please Jim?
Really really looking forward to this coming out and to use it in Logic :D
Any news on a possible release date for the AU please Jim?
Really really looking forward to this coming out and to use it in Logic :D
Not yet, but I'll be on it full-time as soon as the 3.0 Pro preview release is out, which will be very soon -- just a few fixes and tweaks left.
Cheers,
Jim
Logos Lover
07-26-2010, 07:13 AM
If using two instances of the AU in a DAW, with each instance for a different track, can one be running at the DAW's tempo, with the other running in "double time" ? (ie x2 DAW's tempo)
EDIT: I guess you must be able to do this by using the Ratio setting.
If using two instances of the AU in a DAW, with each instance for a different track, can one be running at the DAW's tempo, with the other running in "double time" ? (ie x2 DAW's tempo)
EDIT: I guess you must be able to do this by using the Ratio setting.
Any of the sequencer speed settings allow you to do this -- how quickly the steps are played is totally changeable at any time.
Cheers,
Jim
KrisM
07-26-2010, 08:19 PM
Any of the sequencer speed settings allow you to do this -- how quickly the steps are played is totally changeable at any time.
Cheers,
Jim
I feel giddy...
Logos Lover
08-26-2010, 08:25 PM
Some more questions for you Jim...
In Numerology to input note data from a connected midi keyboard you set the MIDI Input for the stack, click the little "E" button on the MonoNote's transport. Then in the dialog that opens, set the Rec Mode to "Step". As the sequence runs and notes are played a little cursor moves across the sequence, recording each note as its played.
Will the AU allow to enter notes in the same way from a connected midi keyboard?
And will the AU be able to control a) connected midi hardware synths?
and b) synths connected and being controlled using Silent Way?
(just wondering about AU's limitation in not allowing to send MIDI data..... unless i have that wrong?)
Some more questions for you Jim...
In Numerology to input note data from a connected midi keyboard you set the MIDI Input for the stack, click the little "E" button on the MonoNote's transport. Then in the dialog that opens, set the Rec Mode to "Step". As the sequence runs and notes are played a little cursor moves across the sequence, recording each note as its played.
Will the AU allow to enter notes in the same way from a connected midi keyboard?
Probably, but that is not implemented just yet... ;)
And will the AU be able to control a) connected midi hardware synths?
and b) synths connected and being controlled using Silent Way?
(just wondering about AU's limitation in not allowing to send MIDI data..... unless i have that wrong?)
Yes, though the various forms of sequencing plugins will not themselves support hosting of AU's, so you'd have to host SilentWay in the DAW itself -- or use Numerology in ReWire mode --what irony... ;).
Anyway, here are the full details on AU's and MIDI generation:
The AU spec includes an API for AUs to generate MIDI, but no hosts that I know of yet support it. Perhaps it has slipped into Logic w/o anyone noticing, so I plan to re-test. This is the most ideal situation, as it would provide latency and jitter-free MIDI communication from one AU to other plugins and/or the host itself.
Regardless of all that, any program (plugin or otherwise) on OS X can create (or connect to) a MIDI port and generate MIDI directly. Unfortunately, in the AU case there are a couple annoying problems: namely latency and jitter.
Latency (a short delay) happens anytime you send MIDI from one program to another. There are various ways to compensate, but in the case of the NumerologyAU, it looks like some form of clock offset will be the most convenient solution.
Jitter, a semi-random timing variation in transmitted messages, happens anytime you try to generate MIDI in a modern multi-tasking OS without using special 64-bit timestamps. In most cases, these timestamps come from an audio hardware device and are used to ensure accurate MIDI timing, whether going out to a hardware MIDI port or another application. Unfortunately, once again, even thought the AU spec provides a way for hosts to transmit this information to AUs, hosts don't seem to provide this information. I have implemented a rather novel (and somewhat tricky) solution to this problem for the Numerology AU, so hopefully both jitter and latency will be non-issues.
What will probably not work is track freezing, since that happens at super-realtime rates, and there's no way for inter-app MIDI communication to work in that case.
Also, while I'm on the subject, I am well aware that VST (and VST hosts) support MIDI generation by plugins, so I'll definitely be looking into that more closely.
Cheers,
Jim
blurk
08-29-2010, 05:30 AM
The AU spec includes an API for AUs to generate MIDI, but no hosts that I know of yet support it.
Chicken and egg. Hosts don't want to implement this because no plugins use this capability yet, but no plugin developers want to implement this due to lack of host support. That said, I believe Bidule does support AUs generating MIDI. I know your time is limited, Jim, and building a feature supported only by a niche host is not an efficient use of your time. But I think this is really an opportunity stand out (even more). Only once this feature is adopted by niche players will the mainstream (possibly, hopefully) sit up and take notice.
Jitter, a semi-random timing variation in transmitted messages, happens anytime you try to generate MIDI in a modern multi-tasking OS without using special 64-bit timestamps. In most cases, these timestamps come from an audio hardware device and are used to ensure accurate MIDI timing, whether going out to a hardware MIDI port or another application. Unfortunately, once again, even thought the AU spec provides a way for hosts to transmit this information to AUs, hosts don't seem to provide this information.
However, I don't know if Bidule supports that at all. Oh well.
I generally agree, it is a bit of chicken and egg thing, but then, since Apple is the source of the AU spec, and Logic is from Apple, I would expect better compliance -- regardless of them being separate teams. Anyway, it is a known bug. When I reported it (bugreporter.apple.com), it was marked as a duplicate of bug #5650414, but of course, there is no way for me to see the status of bug 5650414....
If any host supports MIDI out from AUs, I would expect it to be Bidule, and I'll check it pretty soon. As for timing, if the host supports direct MIDI out from the AU, then timing is a non issue-- the way the events are reported handles that automatically.
Cheers,
Jim
ignatius
08-30-2010, 12:10 AM
i'm hopeful that the numerology AU will work in audiomulch sending midi out to other plugs inside audiomulch. :confused:
i'm hopeful that the numerology AU will work in audiomulch sending midi out to other plugs inside audiomulch. :confused:
It should, but I haven't tested w/ audiomulch yet, I'll put it on the list.
Jim
blurk
09-05-2010, 08:02 AM
i'm hopeful that the numerology AU will work in audiomulch sending midi out to other plugs inside audiomulch. :confused:
FWIW, the release notes for v2.1.1 of Audiomulch say:Mac: fixed crash when creating Audio Units that provide MIDI output (e.g. Bidule, Chipsounds, Kore2).
So (a) if you do try, make sure you get the latest version and (b) there's a hint for other AUs that do provide MIDI out. Plogue is definitely a niche player, but NI are just a tad more mainstream.
If any host supports MIDI out from AUs, I would expect it to be Bidule, and I'll check it pretty soon.
Cool, that would be great, thanks.
I generally agree, it is a bit of chicken and egg thing, but then, since Apple is the source of the AU spec, and Logic is from Apple, I would expect better compliance -- regardless of them being separate teams. Anyway, it is a known bug. When I reported it (bugreporter.apple.com), it was marked as a duplicate of bug #5650414, but of course, there is no way for me to see the status of bug 5650414....
If any host supports MIDI out from AUs, I would expect it to be Bidule, and I'll check it pretty soon. As for timing, if the host supports direct MIDI out from the AU, then timing is a non issue-- the way the events are reported handles that automatically.
Cheers,
Jim
I can confirm that Bidule supports MIDI out from AU.
BTW, did you get any progress or insight regarding the timing issues with Logic on MIDI recording from AU using virtual ports? I'm really curious why Logic behaves so badly compared to other hosts, eg. Ableton Live.
BTW, did you get any progress or insight regarding the timing issues with Logic on MIDI recording from AU using virtual ports? I'm really curious why Logic behaves so badly compared to other hosts, eg. Ableton Live.
Between the 3 major hosts I'm testing with -- Logic 9, Live 8 and DP 6, the behavior is the same: no valid host timestamps for AUs, and no support for direct MIDI out. No matter, I've implemented a special note scheduling algorithm and a millisecond-based clock timing offset to handle all that.
Cheers,
Jim
Between the 3 major hosts I'm testing with -- Logic 9, Live 8 and DP 6, the behavior is the same: no valid host timestamps for AUs, and no support for direct MIDI out. No matter, I've implemented a special note scheduling algorithm and a millisecond-based clock timing offset to handle all that.
Cheers,
Jim
Interesting approach. I can't wait to try it out in practice.
zipzing
09-12-2010, 05:19 AM
That was Logic, this is Ableton Live:
The long awaited holy midi graal for Live users !
i alredy plan to korgNanoKontrol it .
cant wait to get it
mitch
09-12-2010, 02:03 PM
+1 on Audiomulch...Numerology and Audiomulch together boggles the mind...
thanks.
-m
vBulletin® v3.8.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.