image description


Old FirePods: No MIDI in Windows 7 64bit (5.13 drivers)?
  Forum Index » Inspire, Firebox, FP10 (Firepod) 
Author
Message
MasterHouse
Prenoob

Joined: 08/08/2011 19:21:26
Messages: 3
Offline

Hi,

We have 2 old FirePods in our studio that worked in Windows XP no problems til 2 days ago .

After upgrading to Windows 7 64bit with the new 5.13 drivers we have the following situation:

- The 2 Firepods are installaded ok (blue led)

- Audio ok

- No MIDI ports are shown in Cubase or any software...

Do we have to upgrade firmware? There is no option for any upgrade at the control pannel

of the driver.

Thanks,

Amaury Machado
MasterHouse
Prenoob

Joined: 08/08/2011 19:21:26
Messages: 3
Offline

Hi,

Just adding information:

We have an spare Edirol UA-25, so I installed it.

Now we're using the MIDI ports of the Edirol and the

audio from the FirePods.

Still waiting for some help or solution.

Thanks,

Amaury Machado

This message was edited 1 time. Last update was at 09/08/2011 06:13:55

Monolithent
Supreme Baconator
[Avatar]
Joined: 28/07/2010 18:47:25
Messages: 13464
Location: Central New Jersey
Offline

I think you have to bump them up to FP10 to get them to work right on Win 7 but I'm really not certain.
http://support.presonus.com

Tallest guy in the Mod Squad with all his hair still on his head.

No I'm not a freaking pilot!! The Air Force won't let me have a suit with a zipper...or sometimes shoestrings.

My advice and suggestions should never be considered advice or suggestions. These are mostly insane ramblings of a poor aircraft mechanic who can, strangely enough, still hear.

StudioLive 16.4.2, AudioBox 1818VSL, AudioBox 44VSL, Faderport, Digimax FS,, M-Audio Firewire 410
--MultiBoot System--
Win Vista 64/XP Pro/7 x86/7 x64 - Mac OSX Snow Leopard/Lion
Gigabyte motherboard--SYBA TI Firewire XIO2200A--i7 2600k Quad Core--16 GB DDR III--Custom 2U Rackmount--4 TB Raid (all internal SATA II)--19" Samsung HDMI LCD on pivoting VESA 1U Mount
Studio One v1 Pro x64
Studio One v1 Artist
Studio One v2 Artist
[Yahoo!]
MasterHouse
Prenoob

Joined: 08/08/2011 19:21:26
Messages: 3
Offline

Hi, Monolithent

How to bump them up to FP10?

There's no firmware upgrade available...

Can you be more specific?

Thanks anyway.

Amaury Machado
jniff
Prenoob

Joined: 11/08/2011 07:05:55
Messages: 8
Offline

I am having almost the same problem. OS is Win7 Pro 64, and I'm using Sonar X1. Firewire port is on Intel MB and is supported TI chipset. The Firepod syncs fine, and audio plays and records without issue, however neither Sonar nor Windows recognizes the Firepod's Midi out. Any help would be greatly appreciated.
jniff
Prenoob

Joined: 11/08/2011 07:05:55
Messages: 8
Offline

I should add that I even tried reinstalling the driver after installing Sonar. Same problem as before in that the Midi Out is not recognized. If I connect to my WinXP PC, everything is fine, so it's not the unit.
cgad
Prenoob

Joined: 24/02/2012 23:16:08
Messages: 4
Offline

hi!

did somebody every find a solution? i have the same problem and i am super annoyed! the fp10 is really great and audio works but if this wont be fixed by presonus i will never go again with this company.

would be great if you could point me somewhere, i am pretty lost.

running it on win 7 ultimate 64bit on a HP workstation notebook 8710w

thanks in advance!
Trayj57
Prenoob
[Avatar]

Joined: 28/11/2012 22:40:20
Messages: 4
Location: Nashville TN
Offline

Did anyone get a fix for Win7 64 bit Firepod ? I have the same problem just got a new PC and can't get the midi port to show up and read midi with the Firepod.
Worked great with my XP PC...anyone from Presonus here have an answer please I have tried everything still not working.
This unit has worked great until now I would think someone here will have an answer?
Thanks Tony
www.tonyrayjones.com
[Email] [WWW]
jniff
Prenoob

Joined: 11/08/2011 07:05:55
Messages: 8
Offline

I'm not sure what your exact problem is or what exactly it was that I did to get it to work, but I'd email Presonus and ask for the latest driver. Install that. I also found that renaming your Firepod in the Presonus utility caused the midi ports not to show up. It's been over a year, but I think what worked for me was uninstalling (if you've already installed it - Presonus has instructions on how to manually uninstall, so as to remove all registry entries, etc.), and then re-install with the latest driver. I would not re-name the Firepod! Hope this works for you. I do know it caused me some headaches, but all is working well now (Win 7 64 and Sonar X2). Good luck!
Trayj57
Prenoob
[Avatar]

