]]>
]]>
]]>
it could also not work if you had engine stopped.
What I know is that I forgot something... I'll try later, after work!I customized the touch faders to work as Hammond organ drawbars, they look nice! I prefer this solution over the customized knobman fader solution, because I don't like the fact that I have to move the mouse horizontally to make the drawbar move vertically.
Statistics: Posted by sguyader — 06 Jun 2019, 16:00
]]>
]]>
Statistics: Posted by sguyader — 06 Jun 2019, 15:28
]]>
Statistics: Posted by nay-seven — 06 Jun 2019, 15:17
]]>
Statistics: Posted by nay-seven — 06 Jun 2019, 15:16
]]>
I did check this Control/MIDI, and I tried to enable these parameters, but none of them seemed to allow what I want: I'm not trying to output MIDI data from the touch faders, I need them to move on screen when I move the physical faders from my controler (i.e. I want them to react to input MIDI data). I didn't find any "learn" switch whereas I can find it for regular faders.Check Control/MIDI tab, there you can enable any of 4 different types of parameters (X,Y,Z, switch) to output different CC's on assigned channels and also use Learn switch for any of them.
notice that you need your controller enabled in the input of the rack, also engine needs to be on for it to work.
Statistics: Posted by x.iso — 06 Jun 2019, 15:13
]]>
But it's possible to reproduce by patch with counter module.
Can you elaborate on this?Statistics: Posted by sguyader — 06 Jun 2019, 14:40
]]>
Check Control/MIDI tab, there you can enable any of 4 different types of parameters (X,Y,Z, switch) to output different CC's on assigned channels and also use Learn switch for any of them.
I did check this Control/MIDI, and I tried to enable these parameters, but none of them seemed to allow what I want: I'm not trying to output MIDI data from the touch faders, I need them to move on screen when I move the physical faders from my controler (i.e. I want them to react to input MIDI data). I didn't find any "learn" switch whereas I can find it for regular faders.Statistics: Posted by sguyader — 06 Jun 2019, 14:38
]]>
I wanted to try the touch faders, but... I couldn't find a way to assign them to physical faders on my midi keyboard, are they touch- and mouse-only?
Check Control/MIDI tab, there you can enable any of 4 different types of parameters (X,Y,Z, switch) to output different CC's on assigned channels and also use Learn switch for any of them.Statistics: Posted by x.iso — 06 Jun 2019, 11:50
]]>
But it's possible to reproduce by patch with counter module.
Statistics: Posted by joffo78 — 06 Jun 2019, 08:40
]]>
]]>
Statistics: Posted by nay-seven — 05 Jun 2019, 09:09
]]>
Just for fun, here's how my workspace looks like (with a detail of my B3 organ patch, with drawbars assigned to faders of my keyboard
):
Statistics: Posted by sguyader — 05 Jun 2019, 05:30
]]>
Statistics: Posted by sguyader — 04 Jun 2019, 02:23
]]>
Yes I know for CPU, what concerns me more is RAM usage, especially for sampler VSTi's such as Kontakt Player with sample libraries loaded.Dont worry About cpu usage with the grid . 32 rack is nothing and patchs are not calculated where there are desactivated.
!
Statistics: Posted by joffo78 — 04 Jun 2019, 02:15
]]>
Dont worry About cpu usage with the grid . 32 rack is nothing and patchs are not calculated where there are desactivated.
Yes I know for CPU, what concerns me more is RAM usage, especially for sampler VSTi's such as Kontakt Player with sample libraries loaded.Oh! I didn't try that, I thought that "pause" would really pause everything. I'll try that later.For your section problem it's possible to set it at pause instead off loop at the end
Thanks!
Statistics: Posted by sguyader — 03 Jun 2019, 21:17
]]>
]]>
]]>
I also already thought about creating 2 racks for each VSTi which can be played from either of the 2 keyboards (some other VSTi's are always played from the same keyboard, so for those only 1 rack is enough). However, I wanted to see if there's a more "economical" way to allow selecting the device from the grid. I think I have already tried to drop a device on the grid, but it didn't allow me to do it, I could only drop devices in the I/O sections of a rack (I'm using the latest HH build).
I have 16 songs in, my setlist, wouldn't it be too heavy to have 16x2 = 32 racks in the same workspace, knowing that some of those VSTi's are quite heavy on system resources? (I know CPU is not concerned as long as the racks are turned off, but they still reside in memory).
I also tried to use some rack preset recalls in grid sections, but the problem is that when the reading head of the section loops back, it cuts the audio output: if I'm playing sustained chord at that time, it gets cut and I have to hit the chord again.
I was hoping there would be some clever solution to avoid duplicating the racks.
Statistics: Posted by sguyader — 03 Jun 2019, 20:09
]]>
-First i suggest you to create one rack for each input (your 2 keyboards for example)
- Create 2 vsti racks for each song . Put for each only vsti needed by each keyboard as differents patchs.
It doesn't matter if you create several rack with the same vsti inside. i think it's more important to have a clear "vision" of your workflow.
So if you've for example a song that use 3 vsti for each keyboard create to rack with There. ccreate as a section you have changes during your song . drop your two racks on all this section and your vsti patches only on the section that there are needed.
If you have different preset for the same vsti create different items on the same patch for each section and recall your preset number on the section grid preferences.
I hope it could help you.
JF
Statistics: Posted by joffo78 — 03 Jun 2019, 19:41
]]>
I'm a new user and please forgive me if my question has an easy answer, I couldn't figure it out.
Here's a description of my needs:
I want to see if I can use HH as a VSTi host, controlling several instruments from 2 keyboards in a live situation. Basically I use 6 VSTi's, each one with a number of presets to be loaded according to the actual song during the live set. I need the switch to be relatively fast, as sometimes I need to start the next song quickly after the previous one.
Here's what I have tried.
Scenario 1
The simplest solution I found:
- for each song, create a workspace, load only the required VSTi's
- each VSTi is a patch in its own rack, with the right MIDI device assigned
- save a workspace for each song
This way I can add each song/workspace to the "playlist" module to switch between songs. It's great but... the unloading/loading of racks takes too much time. Whatever the number of racks to load, it always takes overall 7 seconds until I can play a note. This is way too long.
Scenario 2
- create one complete workspace with the 6 racks containing 1 patch/VSTi
- create presets in each patch
- In the grid, I drop each patch/preset needed for one song in the same section (1 section = 1 song)
- add an automation with bypass on/off (so that the unused racks are not computed)
The good thing is that switching to next song is fast, since all the racks are preloaded in the workspace.
The less good thing is that each plugin occupy some RAM resources, in particular have a rack with a NI Kontakt Player instrument based on samples (Horns section) which occupies 1.3 GB of RAM by itself. It doesn't leave a lot of free RAM.
The bad thing: the input devices are not saved with the patch presets, so this leads to some undesirable side effects: some VSTi's listen to all the MIDI channels at the same time, and I get layered sounds where I don't want (because for some songs I want one VSTi to be played from keyboard #1, while for another song I need the same VSTi to be played from keyboard #2).
Scenario 3
- save rack presets according to the songs, with the relevant input MIDI device turned on/off
- drop the rack presets into the grid (instead of patch presets)
The good thing is that now it recalls which keyboard should trigger the VSTi.
The bad thing is that when I switch to the next song, the patch display doesn't update and is not reflecting anymore the settings used in the current song (I need to have a view of the knobs/faders/buttons that I have configured, particularly for the B3 organ VSTi which is central to my gigs, and which I tweak the drawbars and Leslie cabinet settings a lot during the performance).
So, my questions are:
- in scenario 1, is there a way to avoid the 7 seconds delay between each song? (I guess not, but I'm asking just in case)
- in scenario 2, is there a way to set up either the input MIDI device, or the MIDI channel used, and save that setup in the patch presets? I'm sure there's a easy way but I couldn't find it.
- in scenario 3, is there a way to have the patches UI reflect the changes when switching to a new rack preset?
Thanks in advance!
Statistics: Posted by sguyader — 03 Jun 2019, 18:57
]]>