Please ensure Javascript is enabled for purposes of website accessibility Jump to content
Line 6 Community
Welcome to the Line 6 forums!
Apply to Join our Public Beta Testing Program!
Limited Support of Legacy Products
ideascale Retirement

stuartbuchan

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

stuartbuchan's Achievements

Newbie

Newbie (1/14)

  • One Year In
  • First Post Rare
  • One Month Later
  • Conversation Starter Rare
  • Week One Done

Recent Badges

0

Reputation

  1. stuartbuchan
    I have a post up already about transferring SysEx files to/from my M13 but this is specifically about getting a CLEAN dump from the M13. I now know for sure that when I have a good, clean 16 messages of 157 bytes each, that I can successfully load that scene onto the M13. However, if I then do a dump of that same scene back to either my PC or MacBook Pro, that extra bytes are added the files gets corrupted. How can I ensure that when I transfer SysEx MIDI files as a manual dump that it is CLEAN? Has anybody had this same issue?
  2. stuartbuchan
    Here are screenshots from my MacBook Pro to show the difference in the two files. The highlighted areas are the message including the name of the scene P-Dub!
  3. stuartbuchan
    Update: I found a YouTube video (Line 6 M13 scene for worship) by Blake Fischer that has a downloadable SysEx file, which loads perfectly as a scene named "P-Dub!". So I now know 100%, that given a good file, my midi setup for loading back SysEx files works! However, when I export that same file from the M13 as a scene dump, to either my PC or new MacBook Pro, do a factory reset and then reload my saved SysEx file, nothing happens. The file seems to be corrupt. For the "P-Dub!" scene in SysEx Librarian, it shows the Manufacturer as "Line 6 (Fast For" and then it gets truncated with #.. showing 16. My saved file of the same scene shows up as Various in Manufacturer and 31 in #.. Does anyone have any idea what is causing this apparent MIDI output corruption and whether it can be resolved?
  4. stuartbuchan
    I have been struggling to get my saved SysEx scenes loaded back onto my M13. I've tried every method but so far, without success. My latest attempt was using a MIDI SysEx Transfer Utility (MSETU) from the Microsoft Store. It does a validation check and I received a message saying that it was invalid as F0 and F7 were mis-matched! MidiOx transfers the data, as I can see the data in the Monitor and the flashing screen 4. However, if this MSETU message is correct, then it won't update. Does anyone know what the SysEx is meant to be, v.v. F0/F7 messages matching? Also, are there SysEx files online that are downloadable, or can someone attach an example for me to try? Thanks in advance.
×
×
  • Create New...