Old Motifator threads are available in the Archive.
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
I used Studio One for ease of sequencing my midi data. I export to midi(.mid) and I get a 175kb midi file which I save to my flash drive. When I transfer the flash drive to the Motif XF the XF sees two midi files with similar names; 1 is 170kb and the other is 5kb. If I tried to load the smaller one the XF says “No Data”, if I try to load the bigger one the XF stays in the “Now Loading” screen for ever and non responsive. The only thin I can do at this point is power off and back on. Anybody having a similar issue and knows how to solve it? |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
Just FYI I tried the same thing with Logic Pro X and the same thing happened. |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
What happens if you unzip and load this? |
DavePolich
Total Posts: 6820
Joined 07-27-2002 status: Guru |
Make sure you have taken care of these items: 1. Export your file as a Standard MIDI File Type “0” (one track contains all the data), with a “.MID” in the name (as in “My Song.MID")...IF you are exporting it to the XF. If you are trying to open it in Logic (don’t know why you would, since you already have Studio One), then it should be saved as a Standard MIDI File type “1” (separate tracks).
2. You should have a pre-programmed Song Mix set up on your XF with the
3. When loading the SMF (.mid) file, choose the larger one. I think you may be on a Mac because that 5kb file is what shows up on your USB stick if you loaded the file from a Mac. It’s a Mac thing, the 5KB file is a “phantom” file which shows up falsely when the USB drive is inserted into your XF and the FILE screen is called up. 4. Load the SMF to the song location where you made the mix template for your sequence. |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
This is the exact same process I have done. The XF freezes while loading the midi file. |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
I’ll try to help you once more… What happens when you load my file? |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
I had to take my XF on the road and haven’t had a chance to try this. I will set it up again today and try it. |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
I loaded your file without a problem. It took about 1 second. I have a feeling the problem is caused by the format that the DAW is outputting the file in.
In Studio one I only have two options:
I assumed . mid would be the appropriate but neither have worked for me. It appears there are not as many options for exporting midi in Studio One as their is with Cubase. |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
OK, well that at least clears the Motif side of this. If you’d like to post a zipped .MID exported from Studio One, maybe we can determine why it’s not compatible. It doesn’t have to be anything special, just one that doesn’t seem to load to your XF. |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
Find attached one of the Studio One exported midi files that failed. File Attachments
Test.mid.zip (File Size: 80KB - Downloads: 172) |
DavePolich
Total Posts: 6820
Joined 07-27-2002 status: Guru |
Thanks for posting the file. The cause of your problem is exactly what I
Type “1” = all Midi data on separate tracks.
The XF cannot load or read a Type “1” SMF. Your file must be saved as a
I was able to open your file in Digital Performer 8, and could see right
|
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
Thanks for the check. That’s what I was thinking. Sadly the only options I could find is to save as .mid or .midi. I need to do some more research with the Software. Thanks again. |
5pinDIN
Total Posts: 11891
Joined 09-16-2010 status: Legend |
It’s true that the file you posted is a Type 1. It’s also true that the Motifs will only save as Type 0, but they’ll load either Type 0 or Type 1. I’ve loaded Type 1 to my XS and XF without problem many times. As a test, I converted the file that I previously linked to. It’s now a Type 1, zipped and attached. You should have no trouble loading it. I’m not sure what the problem is with what Studio One exports, but there’s something other than Type that’s an issue. File Attachments
Xs'd Up PC2 Type1.zip (File Size: 20KB - Downloads: 169) |
energizer1389@gmail.com
Total Posts: 54
Joined 05-09-2013 status: Experienced |
Yes and Yes. The file you changed to Type 1 loaded without a problem. I Solved my issues with Logic Pro X and successfully exported as midi type 1 and imported to the XF without a problem. So apparently there is some issue with Studio One. I will try to find out how to solve the issue just because I hate to leave stuff unresolved but honestly Im going forward with Logic Pro since I finally have it functioning well and properly synced to my XF. Thanks to 5pinDIN and DavePolich for your help. This was a headache at first but it was worth it. I learned how to properly transfer songs between DAWs and my XF and also figured out how to record all midi in real time from one to the other by syncing properly. I already had learned about Mixing and Templates so I’m gooood! |
Bad_Mister
Total Posts: 36620
Joined 07-30-2002 status: Moderator |
There’s that incorrect information again. 5PinDIN has it correct. The Motif XF can load either Type 0 or Type 1, it saves only Type 0. To understand this....
It is far too simplistic to say that Type 1 is separate tracks, and Type 0 is one track (sic). That’s actually wrong.
Type 1 as an example, you could have 3 different multi-timbral tone engines, each with there own 16 channels, such that you could direct a certain MIDI channel 1 track to just tone engine A, while a separate MIDI channel 1 could be routed to tone engine B, and yet a third MIDI channel 1 could be routed to tone engine 3. In a DAW you can understand how you may be routing tracks via different ports to different tone engines. Multiple track but each track has 16 MIDI channels. Used in a system that has multiple Ports. Type 0 in this same situation would output all data designated channel 1 together to a single channel 1 destination. All data designated channel 2 together to a single channel 2 destination… And so on. An example where a TYPE 1 setup is great would be if you multiple devices each being addressed in a discreet way. A system with different simultaneous ports is an example of a TYPE 1 file. It would translate to a Motif XF, if all channel 1 data is set to play from just one, not multiple, devices. So you can see how a Type 1 includes the situation that describes a Type 0… when it makes sense for a single 16-Part Multi-timbral tone engine. An example where a TYPE 0 setup is great would be if your device has one set of 16 MIDI channels ( like your Motif XF) obviously you can have more than one track. And this is why Type 0 is the universal donor ... Like Type “O” blood, a Type 0 MIDI file can be read by all MIDI systems… With a basic 16 channel capability. By the way, a MIDI “track” is mainly for convenience when editing data. A MIDI note-on event actually includes the MIDI channel. You can choose to look at all data on separate tracks, but MIDI data in a single port system is 16 channels of data. A single stream would be a better way to think about it. And yes, as you can see ... A Motif XF can load a TYPE 1 Standard MIDI File or a Type 0 Now to be completely clear, you can have a situation on your Motif XF where you have several separate tracks that are assigned to MIDI channel 1. Here’s what I mean:
You are working out a stride piano piece. You might set Track 1 of the XF to record the right hand.
You then set track 2 to playback on MIDI channel 1 because the left hand part can use the same piano Voice. This is done from the main sequencer screen, press [F3] TRACK, [SF1] OUT here you can set the transmit Out channel of each of the sixteen Tracks. Set slot 2 = channel 1. Both are on separate tracks in your XF. But when you save (export) this as a Type 0 file these two items will be placed together… Loading back a Type 0 file will place the right hand and left data together - that’s what type 0 does, all data assigned a channel are output together. That TYPE 0 SMF will load back in merging these two separate tracks together. Make sense? Sorry, if they taught MIDI in schools probably this would be common knowledge. But I run into people who have been using MIDI for all thirty years who get this one mixed up. And if you work for Yamaha you have to live with the false statement that the XF doesn’t load Type 1 cropping up, from time to time.
I’ve even heard people say type 1 is “professional” and type 0 is “entry level”. Yikes! How silly does that sound.
But if your goal is distribute a MIDI file to the most people, how professional would you be if you used a proprietary layout or personal layout for your file? Not very. Using Type 0 would be a smart way to distribute a MIDI song file so that the most people could load and use it. It’s not that it just professional, it’s smart. “On 1 Track” (sic)… How many tracks are there on the Motif XF? |
DavePolich
Total Posts: 6820
Joined 07-27-2002 status: Guru |
My bad. I was mistaken in thinking that the XF could only load type 0 MIDI files. That’s
Apparently the problem is how the OP’s .mid file was saved from Studio One. |