Author |
Message |
ripe909
Joined: Sep 09, 2007 Posts: 8 Location: TX
G2 patch files: 1
|
Posted: Mon May 19, 2008 5:29 am Post subject:
2Qs: trace module? recording seq triggers? |
 |
|
Hello,
I just jumped on the G2 engine bandwagon ($799 from MF!).
I have two quick questions...
* Is there a trace module within the patch editor? I would like to see what some values are as they change. I have been using an A/D module, but it's not the friendliest way to read a value
* Is there a way to record incoming triggers to a Note Seq? I want the triggers to be recorded at the same time as values from incoming MIDI notes... so far I could only see controlling them manually with a pushbutton.
cheers
ripe |
|
Back to top
|
|
 |
Fozzie

Joined: Jun 04, 2004 Posts: 875 Location: Near Wageningen, the Netherlands
Audio files: 8
G2 patch files: 49
|
Posted: Mon May 19, 2008 7:47 am Post subject:
Re: 2Qs: trace module? recording seq triggers? |
 |
|
ripe909 wrote: |
* Is there a trace module within the patch editor? I would like to see what some values are as they change. I have been using an A/D module, but it's not the friendliest way to read a value
|
Cool that you got an engine!! Get ready for sleep deprivation, stroopwafels and pure patching bliss
About a trace module; there isn't one (to the regret of many users), however for quick visual reference you can use this hack: feed the signal you want to visualize into a midi CTRL send module (CC value input), set to an unused CC# and the midi channel to "slot A" (assuming you are patching and reading out in slot A; do not use "this slot"). Now insert a Constant module (level group) somewhere in your patch, right-click to assign a midi cc to it and select the same midi CC# as you assigned to the midi ctrl send module.
Works quick 'n dirty, since resolution is low and only works on 0-64 without scaling or other adaptations, but gives a quick visual reference. Quick example attached (didn't try it, but should work).
Other quick reference is putting the signal into a mixer with VU meter, such as the mixer 4-1b. They are slooowwwww however.
Description: |
|
 Download (listen) |
Filename: |
visual reference.pch2 |
Filesize: |
902 Bytes |
Downloaded: |
1475 Time(s) |
_________________ Spinning at ~0.0000115740740741 Hz |
|
Back to top
|
|
 |
ripe909
Joined: Sep 09, 2007 Posts: 8 Location: TX
G2 patch files: 1
|
Posted: Mon May 19, 2008 11:08 am Post subject:
|
 |
|
Thanks for the tips... I guess I will continue to use the A/D it's not that bad to read the value from, but it doesn't have a history.
Something that graphed an input against time would be awesome, but I can't sacrifice the patch load to do it via controllers.
cheers
ripe |
|
Back to top
|
|
 |
dasz

Joined: Oct 16, 2004 Posts: 1644 Location: victoria, canada
Audio files: 29
G2 patch files: 56
|
Posted: Mon May 19, 2008 4:42 pm Post subject:
|
 |
|
There is one more hidden trick, you can assign the VU meters of the 4 stereo mixer, or output modules (output 2 and output 4), etc to the g2 panel (right click over the vu level and assign it to a knob), it's a peak hold assignment, not the accurate solution that Fozzie recommended (the best option as far as I know), aaaand can assign to the panel are the output gate indicator of LFO A & B.
I don't know if there are others.
/Dasz |
|
Back to top
|
|
 |
iPassenger

Joined: Jan 27, 2007 Posts: 1068 Location: Sheffield, UK
Audio files: 5
G2 patch files: 78
|
Posted: Tue May 20, 2008 2:00 am Post subject:
|
 |
|
If you wanted to see the control data (dial movement/motion) recorded, graph style, over time.
You could use the ctrl send trick and just record the controller data into as DAW, like Ableton/Cubase etc..
Also i don't think the ctrl send modules use very much dsp power. _________________ iP (Ross)
- http://ipassenger.bandcamp.com
- http://soundcloud.com/ipassenger |
|
Back to top
|
|
 |
|