Welcome Guest! To enable all features please Register.

Notification

Icon
Error
db Gain using Spotify
Options
Previous Topic Next Topic
natstick Offline
#1 Posted : Wednesday, November 23, 2011 3:54:07 PM(UTC)
Rank: Newbie

Joined: 11/23/2011(UTC)
Posts: 2
Hi all,
I'm enjoying using Jamcast and its exactly the solution I'm looking for me. (bar the ability to watch films on laptop and listen to the soundtrack via av amp as you can do with a 3mm heaphone socket beacause of the delay)
Just a couple of things though:
While streaming from Spotify using the virtual souncard, I find that I need to turn my amp (VSX-LX55) up considerably, and this doesn't allow me the headroom I'd like to play music at the volume I sometimes enjoy.
In comparison, using Media Player, Foobar or any other media player, I dont have this issue, and have MORE than enough volume to play with.
There is a big difference in output.
I also feel that "pushing" the amp harder using Spotify is not helping the audio quality, so there is a noticeable difference in quality from streamed MP3's to locally stored MP3's of the same source and bitrate.
Is this to be expected? Anyone else experience this?

Just one more question regards the Force mp3 capture stream.
Does this affect any lossless files played?

Thanks
Back to top
Scott Offline
#2 Posted : Sunday, November 27, 2011 9:08:19 AM(UTC)
Rank: Administration
Scott

Joined: 1/25/2009(UTC)
Posts: 1,615
Location: Orlando, FL, USA
natstick;3576 wrote:
Hi all,
I'm enjoying using Jamcast and its exactly the solution I'm looking for me. (bar the ability to watch films on laptop and listen to the soundtrack via av amp as you can do with a 3mm heaphone socket beacause of the delay)
Just a couple of things though:
While streaming from Spotify using the virtual souncard, I find that I need to turn my amp (VSX-LX55) up considerably, and this doesn't allow me the headroom I'd like to play music at the volume I sometimes enjoy.
In comparison, using Media Player, Foobar or any other media player, I dont have this issue, and have MORE than enough volume to play with.
There is a big difference in output.
I also feel that "pushing" the amp harder using Spotify is not helping the audio quality, so there is a noticeable difference in quality from streamed MP3's to locally stored MP3's of the same source and bitrate.
Is this to be expected? Anyone else experience this?

Just one more question regards the Force mp3 capture stream.
Does this affect any lossless files played?

Thanks

Hey natstick,

Thanks for the feedback! To be clear, are you saying that using Media Player, foobar, etc. via the Virtual Soundcard you have no issues with volume, whereas with Spotify you do? Just wasn't clear if the other media apps were via the VSC as well...

ForceMP3CaptureStream only affects the Virtual Soundcard stream. Anything else beneath "My Music", etc. is not affected by the setting.

Hope this helps.

Thanks!
Scott
Jamcast Technical Support
Docs: http://www.sdstechnologies.com/Wiki/
Back to top
WWW BLOG
natstick Offline
#3 Posted : Sunday, November 27, 2011 4:42:57 PM(UTC)
Rank: Newbie

Joined: 11/23/2011(UTC)
Posts: 2
Hi Scott,
Thanks for the reply.
I'm somewhat embarressed to say that that Spotify does respond to audio volume changes, where I have found other media players don't, hence me not trying!
All I can say is that your virtual souncard meets my expectations and more, meaning I will be a paying customer by tomorrow.
I still have a random issue regarding the response time to changing tracks in Spotify, however.
Initially, I would need to wait over a minute at times for a track change to filter through.
I have since found the response time to be a regular 6-8 secs, which I'm more than happy with.
But, tonight. Its reverted to 44 secs at last count, without any other activity on the network, leaving me a bit mystified.
Any thoughts would be welcome.
Cheeers
Natsttick
Back to top
Scott Offline
#4 Posted : Friday, December 09, 2011 8:58:18 AM(UTC)
Rank: Administration
Scott

Joined: 1/25/2009(UTC)
Posts: 1,615
Location: Orlando, FL, USA
natstick;3586 wrote:
Hi Scott,
Thanks for the reply.
I'm somewhat embarressed to say that that Spotify does respond to audio volume changes, where I have found other media players don't, hence me not trying!
All I can say is that your virtual souncard meets my expectations and more, meaning I will be a paying customer by tomorrow.
I still have a random issue regarding the response time to changing tracks in Spotify, however.
Initially, I would need to wait over a minute at times for a track change to filter through.
I have since found the response time to be a regular 6-8 secs, which I'm more than happy with.
But, tonight. Its reverted to 44 secs at last count, without any other activity on the network, leaving me a bit mystified.
Any thoughts would be welcome.
Cheeers
Natsttick

Hey Natstick,

Great! Smile

Regarding the playback delay, you'll have an initial playback start delay of around 5 seconds typically (sounds like 6-8 in your specific case). However, each time the playback device has to rebuffer audio, this playback delay will increase. At some point, according to the buffer setting in Jamcast, that extra "in the past" audio data that is accumulating on the server will get dumped in favor of keep your delay from realtime as small as possible. The buffer flush will be experienced by you as missing a chunk of audio, and the capture buffer size can be adjusted to your preference via the Virtual Soundcard tab in Jamcast Server Manager.

Does this make sense, and can you see any correlation between this behavior and what you're experiencing?

Thanks!
Scott
Jamcast Technical Support
Docs: http://www.sdstechnologies.com/Wiki/
Back to top
WWW BLOG
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.323 seconds.