AUv3 MIDI tools going cheap

tom_tmtom_tm
edited January 2019 in General chat

I don’t know if this is of any interest to anyone, but here is a suite of AUv3 MIDI tools for use in DAW's such as NS2 etc at an introductory price of 99p (99¢). The price is going up by 80% on the 1st of Feb, so perhaps worth a punt?

http://audioveek.com

Comments

  • dendydendy
    edited January 2019

    not working in NS2 at the moment...

  • drezdrez

    bought knowing they will!

  • tom_tmtom_tm

    This is why they’re cheap I guess. Because they SUCK in NS2!!

  • tom_tmtom_tm

    ;-)

  • tom_tmtom_tm

    @drez said:
    bought knowing they will!

    That’s the spirit. I will wait too, then if nothing has happened in two weeks time, I’ll troll the developer.... no. Wait...

  • blueveekblueveek
    edited January 2019

    @tom_tm said:
    This is why they’re cheap I guess. Because they SUCK in NS2!!

    @dendy said:
    not working in NS2 at the moment...

    A slightly more accurate wording would be to say NS2 is not compatible with these kinds of MIDI audio units. They work fine in every other popular host, such as AUM, apeMatrix, Cubasis and BM3, even Audiobus.

    The problem here is very likely the same one that affects other plugins such as StepPolyArp, discussed here.

    Rest assured that I'm happy to collaborate with @Blip Interactive on this and make any changes to the plugins if needed to make them work. But as far as I can tell, at the moment it's impossible to do anything before NS2 is updated.

  • dendydendy
    edited January 2019

    yeah i believe @drez made good decision and sooner or later problem will be fixed.. looks like very nice set of tools, looking forward for using midi monitor, would be handy tool for testing midi plugins ! Good work !

    just to summarize issues i found, maybe you get sime ideas - looks like 3 basic independent issues to me..,

    • instrument doesn't load at all, it stay stucked in "loading" state (wondering if it should be some kind of issue that your plugin implements just midi streams not audio and NS is waiting for audio stream ? Just my random thought)

    • MIDI route - after loaded, UI disappears (it blinks for a while) and audio engine starts dropping heavily - when plugin removed, audio is again ok

    • midi monitor doesn't show any data, Latch does nothig - didn't try rest - but this looks like it should be theoretically same root issue like with SPA

  • blueveekblueveek
    edited January 2019

    Thanks for testing things out @dendy.

    For the "Route" units (both instrument and effect), your hypothesis is interesting, and I'll do some more digging on my end.

    For the other units, they expect MIDI data to come in from the host via AURenderEvent realtime event list head, and also advertise their output to the host via MIDIOutputNames (Matt will know what I'm talking about).

  • dendydendy

    :+1:

  • flockzflockz

    @blueveek said:

    @tom_tm said:
    This is why they’re cheap I guess. Because they SUCK in NS2!!

    @dendy said:
    not working in NS2 at the moment...

    A slightly more accurate wording would be to say NS2 is not compatible with these kinds of MIDI audio units. They work fine in every other popular host, such as AUM, apeMatrix, Cubasis and BM3, even Audiobus.

    The problem here is very likely the same one that affects other plugins such as StepPolyArp, discussed here.

    Rest assured that I'm happy to collaborate with @Blip Interactive on this and make any changes to the plugins if needed to make them work. But as far as I can tell, at the moment it's impossible to do anything before NS2 is updated.

    Ns2 doesn’t work with a bunch of 3rd party stuff atm. Vibe around here is ‘so what, obsidian is sooo efficient, just don’t use other plugins and employ workarounds’. No one seems to feel urgent, short changed or vocally pissed about the compatibility issues so I doubt it’ll get fixed any time soon.

    Your apps are great in bm3 btw. Nice work :)

  • tom_tmtom_tm

    Great stuff @blueveek. Thanks for clearing that up. I really look forward to using your software. I already use AUM so they’ll get plenty of use there.

  • blueveekblueveek
    edited January 2019

    Good news, I've confirmed with @Blip Interactive that everything will work fine in a future release of NS2.

    I've also already released a new version of MIDI Tools on the App Store that anticipates for that future version of NS2, so everything goes smoothly.

    Thanks everyone for your patience.

  • tonemantoneman

    @tom_tm said:
    I don’t know if this is of any interest to anyone, but here is a suite of AUv3 MIDI tools for use in DAW's such as NS2 etc at an introductory price of 99p (99¢). The price is going up by 80% on the 1st of Feb, so perhaps worth a punt?

    http://audioveek.com

    Done. No brainer. Thanks, Tom I love deals like this.

  • dendydendy

    @blueveek said:
    Good news, I've confirmed with @Blip Interactive that everything will work fine in a future release of NS2.

    I've also already released a new version of MIDI Tools on the App Store that anticipates for that future version of NS2, so everything goes smoothly.

    Thanks everyone for your patience.

    Good work :+1: Confirming MIDI route (both instr. / fx) is not crashing anymore, looking forward to Matt’s part of job.

    I want ask one thing. Curious how MIDI route works. I was expecting that if i put MIDI Route FX on channel 1 (destination set to network session1, channel 1), channel 2 (set input "network session1, channel 1") would play - but that is not the case .. I tried change destination to "Cubasis" but wit no success..

    What i'm doing wrong ?

    (of course i tried it in Cubasis, i guess in NS it would work only after Matt's update)

  • blueveekblueveek
    edited January 2019

    @dendy said:

    If you haven't seen it, here's a quick video showing how MIDI Route (instrument version) works:

    Check the second half of the video for routing from one track to another, into the same app.

    This setup should translate identically to other DAWs too, such as Cubasis. To be clear, NS2 is still unable to make use of the effect version, but the instrument version works properly.

    If you're still having trouble (e.g. with Cubasis), send me a PM, we'll get to the bottom of it.

    EDIT: a few further clarifications below.

    I recommend using MIDI Bus for in-app routing, because that will work specifically with AUv3 MIDI, and doesn't require applications to advertise themselves as a MIDI destination.

    However, MIDI Route will work fine as long as the targeted destination is actually advertising itself as a destination using Core Midi (not AUv3 MIDI) on iOS. NS2 doesn't seem to do that at the moment.

  • dendydendy

    ok thanks, will check video try it in cubasis ..

  • blueveekblueveek
    edited January 2019

    @dendy said:
    ok thanks, will check video try it in cubasis ..

    Works fine in Cubasis from what I've tried.

    Simplest possible setup:

    Using Route to route midi from one track to another:

    1. Create a midi track A with some notes in the timeline
    2. Select "None" for track A's midi input in the sidebar
    3. Add MIDI Route as either an instrument or effect for track A and select "Cubasis" as destination
    4. Create midi track B with no notes in the timeline
    5. Select "ALL" for track B's midi input in the sidebar
    6. Add whatever instrument for track B (e.g. piano).

    Now the notes on track A are routed to track B.

    Using Bus to route midi from one track to another (preferred):

    1. Create a midi track A with some notes in the timeline
    2. Add MIDI Bus as an effect for track A, with "Send post" and Bus #1 (switch off "Rec to Track")
    3. Create midi track B with no notes in the timeline
    4. Add MIDI Bus as an effect for track B, with "Receive combine" and Bus #1
    5. Add whatever instrument for track B (e.g. piano).

    Now the notes on track A are routed to track B, without relying on Cubasis advertising itself as a MIDI destination.

    Let me know if you need any more help.

  • dendydendy

    Using Route to route midi from one track to another

    Yeah this is what i did but it refuses to play, no sound from track B :open_mouth: very strange

    Track A / B configuration (there is default piano cubasis patch on track b)



    Using Bus to route midi from one track to another

    You wold not believe, butt without success too :open_mouth:


  • dendydendy
    edited January 2019

    OOOh i found what is problem."REC TO TRACK" button on B channel, should be disabled :)) It's like if it is enabled, Cubasis is NOT passing notes from MIDI FX into instrument but directly to track, if its disabled, Cubasis is NOT passing notes to track but to instrument :)

    It's the Cubasis way how to record MIDI going out of MIDI FX into track. A bit strange way, hope Matt will come with some more smart "buttonless" solution :)

    Anyway - your plugins works seamlessly !

  • blueveekblueveek

    huzzah!

  • blueveekblueveek

    Instrument mode of MIDI Route doesn't need to deal with the "REC TO TRACK" shenanigans.

  • dendydendy
    edited January 2019

    No, that button works just for MIDI Bus plugins .... MIDI Route still doesn't work no matter if i use it as FX or Instrument in track A - track B doesn't receive nothing .. Tried also Route instrument / fx set to "network session 1" and "all ports" and then set as input port "network session 1" in GrooveRider - but it did not received anything from Route runnnin in Cubasis - it looks like Cubasis is somehow blocking MIDI Route output no matter if it is used as instrument or FX ..

    Btw. do you have any "official forum" somewhere ? Maybe that AB thread ? I think it would be good for you to discuss such things not related to NS there, to save your time explaining it again if somebody else would have same troubles like me :))

  • dendydendy
    edited January 2019

    Ok this was just some issue with GrooveRider most probably user error :lol: - tried standalone Dixie and it works, MIDI Route from Cubasis sends notes to standalone running Dixie

    Ok then i think it's solved.. for internal routing within host - MIDI Bus, for external apps MIDI Route .. all cleared. Thanks ;)

  • blueveekblueveek
    edited January 2019

    @dendy said:
    No, that button works just for MIDI Bus plugins .... MIDI Route still doesn't work

    Everything works perfectly well with Route as far as I can tell. Here's a video demonstrating that:

    I 100% agree with regards to moving this conversation over to the AB forums :)

  • dendydendy

    Check my lasts post ;-) It works.. user error :)

  • tom_tmtom_tm
    edited January 2019

    @blueveek can I ask for another MIDI plugin request? Sevish built this rather groovy little MIDI scaler tool to process incoming MIDI inputs to output:

    "MidiNoteScaler is a MIDI effect. You specify a source EDO and an output EDO, and it will change the MIDI note number of all incoming note messages.

    Example use case: you have a MIDI sequence in 12-EDO, and your synth is tuned to 19-EDO. Put MidiNoteScaler in the chain before the synth. Set input to 12, output to 19. Now when you play the sequence, you will hear something very similar to the original 12-EDO music but each note is tuned to the nearest note from 19-EDO."

    Something like this would be an incredibly useful tool for those (like me and many others) who wish to explore microtonal tunings within an app like NS2. Matt has considered the possibility of adding Scala and Tun support to Obsidian at some point in the future, but until that time arrives, something similar to this would be extremely handy- even just to mess around with simple keyboard mapping.

    Eeek! Forgot to add the link....

    https://github.com/SeanArchibald/sevish-vst#midinotescaler

    edit 2: btw it's not a VST, just a Pd vanilla patch that uses Camomile as a VST wrapper.

Sign In or Register to comment.