Jump to content


Photo

JPLAY Femto ASIO does not work with Winamp / Mediamonkey


  • Please log in to reply
13 replies to this topic

#1 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 05 November 2018 - 08:42 PM

Hi,

 

it seems that the Winamp ASIO plugins (also used with Mediamonkey) are shutting down something in the JPLAY Femto ASIO driver. 

 

The test:

 

  • Playing foobar with JPLAY ASIO driver works.
  • Starting Mediamonkey or Winamp with ASIO plugins and Chord ASIO as driver works.
  • Switching to "JPLAY driver": no sound, no error message.
  • Playing foobar gives then following errors:
  • In foobar: "Unrecoverable playback error: Could not initialize the driver"
  • As system message: "Can't connect. Seems JPLAY is not running ..."

jplay.exe and JPLAYfemto.exe are still visible in the windows task manager.

 

Cause ASIO is not supported by Mediamonkey, there is no hope that they fix it.

 

You can find both Winamp plugins here: http://forums.winamp...ad.php?t=452642

 

Best regards

Harald



#2 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 05 November 2018 - 10:02 PM

Same problem with this tool: https://de.freedownl...-KOSTENLOS.html

 

JPLAY message: Can't connect

Unable to connect JPLAY on 127.0.0.1



#3 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 05 November 2018 - 10:59 PM

Same problem with the qobuz app. The JPLAY ASIO drivers shuts down in a way, and the PC must be restarted to play with JPLAY driver in foobar2000.



#4 Marcin_gps

Marcin_gps

    JPLAY team

  • Administrators
  • 2,699 posts

Posted 06 November 2018 - 09:35 AM

Which settings do you use in JPLAY panel? 

Have you tried BitStream to 24bit? 

 

Is there any error from Monkeymote or Winamp - is DSP enabled in these apps? 



#5 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 06 November 2018 - 12:34 PM

Hi,

 

the only app that supports DSP is foobar2000. Mediamonkey, Winamp and Qobuz App do not.

 

The errors are from JPLAY.

 

Windows 10

DAC: Chord Qutest

 

KS: Chord Electronics Ltd. Streaming

Engine: UltraStream
DAC Link: 45 Hz
AudioPC: This computer [20]
XtreamSize: 1000
Bitstream: Native (Best)
Throttle: On
Bitperfect Volumn: Off
Hibernate mode: Off

Fidelzer is not running.

 

I try Bitstream to 24bit now. This may take some minutes ...

 

Regards

Harald
 



#6 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 06 November 2018 - 12:42 PM

24bit has the same effect.



#7 Marcin_gps

Marcin_gps

    JPLAY team

  • Administrators
  • 2,699 posts

Posted 06 November 2018 - 01:10 PM

So foobar works and Winamp and MediaMonkey not playing? 



#8 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 06 November 2018 - 01:18 PM

Yes. foobar works before I start Winamp/Mediamonkey/Qobuz App with JPLAY driver, not after. They kill the driver in a way.



#9 Marcin_gps

Marcin_gps

    JPLAY team

  • Administrators
  • 2,699 posts

Posted 06 November 2018 - 01:35 PM

Yes. foobar works before I start Winamp/Mediamonkey/Qobuz App with JPLAY driver, not after. They kill the driver in a way.

 

Please make sure to close one player before opening another as this may be the cause. JPLAY requires exclusive access to the driver. 

If that doesn't help please contact us on support@jplay.eu for a debug build

 

Regards, 

Marcin



#10 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 06 November 2018 - 02:33 PM

Hi Marcin,

I don't thinl this has something to do with exclusive mode. All my players except foobar do not work with JPLAY driver. I can start Mediamonkey without having foobar started at all, with the same effect. Even if a player blockes the driver, the driver should not shut down at all.

If it where only Mediamonkey, I would blame them to have errors in the output plugins, but it's also Qobuz and the ASIO bridge. The Chord DAC may be a reason, but I don't think that's very plausible, cause their ASIO driver works and in JPLAY, the signals are converted to kernel streaming.
 

Regards

Harald



#11 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 06 November 2018 - 02:44 PM

I contacted the support and let you know when we have a solution.



#12 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 07 November 2018 - 04:03 AM

Hi,

 

in Mediamonkey, it works with the 64 bit ASIO output driver. The driver has thrown an error when I first started it, but now it's running.

 

Sad, but that's no solution for the Qobuz APP.

 

Best regards

Harald



#13 deremder

deremder

    Beginner

  • Members
  • 15 posts

Posted 07 November 2018 - 05:08 PM

Hi,

 

I must correct my last post: it does not work. Mediamonkey crashes, together with the complete audio system. Reset to WASAPI is not available without restarting Windows.

 

There's no workaround and no offer to use the 6.2 version before 7 ASIO is fixed. I'm disapointed.

 

Regards

Harald



#14 Marcin_gps

Marcin_gps

    JPLAY team

  • Administrators
  • 2,699 posts

Posted 07 November 2018 - 05:30 PM

Hi,

 

I must correct my last post: it does not work. Mediamonkey crashes, together with the complete audio system. Reset to WASAPI is not available without restarting Windows.

 

There's no workaround and no offer to use the 6.2 version before 7 ASIO is fixed. I'm disapointed.

 

Regards

Harald

Hi Harald, 

 

Thanks for the report. We're working on fixes for JPLAY Driver, we'll contact you once we make progress. It make take few more days.

I will test with MediaMonkey myself

 

Regards, 

Marcin






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users