Hello, I've loaded Samp 6 on a computer running XP, loaded a session, and can't get it to play. Using Dakota soundcard, which works with other apps. Wondering if there's something I need to check or uncheck in preferences. Please let me know if anyone knows something to try. Thanks
Thanks, I've loaded a VIP, all the waves are in, I hit play or spacebar, and nothing seems to play from anywhere in the song. Using latest Dakota drivers and 512 of RAM 1.8 G. Went thru all options to see if something is checked or not but can't seem to find what it is that isn't configured right. the project is 48kHz/32bit, and I don't get an error report, it simply doesn't play. Can you think of anything? Thanks
When you say "doesn't play" do you mean that the cursor in Samp does not move, or that you cannot hear anything through your soundcard? This sounds more like an issue with the Frontier Design card and not a Samp/XP issue. I can assure you that MANY are using Samp with XP. Are all the Dakota I/O listed and recognized in Samp? If you hit "Y", check under the record and playback settings to see that all the Dakota I/O are selected to be used. It may be that they are not checked for use in Samp yet.
When I try to play a single wave or multitrack VIP, the curser doesn't move, and no audio is playing. The bar below where processing progress & mixdown progress shows up does show a quick light load like something is happening on first attempt to play. All 9 pairs of I/O are listed and checked for Dakota within Samp. This same combo works fine in ME and I'm not as familar with XP as to change settings to optimize for audio, and I can't find where to make sure DMA is enabled for the audio drive. Windows Media player reconizes Dakota and plays thru it. In Samp's program settings, Pent III opt is checked, but the computer has Pent 4 - would this be a factor? Thanks again for helping.
Hmm, that is strange. Usually you should get an error message in Samp if the settings do not match your soundcard. Anyway, it sounds like you are making some headway. If it plays fine now at 16 bits, and your original files are in fact 32/48 and it won't play at those settings, then that truly is odd. Do you now have Samp set to 16/48? What converters are you using with the Dakota for playback? I am sure this is a setting or compatibility issue, but difficult to identify. If you continue to have troubles and cannot play the 32/48 files, then I would post the problem at the Samplitude NewsGroup where lots of VERY knowledgable Samp users hang out. I am pretty confident you will figure out the problem with their help. You can access the newsgroup by going to this site and clicking on the "take me to the mewsgroup" link: http://www.sekd.com/service_newsgroup.htm
Thanks so much for your sincere concern, yeah it blows my mind why things aren't the same running on a better machine. At first I thought maybe version 6 was made before XP but after finding out you and others are using it, I searched the archives here and read someone's post about trying setting the device resolution at 16 bits, and I got things to play. I set the clock to internal on Dakota, and I have a Tango 24 in the first bank of lightpipes and set it to optical which reads Dakota's clock with the most recent drivers installed. I also use an ADAT XT20 for a second bank of lightpipe but that isn't an issue in this situation. I have a few projects to work on before I can dig deeper into this, but at least it's workable. If you know any tips or links to info on tweaking XP for audio, please post, as it's different from what I've been using. When work lightens up, I'll probably get Samp 7 demo a try and see what settings will work and just maybe take the plunge and get the full version. Break's over...
I know you said you loaded the latest drivers for your soundcard, but this may be a clue for you. If I install my Delta 66 soundcard with the drivers on the CD, I get the same thing - won't run except in 16 bit soundcard communication. When I load the new drivers it works in 24 bit. So, even though we're talking different cards, and you have the latest drivers installed, it might make sense to go back to their website and do a fresh driver download and install. Also, try removing your old driver first. I know you've ruled this out, but it still sounds like a driver issue. Definitely worth being double sure.
Good luck, RD
I wrote Frontier Design's support and found out that it is a common problem with Dakota when used with early versions of Samp & XP, remedy is version 7 and it's all fine. Thanks again for the replies, just wanted anyone else to know what to do if they have the same problem.