More > Media Center 11 (Development Ended)
Crash/hang on playing short WAVs [solved]
chrisjj:
When on MCV11 with installation defaults, I drag seeming any approx 2s log WAV to Playing Now and click Play, I get variously:
1 "Media Center has encountered a problem and needs to
close. We are sorry for the inconvenience.", or
2 Hang, or
3 an approx 150ms segment looped, with an odd echo, often followed by hang.
With "Switch tracks: Gapless", this doesn't happen.
Is this a known bug? Is it due for fixing?
jgreen:
I can confirm this, more or less. I created a 2-sec WAV, imported it, and then dragged it to playing now. The first time I hit play it would not respond, the second time it would play twice. It repeated this behavior almost without exeption.
My output is direct sound with a 5-sec buffer. I tried taking the buffer down to .6-sec, and it played properly every time. Took it back to 5-sec, and the problem reappeared.
I tried switching to wave out, and the problem was mostly still there, but with more exceptions.
chrisjj, it will help them if you list your output settings. I think the issue is in the buffer at start of play. If you are using the latest version, you should post this issue to the .310 thread.
chrisjj:
> I can confirm this, more or less.
Thanks. Disappointing to discover such a basic bug in a V11 :(
Before I continue with investment in evaluation, is there a bug list visible somewhere?
> chrisjj, it will help them if you list your output settings.
I thought "installation defaults" defined them, but OK:
Output mode: Wave Out
Output mode settings...
Wave mapper (recommended)
0.5 seconds
[ ] Aggressive reset (enable if you hear bursts of sound when starting
new tracks)
> If you are using the latest version,
I'm using the one currently offered for download, but that's not .310, but Version: 11.0.309.
modelmaker:
309 is the correct latest "release" version.
What are these wav files that are so short? You might be trying to do something that MC was never designed to, or of coarse this may be an area no one has tried before, (very short files), and therefore may need some tweaking.
I don't think I've ever played a file shorter than 7 or 8 seconds in the 3 years I've been using MC and so have never come across this issue.
Unfortunately this is the weekend, so the JRiver team may not see this until monday, but maybe one of the "Beta" testers will help out.
As very few users run MC with default settings, I doubt that even the JRiver has those defailt settings memorized, so it always helps and saves time to list all relevant data that describes how a person uses MC. The more information one supplies, the more helpful the "brain trust" here can be. :)
There were some major changes between v10 and v11, so there are still a few small bugs to be worked out. It may be a big bug to you, but compared to the total development picture... , but I assure you that every issue is looked at.
chrisjj:
> What are these wav files that are so short?
Spacers.
> You might be trying to do something that MC was never designed to
Hey, MC accepted the job.
> or of coarse this may be an area no one has tried before
Now you're depressing me. QA, anyone?
> I don't think I've ever played a file shorter than 7 or 8 seconds
7 seconds is plenty short enough to cause failure mode 3 here.
> the JRiver team may not see this until monday
Thanks. No hurry.
> As very few users run MC with default settings, I doubt that even the
> JRiver has those defailt settings memorized,
No memorisation required - an install will tell them.
> so it always helps and saves time to list all relevant data that
> describes how a person uses MC.
Eh, no!! It takes A LOT of time to manually copy out all the settings from the UI. Or is there a settings .ini or the like I can quote?
> It may be a big bug to you, but compared to the total development picture... ,
Meaning I've yet to find the really big bugs?
Navigation
[0] Message Index
[#] Next page
Go to full version