New Posts  All Forums:Forum Nav:

Jplay anyone? - Page 2

post #16 of 48

Wow, audio player without GUI, even worse than the uLilith ==

post #17 of 48
An idea for further development would be an app or complete firmware replacement for popular players, similar to Rockbox, or Equalizer in iOS.
Edited by J.Pocalypse - 10/11/11 at 9:16pm
post #18 of 48

Sorry, I got sick of waiting for the "Loading" box to go away. Back to F2K. JPlay is doing this disgusting thing.. It'll play music for a bit, then go to static. Audible. Static. No, nothing is wrong with my computer. 3.5GB of RAM should be enough for one 38MB .ALAC file.

post #19 of 48
Static? That's new. Are you sure that everything is ok with your track? Also it could be that your audio interface/driver can't handle that low buffer size... Was it with hi-rez track? What audio interface do you use?

Of course 3.5GB is enough, but mind you that jplay doesn't use 'normal' memory management. Instead we choose largepages, which require one chunk of memory that is not fragmented. Unfortunately Windows fragments memory like crazy (to increase security), so everything that you start makes the fragmentation even worse and eventually jplay won't be able to lock enough memory using largepages.

The loading takes longer because jplay doesn't use disk during playback - all tracks that can fit into filecache are pre-loaded prior to starting playback (zero disk i/o). It's been implemented for a reason - better SQ.

We'll most definitely look into a GUI+remote control solution for the upcoming W8, so more audiophiles could enjoy our player smily_headphones1.gif (Yes, we are aware that gui-less player is for extremist)

Regards,
Marcin
post #20 of 48

Are you sure that everything is ok with your track?

 

Yes. I've listened to it through JPlay and many other music players before with no problems.

 

Was it with hi-rez track?

 

Nope. Just typical 16/44 ALAC.

 

What audio interface do you use?

 

Only things I use for music are my lalptop with ( techincally ) 4GB of RAM, JPlay, uDAC ( the first one ) and my M50s.


Windows fragments memory like crazy (to increase security), so everything that you start makes the fragmentation even worse and eventually jplay won't be able to lock enough memory using largepages.

 

How much RAM would you suggest people have on their machines in order to listen to a full album ( figure 12 tracks ) in FLAC/ALAC ( 16/44 ) and still be able to brows the internet at the same time?

We'll most definitely look into a GUI+remote control solution for the upcoming W8, so more audiophiles could enjoy our player.

 

An Android/iOS remote app would be really nice, if, you could still use it during hibernation/overdrive. If not, it'd still be pretty neat. The complete lack of GUI is just fine with me, personally. I change up settings/skins on other players too often anyhow.

 

 

post #21 of 48
3.5GB should be just fine, but remember to start jplay as the first app, right after Windows boots and never close it. This way you ensure that jplay gets more resources (no other programs were started, so RAM is not so fragmented)

Today we are releasing jplay 3.4. If the problem (static) still occurs with the latest version, send us an email and we'll figure out what's wrong.

Cheers,
Marcin
post #22 of 48

Jplay made a huge difference in my setup. It completely transformed my system, the best thing I ever did.

 

Maybe it depends on how optimized Windows is to begin with as to how big an effect it has. But in my Windows 7 bit perfect setup it was a God send.

 

I'm surprised it hasn't a bigger following. But I'm sold.

post #23 of 48

Personally I couldn't detect any difference between JRiver and JPlay but I can confirm it definitely improve the digital stream (maybe jitter???). My transport is a STX feeding a Mytek Stereo96  through spdif. The Mytek as a clever sync button to compare the original signal and the de-jittered/recloked one. Using JPlay (hybernate mode) the difference between the too is inaudible but it is with JRiver.

I believe people with poorly designed or NOS DAC might benefit but if your Dac does a good job at cleaning up the signal differences might be inaudible.

I do like the hybernate mode as I can just load an album and enjoy the music while not wasting time or getting distracted surfing the web biggrin.gif

post #24 of 48

Rise, thread, from the dead!  I've been evaluating JPLAY for a few weeks now, and while the enforced silences in the trial drive me CRAZY (and the inability to seek thru a song), I find the sound substantially better playing jplay thru foobar than just foobar with WASAPI.  My question is: HOW DOES THAT WORK?

 

I've been reading various discussions on various forums about JPLAY trying to figure out what it's doing and whether I'm swallowing placebo with it... and frankly after my reading I'd prefer to think of it as placebo, but when disabling and enabling the f2k plugin, it just sounds so much better: more crisp, better bass, vocals, highs, and positioning.  I'm having a hard time wrapping my head around spending 99... or at least having a hard time trying to figure out how to convince the wife... but if I think of it like a new DAC, the price suddenly makes sense (right, dear?).


Edited by baglunch - 6/12/12 at 10:29pm
post #25 of 48

I didn't know Jplay was controversial?

 

I was skeptical, installed it, was blown away. Bought it and never looked back.

 

Maybe I am a mental case?

 

Suppose it could be system dependent, if you already have jitter under control it offers little benefit?

 

(Edit: Good grief it does have it's haters out there in forum land doesn't it!)


Edited by ecapsretliab - 6/14/12 at 3:08am
post #26 of 48

Seems the vast majority of people that haven't bothered auditioning jplay are rabidly opinionated about it being snake oil, while at the same time being determined to not audition it.  They have a lot of good points of theory to make about it, but in the end I like what I hear in my headphones when using it.

post #27 of 48

http://www.computeraudiophile.com/blogs/mitchco/jriver-vs-jplay-test-results-156/

 

I wonder if the issue is foobar not configured correctly.

 

I was using foobar + wasapi. Then I tried Jplay and everything went real, stunning.

 

Now I'm using Jriver + wasapi event style. And I'm not sure if I could tell a difference blinded between that and Jplay so...

 

I will continue to investigate.
 

post #28 of 48

I dl'd jriver to see if I could save myself $50 in not getting jplay, and I still prefer the sound of f2k + jplay over jriver + wasapi event style.  I prefer the sound, and I prefer the keyboard shortcuts I can set through f2k (but don't see how to set in jriver).  I'd say the listening experience goes: f2k+jplay > jriver + wasapi event style > f2k + wasapi.  I know jplay has its own player, but I don't want to give up randomly shuffling through my entire playlist, and don't want to give up my keyboard shortcuts/hotkeys that I've set.

post #29 of 48
Currently using Jriver and Jplay together. It's not placebo. It eliminates the brightness that Jriver seems to have without darkerning the sound like other players seem to. The full version on it's own is another step up but I can't stand the cut outs, nor can I afford to buy it. I notice the change even with my onboard audio, I can't wait to hear it with a good DAC.
post #30 of 48

Maybe this thread should be moved to Computer Audio sub-forum to garner more attention? 

New Posts  All Forums:Forum Nav:
  Return Home