RebornOnline
New Member
The device and its driver are provided by Creamware. Creamware Audio GmbH was a DSP-based sound card and synthesizer manufacturer. These cards create synthesized sounds that are used in the production of audio for music and other audio environments. Gateway W340ui Sound Drivers Windows Xp Estimating Costing And Valuation By Rangwala Pdf Iuvcr Serial. Sonic Core Scope V5 Keygen Crack How to Update Gateway Device Drivers Quickly & Easily. EMACHINES T6528 ETHERNET DRIVER DOWNLOAD - Fcc Declaration Of Conformity Using The Start Menu Audio Output Sound Output Mode. High-speed drivers for ASIO 2.0, DirectSound, MME, tripleDAT, GSIF, Sound Manager, OMS MIDI interface (in & out) A16 ADAT/-Analog Converter With 16 analog inputs and 16 analog outputs the combination of a SCOPE PCI card with a Sonic Core A16 AD/DA converter is the ideal solution for multitrack-recording. Highlights of the A16.
- Joined
- Jan 15, 2012
- Messages
- 4 (0.00/day)
| Processor | i920 |
|---|---|
| Motherboard | ASUS P6T-SE |
| Cooling | Intel |
| Memory | Corsair DDR3 |
| Video Card(s) | Asus EAH4850/512/DVI |
| Storage | 6xWD650 |
| Audio Device(s) | Creamware/Sonic Core Scope PCI |
Hi All,
I came here via Google, trying to find a way to hack my 4850 to get rid of the audio device.
To cut a long story short, the audio device is causing a hardware level (i.e. it looks fine in the os) IRQ conflict with my PCI sound card.
I've tried every PCI/PCIe combination, no matter what I do, either the VGA or 'Multimedia Device' are conflicting with my sound card. The end result is that when running audio software (like Cubase) my PC crashes after a while, faulting module is usually the sound card driver.:shadedshu
If I stick on an old ATI x1300 then it all works fine. I can stick with the x1300, but I do like to game every now and again.
Now, my card is the DVI version, so I'm not using any HDMI connectivity at all and the HD Audio on the card is totally surplus to requirements. I know I can disable the driver in the OS, but this won't stop the underlying conflict.
So what I'm really hoping is that there is some way to hack the firmware to totally disable the HDMI / HD Audio device so that it doesn't pick up the IRQ line.
I saw the RBE software, which looks awesome, but I don't think it can do this (might add this to feature suggestions)
So guys, is this possible do you think?
Thanks!
I came here via Google, trying to find a way to hack my 4850 to get rid of the audio device.
To cut a long story short, the audio device is causing a hardware level (i.e. it looks fine in the os) IRQ conflict with my PCI sound card.
I've tried every PCI/PCIe combination, no matter what I do, either the VGA or 'Multimedia Device' are conflicting with my sound card. The end result is that when running audio software (like Cubase) my PC crashes after a while, faulting module is usually the sound card driver.:shadedshu
If I stick on an old ATI x1300 then it all works fine. I can stick with the x1300, but I do like to game every now and again.
Now, my card is the DVI version, so I'm not using any HDMI connectivity at all and the HD Audio on the card is totally surplus to requirements. I know I can disable the driver in the OS, but this won't stop the underlying conflict.
So what I'm really hoping is that there is some way to hack the firmware to totally disable the HDMI / HD Audio device so that it doesn't pick up the IRQ line.
I saw the RBE software, which looks awesome, but I don't think it can do this (might add this to feature suggestions)
So guys, is this possible do you think?
Thanks!
Error in Max8 window: ad_asio: ASIO Stop() returned -997
Hello Maxers. I get this errors messages in Max Window as soon as I launch MAXad_asio: ASIO Stop() returned -997 when using my sound card
ASIOCreateBuffers error -997when using my default Alienware sound card
I do not get these messages in the last version of Max 7.
Hello, I am using Windows 10 and Max 8.01 ( the last Max version now). in an alienware computer. I am also using a RME 802 audio interface. All my Windows and soundcard drivers are up to date. Any ideas about how can I fix it?
Sonic Core Sound Cards & Media Devices Drivers
- I haven't wirked with Windows/ASIO since many years, but does your sound cards work with other software? That it fails with both cards may hint to a system problem....
- Yes, they work fine with other software. I can use audio in Max, the only thing that I can not do is recording audio when I try to record my screen using GeForce Experience which is a software to record OpenGL graphics, i.e video games. ( I need to do this to record my Jitter performances).The same software (GeForce Experience) can record audio in Max7 and also in video games so I assume that the problem is not WIndows 10 or GeForce Experience . Since Max window is displaying an error it is possible that it will be the problem.
- Same here. Just dropped a mail to the support team, hopefully they will come up with a solution...
- I have the same error messages:ad_asio: ASIO Stop() returned -997with the ZOOM UAC2ad_asio: ASIO Stop() returned -1000with the RME HDSPe Expresscard
- Following, Im also having issues with ASIO and Max8. I'm not a regular Windows user, so I just thought it was a hardware issue.
- ad_asio: ASIO Stop() returned -997 RME Babyface ProDriver: ad_asio ASIO Fireface USBThe issue also appears when I select ad_asio ASIO4ALL v2.It does not appear when I select ad_portaudio ASIO and select ASIO Fireface USB as my input.
- I've opened a support ticket, too - the problem with these ASIO error messages is, there is or has been no real reproduceable effect regarding audio processing so it's hard to trace it down. Maybe there is one now as described below.I've experienced the same restart problem with two complex standalone MAX applications - logelloop5 and MSDP2 running on Windows 10 1809:If I have my ASIO devices connected I can run the app only one time - if I close/quit I cannot restart the app until I restart the computer. A second attempt to start the app after having closed/quit the app results in a hang and within the Task Manager or Process Explorer it is visible that the app is not loading RAM anymore, not as much as during the first start. If I disconnect the ASIO devices and choose the ad_portaudio mme driver there is no such problem.The mentioned standalone applications are available for download. MSDP2 is free and the sources are available here: https://github.com/MusicSDP/source-codeBecause MSDP2 sources are available I was able to test it and the problem described above is existing in case of running the patch from the sources, too.To check if the ASIO Stop() error messages reported in this thread are related to the 'restart problem' I've described it would be cool if some other ASIO device users which are experiencing the error messages this thread is about could check if they are having the same problem with e.g. MSDP2 or logelloop5. It would be also of interest if some ASIO device users not seeing the ASIO Stop() error messages are having the 'restart problem', too. With the MSDP2 sources the 'restart problem' exists only if the main patch and MAX is closed via the menu entry Exit, it does not exist if the button 'Close this patch' is used.Cheers
- The runtime application restart problem is solved so far but MAX is still printing the error messages. I have reinstalled both ASIO drivers and I have selected on board HD Audio Device as the systems default audio device, instead of the UAC 2 or the RME. Thus even if these ASIO error messages are still printed to the MAX console both applications mentioned above are restarting just fine.
- Hi everyone,I have the same error message, with the lastest version (8.1). Does someone have a solution?
- Hi there. The same with me (I'm using a Sonic Core Scope PCI audio card).