Forum Replies Created
-
AuthorPosts
-
MikeParticipant
It would only allow one cluster per bank (as it is now).
cheers
ripeMikeParticipantMy original request for arbitrary clusters was for an implementation similar to the current, just removing the side-by-side restriction. I don’t know how desirable it would be to have completely arbitrary clusters across banks, etc!
Here was my diagram regarding a possible implementation of clustering:
cheers
ripePost edited by: ripe, at: 2008/05/16 20:22
MikeParticipantI think when I spoke to Gabriel about it (arbitrary clusters), he mentioned it would be a fundamental change to the way clusters work and would require some sizable effort.
I agree on the point about zero page length and a race condition… that wouldn’t be good!
cheers
ripeMikeParticipantThis a short loop I made (sequenced on the Octopus). It is really a demo to show the sound of the Virus TI I just purchased, so not a completed song.
cheers
ripeMikeParticipantah, yes, that would be it. This feature was only just included in the 1.42 update.
cheers
ripeMikeParticipantIt seems to be working for me… You are holding the relevant selector in order to perform the additional paste operations, correct?
By the way, I love this feature!
Thanks
ripeMikeParticipantI can see a nice use for sending MMC as well.
The octopus *doesn’t* send MTC currently, it sends MIDI clock, along with MIDI start and stop.
MTC is a time based protocol, while MIDI clock is tempo based.
With MMC you can control the transport on a sequencer or multitracker, which could still be acting as the MIDI clock master.
We would need to be able to designate whether the Octopus is MMC master or slave.
cheers
ripeMikeParticipantFor me, it means I could use a foot controller (via MIDI) to enable/disable recording, which frees up my hands to perform correctly when punching in.
The track arming is less important for me, but it should be trivial if adding the other functionality at the same time.
cheers
ripeMikeParticipantYes I suppose I see the logic in that, for the single button operations it would make more sense.
I have been more in the habit of saving the entire machine state when I get to a milestone, to safeguard against the occasional crash, rather than protecting from user error, which UNDO would be handy for.
cheers
ripeMikeParticipantI am a bit unclear on what exactly would be possible to "undo"? Only a single button push, or something more structured?
For example, if I rotate a knob (POS) to change track timing by 8 steps, would UNDO only move the track steps back by one knob click? If I change a track base note three times to find the correct note, would it only undo the last selection?
I guess I don’t understand what undo is for that makes it better than the current PLAY implementation?
Granted I almost never wish for an undo function, or use the PLAY mode either.
cheers
ripeMikeParticipantI do something similar to most.
I have a Yamaha AW4416 feeding clock to the Octopus, which has a controller merged on one input.
Then I have one Octo output dedicated to an RS7000, and the other feeding the rest of the studio, MachineDrum, monomachine, etc, etc.
I build all songs on the Octo (still wishing for arbitrary clustering!). So there isn’t a computer involved! Most of the time I have sub sequences running on the Elektron boxes because of the parameter locks they can do.
I have a MIDI switchbox to change the routing of the controller because I don’t need it inputting to the Octo all the time (MIDI echo would take care of this!).
cheers
ripeMikeParticipantYup, I have just removed them.. Don’t want to tarnish any reputations for the best Step sequencers in the world
cheers
ripeMikeParticipantI posted a video of the step toggling problem as well, again it looks like it’s just the same issue with the note being incorrectly recorded. When the track is CLRed it goes away.
Link:realtime record 2
I can’t capture the crash on video, it happens fairly randomly.
cheers
ripeMikeParticipantI think it is just an extension of this bug. After it happens, you can no longer activate/deactivate the first step in the second chained track. If you push step 1 in the second track, it activates the first step in the first track. I usually clear a track by toggling steps individually (when working on a specific sequence)
I tried actually clearing the track (with CLR mutator) and it did eliminate the bad step. So I guess it is not permanently damaged.
You said it would take some considerable work to fix this bug though right?
Thanks!
MikeParticipantI posted a video of the bug happening a couple of times. You have to record a note right at the transition of the tracks. In the video you see that the step for the wrong track is activated, but the sound is in the correct place.
here is the vid:
Link: realtime record bugIncidentally after recording the video, the octopus froze/crashed and I had to restart.
cheers
ripe -
AuthorPosts