Hello! Is there any way to remove unwanted silence from 1500 midi files. Im making a midi pack and when im exporting from logic the silence in the beginning also gets exported. Would be so happy for answers because this is stressing me out! Thanks a lot!
Okay, I understand! Do you know any other way to do it? Otherwise, how long would that take to add? I have a deadline by this weekend and would need to remove the silence from all 1500 files. It would literally take sooo many hours to do myself. I understand you might not work that way, but it would help so so much!
You may find some unusual problems when playing from the first note with quite a few keyboards. Although you can’t HEAR anything, that doesn’t mean nothing is going on! If sysex is being used to set things up for the sequence, starting from the first note skips it, and you may hear considerable differences in the sequence if it isn’t ‘played’.
If the sysex is simply a GM/GS reset, perhaps not, but if the sysex does anything more complex it can make a huge difference. I would advise you to listen carefully to each sequence rather than do a batch convert unless you know for SURE that there’s no sysex.
Modern MIDI modules use sysex for a lot of things, from setting up effects processors for specific sounds, to micro editing drum kits. Make sure you aren’t losing out on that stuff!
If you are using VSTI’s in Logic, it will depend a lot on whether the virtual instrument is set up by the DAW for that particular song, or whether you need to send codes to it to adjust things.
BTW, Bruno, if you are watching this, some keyboards get around this problem by pre-sending the sysex as soon as the SMF is selected, and then starting from the first note when the user hits ‘Start’. This might work for QMIDI... If all the data PRIOR to the first note is sent out before the Start command on selection of the file (not just sysex but also any CC32/00, PC and controller codes) then the user ought to be able to press Start without any unexpected consequences.