because of some setting that is misread by the DAW, it starts generating digital noise - crackling.
This leads to system calls from the DAW and this leads to overloading.
But it turns out to be very difficult to open and edit the MIDI files to see what that setting is, but I think if Samplitude can output a Text Document with the Notes from that MIDI file there will only be notes and then can Audacity that Text Document with NOTI to create a MIDI file ?
If this is possible, maybe only the Midi notes will remain without the other settings in the current Midi file and the problem will disappear. There will be no such overload.
Is it possible in Audacity to export Notes to a text document from a MIDI file and vice versa Notes to a Midi file?
If it is not possible now it will be very good to do it because it is a problem with many Midi files and an even bigger problem with what to open and fix.
The closest that Audacity gets to that is that you can export Note tracks (MIDI) as .GRO files.
.GRO files are “Allegro Music Representation Language” files, which is a text based format. The format specification is here: Allegro Music Representation Language
Hello, I see that it exports the MIDI file as a .gro file, which can read the content more clearly.
In fact, is it possible to edit such errors in the MIDI file that lead to confusion in the DAW?
And also if I send you such a file to look at, can you tell what is causing the confusion?
Something pointless or wrong there?
Would you be able to take a look and send it back to me as a .gro file with the text highlighted that needs to be fixed or removed? If you understand what is not right there
That way I’ll know who it is and fix all the other MIDI files.
This will help others in the future when they open the thread
This topic was automatically closed after 30 days. New replies are no longer allowed.