Page 1 of 2
still in the test period...
Posted: Mon Aug 17, 2009 23:59
by VJ99p
how do you force it to stop declaring "Resolume Avenue" each minute?
Re: still in the test period...
Posted: Tue Aug 18, 2009 00:24
by VJair
you buy it.
Re: still in the test period...
Posted: Tue Aug 18, 2009 00:35
by VJ99p
I see. as i said i'm still testing avenue - what happen to the midi mapping method? i cant map each layer individually? i cant assign midi note to effects? i cant map each layer opacity or make layer 2 or 3 play only?
how can assign midi notes to play-pause- random and no matter which layer i'm using?
Re: still in the test period...
Posted: Tue Aug 18, 2009 10:00
by bart
VJ99p wrote:i cant map each layer individually?
No this is unfortunately not possible yet but we are working on this.
Re: still in the test period...
Posted: Tue Aug 18, 2009 14:06
by GeeEs
Not possible?? huh... this is strange... or maybe I just don't understand the problem
I bet I mapped 3 different layers individually this weekend without any problem...
I connected: scale / opacity / size and anchor parameters from 3 different layers to different CC parameters in FruityLoops... (all thrue 1 MIDI channel)
Worked like it supposed to imho... (mapping on -> click the desired parameter -> move knob on MIDI out in FruityLoops -> get the CC number in the yellow mapping field)
Made some automation tracks for all the CC parameters and they just started to move in Resolume when I started FruityLoops... (all 3 layers independent)
Re: still in the test period...
Posted: Tue Aug 18, 2009 15:36
by gradek
Yeah, I'm confused. Mapping the active layer is possible with application layer mapping mode, and mapping individual layers is possible with application deck mapping mode.
Re: still in the test period...
Posted: Tue Aug 18, 2009 16:14
by bart
Yes, you map opacity etc for each layer by selecting Focus: Deck when mapping. But mapping the transport controlls for each layer does not work as expected.
Re: still in the test period...
Posted: Tue Aug 18, 2009 16:44
by GeeEs

still confused...
As we speak I have bounded 21 MIDI notes and 6 CC parameters to 3 different layers transport controls (play forward / play backward / etc...). So actually 7 MIDI notes and 2 CC parameters per layer individual... It's really working fine here...
Although!!! I first deleted the preconfigured MIDI mapping which loads to Layer 1 clips (C0-D0-E0-F0.. etc...)
Before deleting this standard mapping I got conflicts because of this! Actually I just deleted all standard mappings before I started mapping my own controls.
(I found that it's not posible to map the transportcontrols if there is no clip / or a still image(jpg) loaded to that layer!!)
[edit] When set to "play once" in the layer transport controls, the clip unloads from that specific layer after it's been played once (like normal i guess)... After that, there is no visual (yellow) feedback from the buttons when a MIDI note is pressed for that layer transport controls, it's still there though

! )
Re: still in the test period...
Posted: Tue Aug 18, 2009 23:45
by VJ99p
GeeEs - from your Attachment I see that you managed to map all Three layers? the default in Avenue gives you the choise only for one layer. can write down here what you change? where?
Re: still in the test period...
Posted: Wed Aug 19, 2009 00:10
by gradek
So just by deleting the preconfigured MIDI mapping file you were able to do this? I wonder how that works. I'm not using the default, although my mapping config is based of the default file, I just saved under a new name after I did my mapping. You think some controls get unlocked if there is no midiconfig for resoulume to read when the app is launched?