Me again =)
Just to make sure we're all on the same page, after a brainstorm session,
Albert and I had
the idea of making 2 views, the Compact and Advanced:
Advanced: Features 4 complete FXWidgets (Dropdown, Wet/Dry, 4 Parameter Knobs)
Compact: 4 Knobs (linked to the Wet/Dry of the corresponding FX from Advanced)
Check it out: Interface Mockup #4.
More info: http://bit.ly/ac1jYO
Thanks!
On Jul 6, 2010, at 10:29 AM, Bruno Buccolo wrote:
> Hello guys,
>
> I've designed 2 new options:
>
> #2 - attends to albert's request of saving more space (I really like this
> one, extra space = more units?)
>
> #3 - ultra compact version, lay out without using the EffectsUnits Tab/Page.
> This looks a little cluttered in my opinion, but could work out if we lowered
> the Library. Took out the flanger knobs and rearranged some knobs.
>
>
> Interface Mockup #2 Interface Mockup #3
>
> There you go.
>
> Thanks!
>
>
> On Jul 6, 2010, at 8:55 AM, Bruno Buccolo wrote:
>
>> Hi guys,
>>
>> @jus:
>> The workflow will be something like:
>> 1. User chooses the desired effect (from dropdown box)
>> 2. User chooses which channels will be processed (we can have a master
>> button too)
>> 3. User tweaks parameters and play with them.
>>
>> *Can the effects be enabled for master signal (sum) too or "only" to channel
>> X?
>> I was just thinking about a Master button, might be useful with n-decks.
>>
>> *Can Effect 1 be enabled for channel A with other parameter then channel B
>> at the same time?
>> I don't think so, but it could be done by loading the same effect into the 2
>> units.
>>
>> *Can effect settings or/and effect chains be saved for later use/sharing?
>> The effects settings will be saved in presets, which can be shared, but both
>> users would need to have the ladspaeffect.so library. I haven't thought
>> about storing the chain setup.
>>
>> *What about the effect routing, it always goes from bottom to the top?
>> (Channel X-->Effect1-->Effect2-->Effect3-->Master)
>> or can the effects be rewired to something like this
>> (Channel X-->Effect2-->Effect1-->Effect3-->Master)
>> Well, it's actually unit based, so if you need Effect 2 before Effect1, you
>> can load it on a upper unit.
>>
>> *Is the content (buttons, knobs) in the effects tab skinnable with the
>> current skin system?
>> Yup, the knobs will be reused, but the other buttons are skinnable. The
>> fxunit itself will have a skin file, so it's easier to play around with it.
>> =)
>>
>>
>>
>> @albert:
>> I did realize I was using up a lot of space, but that was the spot I had to
>> place the fxunit on the Outline skin.
>> I'll come up with more compact version of it, so we have at least one more
>> option =)
>>
>> RJ is currently at India, he hasn't commented yet bacause it's a totally
>> different timezone.
>>
>>
>> Cheers!
>> Thanks guys for the feedback!
>>
>>
>> On Jul 6, 2010, at 2:31 AM, Albert Santoni wrote:
>>
>>> Hi Bruno,
>>>
>>> Great mockup! I'm looking forward to playing around with this.
>>>
>>> My main suggestion is to consider making each effect unit more compact.
>>> Maybe move the knobs up directly beside the combobox or something like
>>> that. In your mockup, half the space in each effect unit is empty.
>>>
>>> What is the end goal for the GUI part of this? We could keep a larger
>>> "Effect Units" widget (ie. the contents of your pane in the tab right now)
>>> for when we rewrite the GUI, but is it worth perhaps considering writing a
>>> smaller widget that fits into our existing skins (without using the tabbed
>>> widget)?
>>>
>>> I'm just throwing ideas out there to get the conversation going. I'm not
>>> sure at what phase you and RJ are at with the design. Either way, I'm
>>> looking forward to more LADSPA stuff!
>>>
>>> Thanks!
>>> Albert
>>>
>>>
>>>
>>>
>>> On Mon, Jul 5, 2010 at 8:29 AM, Bruno Buccolo <[email protected]>
>>> wrote:
>>> Whats up Mixxxers?
>>>
>>> I've just designed this mockup, I'd love to know your opinions and have
>>> your feedback.
>>>
>>>
>>> Interface Mockup #1
>>>
>>> This mockup features 2 EffectsUnitsSlots. (the # of slots could be
>>> preference-based)
>>>
>>> Now describing the EffectsUnitSlot (top to bottom):
>>> Dropdown box to select the desired effect.
>>> Next/Previous buttons to change the currently loaded effect using MIDI.
>>> Channel buttons to enable/disable the process() of the loaded effect on
>>> that channel.
>>> Wet/Dry knob.
>>> Four effect-based parameter knobs. (the # of knobs available could be
>>> preference-based)
>>>
>>> After the design is approved, I'd like to write a post about it on our
>>> blog, to tease our users :D
>>>
>>> Cheers!
>>>
>>> Bruno Buccolo
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Sprint
>>> What will you do first with EVO, the first 4G phone?
>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>> _______________________________________________
>>> Mixxx-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>>>
>>>
>>
>> Bruno Buccolo
>>
>>
>>
>
> Bruno Buccolo
>
>
>
Bruno Buccolo
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
