Drag & drop midi problem issue

If you drag & drop midi to a renoise track it creates a new pattern and a track and also a new instrument. So you have to move the pattern and swap the instrument number to the right one.

So… how could you import midi directly to the correct instrument number and in the track that you are draggin to?

Thank you,
Carles.

same.
This is a problem when using plug-ins that generate MIDI clips, such as Scaler 3 or Melody Sauce.
Does anyone have a solution?

Firstly…This is a funny situation…

Secondly,you will have help…Be patient

So the only way is to develop tools.
Do you think that is technically possible?

(I’ve again responded to fast)

You use a tool to create something which should be done by human…

Side effect

Maybe using 2 renoise sessions could be more convenient

You can copy-paste between sessions

It would be interesting to see how to hijack this situation.

1 Like


Could work.

There is no doubt about that, but the complexity of midi re how to fit it into current track tempo and lpb could be a nightmare.

The first good point is that Renoise assign the same instrument name for all midi import…With a bold font for all import point…A marker for each import

what even does that mean?
do you have a screenshot to further explain this?

image

2x (3x tracks) import

No bold😅(Strange)
But the name will help


The name of the tracks can help also

A tool with a simple box which ask “how many tracks per import?” will do the work…A divider

“Consolidate MIDI imports”

All the imports made after the first will have the instruments number of the first

Track merge in a serial manner

Unfortunately, the current MIDI import is completely unusable for any serious work. I still can’t understand the strange logic behind how it was implemented from the very beginning — it just doesn’t make sense. There are plenty of successful examples out there that actually support and inspire creativity. Here, the function technically exists, but it’s so poorly executed that I simply can’t use it. Every import turns into a tedious routine: reassigning channels manually, fixing things one by one — it all wastes a huge amount of time. I really believe it shouldn’t be this way.

1 Like

Some experimented Renoise LUA coders could verify that…feasable or not
They know the LUA API

Cud u send me a multichannel midi as an example file attachment over Discord or over here?

there are several bottlenecks there that if fixed will fix this problem. if you try to drag a midi script from sonic charge microtonic you will clearly understand what I mean

i don’t have sonic charge microtonic - can you drag a midi out of that for me?

1 Like

Edit:
Sry this is patches for microtonic, not midi files

Microtonic midi import.xrns (32.4 KB)


2 first import are the same pattern (chained patterns)



2 next are the same (not chained)



Shorter MIDI files than Renoise patterns can be a problem


EM Easy Listening (100) A-C (chained).mid (1.4 KB)
SC Lemon Track (155) A (not chained).mid (381 Bytes)