Osmose Firmware 2.1.21
Hapax new 2.30 Beta obviously
Osmose DIN MIDI OUT to Hapax DIN MIDI IN (same result with only USB)
Hapax USB HOST to Osmose USB
Osmose āusb haken modeā disabled
Osmose āhaken local controlā off
Hapax track1 MPE
Input MIDI A MPE 1ā¦16
Output USB Host 2ā¦12 lower Zone
My result sill the same (see first post). If I look at the Midi Montor - only data on channel 1 is incoming and only data on channel 2 is outgoing. Seems odd. I filtered for PB Midi data - only the 8192 is received and sent.
Has anyone noticed any clock jitter issues since this update? Timing was rock solid before using Hapax (Dawless) as the master clock and now feel like i get these frequent jitters that are knocking things out of time slightly. Will do some tests to see what the cause might be, but iāve never had this before and everything is setup the same as it has been
I actually noticed something similar the other day but it was late and I wasnāt sure if the bad guy was the Hapax or my computer (was overdubbing with a vst) so I just shut everything down for the might and not actually gone back to it yet.
Iāll have another go tonight and see if I can replicate
Iāve not been able to replicate it tonight, so think it was just my computer being annoying.
It wasnāt jittering so much as the tempo was slower than the recording Iād made a few minutes before, so Iād probably pressed something accidentally in Reaper after a glass of wine or two. Works fine tonight.
@MADVILLA what exactly are you experiencing? I could try to give your scenario a test if you like?
So for me, iām only experiencing jitter when using the Hapax as the master clock for my hardware synths. I tested sending midi clock out of both the Din Port and the USB device port so far and they both are are very jittery. When i use Ableton, i sync Hapax with CV using CV Tools and that has been rock solid. So i figure the issue is only occurring when using Hapaxās internal clock. And just to add, the jitter is not a minor tempo shift, rather a very noticeable skip/lag thats been knocking my MPC out of time.
I use a MioXL midi patchbay for all my gear so iām gonna test running midi direct to my synths/drums to make sure its not an issue with the MioXL!
At first I wasnāt so hyped about this update and was in doubt of itās usefulness (for my setup anyway).
But I recently updated Logic from X ā 12, and this update makes it a lot easier for midi ins and outs to and from the daw. So 2.30 D on Hapax means deeper integration between Hapax and DAW in a hybrid setup, using plugins and hardware ā it all plays nicely together. Itās now easy to sequence any hw synths on the Hapax OR just use it as a midi interface and sequence everything from Logic ā maybe some fx tomfoolery on the Hapax, with automation and random notes here and there ā anythingās possible!
(This is just an appreciation post for use cases I hadnāt thought of. Well done Squarp!)
Iām jumping into the discussion to add a quick practical use case for virtual MIDI cables.
In a DAW (Ableton, in my case), since each MPE plugin uses a full 16-channel MIDI cable, I can route Hapax to each individual synth using the virtual Device outputs.
For example: HAPAX ā USB DEVICE 1 OUT ā Ableton Track 1 IN HAPAX ā USB DEVICE 2 OUT ā Ableton Track 2 IN
etc.
All of this while using the same physical MIDI cable.
Sorry if this is obvious to some of you, but after reading the comments, I felt this might be useful.
Hapax TRK 1 sequencing Plugin 1 on Logic via virtual midi in port āHapax 1ā. Using Hapaxās effects section to randomize and shake things up in a way not easily possible within Logic AFAIK
Hapax TRK 2 sequencing Plugin 2 on Logic independently of the previous track via virtual midi in port Hapax 2.
Logicās step sequencer (which btw has multiple play modes and ptn lengths per note!) sequencing HW Synth 1 going through Hapax as virtual midi out port Hapax 1, thus not interfering with any other inputs to Hapax.
Audio files playing from Logic nicely in place and synced with everything
I know all of this has sort of been possible before using different midi channels, but the Hapax update makes this a lot easier to manage at least with Logic. Also the possible track count went up from 16 to 16 x 16. Before the latest update Hapax was one midi device with 16 channels. Now with fw 2.30 D it has 16 virtual ports, e.g Hapax 1 (ch 1-16), Hapax 2 (ch 1-16) and so on. Probably has most to do with being MPE capable, but has other benefits as well.
Is this using the USB B/Device port or the USB A/Host port from the Hapax to the computer? This sounds like what Iām planning on doing, but Iāve never really messed with USB midi until now.
At exception of fonctions for DAWs whare are the changes with this update ?
Iām still desperate with solar energy actually so if someone can tell me I will look directly to check the new things
Okay after some rigorous testing today, i think i figured out the jitter issue. I think the problem was that on my āSync Inputā settings, even though i switched the clock source to āInternalā. I left the CV Reset and CV Play Enable settings on, so there might have been some crosstalk or something in my CV connections that were causing the Hapax to jib out. Turning both of those CV settings completely off has stabilised the internal clock which makes sense, but i dont recall this being an issue in previous versions. Especially since there isnt any proper CV signals being sent into the Hapax when the issue occurs..
Didnāt even think about sending midi out through the hapax into hardware. Thats pretty great. Plus i should be able to record that daw midi into the hapax and tweak it further, correct?
I see the same thing and I bought the Hapax do go dawless soā¦ Joke apart Thank you Squarp Team for the nice update
Still wait for basic features that are not here like: a fold option to have a better view of notes on the tiny screen, proper note/step repeat, usable one button live looping , min/max range for cc and nrpn and assignā¦
Iāve always been dawless, and for the initial creative process that works best for me. However when it comes to working out complex arrangements, especially āglueingā sections together, it gets very complicated dawless, you spend a lot of time working with conditionals and other stuff that gets more in the way of the creative process.
Hapax is great for the blueprint and live version of track, for an album version, I get drawn to linear sequencers.
Joke apart Thank you Squarp Team for the nice update