3 ms·

I think you could probably just clone the HDD to an SSD using a Linux live CD and "pv" or whatever and have no issues. I've done that for Windows installs in th

I think you could probably just clone the HDD to an SSD using a Linux live CD and "pv" or whatever and have no issues. I've done that for Windows installs in the past with very little trouble. Only issue I had was expanding the partition on the new drive with the recovery partition in the way.

jacquesm 4y ago
Yes, I see that as one possible avenue. The possible issue with that approach is that the SSD is able to interrupt the OS at a much higher rate than an SSD, which may well increase the throughput of the system as a whole but cause latency issues substantial enough to cause drop outs. These cards run with very small output buffers to reduce their latency and any kind of delay will deplete the buffer resulting in a buffer underrun condition and that manifests as a drop-out in the audio stream. Another alternative is to get rid of the whole kaboodle and do it all in software, that's definitely a possibility with present day gear but I'm kind of partial to this old rig, it sounds great and is very comfortable to work with, much nicer than any pure software solution that I've seen so far.
- password4321 4y ago
  Maybe swap out the drive and see what happens? You should be able to swap back pretty quickly...
  - jacquesm 4y ago
    I may just do that. If anything this thread has given me the push to go and do something about it because the irritation is definitely there.
- eropple 4y ago
  > Yes, I see that as one possible avenue. The possible issue with that approach is that the SSD is able to interrupt the OS at a much higher rate than an SSD, which may well increase the throughput of the system as a whole but cause latency issues substantial enough to cause drop outs. If this is a thing, you are already in burn-it-down territory with your hardware. I've been doing audio for a pretty long time, and I struggle to conceive of a system so marginally-fit-for-purpose-but-still-extant where drive interrupts will threaten audio timings.
  - jacquesm 4y ago
    Indeed, it is pretty dicey the way it is set up. The machine that came with the deck had the software installed, a broken firewire card, no installation media. Getting it to work was incredibly tedious and I don't doubt that it is a very fine line between success and failure but work it does, no registered drop outs across many, many hours of working with all audio channels live. If it wasn't for the firewire requirement this would be a very easy problem to solve. I don't understand why that standard is now so blacklisted that it isn't even supported any more by more modern incarnations of windows. Good article on the subject: https://arstechnica.com/gadgets/2017/06/the-rise-and-fall-of-firewire-the-standard-everyone-couldnt-quite-agree-on/ https://arstechnica.com/gadgets/2017/06/the-rise-and-fall-of...

jacquesm 4y ago

Yes, I see that as one possible avenue. The possible issue with that approach is that the SSD is able to interrupt the OS at a much higher rate than an SSD, which may well increase the throughput of the system as a whole but cause latency issues substantial enough to cause drop outs. These cards run with very small output buffers to reduce their latency and any kind of delay will deplete the buffer resulting in a buffer underrun condition and that manifests as a drop-out in the audio stream. Another alternative is to get rid of the whole kaboodle and do it all in software, that's definitely a possibility with present day gear but I'm kind of partial to this old rig, it sounds great and is very comfortable to work with, much nicer than any pure software solution that I've seen so far.

password4321 4y ago
Maybe swap out the drive and see what happens? You should be able to swap back pretty quickly...
- jacquesm 4y ago
  I may just do that. If anything this thread has given me the push to go and do something about it because the irritation is definitely there.
eropple 4y ago
> Yes, I see that as one possible avenue. The possible issue with that approach is that the SSD is able to interrupt the OS at a much higher rate than an SSD, which may well increase the throughput of the system as a whole but cause latency issues substantial enough to cause drop outs. If this is a thing, you are already in burn-it-down territory with your hardware. I've been doing audio for a pretty long time, and I struggle to conceive of a system so marginally-fit-for-purpose-but-still-extant where drive interrupts will threaten audio timings.
- jacquesm 4y ago
  Indeed, it is pretty dicey the way it is set up. The machine that came with the deck had the software installed, a broken firewire card, no installation media. Getting it to work was incredibly tedious and I don't doubt that it is a very fine line between success and failure but work it does, no registered drop outs across many, many hours of working with all audio channels live. If it wasn't for the firewire requirement this would be a very easy problem to solve. I don't understand why that standard is now so blacklisted that it isn't even supported any more by more modern incarnations of windows. Good article on the subject: https://arstechnica.com/gadgets/2017/06/the-rise-and-fall-of-firewire-the-standard-everyone-couldnt-quite-agree-on/ https://arstechnica.com/gadgets/2017/06/the-rise-and-fall-of...