Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption

Author
Beepster
Max Output Level: 0 dBFS
  • Total Posts : 18001
  • Joined: 2012/05/11 19:11:24
  • Status: offline
2015/04/04 14:40:22 (permalink)

Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption

Hi, all. Everythings fine (I think). Just had a couple things happen a while back and wanted to pick your brains before I forgot.
 
1) I had exported a wav out of Sonar Platinum. It was just intended to be a song segment but it ended up being longer than I wanted (I screwed up). So instead of reimporting/starting a new project I figured I'd snip it down in Pyro Audio Creator. I opened the wav with Pyro (this was maybe thirty seconds or so after closing Sonar) and began playback. I immediately experienced a Blue Screen o' Death. I have never had one of those before (or since) so just wondering what may have been the culprit. I'm guessing the audio driver/interface went screwy somehow but Beeped if I know what happened. I ain't no tech.
 
2) I was recently working on a CWB that was not really ideal but was working more or less okay until I did some Loop Recording. It was created in SPlat and I was recording into SPlat. After I did a bunch of passes with Record and Looping enabled (which recorded fine) the project started acting funky. Timeline started turning black (the white overlay graphic disappeared), Playback would not start reliably, started getting Audio Engine dropouts, etc. I kept closing the project hoping that would help, it didn't. I rebooted, that didn't help. Eventually the project became unusable. This was audio being recorded (guitar stuff) and they were just scratch/practice tracks so no biggie. I reverted back to an earlier version and rerecorded without Loop on and everything was fine (more or less). I never really use Looping while recording because it caused me problems in the past (in X2) and the symptons were similar. I've read about Loop record issues but they seem to be about MIDI stuff and things going out of sync. Just wondering if Loop Recording is causing anyone else any problems and if so what kind of solutions have been found. I'm more interested in diagnosing potential system/stupidity issues than actually using Loop Record because I'm fine with pressing R... I was just doing somehting specific where looping was beneficial.
 
Anyhoo... no emergency. All in all everything has been working fine so far with SPlat. I'm just curious.
 
Sorry I haven't been around the past few days and I may not reply right away. Haven't been logged in because I'm not feeling well and am kind of preoccupied but will be watching and hope eveyone is well.
 
Cheers.
#1

4 Replies Related Threads

    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re: Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption 2015/04/05 10:47:27 (permalink)
    The "Blue Screens of Death" are always caused by these 2 things. Drivers or Hardware failure.
     
    Could it be a coincidence that some sort of hardware in your PC is just showing sings of failure when you are using those 2 software programs? Yea, it could be, but I would rule out Drivers first, then start ruling out your Hardware.
     
    CJ

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #2
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption 2015/04/05 14:19:05 (permalink)
    I'm thinking there was some kind of interface (or maybe a combo of interface and onboard) driver freakout when I closed Platinum and then opened up Pyro. As I said I'm no tech but obviously peruse many forums and have seen these issues mentioned (but don't really understand them).
     
    I did also recently change my video display settings and updated my Korg padKontrol drivers. Other than that, and installing Platinum, there have not been any changes to the system and I used to be able to switch between Sonar (X2/X3) without issues (but could not have both running because I have everything set to ASIO).
     
    I'm doing some work (in between being a sick weirdo) but after that is done I'll be doing some hardcore maintenance or perhaps a full reinstall of everything. I really hope this isn't a hardware issue. That would blow.
     
    Thanks and...
     
    Cheeeeeers.
    #3
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption 2015/04/05 14:32:27 (permalink)
    And just for reference...
     
    ASUS PZ Pro series MOBO (I'll update with the exact model later but it's one of those fancy high end ASUS boards from a few years ago)
    16 GB Corsair Vengeance DDR3 RAM
    7200 rpm HDD (C programs 500gb, E storage 1TB) Can't remember if I got Cav Blacks or Barracudas (I always forget which but they're nice... again I'll update once I get at my records)
    Gigabyte GEforce 210 NVIDIA
    Intel i7 2600k (not overclocked or anything weird)
    Focusrite Scarlett 18i6
    Korg padKontrol (mentioning it because I just updated the drivers but it was not in use)
    Win7 64
    X1 Prod Suite, X2 Pro, X3 Pro, Sonar Platinum Braintree, latest release of Pyro Audio Creator (unless they've updated it in the past year which is doubtful)
     
     
    Only things I've updated recently are the Korg drivers, Windows (about a month ago), Microsoft Security Essentials. The DAW remains offline 99% of the time unless I'm updating Windows and MSE (but occasionally do certain other things on secure sites that are trusted and I keep the system locked down like a drum when I do).
     
    I could go on but whatever... that's more sys specs than is usually presented. I will provide more as needed.
     
    Really though this seemed to be an isolated incident. If it persists or I experience other issues it's nice to have it doc'd amongst the braintrust here.
     
    Cheers.
     
    Oh and still wondering if the Loop Record thing is common. As I said it used to do dumb crap in X2 and I pretty much abondoned it. Audition tends do do stupid crap as well but not corruption.
    #4
    pwalpwal
    Max Output Level: -43 dBFS
    • Total Posts : 3249
    • Joined: 2015/01/17 03:52:50
    • Status: offline
    Re: Twofer: 1) Got a BSOD after closing SPlat then opneing Pyro 2) Loop Record corruption 2015/04/07 05:58:39 (permalink)
    thoughts regarding (1) does pyro behave itself usually? (i never used it, i have the sony apps)... are you set to "share drivers" in sonar? did you try & repro? could sonar have been still "shutting down in the background" when you launched pyro? etc
    good luck

    just a sec

    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1