Forum Replies Created
-
Posts
-
I’ll be damned. Everything is working properly now, through the Virus or otherwise. I know I tried rebooting the Octopus when I had the problem, but I can’t say for sure that I rebooted my computer or the virus. Definitely working as it should.
I swear this happened, though. I’ll keep an eye out for it happening again. I think the specific, repeatable nature of the error must mean that it was an Octopus glitch, because I can’t see how any other part of the chain having a problem would produce such precise results. Would you more knowledgeable types agree with that?
Thanks for your help, anyway. Sorry for having mobilized the troops over nothing.
Actually, maybe that is the issue. I still think it’s unlikely that the Virus is dropping some notes on the MIDI interface side (I have been checking the MIDI, not trusting my ears), but looking at my post dates, I did notice this the day after I updated the Virus OS, so…
I’ll check it when I’m at home tonight.
I’m plugged into my Virus MIDI in, with Virus Control active in Ableton, which should route everything that the Virus gets directly into Live. Ableton has a MIDI in indicator, which is where I’m able to see that there’s no note on happening for certain notes. It’s theoretically possible, I suppose, but highly unlikely, that the Virus is somehow filtering certain notes out. If it were random I would think it more likely than the precise behavior I’ve seen.
Should I try the OS beta? Is it reasonably stable? I’ll try another MIDI interface, as well.
Can anyone confirm this, please? If they write a legato trill on two tracks, does the second note play properly? (Mute any other active tracks).
The plot thickens. I went back to an older sequence and discovered that it’s happening there, as well, and may have always been happening with my Octopus.
The reason I didn’t notice it previously is that a note on any page has the effect of my last sentence in the post above this one. That is, when my drum page is playing, they create the "in between" notes which cause the monophonic synth page to play properly.
Example:
The monophonic synth page is playing 4 notes, such that the first two notes are legato and the last two are stand-alone.
If the drum page is playing, with a note anywhere from the first beat (where the first monophonic note is on the other page) to before the second note of the monophonic page, the monophonic part plays properly. (That is, it plays: Cnoteon, D#noteon, D#noteoff, Cnoteoff).
If there are no notes on the drum part before the D#noteon, but there IS a note before the Cnoteoff, then I get the following: Cnoteon, D#noteoff, Cnoteoff.
If there are no notes on the drum part before the Cnoteoff, then I never get a Cnoteoff. I get Cnoteon, D#noteoff. If I get rid of the D# note, as well, then the Cnoteoff plays correctly, regardless of what’s going on in the drum track.
The drum notes are different than C and D#. This seems to happen regardless of page in the grid and what channel the monophonic part is playing on, and is independent of the device that it is playing. I may have never noticed this before because I usually start by programming a drum part.
Can someone try to recreate this? I’m 99% certain I’m on the latest non-beta OS.
Hmmm, happening the same across all pages, all channels. If the first note is shorter than the second, they both play. If the first note ends before the second one does, it plays the correct length, but stops the second note from sending a note on. If the first note ends after the second one, the first note never gets a note off message, and second note never gets a note on.
If I add another note in between them, that middle note will only send a note off message, but then the third note will play correctly.
Post edited by: adam, at: 2008/09/07 06:13
I’d like this too. Ideally what I’d like to be able to do is specify exact values that each row (1-9) represents when I’m looking at the MCC map. It seems the way things are set up that it’s very difficult to get a value close to zero sent without reducing the CC scaling factor way down.
The way things are set up right now, the numeric quadrant of the circle does nothing while you’re holding a button in rows 1-9 while looking at the MCC map. Could it be made such that if you hold a button in a particular row, you could then set a value in the numeric quadrant for all values set to that row to share?
Example: I hold any of the row one buttons and enter a 1 in the numeric quadrant. I then hold any of the for 9 buttons and enter 127. I’m not sure if you’d still want to enable map factor scaling in this mode, or have this function be an "absolute MCC map" that bypasses the map factor setting. Either one would work for me. I can then have the precise values that I want, and I don’t think I could achieve this otherwise, because the map factor would either scale down the 127 or scale up the 1. Unless I’m missing something…
(I’m going to cross-post this to new feature requests as well.)
Post edited by: adam, at: 2008/08/26 08:04
