Search the Community
Showing results for tags 'wasapi'.
Found 2 results
For the past year or two I have been unable to set up my Line 6 POD XT Pro to record properly into Reaper. I had to have a friend round to have a poke around for me with hopes that he may be able to fix it so this is said friend typing on my behalf! Presently, I am able to record but playback is very crackly. My setup is a little unconventional. I have an audio out port from my PC going to one of the Aux in's on my stereo system, to which my standard hi-fi speakers are connected. The POD XT Pro is connected to the PC via the usual firewire cable. However, I have to have a cable running from the Phones jack to the other Aux in port on my stereo system, so I have to toggle between the two Aux inputs depending on whether I want to hear sound from my PC (including audio playback from Reaper) or sound from my Line 6. Bit of a nuisance as it means I can't really jam along to YouTube videos or mp3s or whatever. I know this setup is weird but it's all I have. To attempt to solve the crackling problem I went to Preferences in Reaper and saw that the current Audio system setting in Audio > Device is "WASAPI (Windows 7/8/Vista)" My friend said that the norm is to have whatever ASIO device is available, so we tried this, and there are 2 sub-options of ASIO Driver, these being ASIO PODxt Pro or ASIO4ALL v2. Using ASIO PODxt Pro resulted in horrible noise when both recording and playback (earlier on trying it there was no sound at all). Using ASIO4ALL v2 resulted in smooth playback of existing recorded sounds but would not record anything. I presume the fact it says 'Not Connected' in the inputs section has something to do with it but there are no other options for some reason and the ASIO Configuration dialogue didn't give us any answers. I have made sure that the Aux input channel is on the right one every time with respect to whether I'm recording or playing back, so I presume the noise or recording issues are nothing to do with that but may make things more complicated. So can anyone advise how to eliminate the playback crackling when using WASAPI / ASIO PODxt Pro and/or how to get recording to work when using ASIO4ALL? System basic specs: Windows 7 Processor: Intel® Core i3 CPU 540 @ 3.07GHz 3.07 GHz Installed memory (RAM): 3.00GB System type: 64-bit OS Unfortunately I'm not especially computer literate so if anyone can help but explain things in layman's terms as much as possible that'd be great!
lemonjimm posted a topic in POD Farm / POD Studio / TonePortI posted this under a general Win 10 topic yesterday but the thread went in another direction...so I'll post again in hopes that someone else is seeing this same issue. To clarify, audio works fine for most default applications and Toneport ASIO works fine in DAWs like Live, Reason & FL Studio. Other programs - those that need to see drivers other than ASIO - will not be able to use their driver unless the Toneport USB is disconnected. Please read through the post before offering standard troubleshooting advice - thanks. USB 2.0 & 3.0 were also tried. On 8/7, I posted this on the Audacity forums after trying to get this sorted out with a Cycling '74 tech over email. We definitely have a pattern here - I've been looking at this all day. Plug in an ASIO USB soundcard and Audacity does not "see" any MME, WASAPI or DirectSound drivers/devices. Unplug and Audacity comes up. Windows 10 upgrade (build 10240) Audacity 2.1.1 Line 6 Toneport UX1 - 126.96.36.199 driver Realtek High Def Audio on board - 188.8.131.5235 driver (was disabled until today) My audio cable setup now is the MME on board device feeding into the monitor in on the Toneport (a typical setup) This also happens for Cycling 74 Max 6 & 7 Max 4 Live in Ableton Live can open devices but can't edit I believe that MSP (associated with Max) can only run under MME as well, so there appears to be a link. Ableton Live 9.2 cannot see MME until USB is unplugged Reason 7.1.1 & FL Studio 11.1.1 can see everything all the time BTW the Toneport cannot be controlled by the Windows Audio tray icon (Control Panel applet). You can only change volume with the hardware knob on it. I've tried - writing to Cycling - they said the audio driver loads right before the Max program crashes - Using just the TonePort (my on board Realtek card has been disabled pre-Win 10 - I only enabled it in BIOS when I saw other users were having these types of results) - with Max 6, I uninstalled both 64 and 32 bit versions and then reinstalled 32...then reached for Max 6, 32 bit - only works if Toneport is unplugged - 41 and 48K for both devices - swapping default device - toggling the exclusive device checkboxes on both soundcards - reinstalling all the Line 6 software - suspiciously, their Win10 driver has a date of 2013 on it! I was subsequently asked on the Audacity forum if Audacity 2.0.3 worked, so I installed it into another folder and it worked...now if I can only get Max and Max4Live to work Of course, I'd rather use the latest Audacity. Thanks!