Centrafuse RC3.1 Bugs - Page 4

midiwall · 09-24-2006, 07:10 PM

Quote: Originally Posted by justintime

I don't think it was necessary to put a NO GUI flag on the application setup dialogs...

When you set up NON-GUI apps, you leave out the window name param

Seconded!

Updates..

Quote: Originally Posted by veetid

SAPI is setting your mic level at 50 based on how you trained your profile, do you have voice enabled?

I doubled checked... I don't have voice enabled anywhere in CF. No prompts, not in Nav, no voice control.

Quote:

My startup location rights fine on 4 different machines and noone else has reported this...

I have a repro, and it doesn't involve restarting CF.

Settings
General
Setup
RIGHT arrow
Startup location
Pick a plugin, not a function. "TRAFFIC" will show the bug
OK
Save
Yes
Go back to Setup (no restart required)
RIGHT arrow
Note "Startup location" is blank.

veetid · 09-24-2006, 11:16 PM

Quote: Originally Posted by midiwall

Seconded!

Updates..
I doubled checked... I don't have voice enabled anywhere in CF. No prompts, not in Nav, no voice control.

I have a repro, and it doesn't involve restarting CF.

Settings
General
Setup
RIGHT arrow
Startup location
Pick a plugin, not a function. "TRAFFIC" will show the bug
OK
Save
Yes
Go back to Setup (no restart required)
RIGHT arrow
Note "Startup location" is blank.

non-GUI flag removed, no window name I assume non-GUI plugin...

The MIC getting set to 50 might be because you have it set as your line-in device for XM or Radio... I set this level because if users have it too high and don't know to adjust it, which they can adjust later through the mixer, then the sound is distorted... I guess I should remeber where you set it and save it maybe... Is it causing an issue?

You are right... I wasn't testing with a plugin/web link... I will get this fixed...

david

hatton920 · 09-25-2006, 05:36 AM

David nav searching is taken longer again in this release.

VMS · 09-25-2006, 08:28 AM

Quote: Originally Posted by veetid

I have one other person who has received this bug, I have to track it down... The only thing I changed was add that new visual... Try removing all the visuals from the visuals folder, back them of first of course, then try to reproduce as hard as you can...

If it does not happen again then it's simply that new visual I added, hopefully... That is the most generic .NET error possible and leads me no where to find the solution, I hoping it's just the new visual I added...

Let me know...

david

Not the visual, i've just deleted all the vis and still got the error, i think its in the skin.

midiwall · 09-25-2006, 10:09 AM

Quote: Originally Posted by veetid

non-GUI flag removed, no window name I assume non-GUI plugin...

Thank you!

Quote:

The MIC getting set to 50 might be because you have it set as your line-in device for XM or Radio... I set this level because if users have it too high and don't know to adjust it, which they can adjust later through the mixer, then the sound is distorted... I guess I should remeber where you set it and save it maybe... Is it causing an issue?

Yes, it definitely is. THIS is the cause of my reported issues with the audio from (my) XM "doubling", i.e., I hear the direct playback from the XM receiver (via the MIC input) and the delayed playback from the WAV output.

fwiw, it's happening on return from hibernate as well. i.e., not just on CF startup.

veetid · 09-25-2006, 10:14 AM

Quote: Originally Posted by midiwall

Thank you!

Yes, it definitely is. THIS is the cause of my reported issues with the audio from (my) XM "doubling", i.e., I hear the direct playback from the XM receiver (via the MIC input) and the delayed playback from the WAV output.

fwiw, it's happening on return from hibernate as well. i.e., not just on CF startup.

So it just doesn't set it to 50, but actually un-mutes it? It should be getting muted...

I will check it out...

david

veetid · 09-25-2006, 10:15 AM

Quote: Originally Posted by VMS

Not the visual, i've just deleted all the vis and still got the error, i think its in the skin.

The one guy who fixed it was using an old skin... If you are using the default skins in RC3.1, those will not be the problem... If you try to use any non RC3 skin it will fail for sure...

david

ont · 09-25-2006, 10:36 AM

david,
is there a posibility to let me know what I need to change in my skin's xml to make it compatible with rc3? I just don't want to completly rework the xml to fit every CF release, just so that this bug does not happen!

veetid · 09-25-2006, 11:31 AM

Quote: Originally Posted by ont

david,
is there a posibility to let me know what I need to change in my skin's xml to make it compatible with rc3? I just don't want to completly rework the xml to fit every CF release, just so that this bug does not happen!

just run a compare against the files... there were hardly no change from RC2 to RC3, but if yours goes back to RC1 there were some changes...

check the image folders, there are a few new images...

any simple XML file DIFF program will let you know what changed...

david

midiwall · 09-25-2006, 12:18 PM

Quote: Originally Posted by veetid

So it just doesn't set it to 50, but actually un-mutes it? It should be getting muted...

I will check it out...

Just to be sure we're on the same page about this...

When you say "unmute", I'm thinking that you mean in the Windows mixer, right? If so, then yes. If there's some sort of a mute function within CF itself, then I don't know about it.

veetid · 09-25-2006, 01:37 PM

Quote: Originally Posted by midiwall

Just to be sure we're on the same page about this...

When you say "unmute", I'm thinking that you mean in the Windows mixer, right? If so, then yes. If there's some sort of a mute function within CF itself, then I don't know about it.

basically when you set your XM line-in channel Centrafuse is suppose to mute it for you, so it wouldn't matter if it was at 50 or 0 or whatever... It's all about the recording section of the mixer, which I also set and auto select so I can record into the buffer and playback through Centrafuse...

This gives the pause/play/rewind and the ability to modify the XM sound with the EQ...

I guess it's not muting for you for some reason, it does on my M10000, but I have it on my list to look into...

I also think I found a way to speed up the XM channel changing

I just have to setup all my XM hardware and get back into XM mode and get all those XM bugs knocked out...

david

bowtie4532 · 09-25-2006, 03:36 PM

My Line In is going to 50 when I go to XM and it is distorted. I am not getting doubling, just too loud. I have to go to the Mixer and turn down the line in and that fixes it, until I go back in to XM and the line in goes right back to 50 and the distortion is back.

midiwall · 09-25-2006, 03:43 PM

Quote: Originally Posted by bowtie4532

My Line In is going to 50 when I go to XM and it is distorted. I am not getting doubling, just too loud. I have to go to the Mixer and turn down the line in and that fixes it, until I go back in to XM and the line in goes right back to 50 and the distortion is back.

Hmmm...

David, I wonder if this _isn't_ SAPI related, but is more directly tied to which line the XM module is expecting input on?

veetid · 09-25-2006, 04:39 PM

Quote: Originally Posted by midiwall

Hmmm...

David, I wonder if this _isn't_ SAPI related, but is more directly tied to which line the XM module is expecting input on?

It most likely is... I do set the level for record when you use Radio or XM... I guess I should make this configurable or maybe remember what you set in the mixer...

Let me think on it...

david

bowtie4532 · 09-25-2006, 04:52 PM

Yeah make it remember what I set it on would be the best for me. That is the only problem that I am having. Keep up the good work David!