Centrafuse RC3.1 Bugs - Page 5

midiwall · 09-25-2006, 06:00 PM

Quote: Originally Posted by veetid

It most likely is... I do set the level for record...

Record? For the buffering I figure?

Hmm, okay, so maybe the issue is that you're setting the _output_ mixer level for MIC/LINE at the same time you're setting the _input_ mixer level for recording. Go ahead and set the INPUT level, but leave the OUTPUT level at the user's setting - or... !

Since you know which _input_ has the XM audio on it, then just MUTE the _output_ for that line. Actually, there's a "nice feature" buried in there... Allow access to individually MUTE the various outputs on the CF mixer. A clickable label called "MUTE" below the level slider would be cool. Or, go one step further and make it a tri-state switch - MUTE/SOLO/LIVE.

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

Quote: Originally Posted by midiwall

Record? For the buffering I figure?

Hmm, okay, so maybe the issue is that you're setting the _output_ mixer level for MIC/LINE at the same time you're setting the _input_ mixer level for recording. Go ahead and set the INPUT level, but leave the OUTPUT level at the user's setting - or... !

Since you know which _input_ has the XM audio on it, then just MUTE the _output_ for that line. Actually, there's a "nice feature" buried in there... Allow access to individually MUTE the various outputs on the CF mixer. A clickable label called "MUTE" below the level slider would be cool. Or, go one step further and make it a tri-state switch - MUTE/SOLO/LIVE.

It is suppose to only be setting the level for the recording input and not touching the output... It's also suppose to be muting the output...

It appears it not working right with your soundcard... What soundcard do you have?

david

midiwall · 09-25-2006, 06:54 PM

Quote: Originally Posted by veetid

It is suppose to only be setting the level for the recording input and not touching the output... It's also suppose to be muting the output...

It appears it not working right with your soundcard... What soundcard do you have?

Ahh right... I guess you've mentioned that before.

It's the stock chip set that's on the motherboard of this machine. From the website, all they say is that it's "SoundBlaster AdLib" compatable. I can lookup the driver info if you think it'll help.

ref: http://www.ezgo.it/E3032SpecEngl.htm

If you're setting the output, but it's "not taking", though the level slider works manually, then is there something different about how the slider works versus what you're doing in INIT?

LEiPiE · 09-25-2006, 07:01 PM

Quote: Originally Posted by veetid

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...

I can now second VMS' findings.
Removed all visuals and using the standard RC3.1 Onyx WS Night skin I let it play while in the Media Screen. After I think 20 min (should have noted the start time

) I got the error again.

edit: also able to get this error with Onyx WS Day, so it's not the skin per se either.

Maximus · 09-26-2006, 04:21 AM

Removing CAM-plugin disables all other plugins.

If I'd remove the CAM-plugin, either trough the menues or manually through the explorer, none of the other plugins are visible or even loaded.
Adding the plugins once again fails without errors, they simply don't show in the list.

When you remove the CAM-plugin through the menues, the other plugins are fully functional until you restart CF.

No errors reported in the error.log file.

/M

holybob · 09-26-2006, 04:32 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

Hi David,

I also received this error. I installed RC3.1 straight after RC2 (I obviously uninstalled everything first....).

You're right - it is the vis which is causing the issue. If I remove the new vis (rabbithole11.svp) from the directory then it doesn't crash.

PS. Great work - this is now looking like a product I'd be happy to part with cash for.

Bob

justintime · 09-26-2006, 07:32 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!

Search google for EXAMXML, download it, and go to the 'compare options' dialog, and set 'ignore contents'. It will compare the structure of the XML files for you.

SOS · 09-26-2006, 10:31 AM

shareware not freeware....

I dont need fancy features, just compare the 2 files in a GUI and allow me to edit either side. Then Im happy

midiwall · 09-26-2006, 10:48 AM

Quote: Originally Posted by SOS

I dont need fancy features, just compare the 2 files in a GUI and allow me to edit either side. Then Im happy

There's always WinDIFF - an oldie, but it still works:
http://www.grigsoft.com/download-windiff.htm

And... CompareIt! and SynchronizeIt!
http://www.grigsoft.com/index.htm

veetid · 09-26-2006, 11:20 AM

Quote: Originally Posted by Maximus

Removing CAM-plugin disables all other plugins.

If I'd remove the CAM-plugin, either trough the menues or manually through the explorer, none of the other plugins are visible or even loaded.
Adding the plugins once again fails without errors, they simply don't show in the list.

When you remove the CAM-plugin through the menues, the other plugins are fully functional until you restart CF.

No errors reported in the error.log file.

/M

This was reported before, but I cannot reproduce.. If I delete the CAM folder manually or through the GUI, I can reload the others just fine...

Who all is having this issue... It has to be a setting...

david

veetid · 09-26-2006, 11:23 AM

Quote: Originally Posted by holybob

Hi David,

I also received this error. I installed RC3.1 straight after RC2 (I obviously uninstalled everything first....).

You're right - it is the vis which is causing the issue. If I remove the new vis (rabbithole11.svp) from the directory then it doesn't crash.

PS. Great work - this is now looking like a product I'd be happy to part with cash for.

Bob

I've gone back to the original visuals... I will have a new release within days... Users might have to do another install because I had to redo a few things relating to the updater, but hopefully I got them all and we will have another updater test later this week...

after this upcoming release, which again will get all known issues fixed, I will focus on finally putting some time towards those XM issues...

david

midiwall · 09-26-2006, 01:03 PM

Quote: Originally Posted by veetid

after this upcoming release, which again will get all known issues fixed, I will focus on finally putting some time towards those XM issues...

justintime · 09-26-2006, 01:11 PM

I checked for updates today, and it says it found one. Although I am already at 0.97.0.2.

Strange!

bowtie4532 · 09-26-2006, 02:20 PM

Mine updated too. Must have changed something. It updated just not sure what got updated.

veetid · 09-26-2006, 02:46 PM

Quote: Originally Posted by bowtie4532

Mine updated too. Must have changed something. It updated just not sure what got updated.

We were running tests... sorry about that... Trying to get the updater nailed down with the reported bugs for the next version...

I thought we disabled it to outside users, guess not

david

User Name		Remember Me?
Password