Joined: 28/11/2012 22:40:20
Messages: 4
Location: Nashville TN
Offline

Thanks for the reply my problem is I did install the new drivers from the website onto my win7 PC I didnt install the old ones from the CD.
Audio works fine..just can't get the midi to show up at all to connect.
As far as renaming it...not sure what you mean here's the name always been that.
Midi is the only problem Im having with it.
Thanks Tony
FP.jpg
[Thumb - FP.jpg]
 Description [Disk] Download
 Filesize 118 Kbytes
 Downloaded:  279 time(s)

[Email] [WWW]
jniff
Prenoob

Joined: 11/08/2011 07:05:55
Messages: 8
Offline

Looking at your screenshot, I see your Firepod has been re-named Tony's Firepod, and that you have 'Include device name in ASIO' checked. Originally, I installed the driver, and then renamed my firepod (originally something like 000C407) to John's Firepod and checked the ASIO box. Everything worked fine, except - like you - no MIDI. I tried multiple things, to no avail. What I finally tried - and what solved the problem was this. I uninstalled everything Firepod related, and then reinstalled the driver. This time I did not rename the device or check the ASIO box. Everything worked fine, and the MIDI showed up. It's been over a year now, and I've had zero problems. I've assumed, but never renamed to verify, that renaming the device and checking the ASIO box somehow prevents Windows 7 from seeing the MIDI ports, and thus your DAW, etc. from seeing them, as well. Like you, I was previously running XP, and had renamed the device without problem in XP.

Here's some instructions I used. It involves editing your registry, but should completely uninstall the device and allow you to re-install with its original name. (I think if you use only the add/remove programs, it might reinstall with your re-named name). If this works, let me know, as it would lend evidence to my theory. Good luck!

Below are the instructions PreSonus sent me for a Firestudio I had. I can't remember exactly what steps I followed, but I made sure to check that if any of these registry items, files, etc. were present, that I deleted them. You may want to uninstall the firepod drivers with add/remove programs, restart, and then delete any of the files/registry items still existing, restart, and then reinstall the device and don't rename it. ----

*Be aware that these steps may not remove everything associated with the application and can impact other applications on the computer. Have a backup or restore point and use caution*

• First, connect the unit, then go to Start>>Right click on Computer>>Select Properties>>Select Device Manager in the left column>>Go to Sound, Video and Game controllers. Find the PreSonus device, right click on it and uninstall.

• Next, go to Start>>Control Panel>>Go to Programs and Features, find the drivers (your device and/or Universal Control) and remove.

• Next go to Start>>Computer>>Local Disk (C>>Program Files>>PreSonus and delete the device folder and/or the Universal Control folder. (It’s okay if it’s not there.)

RESTART YOUR COMPUTER***

Now we need to edit the system registry. First, disconnect your interface. (For the instructions below, "Go to" means click on the "+" sign next to the indicated file to expand its contents. You will only be working in the left-side window of the Registry Editor, please ignore the right window completely.)

• Go to Start. Type Run>>Type in regedit and click enter>>Go to H_KEY_LOCAL MACHINE>>System>>Current Control Set>>Enum>>1394>>right click and delete the PreSonus key. If it gives you an error, then right click again, select permissions, select Allow for Full Control. Click ok. Right click on the file again and delete.

• Next go to H_KEY_LOCAL_MACHINE>>Software>>PreSonus>>right click and delete the Devices folder.

• Next go to H_KEY_CURRENT_USER>>Software>>PreSonus folder. If you see a folder with your device name, right click and delete it.

• To remove the application entry from Add/Remove Programs (if present), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall>>PreSonus and right click and delete the device folder in the title and/or Universal Control folder.

• Some applications have Services attached to them. If this is the case, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services, locate and delete the service.

Exit the registry editor.

guitartoys
Prenoob

Joined: 10/12/2011 19:16:50
Messages: 20
Location: McLean, Virginia USA
Offline

Wow, ran into the same issue today.

I could not for the life of me get permissions to delete the keys in the registry for the 1394 devices.

How I ended up making it work was to erase the name that I gave the unit (yup, I got creative, and gave it a name). Then saved it with a blank name.

Then uninstalled and reinstalled and now it works.

I'm not going to mess with it any more.

M
eVGA SR-2 M/B, Dual Xeon X5690 Hex cores, 12GB RAM, LSI 8 Channel RAID controller, 4 Vertex 3 SSD in RAID 0, Four 2TB WD Blacks in RAID 5, Plextor Blu-Ray, Dual GTX580 in SLI, with Three ASUS 3-D 23" displays. All water cooled. Presonus Studio Live 16.4.2 and FirePod, NI Komplete Audio 6, M-Audio Xponent. CMC Transport, iPad with AC-7, V-Control Pro, Lemur, M-Audio BX-8 and KRK Rokit 10 sub
 
Forum Index » Inspire, Firebox, FP10 (Firepod)
Go to: