Jump to content

hooshka

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hooshka

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    4
  1. I've got a FPP and I'm running the Vyzex Editor/Librarian software on a late 2009 MacBook Pro using an M-Audio MidiSport 2x2 MIDI interface. The FPP and the Vyzex software work fine with being able to change patches on the hardware from the software and move patches around using the software. But when I download an "l6t" file from the website and try to import it into my FPP via Vyzex, I get an error that says it cannot import the file. I read in the Vyzex manual that only FPP, PocketPOD and POD 2.0 l6t files can be opened on the FPP. How does one recognize these file types from the list of l6t files on the webpage? Any other help on being able to import l6t files into my FPP would be appreciated. The default factory patches are okay for a while, but now I'm ready to expand into some different sounds that others have created. I'm also looking for a patch for the FPP that creates a pad sound. Any ideas?
  2. I had a similar issue w/ the Vyzex Editor/Librarian but was using the MIDI port of my MOTU 8Pre audio interface. For some reason the MIDI interface on the MOTU stopped working. It took me a while to figure it out, but I had a M-Audio Midimann MidiSport 2x2 and attached to my MacBook Pro USB port and one of the two MIDI ports from it to my FPP....viola!! It worked fine when I fired up Vyzex. Be sure to attach the M-Audio MIDI interface to the computer first and make sure the MIDI settings with Mac OS recognize the M-Audio interface. It is these settings that allow Vyzex to know what MIDI interfaces are available on the computer. Then, from within the Mac OS MIDI Settings dialog screen, make the connections from the M-Audio to the FPP (you may need to create a new FPP instrument in the settings window). See image I've attached to this response. You might also need to reset the MIDI IN/OUT settings within Vyzex so they point to the "Floor POD Plus" as defined in the previous step of setting up the MIDI environment within the Mac OS. Good luck...
  3. I had some follow-up findings on this topic. I tried a completely different MIDI interface device (non-MOTU) with the Floor POD Plus and everything worked fine. So, the issue appears to be in the MOTU interface I'm attempting to use. Right now I'm a little baffled by the whole thing because I've been able to repeat the symptoms with a second MOTU interface of the same model. So, it appears to be an instability of the MOTU architecture within the Apple computing ethos. It works fine for months...and then...WHAM!!...relentless failures. Frustrating to be sure...any thoughts are appreciated.
  4. I have a late 2009 MacBook Pro model 5,3 running Mac OS 10.9.6 (Mavericks) and using the Firewire 400 interface with a MOTU 8Pre Audio Interface. The 8 Pre has a single MIDI port (IN/OUT) that I have been using to connect my Floor POD Plus to the laptop running the Vyzex Editor/Librarian. Everything was fine...I would start up Vyzex and the Floor POD Plus would be found and the download from it would commence and I could do all of the great things the editor facilitated. Then the power supply assembly of my MOTU interface quit working and the MOTU unit would not even turn on, much less process any audio or MIDI data. I replaced the power supply assembly and the MOTU seems to work fine - all the inputs and outputs work as before...except...now, when I fire up the Vyzex software, it does not find my Floor POD Plus. I've checked, changed, and verified over and over all the Mac OS Audio/MIDI settings. The OS is seeing and recognizing the MOTU interface MIDI port. I have other MIDI ports being used by other equipment and they seem to work fine in the Mac OS. The Vyzex software error messages tell me to reset the MIDI IN/OUT ports in the software, which I do and still get no recognition of the Floor POD Plus. I employed the MIDI Monitor feature of the Vyzex software and see MIDI data being broadcast by the Floor POD Plus when I move the volume pedal, press any foot switches, or turn any of the knobs. I got a stand-alone MIDI Monitor program and installed it on the computer, and again, I see MIDI traffic on the bus from the Floor POD Plus. So the Floor POD Plus MIDI OUT function seems to work, but the Vyzex software is not seeing it. I don't know if the Floor POD Plus MIDI IN is the problem such that it isn't seeing the interrogation message from Vyzex and doesn't know to respond to the message, or if it is something to do with the Vyzex software setup. Now, more often than not, the Vyzex software freezes because MIDI OUT data from the Floor POD Plus is swamping the software MIDI interface. This is driving me insane. I've reinstalled the MOTU Interface drivers. I've resinstalled the Vyzex software. I've changed out MIDI cables attaching the Floor POD Plus to the MOTU Interface. I don't know what else to try since it worked before the MOTU Interface power supply failed. Is there a way to completely reset the Floor POD Plus so that the MIDI IN/OUT port is reset to some factory default condition. Maybe there is a MIDI Buffer in the unit that needs to be cleared. Any ideas would be much appreciated.
×
×
  • Create New...