MIXVIBES Dj Community old forum

Good morning everybody!

For me there was no need to switch from Producer to Cross in the past, because i love my Producer and spended a lot of time with customizing and optimizing (selfmade skins, 15kb MIDI mappings ) until i found the optimal setup which gets the most out of my equipment and fits perfect to the way i make music.
As a Betatester i am proud doning a little bit
contribute to the further development of Mixvibes and i like to share my experience to help other members of the mixvibes community.
So time has come to take a deeper look into Cross
Here are the first impression and questions which i got during set up MIDI.
Sorry if it looks like i want to badmouth Cross, that is definitly not my intention

- I dont know why but my Korg Zero 8 and Novation SL Mk2 are not shown in the available MIDI devices. I have to route them both to a MidiYoke port and use this.
- Why cant the same controller (with different values) be mapped more then one time anymore? This is a big limitation for many operations. The only workaround seems to be using "cloned" virtual MIDI devices each with its own controller mapping.
- Pitchbend: there should be also a autorepeat option to get an increasing bend value while the button down is held down.
- Locators: why is there not used the old DVS/Producer "memo" command anymore? It is much more efficient.
I used it the way that hitting a locator while hold down memo saves the locator and without holding memo it jumps to the locator.
- BeatGrid: it would be better if moving left/right and shrinking/expanding size couldt also be done with an relative encoder. For now i use the "cloned" MIDI device workaround mentioned above.
- Why is the Sync mode button "hidden" in settings window. There is enough space next to the beatmatcher´s zoom fader
- Following commands are not clear to me, may someone can tell me what they do:
Perform secondary action on active browsable
Focus the spotlight
Shift logic
Shift selector


So this was the first part...
The next one will follow these days.

Best regards
Marxon

Wow - where does one start !!!
I know one answer for you Marxon! hehehe

Focus function:(edit...i have no idea )

Cheers

no, fucus just highlights the search-filed nothing else.

Marxon wrote:- I dont know why but my Korg Zero 8 and Novation SL Mk2 are not shown in the available MIDI devices. I have to route them both to a MidiYoke port and use this.

May be agent/translator linked.

- Why cant the same controller (with different values) be mapped more then one time anymore? This is a big limitation for many operations. The only workaround seems to be using "cloned" virtual MIDI devices each with its own controller mapping.

Still on the 1:1 behavior, may be modifier can help you there.

- Pitchbend: there should be also a autorepeat option to get an increasing bend value while the button down is held down.

The bend values are based on the type of bend and its settings not on the more you press the more you bend.

- Locators: why is there not used the old DVS/Producer "memo" command anymore? It is much more efficient.
I used it the way that hitting a locator while hold down memo saves the locator and without holding memo it jumps to the locator

You're talking of deleting/replacing a locator there ?

- BeatGrid: it would be better if moving left/right and shrinking/expanding size couldt also be done with an relative encoder. For now i use the "cloned" MIDI device workaround mentioned above.

True instead of 2 buttons : could be cool.

- Why is the Sync mode button "hidden" in settings window. There is enough space next to the beatmatcher´s zoom fader

Because you set it to your liking, not supposed to change it often.

Perform secondary action on active browsable

On each section of the browsable item there is a main action and a secondary one.
Don't remember in details but should be easy to understand once mapped.

Focus the spotlight

Simply put the cursor into the spotlight. Click & type.

Shift logic

Used to layer commands with a button.

Shift selector

Can't remember : I never use it.

Hi Support,
thank you for your support and sorry for my late reply.

May be agent/translator linked.

Problem fixed viewtopic.php?f=358&t=25297

Still on the 1:1 behavior, may be modifier can help you there.

Problem fixed i route these controllers to a virtual MIDI port so Cross receives the same signal from 2 different MIDI devices, both with theire own controller mapping

The bend values are based on the type of bend and its settings not on the more you press the more you bend.

Of course this not depends on the button pressure force!
I should depend on how long the button gets pushed.
Exactly like those INC and INT flags in Producer/DVS if you can remember them.

You're talking of deleting/replacing a locator there ?

Yes ecaxtly. But I was able to set up Cross modifiers to get the same behaivor

- BeatGrid: it would be better if moving left/right and shrinking/expanding size couldt also be done with an relative encoder. For now i use the "cloned" MIDI device workaround mentioned above.

True instead of 2 buttons : could be cool.

Because you set it to your liking, not supposed to change it often.

What if i like to change it often
But no problem this is not a big issue, i can life with this

On each section of the browsable item there is a main action and a secondary one.
Don't remember in details but should be easy to understand once mapped.

Ok i am gonna play around a little bit more.

Simply put the cursor into the spotlight. Click & type.

ahhhh.... Things could be so easy from time to time.

Again, thank a lot for answering my questions

cheers
Marxon

I know you say you have a fix for your novation device useing MIDI yoke,Just to add my finds, i have owned 4 novation automap devices over the last 3 years, and the problems are always too do with the novation drivers, i get problems all the time with my music production setup and also to this date with my novation impulse and automap 4.4, even when the novation drivers show up in my windows device manger setup, they are not always detected by my software.

I have been troubleshooting this stuff with novation on and off for years, and do not expect any resolve, its just bad drivers and tempramental automap software, not that you need automap but just thought i should mention about novation on the whole.
I had to run Cross of my PC the other day instead of my laptop, and on my PC only' i have automap/novation impulse keyboard and these did show up in Cross MIDI in/outs for me, but in my 4 production Daws i have, it is a pain in the backside, i gave up on automap and just use basic MIDI, becuase automap keeps failing to detect, more so down too the novation drivers, again i know this becuase on times the Novation driver can also fail to show up in device manager.
its quite a long winded story to explain in full, but take it on me, that it will not be Cross at fualt in the case of your novation controller, Novation Gear has its charm, but is not very reliable.