Well..........I've decided that if they won't record at 60kHz, I'm gonna start whining.garyb wrote:unofficially? yes.
Sample rates.....what's up with 88.2?
-
areptiledysfunction
- Posts: 137
- Joined: Tue Oct 17, 2006 4:00 pm
- Location: Durango, CO
-
areptiledysfunction
- Posts: 137
- Joined: Tue Oct 17, 2006 4:00 pm
- Location: Durango, CO
Hey Gary..speaking of Dynatube....I've found this file here calledgaryb wrote:thanks DJ. yes that's a dynatube. p100 reverb too.
Neil-horsepower, yes. i not speaking only about gear, but also about skill. i don't mind giving it up. i still like my mix.
there can't seriously be a right or wrong can there? it all sounds competent.....
dynatube_Bundle_Nokeys.oxe
How/where do I load this up? (sorry, it's 6:00 AM here and this week has already been such a cluster**** that I'm sorta' burned out so I've decided to mix like boiling spagetti and have reverted to throwing stuff against the wall to see what will stick....thing is, I don't want to "stick" this file in the wrong place. Anything that starts with "dyna" sorta sounds explosive and if I have to "R" another "FM" in the next 12 hours I'm going to go postal.)
unless you plan to aquire the Dynatube bundle you can simply ignore the file (or any nokeys.oxe ...
the 'nokeys' just means it doesn't include a 'pre-generated key' for your board's serial number, as it was the case with the former online shop.
the most stupid naming one can imagine...
anyway, oxe-files are installer files which are executed automatically on the next Scope restart (if put in the respective folder).
In this case it would install the Dynatube bundle, but the first time you (want to) use it, a registration dialog with a request string will popup.
That string is to be transferred to CWA via mail. They will generate the corresponding 'real' key, mail it back to you and you'll enter it in that box... where you just copied the 'transfer string' (as it's called) from.
In the meantime you may close the box as the process will need at least a couple of hours, sometimes days - as usual, ...it depends..
It's not as complicated as it reads. Since the devices are registered to the Scope card, you're never bothered again with a new key when changing system etc.
On the other hand it was even easier when the whole process was handled straight online, but unfortunately the procedure is also an invitation for hackers... you could run a key generator against their server, for example...
cheers, Tom
the 'nokeys' just means it doesn't include a 'pre-generated key' for your board's serial number, as it was the case with the former online shop.
the most stupid naming one can imagine...
anyway, oxe-files are installer files which are executed automatically on the next Scope restart (if put in the respective folder).
In this case it would install the Dynatube bundle, but the first time you (want to) use it, a registration dialog with a request string will popup.
That string is to be transferred to CWA via mail. They will generate the corresponding 'real' key, mail it back to you and you'll enter it in that box... where you just copied the 'transfer string' (as it's called) from.
In the meantime you may close the box as the process will need at least a couple of hours, sometimes days - as usual, ...it depends..
It's not as complicated as it reads. Since the devices are registered to the Scope card, you're never bothered again with a new key when changing system etc.
On the other hand it was even easier when the whole process was handled straight online, but unfortunately the procedure is also an invitation for hackers... you could run a key generator against their server, for example...
cheers, Tom
DJ got his dynatube bundle keys with his Scope Home + A16 Special bundle available in the USA (check the allkey for the Scope Home)
DJ >> Simply place the OXE in the OXE file in your
C:\Scope 4.5\App\Oxe
if there is no OXE folder in app simply create one
close Scope and restart it and it will install by itself.
then I suggest to reboot system. and Voila............you got the ......tube
DJ >> Simply place the OXE in the OXE file in your
C:\Scope 4.5\App\Oxe
if there is no OXE folder in app simply create one
close Scope and restart it and it will install by itself.
then I suggest to reboot system. and Voila............you got the ......tube
Ok so back when this thread was on page2 I created a simple 88.2 file synthesized in Wavelab, and attempted to sync my Scope boards to my RME (via adat & bnc both). I got dsp overload errors both times, so I started a new project, removed ALL modules (i/o's etc) and tried again. I got dsp errors again and then Scope refused to do anything else, throwing up dsp errors for anything i did (new project etc).
So, I restarted and now Scope won't run at all. I already tried a reinstall of the Scope software, I ran SiSandra burn-in tests to check ram etc, checked HD and anything else I can think of.
When run, SFP.exe reaches 6,792 K of ram usage and then sits there at 0% cpu usage indefinately. It never shows the Scope logo or any form of error message, or indeed ANYTHING other than SFP.exe showing up in the process list and hanging.
I can't imagine that I fried my boards doing the 88.2 testing, especially since I've noted many times that for some reason the cards actually IDLE at 88.2 (my RME sees 88.2 as the sync input until Scope initializes the cards). That may be due to my RME machine usually being set to 44.1 and the scope cards 'seeing' that somehow and double clocking, or it might just be the hardware's default, i'm not sure.
In any case, unless you guys have any thoughts I think i might have to send the cards to Creamware. Married 2 days ago and $130 left in my savings, what fun. Ah well...I'll just hope someone has an idea I haven't thought of.
So, I restarted and now Scope won't run at all. I already tried a reinstall of the Scope software, I ran SiSandra burn-in tests to check ram etc, checked HD and anything else I can think of.
When run, SFP.exe reaches 6,792 K of ram usage and then sits there at 0% cpu usage indefinately. It never shows the Scope logo or any form of error message, or indeed ANYTHING other than SFP.exe showing up in the process list and hanging.
I can't imagine that I fried my boards doing the 88.2 testing, especially since I've noted many times that for some reason the cards actually IDLE at 88.2 (my RME sees 88.2 as the sync input until Scope initializes the cards). That may be due to my RME machine usually being set to 44.1 and the scope cards 'seeing' that somehow and double clocking, or it might just be the hardware's default, i'm not sure.
In any case, unless you guys have any thoughts I think i might have to send the cards to Creamware. Married 2 days ago and $130 left in my savings, what fun. Ah well...I'll just hope someone has an idea I haven't thought of.
Valis, here's a few things you could check before sending your boards for repair :-
1. Check that you're boards are properly seated incase you de-seated a board slightly when fiddling with cables round the back.
2. PSU (you never know)
3. If you have another HD handy, you could wipe it & do a fresh XP install on it. In this case I'd just disconnect the old HD (after writing everything for a fresh install to cd or dvd), connect the new drive in it's place, Install XP & essential drivers on the new drive, Install SFP etc etc... If all goes well & Scope is working again, plug the old system disk back in & it'll now be a secondary disk which needs a clean up.
Congratulations on getting hitched btw !!!
1. Check that you're boards are properly seated incase you de-seated a board slightly when fiddling with cables round the back.
2. PSU (you never know)
3. If you have another HD handy, you could wipe it & do a fresh XP install on it. In this case I'd just disconnect the old HD (after writing everything for a fresh install to cd or dvd), connect the new drive in it's place, Install XP & essential drivers on the new drive, Install SFP etc etc... If all goes well & Scope is working again, plug the old system disk back in & it'll now be a secondary disk which needs a clean up.
Congratulations on getting hitched btw !!!
Yep. I haven't cracked the case yet and tried the usual internal biz because I was preoccupied with tying the knot this week, but I'm wondering if my 4dsp card finally died. I do hope I can get it working because I had promised to finish my end of development on a certain something that everyone is waiting on over christmas, and without being able to check results in Scope I'll be signing off on the release more or less blindly. 
Ok, when I did my scope 'reinstall' I actually just moved all relevant folders from my Scope 4.0 zipfile into the SFP dir that I already had. I decided to rip the machine apart today & do some troubleshooting, I tested all internal connections with all cards/cpu/ram, did some contact cleaning using some caig deoxit 100% and left all audio card connections unplugged (no external sync etc). Scope still doesn't run, so I decided to reinstall using the Scope installer.
But even the installer doesn't run? I sent an email to Ralf but this is rather odd, and everything else I have installed on that machine runs. The Scope zipfile is a recent download and a fresh extraction, etc. I tried an archive on cdr and had the same thing happen, the installer doesn't run at all. Loads up about 7Mb of whatever and just hangs. I wonder if it's checking the cards before the splash screen is even shown, or if there's something else afoot with my machine & the scope software.
But even the installer doesn't run? I sent an email to Ralf but this is rather odd, and everything else I have installed on that machine runs. The Scope zipfile is a recent download and a fresh extraction, etc. I tried an archive on cdr and had the same thing happen, the installer doesn't run at all. Loads up about 7Mb of whatever and just hangs. I wonder if it's checking the cards before the splash screen is even shown, or if there's something else afoot with my machine & the scope software.
yes that's one of the first things I did (along with the drag & drop of Scope 4.0).garyb wrote:the dumb question..
did you try uninstalling the driver and then reinstalling it?
I've now tried pulling each board in turn and fully removed all Scope drivers, and the system 'sees' both boards on startup & tries to install drivers. I've denied it to see if I could get the scope installer working. Both cards at least seem ok to the OS, yet no creamware exe's seem able to run. I have also removed anything installed recently (only sisandra free for the system testing) and backed out any updates from MS from december. The PSU is 100% solid in terms of fan & what hte bios reports for voltages, only 9 months old and the top line from Enermax (350 or 400W don't remember). I even unplugged the aging zip drive and the plextor burner to make sure that it wasn't a psu issue.
Everything else installed on the box runs fine, including all audio apps although there's no soundcard installed so I can't test actual sound in them. I have older versions of adobe software installed that I sometimes use when printers etc. are having compatibility issues with files I send from the modern apps, as well as various general networking utilities and a few games. Everything else runs fine, and I've even been able to install apps that use typical windows installers.
Still no Scope or Setup.exe. odd.
Time to rebuild windows & see if that has any effect I guess.
I don't like system restore, i always disable it & the dll caching as they have caused me problems with poorly written drivers in the past (MOTU, ATI, behringer etc) among other things. It might have helped me here perhaps, but I think I usually get over 3 years out of an average Xp install these days anyway so I don't mind the speedup I get at that point from a reinstall.Neil wrote:Maybe dumber question... did you try a System Restore, going back to the most recent restore point prior to your problems occurring?garyb wrote:the dumb question..
did you try uninstalling the driver and then reinstalling it?
Neil
In this case I just suspect I'm going to get Xp rebuilt and see the same behaviour. If it was something that seemed typical I probably wouldn't have even posted it up here, but I don't even get a board error or dsp error on startup, or even a splash screen from either Scope or the installer app. I find that odd considering everything else I have here runs fine.
In fact I just tried the Scope 4.0 installer on my main daw without the cards installed, and it runs fine, at least up to the prompt for language. That's the part that baffles me, the system seems otherwise fine but unable to run the Creamware exe's.
Don't rebuild Windoze yet... that sucks & you'd have to reinstall & re-auth everything you have in terms of software. So it thinks it's seeing cards that you've pulled? Weird... Try this first, at least:valis wrote:yes that's one of the first things I did (along with the drag & drop of Scope 4.0).
I've now tried pulling each board in turn and fully removed all Scope drivers, and the system 'sees' both boards on startup & tries to install drivers. I've denied it to see if I could get the scope installer working. Both cards at least seem ok to the OS, yet no creamware exe's seem able to run. I have also removed anything installed recently (only sisandra free for the system testing) and backed out any updates from MS from december. The PSU is 100% solid in terms of fan & what hte bios reports for voltages, only 9 months old and the top line from Enermax (350 or 400W don't remember). I even unplugged the aging zip drive and the plextor burner to make sure that it wasn't a psu issue.
Everything else installed on the box runs fine, including all audio apps although there's no soundcard installed so I can't test actual sound in them. I have older versions of adobe software installed that I sometimes use when printers etc. are having compatibility issues with files I send from the modern apps, as well as various general networking utilities and a few games. Everything else runs fine, and I've even been able to install apps that use typical windows installers.
Still no Scope or Setup.exe. odd.
Time to rebuild windows & see if that has any effect I guess.
* Properly uninstall the CW stuff, your DAW app & everything else audio
* Pull all the Audio-related cards/hardware
* Boot up, & get into the BIOS... set all your PCI slots to "auto" or "plug & play" (depending on how it words it in your BIOS
* Save BIOS & continue the boot sequence... if Windows still "sees" any audio hardware, go to the Device Manager & manually disable those pieces it thinks it still sees.
* Manually uninstall the drivers while you're in Device Manager for those pieces.
* Boot up again... by this time it should be fine. If it is, then..
* Set a System Restore point.
* Install your audio cards
* Boot & go... you can re-set IRQ #'s manually in your BIOS later once everything's back up & set up right.
Neil
Everything's already disable that's not needed in BIOS, and all the general PCI/IRQ optimizations you can think of I did when I built the machine the last time. I also don't use any irq steering or any of the like, I prefer to move cards manually until things are juggled into place since, I trust software steering less than copper steering, so to speak.
I had actually torn it down to no drivers (removed duplicate entries manually even) and no cards installed, then built back up by installing one card at a time etc. When I said 'seeing' the cards I meant I got prompted to install drivers (new hardware wizard) for each card on reboot when I installed each in turn, so the cards at least are responsive to query by windows for their id. I'm really leaning away from an IRQ/PCI/etc error here now since I can't even get the exe's to run.
The audio software I have installed is along the lines of Wavelab/Bidule/audiomulch/PD and various spectral analyzers. Nothing that should impact any of this.
It's possible there's a HD issue but everything else seems fine and scandisk has repeatedly shown nothing, nor did SiSandra. Memory tested fine and stripping down to a single stick had no effect.
Reinstall of xp and then trying the cards in another box seems the only steps I can think of next. Seems strange all this should start with trying 88.2, but I now think it's probably not directly related. should I move to problem solving?
I had actually torn it down to no drivers (removed duplicate entries manually even) and no cards installed, then built back up by installing one card at a time etc. When I said 'seeing' the cards I meant I got prompted to install drivers (new hardware wizard) for each card on reboot when I installed each in turn, so the cards at least are responsive to query by windows for their id. I'm really leaning away from an IRQ/PCI/etc error here now since I can't even get the exe's to run.
The audio software I have installed is along the lines of Wavelab/Bidule/audiomulch/PD and various spectral analyzers. Nothing that should impact any of this.
It's possible there's a HD issue but everything else seems fine and scandisk has repeatedly shown nothing, nor did SiSandra. Memory tested fine and stripping down to a single stick had no effect.
Reinstall of xp and then trying the cards in another box seems the only steps I can think of next. Seems strange all this should start with trying 88.2, but I now think it's probably not directly related. should I move to problem solving?
Is it possible you have some duplicate registry entries now that you've reinstalled certain HW??? Did you check that & manually delete any duplicates?
By the way is this the same machine that has your RME cards on it? If so, RME has a utility that'll automatically clean out duplicate registry entries (but only for RME cerds). It's a freebie & I can see if I can find the link or e-mail you the file.
Neil
By the way is this the same machine that has your RME cards on it? If so, RME has a utility that'll automatically clean out duplicate registry entries (but only for RME cerds). It's a freebie & I can see if I can find the link or e-mail you the file.
Neil