Forum Replies Created
-
Posts
-
No, no – it’s absolutely not needed. Converting my images (from horizontal to vertical) is done quickly. I just was asking because in older v5 releases only horizontal fimstrips has been supported (if I remember correctly) – that’s why I exported them in knobman as horizontal. It was just a confusing thing.
OK, I found out that if I’m using vertical filmstrips (instead of horizontal) it’s working. Is that now the way it works or is the non-support of horizontal filmstrips a bug?
Is it possible that the filmstrips of Image/FixedImageSliders aren’t "played" correctly? When I’m tweaking them all the time just picture 1 is displayed, changing the Slider’s settings doesn’t seem to work.
Very nice update, atom! The "feedback" problem with the Tetra/Virus seems to be completely solved… thanks a lot!
Hmm, that’s really weird – can’t explain it myself what happened there. In my case I only use 1 MIDI port which is dedicated to MIDI in/out of the synth. MIDI notes doesn’t go through Ctrlr – I’m sending them directly from the host to the synth. Does this problem still appears when the nanokey is disconnected – and you send MIDI notes directly from the panel? Is just the MIDI in of the nanokey activated (in Ctrlr) – and just the MIDI out of the midisport? But these are only some helpless shots in the dark… Sorry, absolutely no idea what this can be.
Yeah, this "total integration" thing could be very cool. Nice that you be on it!
I did some more tests and find something out, don’t know if it’s helpful:
This problem only appears when the Tetra’s KnobMode is either set to "Passthru" (snap) or to "Relative". If I choose KnobMode = "Jump" there are no problems at all!
… The Virus’s KnobMode doesn’t seem to change this behaviour (in all releases before build 450 everything worked perfect with every KnobMode, but not since 450 – as you know).
Even if this information isn’t helpful – it’s nice that there is a workaround for the Tetra (KnobMode=Jump).In your first comment you wrote about "the [i:oql6676q]standard method[/i:oql6676q] of handling this is to turn the midi thru setting…"
Now you write "Enabling it CAN introduce feedback [i:oql6676q]in certain situations[/i:oql6676q]"
And I can "just sit tight", no problem. It wasn’t me who recalled a 2 weeks old thread?But for sure we completely missunderstood eachother – nevermind & thanks for your help so far (honestly).
msepsis, I appreciate your effort. But the question how to connect the synth was meant rhetorically, because as I already wrote: I use a Tetra and there are NO settings for "Thru=OFF". I only can set the MIDI out to "Out" or "Thru". Because (it’s logical for me) the setting "Thru" prevents that MIDI messages are sent to MIDI out – this makes no sense.
” title=”Wink” /> To answer a few questions:– this "feedback" (stucking values) only appears when the Tetra controls Ctrlr – not the other direction
– every parameter is affected – not only "selection buttons"
– while this stucking appears the MIDI In/Out LEDs (on the interface) are activated (logical: It’s a bidirectional connection). But the LEDs doesn’t stick (they are off when I stop tweaking a knob).
– when I’m tweaking a knob very slowly everything works as usal. But when I like to tweak a know a bit faster, the value sticks at a certain pointAppart from this: Can someone else confirm that MIDI Thru is for avoiding feedback?? I’ve the feeling that the Microwave has some special settings which other synths don’t have – maybe this confuses this discussion?
But a slider with values from -64 to +63 is a bipolar knob. Or do want just this graphic stuff? Then knobman is an great app.
If it’s ok when there are no graphics, try to type the wanted value range in the values of an FixedSlider OR take an normal Slider and do what is written above.minimum value: 0
maximum value: 127
modulatorValue +64
midiValue -64edit: too late
"omutumo":3emc9z1r wrote:Can you make Ctrlr pick up the currently selected preset on the Pulse as you scroll through[/quote:3emc9z1r]
As far as I know: Not at the moment but later.2. question: The answer you can find in your other thread. The magical word is "FixedSlider".
” title=”Wink” />For a "-64/+63" slider set minimum value to "0" and maximum value to "127". Then type directly behind modulatorValue "+64" and type directly behind midiValue "-64". If I remember it right it should work.
Or just take an uiFixedSlider (that’s what I prefer). It seems to be a lot of work to type every value seperatly – but then you can copy/paste and do some other funny discription things (e.g. for an EQ the Hz and dB values, or the semitones of the osc frequence).Sorry to say this but as you supposed this fix really affects a few new issues.
a) When controlling Ctrlr via the Virus C the parameter values get confused. E.g. if I turn a knob on the Virus it jumps always back to value "0". That means if I like to increase the startvalue 50… immediately the parameter/value (visible in Ctrlr GUI and Virus display) are jumping from 50 to 0… then from 53 to 0… then from 55 to 0… and so on – it’s not possible to increase a value step by step (50, 51, 52, 53…). With the Tetra this doesn’t happen (there is still this "parameters get stucked when turning a knob a bit faster" feedback problem). When I control via Ctrlr the Virus everything works as normal/before.
b) sometimes it seems that the MIDI connection breaks (no messages are received anymore – have to restart Ctrlr), but this happens very very rarely so it’s hard to reproduce.
Would be nice if this could be fixable, cause I love to touch my synths directly (not with mouse/controller).
” title=”Smile” />My DSI Tetra is affected by this feedback strongly. But I’m confused. As far as I know MIDI thru is for chaining multible MIDI devices – if you don’t have enough MIDI ports. Of course if you send then on an other MIDI channel (to control an other MIDI device) – the "source channel" of the first synth isn’t affected. The Tetra has MIDI In/Out – but I can set the Out to Thru, but then again it doesn’t send it’s internal MIDI messages to the out anymore (and this seems logical to me)… Even if the Tetra would have an seperate Thru port – how should I connect it to obtain a bidirectional communication? Did I missunderstood you?
Truly fixed! Nice work – for some days I thought that maybe it could be possible that there isn’t a chance to change this.
” title=”Smile” /> Thanks!It seems to me that this change isn’t related to the old JUCE version, because the "clicking bug" appears with release 402 – the "back to arrangement bug" appears much earlier (maybe 10 releases before?). I guess at this time Ctrlr was also using the old JUCE version? Because you’re speaking about the Mac version – the PC version doesn’t have this problem with Ableton?
The latest release didn’t fix this problem, sorry. I try to explain the inner/outer circle better.
The inner knob: This basic/main knob has 2 functions
a) for normal realtime parameter tweaking
b) it determines the starting point of the automation, but it should NEVER be affected by the automation. If this knob is e.g. set to value 50, the automation is related (in percent) to value 50. When the automation has a range from 0% to +100%, the synth is receiving values between 50 and 127. When the range of the automation is from -100% to 0%, the synth is receiving values between 0 and 50. That means that this knob determines the initial point from where the automation starts.The outer circle (outside the basic knob): This circle just has 1 function
a) this is for recording automations (if you don’t have the Maschine hardware). Just click with the mouse on this outer circle and move this parameter (while Maschine is in playback). If you move this parameter you can see in the GUI that it works in percent. Left is -100%, right is +100%.Now, when you automate Ctrlr (by moving the outer circle) the basic knob receives messages, too. This shouldn’t happen, because the initial/starting point of the automation is moving all the time (sometimes more, sometimes less)! That means that the synth never receives the wanted automated values (the range is correct, but because the initial point is moving all the time – the range is moving, too).
Did this explanation was more helpful? It’s not easy for me to explain. But at the moment it seems to me that Ctrlr’s components are sending back their automated values – this [i:5zey1bag]could[/i:5zey1bag] be the reason why the basic knob is affected. As I wrote all other plugins I’ve tested behave behave "normal" – just the outer circle is affected by the automation.
Maybe my post was too long (or not clearly enough?), but this issue/bug is really(!) a serious problem – at least for us Maschine users (in Ableton it works, because the automation concept is different).
The absolutely main reason for me to use Ctrlr is the possibility to automate my hardware. But because of this behaviour automations get destroyed (the range of the automation is moving all the time, because of the automated basic knob) and that’s why: [i:2wjqis2z]if[/i:2wjqis2z] Ctrlr would stay like this – it [i:2wjqis2z]could[/i:2wjqis2z] become useless for me (hate to say this, but it’s true).Is there a chance to fix that? If you need closer informations (or a short video), please tell. A short answer would be nice.
