Hey everybody, first time poster here...
I've got the EXB-FW on my M3 and I'm attempting to use it with Vista x64. I've had VERY limited success with this. I've downloaded the FW 1.10 drivers and tried everything I can think of to get the audio working for the M3 Plugin/Editor, but to no avail. I've tried countless combinations of stream buffer depth and ASIO buffer depth but I can't get the Streaming State to show as running for the life of me (aside from one time, which was short lived). There seems to be no rhyme or reason as to why it's not working, it's just not.
All of my other clocks are set at 48khz, and the KORG logo in the M3 Editor is indeed glowing orange (the color for FW connectivity).
Any help would be EXTREMELY appreciated.
EXB-FW Streaming State Error
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
- Rob Sherratt
- Platinum Member
- Posts: 4590
- Joined: Mon Apr 16, 2007 1:49 pm
Well, I did a little looking around and it does appear that there are x64 drivers included in the installer and they are apparently installed on my computer. Would these be XP x64 compatible only?
Edit: Sorry for the double post.
I've resolved my issue (for now). I wiped the drivers from my computer and rebooted. I then did a clean install of the FW drivers and it seems to be working correctly.
Edit: Sorry for the double post.
I've resolved my issue (for now). I wiped the drivers from my computer and rebooted. I then did a clean install of the FW drivers and it seems to be working correctly.
Problems similar to yours with Vista 64
I took your your suggestion and removed the FW driver and then rebooted my Vista 64 PC. Then I turned on the M3 and Windows started installing three drivers. I had never seen it react this way before. The first one it found and installed. the two listed below it could not find and I cannot get a hint as to where they are. They are not on my CD. Did you see any of this behaviour?
The drivers it could not find:
KORG M3 AV/C Audio
KORG M3 AV/C Subunit
can you give me any help you uninstall and reboot was a good start.
Thanks.
The drivers it could not find:
KORG M3 AV/C Audio
KORG M3 AV/C Subunit
can you give me any help you uninstall and reboot was a good start.
Thanks.
I know for sure the drivers work in XP x64. Vista 64 I don't know. I use x64 which works nearly flawless with the exb-FW.
http://www.korgforums.com/forum/phpBB2/ ... hp?t=46103
According to this thread Vista 64 should work fine as well.
http://www.korgforums.com/forum/phpBB2/ ... hp?t=46103
According to this thread Vista 64 should work fine as well.
There are no stupid questions.., only stupid answers..
(I'm an expert on both)
http://www.soundclick.com/bands/page_mu ... dID=989617
(I'm an expert on both)
http://www.soundclick.com/bands/page_mu ... dID=989617
Bump!
Unfortunately I'm still having the same streaming state error.
Only, now reinstalling the driver does not fix the problem and endless adjustments to the sliders are fruitless. I simply can't get it to work on Vista 64.
I did just try my M3 on a friends Macbook and everything worked perfectly. So it is definitely the drivers / PC hardware. I've tried different firewire ports on my computer (PCI card / on the motherboard) and neither work. I've also tried different FW cables but to no avail.
So on that note I'm pretty sure that it has something directly to do with the drivers themselves. Maybe there are some backdoor fixes that someone really savvy in programming would think of. Or perhaps a conflict with another driver.
But other than that I'm not so sure I'm going to have any luck with this.
Unfortunately I'm still having the same streaming state error.
Only, now reinstalling the driver does not fix the problem and endless adjustments to the sliders are fruitless. I simply can't get it to work on Vista 64.
I did just try my M3 on a friends Macbook and everything worked perfectly. So it is definitely the drivers / PC hardware. I've tried different firewire ports on my computer (PCI card / on the motherboard) and neither work. I've also tried different FW cables but to no avail.
So on that note I'm pretty sure that it has something directly to do with the drivers themselves. Maybe there are some backdoor fixes that someone really savvy in programming would think of. Or perhaps a conflict with another driver.
But other than that I'm not so sure I'm going to have any luck with this.