No Asio device found for my Line6 X3 Live

[unsurx]

Hi,
I just try the new line6 Riffworks edition v2.2.2 and it works fine with my Pod X3 live.
I decided to by the full standard edition.
Now, after installation, when RWS is launched it says that it doesn't found any asio driver !
I reinstalled line6 drivers but nothing.
I don't understand.

[EvanBerard]

Did you try a computer restart? That always does the trick for me

[unsurx]

Yes did it. Idem.
I just reinstalled in "parallel" my line6 Demo version and it works. Asio drivers of the pod are presents in AUDIO SETUP.
I closed it and launched the standard edition and.. nothing, no asio drivers found.
What the matter with this version (2.5.0.3009) ?

[bluesydude]

Download and install this http://www.asio4all.com/.

[Wedgebill]

Download and run the Line 6 Monkey to ensure all your drivers are up to date. Unplug and replug your USB cable before firing up Riffworks. Hopefully one of these options will sort it for you

[sinfreealex]

Download and run the Line 6 Monkey to ensure all your drivers are up to date. Unplug and replug your USB cable before firing up Riffworks. Hopefully one of these options will sort it for you

I never had the Line 6 edition, I went right to standard from T4. I would remove any editions you have, reinstall standard, and take the steps above. I've been using standard (and all updates releases since November) with my X3 Live and loving it.

[d3drocks]

Download and install this http://www.asio4all.com/.

no, thats not the problem. line 6 hardware has its own ASIO drivers.
asio4all wont solve this, as it is for general hardware. if ASIO4ALL sees anything line6, it means that the device's drivers are already installed, and you can use them instead of rigging ASIO4ALL to work with other stuff.

[ShredRex]

Install the Line 6 Monkey and update everything......

[unsurx]

Thanks for your replies.
I just had to reinstalled all my XP system cause some bad sectors on my HD crash it.
Now the system is clean and after reinstall of all drivers, line6 drivers, monkey etc, and Riffworks Standard, it's the same thing. It doesn't see any asio device.
The free RW line6 edition works.
I unplug and plug my POD, reboot, nothing...
Somes new ideas ?

[unsurx]

