Hello to all
First post (technically second) so, "Hello" to everyone.
Just bought HH2 a few days ago and so far I really like it. Tom Helzle brought up the app in a Bitwig thread @ KVR 1.5 years ago telling me it might fit my needs. Great advice Tom, sorry it took me so long to give a shot though. You were right.
I was really in need of a patching environment that would allow me to route midi data as needed, preferably in a graphical interface. So far HH2 is delivering in spades. In just a short period I've been able to create a couple of patches that were close to impossible to setup previously in M4L. To be fair this was more a limit of the Live environment than it was a restriction in M4L though. One patch allows me to take the midi note data from one vst, change its effective range output from 128 to 48 and then have it drive the Root Note Selector on another vst that wanted to see a value from 0-1. At the same time I can use that same data to drive another chain of plugs doing a different function.
This is super simple to do in HH2! And now my mind keeps racing with possibilities and scenarios.
Thanks to the team @ Sensomusic!
I want to become more familar with the app and pour through some of the posts on this board for info before I start in with questions or suggestions. So for now its just "Hello".
Just bought HH2 a few days ago and so far I really like it. Tom Helzle brought up the app in a Bitwig thread @ KVR 1.5 years ago telling me it might fit my needs. Great advice Tom, sorry it took me so long to give a shot though. You were right.
I was really in need of a patching environment that would allow me to route midi data as needed, preferably in a graphical interface. So far HH2 is delivering in spades. In just a short period I've been able to create a couple of patches that were close to impossible to setup previously in M4L. To be fair this was more a limit of the Live environment than it was a restriction in M4L though. One patch allows me to take the midi note data from one vst, change its effective range output from 128 to 48 and then have it drive the Root Note Selector on another vst that wanted to see a value from 0-1. At the same time I can use that same data to drive another chain of plugs doing a different function.
This is super simple to do in HH2! And now my mind keeps racing with possibilities and scenarios.
Thanks to the team @ Sensomusic!
I want to become more familar with the app and pour through some of the posts on this board for info before I start in with questions or suggestions. So for now its just "Hello".
Welcome UncleAge,
And thanks for this post, really important for the team to see new happy users.
And thanks for this post, really important for the team to see new happy users.
Welcome!!!!
"Every act of creation is first an act of destruction." -Picasso
-
secretkillerofnames
- Member
- Posts: 97
- Contact:
Taken me about the same time to get into it and i'm with you 100% UncleAge.
Been wanting something as immediate as Live, with the flexibility of Max (minus the constant wheel reinvention).
I have a rambling blog post here where I discuss my enthusiasm for HH2.
Sensomusic are doing great work!
Been wanting something as immediate as Live, with the flexibility of Max (minus the constant wheel reinvention).
I have a rambling blog post here where I discuss my enthusiasm for HH2.
Sensomusic are doing great work!
-
La Tenaille
- Member
- Posts: 547
- Location: Saint Etienne (France)
- Contact:
7 years later it's still the biggest complaint I could do to UsineUncleAge wrote:And now my mind keeps racing with possibilities and scenarios.
Yes relatively new myself and blown away by this unique special creative software. Welcome
-
Thomas Helzle
- Member
- Posts: 334
- Location: Berlin
- Contact:
Hehehe - coolUncleAge wrote:First post (technically second) so, "Hello" to everyone.
Just bought HH2 a few days ago and so far I really like it. Tom Helzle brought up the app in a Bitwig thread @ KVR 1.5 years ago telling me it might fit my needs. Great advice Tom, sorry it took me so long to give a shot though. You were right.
Doesn't matter how long the journey takes, only the outcome counts...
I sold Live Suite and M4L long ago, Bitwig replaced it beautifully for me and has 100 times better and more flexible routing than Live (any device in any order on a single track, Note and Audio Receivers, universal modulation...).
Usine comes in for me where even that doesn't provide enough flexibility.
Usine IMO could use some workflow enhancements in rather basic patching and "how stuff works" areas (which is where Bitwig shines for me - it works like I think), but functionality-wise it's awesome.
And the new Grid is a good step forwards.
Cheers,
Tom
I am keeping an eye on BWS. After your post I downloaded the latest demo to check out the note receivers. I like the idea but it still does not provide an option to separate incoming midi by channel. This is by big gripe in Live as well. Its the main thing that drove me to HH2.Thomas Helzle wrote:Hehehe - coolUncleAge wrote:First post (technically second) so, "Hello" to everyone.
Just bought HH2 a few days ago and so far I really like it. Tom Helzle brought up the app in a Bitwig thread @ KVR 1.5 years ago telling me it might fit my needs. Great advice Tom, sorry it took me so long to give a shot though. You were right.
Doesn't matter how long the journey takes, only the outcome counts...
I sold Live Suite and M4L long ago, Bitwig replaced it beautifully for me and has 100 times better and more flexible routing than Live (any device in any order on a single track, Note and Audio Receivers, universal modulation...).
Cheers,
Tom
Funny thing is that after I purchased HH2 I ran across a thread on the SquaredHeads forum @ KVR pointing out that the AU version of NORA does allow this functionality to take place in Live. And now I am really stumped as to how it works with NORA but not with any of the other plugins I have tried over the years. Anyway, it doesn't matter much now as my imagination has surpassed what the rest of the app will allow. I'm going to continue down this HH2 path for a while and see where it leads.
Keep up the good work Tom.
-
Thomas Helzle
- Member
- Posts: 334
- Location: Berlin
- Contact:
Yeah, that is a rather annoying limitation in BWS. I work around it by using a controller script that allows to access each midi channel separately on the track input level (see my BWS controller scripts on Github: https://github.com/ThomasHelzle/Toms_Bitwig_Scripts).
But once you are inside a track, you currently can't separate channels (for instance if you have a plugin that is sending out on different channels).
There is a solution to send different channels to multitimbral VSTs like Kontakt, but it's all a bit involved and yeah, the receiver doesn't distinguish them. I hope this will improve over time.
Things like that let me go to HH as well - no such problems here...
Thankfully Moss wrote a great OSC script for BWS, so combining the two became much easier.
I'd love a VST version of HH though.
Cheers,
Tom
But once you are inside a track, you currently can't separate channels (for instance if you have a plugin that is sending out on different channels).
There is a solution to send different channels to multitimbral VSTs like Kontakt, but it's all a bit involved and yeah, the receiver doesn't distinguish them. I hope this will improve over time.
Things like that let me go to HH as well - no such problems here...
Thankfully Moss wrote a great OSC script for BWS, so combining the two became much easier.
I'd love a VST version of HH though.
Cheers,
Tom
Hey thomas, I would be really interested to read some further details on how you integrate the two? I find myself inside Bitwig more often than not these days and would love to have HH open an interacting with my project at the same time.
Re: the MIDI situation in Bitwig, I prefer it over Live as it picks up my OS X MIDI mappings (as opposed to just showing the hardware I/Os directly). Are you on OS X? If so you could maybe use the 'Audio MIDI Setup' tool to define virtual interfaces which are filtered by channel? This wouldn't help with multi-channel VSTs I guess, but it seems like you should be able to patch together hardware based on specific channels.
Definitely more cumbersome than anything in Hollyhock though. Vive l'Usine!
Re: the MIDI situation in Bitwig, I prefer it over Live as it picks up my OS X MIDI mappings (as opposed to just showing the hardware I/Os directly). Are you on OS X? If so you could maybe use the 'Audio MIDI Setup' tool to define virtual interfaces which are filtered by channel? This wouldn't help with multi-channel VSTs I guess, but it seems like you should be able to patch together hardware based on specific channels.
Definitely more cumbersome than anything in Hollyhock though. Vive l'Usine!
-
Thomas Helzle
- Member
- Posts: 334
- Location: Berlin
- Contact:
Hey ceasless,
no, I'm on Windows and use virtual Midi drivers to send Midi to Bitwig (Loop Midi) but otherwise it should work the same.
With my "TomsMultiBiController.control.js" you get every Midi-Channel separately (selectable in the Track header/Inspector) so you are able to send separate Midi channels to different tracks.
To use multi-channel-VSTs in Bitwig is a bit involved though:
- You have the multi-channel-VST for instance on track 1 and select for instance midi channel 1 (from my script) in the track header input dropdown.
- You create an instrument track for each additional channel you want to use, select the channel input in the track header and set it's output from the output dropdown to "Notes to Track" - "Plugins" - and from that list the VST you want to address.
- After you did that, a midi-channel selector shows up in the output selector and there you can select the midi-channel this track should be sent on directly to the VST (doesn't have to be the same as the input).
Sounds more complicated than it is actually.
This way, you have each channel on a separate track which is usually easier to deal with than a combined track (and multi-layer-editing helps with that too).
With 1.2 and group tracks this should become much more painless and foldable.
The OSC4Bitwig script can be found here:
https://github.com/git-moss/OSC4Bitwig
Here is the help page with all currently available messages:
https://github.com/git-moss/OSC4Bitwig/wiki
So via OSC you can connect the two quite thoroughly without going into scripting yourself.
Sending Midi to Usine I also do with Loop Midi and a Hardware Instrument Device (where you also can set a channel).
What I didn't really try out yet is syncing Usine to BWS via Midi Beat Clock (BWS can only be master).
My script is sending it, but I haven't found out yet how to sync Usine to it.
Cheers,
Tom
Edit: Found the MIDI clock settings in the MIDI input port, but activating "receive midi clock" doesn't seem to do anything. Not sure what I'm supposed to do to sync the workspace to it.
no, I'm on Windows and use virtual Midi drivers to send Midi to Bitwig (Loop Midi) but otherwise it should work the same.
With my "TomsMultiBiController.control.js" you get every Midi-Channel separately (selectable in the Track header/Inspector) so you are able to send separate Midi channels to different tracks.
To use multi-channel-VSTs in Bitwig is a bit involved though:
- You have the multi-channel-VST for instance on track 1 and select for instance midi channel 1 (from my script) in the track header input dropdown.
- You create an instrument track for each additional channel you want to use, select the channel input in the track header and set it's output from the output dropdown to "Notes to Track" - "Plugins" - and from that list the VST you want to address.
- After you did that, a midi-channel selector shows up in the output selector and there you can select the midi-channel this track should be sent on directly to the VST (doesn't have to be the same as the input).
Sounds more complicated than it is actually.
This way, you have each channel on a separate track which is usually easier to deal with than a combined track (and multi-layer-editing helps with that too).
With 1.2 and group tracks this should become much more painless and foldable.
The OSC4Bitwig script can be found here:
https://github.com/git-moss/OSC4Bitwig
Here is the help page with all currently available messages:
https://github.com/git-moss/OSC4Bitwig/wiki
So via OSC you can connect the two quite thoroughly without going into scripting yourself.
Sending Midi to Usine I also do with Loop Midi and a Hardware Instrument Device (where you also can set a channel).
What I didn't really try out yet is syncing Usine to BWS via Midi Beat Clock (BWS can only be master).
My script is sending it, but I haven't found out yet how to sync Usine to it.
Cheers,
Tom
Edit: Found the MIDI clock settings in the MIDI input port, but activating "receive midi clock" doesn't seem to do anything. Not sure what I'm supposed to do to sync the workspace to it.
-
Thomas Helzle
- Member
- Posts: 334
- Location: Berlin
- Contact:
Update:
Still no luck with finding any information about how to sync to the midi beat clock from Bitwig.
Incoming OSC from Bitwig works fine.
I send the /play input to MasterSync -> On to sync playback and /tempo/raw to MasterSync -> tempo.
I have absolutely no luck though with sending OSC out of Usine, neither to BWS nor any other OSC tool.
Not sure what I'm doing wrong. (Windows 8.1, Usine 67b).
Firewall is open.
I use OSC Send with the same /play command to the listening port, trace tells me it's sending it out, but no other OSC tools hear anything...
But maybe this should go into another thread...
Cheers,
Tom
Still no luck with finding any information about how to sync to the midi beat clock from Bitwig.
Incoming OSC from Bitwig works fine.
I send the /play input to MasterSync -> On to sync playback and /tempo/raw to MasterSync -> tempo.
I have absolutely no luck though with sending OSC out of Usine, neither to BWS nor any other OSC tool.
Not sure what I'm doing wrong. (Windows 8.1, Usine 67b).
Firewall is open.
I use OSC Send with the same /play command to the listening port, trace tells me it's sending it out, but no other OSC tools hear anything...
But maybe this should go into another thread...
Cheers,
Tom
Greetings estrauss69!
Welcome!
-s
Welcome!
-s
"Every act of creation is first an act of destruction." -Picasso
Hello, loving H3!
I have upgraded to H3 and i am loving the improvements. However, I have been getting audio pops and clicks. This is even when I have the audio buffers and Usine block size set to higher values. This is still happening when I have only one rack and very few patches running.
Is anyone else having the same problem? This never happened with the previous version.
Best Jaydev
I have upgraded to H3 and i am loving the improvements. However, I have been getting audio pops and clicks. This is even when I have the audio buffers and Usine block size set to higher values. This is still happening when I have only one rack and very few patches running.
Is anyone else having the same problem? This never happened with the previous version.
Best Jaydev
Nice to see an introduction post, perhaps there should be a stickied topic for new users as myself, who can't post a new thread until after replying to one. Hence this post.
Hello to everyone!
Hello to everyone!
welcome to the sleepless nights !
http://oli-lab.org
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Welcome to the forum!
Welcome Tim !
-
Christophe Rault
- Member
- Posts: 32
- Location: Belgium
- Contact:
Hello Everyone,
I've been turning around Usine for a year now.
I'm actually working on 2 dance shows here in bruxelles. Both with Usine of course ! !
I'm very happy to start working with this software. It feels like I have a whole new side of sound I'm getting into.
thanks to everyone.
hello to Olivier S and Hervé B !
Christophe R
I've been turning around Usine for a year now.
I'm actually working on 2 dance shows here in bruxelles. Both with Usine of course ! !
I'm very happy to start working with this software. It feels like I have a whole new side of sound I'm getting into.
thanks to everyone.
hello to Olivier S and Hervé B !
Christophe R
Réalisateur radio, metteur en ondes, création sonore, archerie asiatique et vit sur une péniche.
First to the forum here, very glad to see this good forum activity.
All the best to the senso team !
All the best to the senso team !
Hello everyone
New Usine user
New Usine user
Who is online
Users browsing this forum: No registered users and 22 guests
