Thread: Centrafuse RC3.1 Bugs

I have a new one... you're gonna love this.

So, given the bug with not being able to refresh XM channels, I replaced my satchannels.xml file with one from a fresh install of RC3 (not RC3.1). My channels are back (which of course makes sense) and I'm back to using the XM plugin instead of AIMEE. But, here's the fun...

CF is set to startup in XM. It does, and I get audio right at startup. But, it's VERY loud and distorted. Hunting around, I can trace this back to the MIC level being set to 50 when CF loads. So, I turn down the level like I've been doing. _BUT_ when I go BACK into the XM plugin, the MIC level goes back to 50. No lie. 100% repeatable.

As well, when I come back out to MIXER, the MIC level slider is still at 0, but the level is clearly up. I drag the slider up, then back down, and the level goes back to 0. I click back into the XM plugin and... The MIC level comes back to 50.

What's VERY strange is that this didn't happen before. "Before" is defined as RC3 (NOT RC3.1) and before I first clicked on "refresh channel list" for the XM plugin under RC3.

Since I first did that, I upgraded to RC3.1, so is it possible that something changed at 3.1 in how you manage the audio when a plugin gets focus?

Originally Posted by midiwall

I have a new one... you're gonna love this.

So, given the bug with not being able to refresh XM channels, I replaced my satchannels.xml file with one from a fresh install of RC3 (not RC3.1). My channels are back (which of course makes sense) and I'm back to using the XM plugin instead of AIMEE. But, here's the fun...

CF is set to startup in XM. It does, and I get audio right at startup. But, it's VERY loud and distorted. Hunting around, I can trace this back to the MIC level being set to 50 when CF loads. So, I turn down the level like I've been doing. _BUT_ when I go BACK into the XM plugin, the MIC level goes back to 50. No lie. 100% repeatable.

As well, when I come back out to MIXER, the MIC level slider is still at 0, but the level is clearly up. I drag the slider up, then back down, and the level goes back to 0. I click back into the XM plugin and... The MIC level comes back to 50.

What's VERY strange is that this didn't happen before. "Before" is defined as RC3 (NOT RC3.1) and before I first clicked on "refresh channel list" for the XM plugin under RC3.

Since I first did that, I upgraded to RC3.1, so is it possible that something changed at 3.1 in how you manage the audio when a plugin gets focus?

This is the same thing that is happening to me.

Originally Posted by bowtie4532

This is the same thing that is happening to me.

! Dood... I think you're the first person to have the same XM issues that I am. David will be so happy! (seriously - I think he thinks I've been making all this up!)

Originally Posted by midiwall

! Dood... I think you're the first person to have the same XM issues that I am. David will be so happy! (seriously - I think he thinks I've been making all this up!)

I believe you... I will focus on these XM issues as soon as I get the next release out...

It will be my main focus...

david

Originally Posted by veetid

I'm pretty positive it's related to the visuals, especially after seeing your error.log... If the music is playing, the visuals are loaded in memory and ready to render if you to the media screen...

I known where to start looking now... great job!

Cheered too soon I guess...
I've disabled the music autostart, restarted CF and did absolutely nothing and now got this in the errorlog at the moment of startup:
----
9/28/2006 11:56:31 PM
Object reference not set to an instance of an object.
at centrafuse.obdii.resetChip()
----
and CF crashing with the same error after about 20 min of sitting idle...

Trying to reproduce this behaviour, it just resorted to putting in the
Object reference not set to an instance of an object.
at centrafuse.main.loadVisuals()
right after startup.
Dunno if it's gonna crash again as it has only been a few minutes.

I must say: with RC2 (I think) I've made a roadtrip (on a different machine also) and didn't come across this error. Didn't play any music, only used the navigation, was actually a test (needed to pickup something 300km from home and could use some navigation).

Not much of a help I guess... isn't there a way to intercept that general .net error and have CF log what it was doing or something? Or maybe I could run it through some tracer? I have no .net experience, but I have basic debugging skills

Originally Posted by LEiPiE

Cheered too soon I guess...
I've disabled the music autostart, restarted CF and did absolutely nothing and now got this in the errorlog at the moment of startup:
----
9/28/2006 11:56:31 PM
Object reference not set to an instance of an object.
at centrafuse.obdii.resetChip()
----
and CF crashing with the same error after about 20 min of sitting idle...

Trying to reproduce this behaviour, it just resorted to putting in the
Object reference not set to an instance of an object.
at centrafuse.main.loadVisuals()
right after startup.
Dunno if it's gonna crash again as it has only been a few minutes.

I must say: with RC2 (I think) I've made a roadtrip (on a different machine also) and didn't come across this error. Didn't play any music, only used the navigation, was actually a test (needed to pickup something 300km from home and could use some navigation).

Not much of a help I guess... isn't there a way to intercept that general .net error and have CF log what it was doing or something? Or maybe I could run it through some tracer? I have no .net experience, but I have basic debugging skills

It actually is a lot of help....

try removing the OBDII plugin by deleting the directory in the plugins folder... Then see if you still get the error...

david

Originally Posted by LEiPiE

Cheered too soon I guess...
I've disabled the music autostart, restarted CF and did absolutely nothing and now got this in the errorlog at the moment of startup:
----
9/28/2006 11:56:31 PM
Object reference not set to an instance of an object.
at centrafuse.obdii.resetChip()
----
and CF crashing with the same error after about 20 min of sitting idle...

Trying to reproduce this behaviour, it just resorted to putting in the
Object reference not set to an instance of an object.
at centrafuse.main.loadVisuals()
right after startup.
Dunno if it's gonna crash again as it has only been a few minutes.

I must say: with RC2 (I think) I've made a roadtrip (on a different machine also) and didn't come across this error. Didn't play any music, only used the navigation, was actually a test (needed to pickup something 300km from home and could use some navigation).

Not much of a help I guess... isn't there a way to intercept that general .net error and have CF log what it was doing or something? Or maybe I could run it through some tracer? I have no .net experience, but I have basic debugging skills

I have fixed both the errors you have seen in your error.log as well as made some changes I think were causing the issue... RC4 will be out soon and we will see...

david