Forum Replies Created
-
Posts
-
You can pause/play individual tracks (way cool). In Page mode, grab the track (hold down the SEL button associated with the track) and press the Pause button.
The Shaltwerk maybe sends a MIDI song position 0 message to indicate the start-of-song situation. The Octo doesn’t do that. It does send a MIDI clock stop message though.
Could you find out in the Shaltwerk specs what it transmits in that particular situation?
gseher wrote:
Quote:Robert, your proposed method is definitely worth investigating, especially in the light of parallel discussions we had about the way the main player loop works now.Hi Gabriel, yes, I had the same thought. It could be a good time to combine both projects, if possible.
ripe wrote:
Quote:I believe you can do this by selecting all tracks and reducing the STA factor to zero.And clearing the STA map of each track is the more destructive approach.
gseher wrote:
Quote:Well, increasing the resolution of the sequencer could be achieved in at least two ways I can think of now, but one of them (the more promising one) is something I would really need to build a experiment for. The other one bases on the current model and seems very CPU heavy, but still worth validating.What needs to be rewritten in the way the sequencer events are generated and put into the sequencer queue, and the way the sequencer queue is then played back.
There is a component of latency that I need to investigate an experiment. The OS values in the specs are good, but I need to see it running, and hear it play. Realistically, that looks more like a summer project rather than a quick fix.Picking up some missed threads here. Stupid forum software silently logs me out after some time and I think nothing’s happening.
Anyway, I think I’d prefer to tackle the resolution problem with timestamping the outgoing midi events in a sorted queue, and have a high reso timer walk down the list to see what has to go out.
The sequencer code can then run at a much lower reso as long at it manages to correctly timestamp the midi data it queues.
Fun project! Definitelty not a quicky.
Sounds like a good plan! If the knob isn’t doing anything, why not? Maybe mr. Big G. had other plans?
Thanks for the feedback so far, guys.
The rechannel feature is high on the list, to it seems. That will be one of the first things I’ll do. I’m already feeling more at home in the sources.
Hey Arnaud,
as far as I know, the only difference between the legacy and newClassic model is the finish of the wood. On the newClassic model the wood has a piano black finish. The rest (panel, electronics, software) is exactly the same.
Ah yes, I remember the Super Align discussion. I’ll look it up and will probably put it on the list.
Okay guys, I have it working. I managed to compile the v1.42 octopus.elf file with the exact same file size as the official one.
I’m using the binary GNU toolkit provided by Gabriel, and the Octopus version of the eCos libs and include files.
The original eCos v2 distro is not used as far as I see. If that’s correct, there’s no need to bother with the eCos install script, unless you need the GNU toolset of course.
Thanks for the tip Ripe. A VM running linux is a good idea. If no one managed to run the tools natively on the Mac I guess that’s the way to go.
ripe wrote:
Quote:I would wish for the converse function then, "make legato"!What about using a double click instead of a single click in the matrix while setting the length of a grabbed step?