Here an extract of RiffWorksStandard.log (doesn't work) :

1906076640 : Launching RiffWorksStandard
1906077012 : Version 2.5.0.3009
...
1906112480 : DAsioBay::Setup
1906112491 : DAsioBay::FillDeviceList
1906126824 : DAsioBay: number of installed drivers = 2
1906126846 : DAsioBay: Driver name = ASIO FW-1082
1906132688 : DAsioBay loadAsioDriver OK
1906132721 : DAsioBay: ASIOInit OK - driver version: 2
1906132733 : DAsioBay: ASIOGetChannels OK
1906132741 : DAsioBay: InputChannels = 10
1906132748 : DAsioBay: OutputChannels = 4
1906132761 : DAsioBay: Driver name = ASIO POD X3 Live
1906138030 : DAsioBay loadAsioDriver OK
1906138628 : DAsioBay: ASIOInit OK - driver version: 50594659
1906138643 : DAsioBay: ASIOGetChannels OK
1906138651 : DAsioBay: InputChannels = 8
1906138658 : DAsioBay: OutputChannels = 2
1906138682 : DAsioBay::SetDeviceByName
1906138690 : DAsioBay::SetDevice 0
1906139897 : DAsioBay: Driver name = FW884 24-bit loaded
1906139944 : DAsioBay: Buffer sizes min:128 max:64 pref:64
1906139962 : ASIOSetSampleRate returned error: 1906313948 : DNetworkServerConnection::ConnectToServer ping SUCCESS
1906453209 : DLooperBay::SetDriverBay
...

and an extract of RiffWorksLine6Edition.log (works) :

763908206 : Launching RiffWorksLine6Edition
763921028 : Version 2.2.2.3009
...
768463517 : DAsioBay::Setup
768463525 : DAsioBay::FillDeviceList
768480766 : DAsioBay: number of installed drivers = 2
768480788 : DAsioBay: Driver name = ASIO FW-1082
768480796 : DAsioBay: L6ed Ignoring ASIO FW-1082
768480806 : DAsioBay: Driver name = ASIO POD X3 Live
768486969 : DAsioBay loadAsioDriver OK
768487625 : DAsioBay: ASIOInit OK - driver version: 50594659
768487651 : DAsioBay: ASIOGetChannels OK
768487659 : DAsioBay: InputChannels = 8
768487666 : DAsioBay: OutputChannels = 2
768487683 : DAsioBay::SetDeviceByName
768487691 : DAsioBay::SetDevice 0
768491470 : DAsioBay: Driver name = ASIO POD X3 Live loaded
768492182 : DAsioBay: Buffer sizes min:256 max:4096 pref:512
768492207 : DAsioBay::CreateBuffers
768492215 : DAsioBay : ASIOCreateBuffers with inputChannels = 8
768492224 : DAsioBay : ASIOCreateBuffers with OutputChannels = 2
768492231 : DAsioBay : ASIOCreateBuffers with size = 512
768566933 : kAsioSupportsTimeInfo
768567280 : ASIOGetLatencies : InputLatency = 749 latency = 16 msec
768567327 : ASIOGetLatencies : OuputLatency = 1498 latency = 33 msec
768567334 : DAsioBay::GetChannelInfo
...

(Note : I have another ASIO driver for my TASCAM FW-1082)

[unsurx]

Hi,

I found a solution (temporary i hope) for my problem.
RW Standard seems to be disturb by asio drivers of my TASCAM FW-1082.
- I switch off the TASCAM
- I launch RW and its starts now with asio drivers of the POD.
- I switch on the TASCAM

An extract of the log file in this case :

14095293896 : Launching RiffWorksStandard
14095294203 : Version 2.5.0.3009
...
14095331654 : DAsioBay::Setup
14095331668 : DAsioBay::FillDeviceList
14095346292 : DAsioBay: number of installed drivers = 2
14095346315 : DAsioBay: Driver name = ASIO FW-1082
14095351422 : DAsioBay loadAsioDriver OK
14095351446 : DAsioBay: ASIOInit returned -1000 for ASIO FW-1082
14095351459 : DAsioBay: Driver name = ASIO POD X3 Live
14095355763 : DAsioBay loadAsioDriver OK
14095356318 : DAsioBay: ASIOInit OK - driver version: 50594659
14095356347 : DAsioBay: ASIOGetChannels OK
14095356354 : DAsioBay: InputChannels = 8
14095356362 : DAsioBay: OutputChannels = 2
14095356381 : DAsioBay::SetDeviceByName ASIO POD X3 Live
14095356389 : DAsioBay::SetDevice 0
14095359465 : DAsioBay: Driver name = ASIO POD X3 Live loaded
14095360004 : DAsioBay: Buffer sizes min:128 max:4096 pref:512
14095360020 : DAsioBay::CreateBuffers
14095360029 : DAsioBay : ASIOCreateBuffers with inputChannels = 8
14095360037 : DAsioBay : ASIOCreateBuffers with OutputChannels = 2
14095360044 : DAsioBay : ASIOCreateBuffers with size = 512
14095434862 : kAsioSupportsTimeInfo
14095435170 : ASIOGetLatencies : InputLatency = 617 latency = 13 msec
14095435181 : ASIOGetLatencies : OuputLatency = 1234 latency = 27 msec
14095435254 : DAsioBay::GetChannelInfo
...

to be continued...

[scott]

TASCAM drivers seem to have an inherant dislike of RW drivers. My US-428 constantly gave me blue screens when used with RiffWorks, to the point of not using it at all (even though the audio is better quality through it).

[GuitarSlinger]

It may be helpful to email support directly for the Tascam driver problem. In case you want to use your Tascam with Riffworks Standard also, they should be made aware of driver issues.

[strat]

I feel your pain Lickman..RWS has not worked for me either after the last update...Ive done what im supposed to do[contact support/send dump file ect] ...nothing...Im fed up and am going back to the program i used before rws..at least it works...

[strat]

Hi L.man...i still have the l.6 version so i use that some..i also use audacity/magix music maker 14[it takes any vst i can fine] i got several other programs..acid/guitar pro 3/cakewalk ect..the way i record.. full takes or one shot..hit record..1,2,3 go and hit stop at the end works for me..i used rw [when it works] mainly for the drums as its tedious using samples or my drum box and i do use a lot of rex files..sww got my e.mail..when i hear back from support i'll go from there..as of now..i can get by fine...it aint gonna slow my roll..peace brother...