Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rurutia10

Pages: 12 3 ... 9
1
Yep, working fine for me now with both WASAPI and ASIO.

2
Seems like they both enable the same outcome; small delay to stop music at the start from being cut off.

I don't use WASAPI though, mainly sticking with ASIO. I don't like having to fiddle around before I can hear sound from YouTube videos or other sources :o

3
You're welcome. Also, check the edit :)

4
Steven has put a lot of effort in this over the last period.
You might want to try the latest update, and fiddle around with the buffer settings. (also in the .ini file)
Perhaps you are able to solve it for your dac now?
It did solve similar issues for other members too.

For me it's really some 10ms that seems to be able to make the difference. (trying it in foobar2000, that is)
Having it 500ms or longer doesn't make a difference for my setup at all.
With all settings (except directsound) something like the first 50ms is truncated.
(just the very first attack of percussion, guitar string etc.)

The fact that Steven has not been able to fix this for my setup is proof to me it is really a complicated matter, and also very hardware dependent.

For example, I also tried MediaMonkey.
Whilst it has almost identical settings to foobar in regards of setting options for push and event buffers, MediaMonkey also keeps truncating the beginning of the sound no matter what I set those to.

Only foobar seems to like my dac a lot...

I still need to check it out.

Try out the DSP suggestion I was talking about with Foobar btw, while reverting that hardware buffer setting you used to default. If it works, you'll know that it's a software issue and not a hardware one. Players sometimes just struggle with certain dacs.

If you experience songs being cut off at the start while using a DAC, the solution is nearly always to enable a 500 ms silence at the start of every track. This way, what is being cut off is the silence it self, and not the actual music.

Also, for reference, JRiver has this option, describing what I stated above.

"Play silence at startup for hardware synchronization. Some hardware requires a lead time from when a signal is delivered to when sound is produced. This option allows outputting leading silence so no actual sound is lost in these cases. Note that this option is only in effect in two cases - at the first playback after the program starts, and between tracks with different sample rates. This silence will not be played between tracks with the same sample rate."

5
I made a thread on this a year ago in the wishlist forum too. I was in the exact same boat as you, I bought a hifi DAC, but the first second of every song was being cut off. I made a thread in this forum asking for an option to include second(s) silence to the start of every thread. But it was just getting ignored. No one replied to it. Eventually, I just asked Phred to delete the thread, and I stopped using Musicbee and switched to Foobar.

The reason there's a silence is because the DAC needs a second to initialize. There are players out there like Jriver that just take account for DACs automatically, and there's no silence at the start of tracks. For Foobar, there's the DSP "Affix silence". I set it up to play a 500 milliseconds silence before starting every track, and it works well.

Glad it got attention though, maybe I can go back to Musicbee. Used it for years and enjoyed it.

Also, I wanted to add, 100ms is not enough. Try 500ms. It might depend on the DAC you're using though.

Also, please add support for ASIO and/or include an option for silence at the start of tracks :)

6
General Discussions / Re: GUI changes for v3.0
« on: April 25, 2016, 11:18:14 AM »
@rurutia10, you are continually complaining about crashes and issues that i can never reproduce and no one else reports. Its probably best you use another application as i wont spend more time helping you

The only bug worth of note that I've made more than 2 posts about (the crashing bug) has been reported by several others: http://getmusicbee.com/forum/index.php?topic=15050.msg107679#msg107669

I've been using for 3.0 for 5 months now and very much like it, these are minor issues that happen infrequently, if they were big issues I would have switched a long time ago.


7
General Discussions / Re: GUI changes for v3.0
« on: April 24, 2016, 07:11:23 PM »
I've been getting a new bug lately since one of the last updates. If I don't use musicbee for a while, and come back and play a song that's in the middle of the track, the first second will repeat for like 10 times before the song continues playing. No error log.

Also the crashing bug is gone, I suspect it might have something to do with it

Another bug, but this one happens infrequently, but when it does happen it's extremely annoying. Playing an album and a song just gets skipped randomly. For example playing track #3, and when it finishes, it'll play track #5. Then I'll play track #3 again to see what happened wrong, it finished and then it does go to track #4 fine. Weird bug but really annoying.

8
General Discussions / Re: GUI changes for v3.0
« on: March 26, 2016, 04:53:06 AM »
Here is how the crashing bug just happened for me

1. Play a song until it's almost finished
2. Pause the song, take a break from listening (20~ minutes)
3. Come back and play the song
4. Hear my hard drive spinning
5. Crash

9
General Discussions / Re: GUI changes for v3.0
« on: March 25, 2016, 03:28:44 PM »
just in regards to the random freezing that was reported by a couple of people. I have spent quite a bit of time trying to reproduce and walking through the code.
I did make one small change but i dont really think that will be the reason it happened - it might be. So i will leave this for now. If anyone is able to semi-reliably reproduce this then i can spend more time on it

thanks for the hard work

10
General Discussions / Re: GUI changes for v3.0
« on: March 22, 2016, 09:02:24 PM »
@rurutia10 and @Alumni, I am still not able to reproduce any issues using Alumnis settings and by stopping playback just before the end of a track.
It would be useful to know if you are easily able to reproduce the issue yourself by repeatedly performing that action.
If so then i can create a debug version for this.

I haven't even been able to reproduce it manually. lol. it happens way too randomly :/

The last time I got a crash the song was at 50% or so if I remember correctly.

@Alumni

Do you use repeat song a lot?

11
General Discussions / Re: GUI changes for v3.0
« on: March 22, 2016, 08:30:36 PM »
Nothing on the album art icon in artist view for artists with one album?

I don't even mind it that much but just found it weird a feature that was requested has been nerved to compensate another feature in artist view.

also don't think it looks good at all, and should be made optional, but if others here like it..

The reason I asked for that feature was because I wanted it to be as minimalist as possible. Doesn't really do what it says anymore, at least in artist view

12
General Discussions / Re: GUI changes for v3.0
« on: March 22, 2016, 01:30:15 PM »
For artist view it's still there (artists with only one album)

I believe that's why the feature was added, to show the cover of a single album in artist view.

tbh I don't know what's so good about such a small stretched album icon, why do you want to see it like that? Most people have artwork element on a side bar anyways, which looks thousand times better? If you don't have "show album art" enabled, I don't expect any album art at all in the expanded panel.

Maybe make it an option for those who really want to see the album art in such a small size?

OR better yet, for artists with only 1 album, just show the album normally in expanded panel and not directly the tracks, like any other artist with multiple albums. I don't see anything wrong with 1 extra mouse click if it means just seeing the album art in normal size.

13
General Discussions / Re: GUI changes for v3.0
« on: March 22, 2016, 12:30:19 PM »
Sent. Thought it was a weird touch and I wasn't sure it was intended or not since it came out of nowhere xD
missed the most obvious condition of all - when showing album covers in the main panel. Thats fixed for the next update

For artist view it's still there (artists with only one album)

14
General Discussions / Re: GUI changes for v3.0
« on: March 22, 2016, 05:48:39 AM »
was it in the last few seconds of the track?

Actually yes, I'm pretty sure the track was nearly finished when I stopped it.

Okay, we have 100% exactly the same problem then. It always happened at the end of a track for me and when I wanted to play the next song --> crash.

15
General Discussions / Re: GUI changes for v3.0
« on: March 21, 2016, 08:19:09 PM »
for those of you complaining about the new small album picture, can you post a screenshot where the bigger album cover is already showing in the main panel as that shouldnt happen

Sent. Thought it was a weird touch and I wasn't sure it was intended or not since it came out of nowhere xD

Pages: 12 3 ... 9