Oszillo

Stuck notes is a very common task for any machine which is able to handle midi without timestamps (classic).
Why? Because midi protocol is without timestamps by standard. So the note-off msgs are independent send informations. If there are missing ticks (one of the scenarios) or missing note-offs the machines assume the note-off msg will follow. Missing ticks lets the machine wait to go on, even if this sounds like stop cause it doesnt play anymore. The note has to stay open unless a stop or note-off or a tick that tells the notes timeout will arrive and so the machine would know what to do. This is why ALL NOTE OFF (cc0x7b=cc123), active sensing and other methods of the midi protocol exist. To come around those problems.

Unfortunately the deluge also misses sometime note-offs if Song Position Pointers arrive, it will set the playhead position and ignore that it triggered notes already that have to be closed.

In example Ableton sends cc123 before you start & after you stop to tell the machines to close all open notes.

As far i have seen the xml data of the notes from deluge carry their length with them. Meaning the deluge is able to know when to stop notes stored once a note is read. But this is as described not the case when notes arrive via DIN-Midi. Via USB-Midi it would be technically possible to transport length informations with the note-on events with no guarantee the sender is delivering via a timestamped system, so USB-Midi has to behave same as DIN-MIDI is handled first.

ps: there are machines that never send note-off by default. like Roland's Tr-8xx

Hope Rohan finds on some rainy day time to look into this and his outcome would make SPP so stable to be able to use it without midi stop/continue to apply on the next available beat (even if a lot midi specs say applying SPP is commonly used on stopped machines - the SPP number is dependent on quarter notes for reasons)

just throwing that in here..
While being a little bored in lockdown in January I deciphered the Octatrack data format bit by bit.
So since a couple of Months being able to read and write Octatrack sets.
Made an App out of it for Mac to export and import Midi or write complete Ableton v10, v11 Sets from the Octatracks patterns and parameters and project settings.
Meaning i also developed an Ableton Export environment that could be used to do the same with Deluge Data, that way you would be able to create Ableton Songs with your Deluge songs. And in case it runs smooth it would not be limited to just 8 Octa-Tracks.

So already in Alpha phase forcing to go Beta the next weeks.
It has a full Midi implementation and can act as Audio App in the middle between machine and any DAW or running standalone.
Playing, Recording and checking Samples in a AIFF, WAV, m4a, aac and working on flac, caf and maybe rex/rx2 support also.

So why i am posting this here?
After reading some comments in here that i am not the only one being Deluge'ist and Octatrack'ist thinking to do similar export or import options for Deluge Format. Because now it would be possible to transform 8 tracks Audio and 8 tracks Midi into Deluge XML format or the other way around.

Well this is a lot of work even tho it is not that much of a problem like the decoding of the OT was..
To organise further work schedule and having a proper coding plan for the next weeks I would like to know how much interest is in the Deluge Community to have such export/import options..

And knowing the limitations and possibilities of both machines and how they actually accompany each other I am still keen to know more of other Deluge owners having also an OT in their environment and the struggles they have to catch the most out of both..

PS: here a screenshot of the app state the moment.

Currently involved in porting research. Maybe i can make it work in windows and/or Linux as well (no promises yet).
But i can list some features and frameworks i developed and are included already which need to be ported as well.

• midi interface with clock (any but logic) and mtc (logic pro) and nrpn (dave smith/mackie)
• virtual midi port to send to other apps and receive from them
• 64 step sequencer including visual feedback
• ableton link with specialised framework
• ableton export including automation (i think i am the only one who dev a whole extra framework for just that)
• open sound control (fast udp OSC) interface for multiple congruent senders and receivers including value visualiser. (almost like Osculator)
• midi mapping per device with autoload when connected again.
• osc mapping per port/ip and generalised if needed just same as the midi mapper.
• audio recorder, waveview and reader and writer for mp4, wav, aiff, aac, (no mp3)
• the display, yes actually the fastes possible UI element based on trasilions of font particles.
• extra ableton push1 & push2 framework which allows to display screen separated
• sample manager + drag and drop
• sample preview and exchange model
• note trigger exchanger (because on OT sample slots are not dynamic, so resorting is a heavy action)
• project settings editor
• tempo editor
• midi export
• preset manager
• saving

changes in mind..
VST3, AUv3 - hosting
multi document editing

and as you see in the screenshot above the drop down menu in the window header, it could switch to other machines as well that way converting from one to another. Which first hand is at least some interface that would allow to control conversions despite it needs to be coded of course and UI elements need to look accordingly to make it as easy as f**k..

Well, at least thankful some did discover my beep.
So thanks for the feedback so far..

cheers

the invitation i anounched here is erased cause of weirdo mailing i got..

@rudolphrapid said:
I'm not sure automating/modulation sample start and end points can be done with samples read from SD card. Even Octatrack states that such feature is unstable with its Static machine.

Its actually possible with the Octatrack but only for partial wavs in the RAM via SL parameters(tracks page2) not gigabyte wise shuffled stuff from the Card and not as a free sample sized point - only in fixed partials of the whole sample size.
For the Deluge start-point shifting up to the end/loop-cycle point is a matter of sample block-size handling in memory in combination with the stretch algo. But would be a big thing even without reapplied stretching algo. When you can do it by hand, you could do it with code also.

Firmware 3.05
while the machine is playing it works just fine
but when i stop the machine doesnt work properly anymore.
stacking scrolling,
glitches at beginning and ending of the play mode.
sometime endless glitchy loops..

@rohan should i send you my song files? or is this a known bug..