Midi import and recording goes wrong

[mstsfreak]

OS1.24:
Very strange: I always imported midi-sequences made in Cubase and so far it went well. But yesterday the following happened:



Look at measure 26: G#1 84 has notelength 000.000, the next note also. So this note is not hearable. (what a word )
Importing the same midifile in cubase gives notelenghts of 003.000.

Ok, so i edited one of the notes:



Now Fusion plays it as it is supposed to be.
I saved the song:



After saving i got this:



Look at the same note: it returns to being 000.000 again, while on the bottom right side it shows 003.000. It plays 000.000, no note....



Also, in the Trk view editor i can't select the 000.000-notes to edit them.

I discovered excactly the same bug when changing the .MID file to .AFN.

I think it has to do with loading the midi-file into the memory of the Fusion.
Here goes something wrong, because Cubase loads it well.
So i think we have a bug here.

This way the sequencer becomes very inpredictable and very much unusable. If it isn't a bug, then why does Cubase load and play this midi-file as it is supposed to be and the Fusion not?

Also recording directly from Cubase to the Fusion goes wrong. A lot of notes are being recorded with some "latency" and shift in time. Some notes are at for example 026.020 instead of 026.000, or at 030.020 instead of 030.000. There still are timing issues here.

I really hope Alesis will "overhaul" the sequencer and give it a big revision, because it is not usable this way.

Don't get me wrong and i don't want to be negative, because i like this machine a lot, just see it as information for the bugfixers.

EDIT: Is there someway of sending this information to the engineers at Alesis?? It could be usefull to them...

[stuart]

Excellent write up of the problem Mstsfreak, and certainly something the developers could work from if it could be passed to them somehow.

I only started messing around with MIDI import last night, and found several problem after importing a midi file, from the Fusion looking like it was slowing down significantly to the point of almost hanging, to a full blown System crash displaying the reboot required screen. All of the MIDI files that cause the problems load fine in Cubase.

Seems there are still some issues around the import in the latest OS.

Edit: I've searched the forums, and the manual without luck. Could you let me know how did you manage to capture the LCD screen shots, or point me to where it is detailed? Cheers.

[Hollow Sun]

mstsfreak said:

After saving i got this:



Look at the same note: it returns to being 000.000 again, while on the bottom right side it shows 003.000. It plays 000.000, no note....

Ok - guessing here.....

You have two identical notes (D#2) at 026.01.000 and one of them is set to 000.000 so you have two conficting events there - one saying 'Play D#2 at 77 for 000.000' and another saying 'At the exact some time, play the same note at a lower velocity of 14 for 003.196".

Now ... I know this doesn't have any relevance to the G#1 note but PERHAPS deleting that D#2 event of 000.000 will sort it .... two (invalid?) 000.000 events at exactly the same time of which one (D#2) is redundant.

I agree that there are some issues to look at in the sequencer such as this. As you say: "I always imported midi-sequences made in Cubase and so far it went well" and I think in this case, you may have hit on of its 'gremlins'.

I am trying to put myself in the place of the processor here and I am being asked to play two invalid note lengths at exactly the same time. Even if one is fixed (as you did), there's still a shitty event in there.

I dunno - I am guessing. Give it a go - delete that 000.000 D#2 event and see what happens.

FWIW, there is very little that the Fusion engineers aren't aware of with regard to Fusion and they DO monitor the various forums, etc. (which is why the endless whingeing elsewhere is kinda pointless!). Yours in an excellent breakdown of your problem and I am almost certain it will be helpful to them to iron out the issue.

Let us know how you get on with my suggestion.

That'll keep you busy on Christmas day!!!


Steve

[mstsfreak]

stuart said:

Edit: I've searched the forums, and the manual without luck. Could you let me know how did you manage to capture the LCD screen shots, or point me to where it is detailed? Cheers.

Hit assign + T4 together and a bmp will be written to your CF-card.

[mstsfreak]

I have tested it and deleted the 000.000 notes. Now it playes well.
They are indeed doubles and i now know why: I merged some tracks in cubase and that way created some double notes and some notes which are not there in cubase. Fusion makes up some notes. ( i don't know why) see screenshot:



Note D#2 87 does not exist in Cubase.
When i delete the 000.000 notes also this note disappears.
In cubase there is a function called: "delete doubles". I used this function and indeed cubase deleted the double notes.
When i now export to midi-file and load this file into the Fusion all goes well without any problem.
I also discovered that when loading a midifile with doubles, navigating through the TRK event screen went very slowly, now that problem also has gone away.

So always delete your double notes when exporting to midifile!!


You see, this way we keep on learning and learning to understand how Fusion works!! and MIDI.

Maybe the recording problem with shifting notes in time has also to do with doubles. I'll try that another time.

[ajmuso]

Excellent post one and all,
I have seen this a few times, and never really bothered to try and correct or investigate it.... you just saved me a lot of time!!!
just what this forum is all about!!!


cheers

Andy

[mstsfreak]

ajmuso said:

Excellent post one and all,
I have seen this a few times, and never really bothered to try and correct or investigate it.... you just saved me a lot of time!!!
just what this forum is all about!!!


cheers

Andy

Well, thank you!!