Doesanyone know of a workaround that would allow SoundBlaster to be used while BB x1 is installed. Have lost all my sound ability because part of the SoundBlaster software must be disabled in order for X1 to run. Real shortfall of the system.
Not sure what you mean.
the printer will run independently of your computer. in fact you dont even need a computer to run the printer. so how does a piece of computer hardware keep the printer from running?
the printer does not care about your computer.
guess I was not clear. I was not speaking of the printer at all. Just the software used by BB to slice the item. It conflicts with SoundBlaster so you get an error notice. Once you disable SoundBlaster it all works just fine. I did not intend to mention the printer at all in my initial post, surprised I did.
Funny. They are still one of the top rated sound cards in the industry. And no, it does not interfere with any other software. But there was a gentleman on here that experience the same error due to the sound card. Apparently BBL is aware of it because they have a very distinct error notice for it telling you what you must disable.
Seems I can not submit a support ticket as it requires so much information that I can not provide like end date and log files. What a complicated support ticket just to ask a simple question. I can understand why much of it is needed, but to make it mandatory before you can submit a simple question.
For the life of me I can not find BBL on GitHub, even though your link took me to the sign on page. Oh well try something else. Maybe I will just have to build another PC to get sound. For us old farts this stuff is a little complicated. But thanks.
Indeed that is the correct link and it takes me to GH where I have to sign in. I have had a GH account for some time but can not figure out how to navigate it. As for the error msg I can not recall the exact verbiage. Should have taken a screenshot. But it mentioned a particular type of file that was interfering with the initial BBL setup. Found the file and delayed and tge install went fine. Another man on here had the same problem and as I recall he showed an image of tge error. I will look for it and get back to you.
My bad. I got an error message saying that one creative labs file would interfere with the initial setup of my X1when I first unpacked it. I never moved forward to see what it would do if I did not uninstall the soundblaster file, I just uninstalled it and the X1 started just fine. Have not yet tried to reinstall Soundblaster. Will do so soon and see what happens. Another gent had the same problem and spoke of it on the platform.
New to Suse and Tumbleweed, but I love it.
However I am not able to hear any sound as my audio card is a SoundBlasterX G6, connected via USB.
Creative does not have any drivers for this model (has for others though).
We are fortunate to have such an alsa developer (Takashi Iwai) who is also a packager/maintainer for openSUSE as well, so raising a bug report may also get the required attention, although please be aware that driver development sometines takes considerable time and effort, and may involve reverse engineering to get a working driver. (Hopefully, this chipset is similar to other soundblaster devices that are already supported by the snd-usb-audio driver.)
With my limited knowledge on this topic, I can not tell from this thread if the issue is with the USB-driver not supporting the hardware, or if there is a configuration issue. There is a diagnostic script I like having run, which gives more information, and can help lead to even more diagnostic steps.
If I am correct, (based on the above),how about plugging the USB device in BEFORE you boot, and only then boot your PC, and see if that makes a difference? Maybe re-run the diagnostic script in such a case, to see if the dmesg yields anything different.
You got me thinking with the USB staff, and I checked mobo manual. There are two USB controllers, on is 3.0 and the other 3.1. 3.0 is embedded in the X99A chipset, but 3.1 is an external chip, made by ASMedia.
I checked and the card was connected on the ASMedia chip, which is either not recognised by Suse, or it is initialized late, therefore making the card disconnect.
I moved the cable to one of the 3.0 ports, and works like a charm!
Hi. I originally wanted to know why I was having trouble listening to some midi and mp3 files on my new computer, which I had created on MM11 on a different computer. The new computer (Windows 7, 64 bit) has MM17. I copied my old files onto the new computer. Instead of piano on the midi files, it sounds almost like bongos or the harp. Something was very clearly not right. Some vocal mp3 files were just a disaster.
Here's what I figured out. It all depends on where I plug in the speaker cord. If I plug it into the green speaker hole on the back of the processor, I have no trouble at all listening to the mp3 and midi files the way they're supposed to be. BUT, I can no longer record using What U Hear. The audio driver is there, but when I record what I play on youtube, for example, it comes out only as very loud static.
Now if switch the speaker cord from the green hole that's already on the back of the processor to the green speaker hole on the Creative Soundblaster Recon 3D PCIE pcie card, then the What U Hear recording works great, but many mp3 and midis suddenly sound awful, as I described above.
With my old computer with MM11, I'm pretty sure the speaker cord was plugged into the green hole that was NOT in the old soundblaster card. It was in the hole that came standard on the back of the processor. What U Hear worked fine, as did all the mp3 and midi files.
My question is probably obvious by now. What do I have to do so that I can record using What U Hear and also have all my mp3 and midi files function correctly? I can't keep switching the cord back and forth between green holes. Thanks very much.
With all due respect, I don't know any more than I did before. For playback, I do have the realtek HD speakers. MM17 plays the files I made in MM11 when I plug the speaker into the processor's green socket. If there were a synth problem, I would expect that MM17 wouldn't play those files whether I used the processor's green socket or the soundblaster's.
To use the onboard Realtek sound card/chipset for What U Hear recording (and which you gives you the correct playback) you need to follow my instructions in the post I referred to , in order to turn on the Stereo Mixer which is probably disabled. Ignore the rest about the microphone.
For What U Hear recording you use the Realtek Stereo mixer as the source, with your audio input fed into the Microphone or Line in socket on the Realtek card and the speakers plugged in as detailed below. However this can lead to the introduction of echo as I stated below depending on the what and how you are recording.
If all else fails in theory you should be able to use one sound card/chipset for recording and the other for playback - in your case, as the Realtek gives the correct sound, try using this for playback and the Creative for recording.
Also, I have 2 sound cards because when I bought the computer, one was already in there. There was sound, so I'm just assuming that it's because there's a sound card there. When I added the Soundblaster card, that was the 2nd.
Sorry - I didn't comment on your instructions in the post you referred to because I had already made sure that everything was enabled, including Stereo Mix. Quite honestly, I don't know how Stereo Mix relates to What U Hear or any other recording device.
I went into MM17 and saw that it's using Microsoft GS Wave table synth. All drivers have been updated. As far as I know, there are no other audio enhancements. You asked about the THX sound synth. How can I tell if that's turned on?
I have 2 sound cards because when I bought the computer, one was already in there. There was sound, so I'm just assuming that it's because there's a sound card there, which I guess was the Realtek. When I added the Soundblaster card, that was the 2nd.
Hi all,
Just picked up a SB Z card and tried to get it working under Arch with zero success. I can't get any sound out of any of the outputs. It works perfectly under Win10 however so the HW is not the issue.
That's interesting, it does contain the usual, but it never occured to me to omit the ca0132 driver and using the generic HDA, so that might be another interesting bit, though it reads like that wasn't as successful either.
On my system the soundblaster was the onboard card. After a few weeks of attempting to find a working solution I switched to a Xonar DGX (which also was in a sale and also around 30$ coincidentally) and haven't had an issue with that.
Excellent. Just one note... the author told me that the Creative gave him the right to redistribute firmware so it will land in linux firmware at some point around 4.18 release. It might conflict with the one you have now so if you get the error from pacman about it, just delete it and then install the package.
Thanks, I've built the kernel with a custom pkgbase, so it doesn't interfer with the stable -ARCH stock package. It's just a little hassle to rebuild the kernel each time, and rebase the patches on top of the latest stable version.
3a8082e126