|
Post by gouge on Apr 23, 2015 8:41:04 GMT -6
that's my story too svart.
other than forgetting plug something in to the insert on the desk and loosing the signal flow I've had no issues with reaper and pc and i use it the same way as you but with lynx. pcie. before that was maudio delta on pci and PC. no bugs in that system at any point.
i know it's not much help to you john but it does help to know that there are options out there that have no bugs.
|
|
|
Post by Johnkenn on Apr 23, 2015 8:42:03 GMT -6
I also need to label cables...good lord
|
|
|
Post by gouge on Apr 23, 2015 8:42:08 GMT -6
I love the Spanish inquisition New band? monty python. grew up on a solid diet of British comedy.
|
|
|
Post by Johnkenn on Apr 23, 2015 8:42:33 GMT -6
start the session in Cubase - opened it up and immediately experienced a cubase bug that I've had since the SX days: Record enable can't be turned off on the first track of the session Should have stayed on Pro Tools Guess what I used to track? PT.
|
|
|
Post by tonycamphd on Apr 23, 2015 8:51:12 GMT -6
When Winetree and I did our little shootout, it was TOTALLY one of those days, from unruly safes to buzzing mics, snags galore!
|
|
|
Post by donr on Apr 23, 2015 9:13:47 GMT -6
I hate it when you can't figure out why something DAW related doesn't work the way it's supposed to.
|
|
|
Post by matt on Apr 23, 2015 12:48:04 GMT -6
Two Saturdays ago, I couldn't get MIDI working between the DM10X drums and BFD. Nothing worked. I ended up abandoning the current session in PT and creating a fresh one. Fixed - after 2 hours of moaning/groaning. It was brutal.
|
|
|
Post by Ward on Apr 23, 2015 20:36:27 GMT -6
svart... 8. Delete preferences files. 9. Delete settings files. 10. Move all plugins to a folder you create and name that folder "system 8". Then restart. Move plugins (one at a time) back into plugin folder with the DAW running. Once all are back in, and providing the DAW doesn't crash. Restart.
|
|
|
Post by svart on Apr 24, 2015 9:44:37 GMT -6
I replied to this thread yesterday and last night while recording I started having some issues.. Random dropouts of random channels. It only happened a couple times during the night, but damned if I could figure out why. It seemed like no sooner did I start tracking one issue, it went away and another popped up.
At least one of the problems was tarnish on a cable I think. Not sure what one of the other issues was. it seemed that I was getting no signal from the internal streams between Reaper and SSL Mixer but I rebooted and it kept happening and finally went away after a couple minutes.
|
|
|
Post by Johnkenn on Apr 24, 2015 10:15:16 GMT -6
LOL - Karma is a bitch.
|
|
|
Post by unit7 on Apr 24, 2015 10:41:09 GMT -6
A friend gave me this for my 50th BD. It's real embroidery from a 300 year old (swedish?) tradition, usually with quotes from the bible. This translates 'But...why isn't there any sound?' My friend obviously heard me say that a few times (too often). Attachments:
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 24, 2015 13:14:38 GMT -6
Hahaha, that's great, Paul! One of that quotes too many people heard from me too often!
|
|
|
Post by darlenelash on Mar 8, 2017 1:21:53 GMT -6
|
|
|
Post by stratboy on Mar 8, 2017 5:25:24 GMT -6
Welcome to RGO, darlenelash.
|
|
ericn
Temp
Balance Engineer
Posts: 14,957
|
Post by ericn on Mar 8, 2017 7:15:46 GMT -6
Welcome to our little corner of the internet, hope to see more of you!
|
|
|
Post by subspace on Mar 8, 2017 8:01:38 GMT -6
I can't say I've had too many issues like this, being mostly OTB and on PC, but I've had a strange issue happen twice over the last 2 years that I can't explain. I use reaper as my DAW, but I don't use any of it's routing options. I set up the streams for each channel and then that's it. My SSL MX4 DSP card runs a software mixer that allows the SSL routing and plug-ins to run on DSP chips rather than on the CPU. Extremely low latency and system usage! Anyway, I have a full digital routing system built in SSL Mixer so that I can route my streams and split out headphone mixes to be sent to the headphone pods. The problem I had was that the inputs for the first 8 channels to the SSL Alphalink seemed to get feedback from the outputs and it would go full scale digital noise on just those first 8 channels. It would not show this on the SSL Mixer channel strips at all. The other channels were fine. So, this being in the middle of a session, I tell the band to go get something to eat while I figure it out. 1. Close softwares and restart.. Same problem. 2. Reboot computer.. Same problem. 3. Reboot Alphalink AND computer.. Same problem. 4. Check connections to Alphalink and computer.. Same problem. 5. Load in fresh SSL Mixer profile.. Same problem. 6. Start new Reaper project.. Same problem. 7. Turn whole studio off for 5 minutes, let everything power down and reboot.. Same problem. So I'm sitting there with all this noise going, the band walks in from dinner. I'm like "well, I have no idea what's going on, I guess my converter box went bad" and no sooner do I say this and the noise stops and doesn't come back. And it hasn't come back in 4 months. It did this last year when I first got everything together and was working out the workflow bugs, but it went away after a few minutes and hadn't happened again until this last time. I have no idea what caused it. I took my alphalink apart, checked all the connections, solder joints, opamps, etc. Everything looks A-OK with it. I suspect some kind of firmware/software bug that happens with some specific combination of things happening. That's about it for anything within the last 6 years or so. Before that I had my previous computer get a little iffy once, it turned out the power supply was starting to go bad, and the power was dirty/low. It finally refused to boot one day and a new supply was installed and all the strange problems I had prior went away. I realize this was two years ago but per chance was this feedback on the first eight channels of an AlphaLink unit? Manifested by full scale pegged meters and white noise? Just wondering...
|
|
|
Post by rocinante on Mar 8, 2017 8:38:34 GMT -6
2 of my neve pres have failed. Or was it the mic? It was both! But then they worked. Oh the panic as im bugging out cause both mic pres are definitely dead. But no its the mic! Holy shit is it the converter? No thats fine and now the mic pre seems to be working. But the fucking mic isnt picking up the guitar. And this customer is being really nice and helpful and i feel like i must look like one of those: "just got a keyboard and fucking ableton and fruity loops and so now i am an engineer" schmucks. And so i shut it down and it comes back on and everythong works. Until next time. And there was a next time. And no the fucking 'force' was not with me.
|
|
|
Post by svart on Mar 8, 2017 10:41:41 GMT -6
I can't say I've had too many issues like this, being mostly OTB and on PC, but I've had a strange issue happen twice over the last 2 years that I can't explain. I use reaper as my DAW, but I don't use any of it's routing options. I set up the streams for each channel and then that's it. My SSL MX4 DSP card runs a software mixer that allows the SSL routing and plug-ins to run on DSP chips rather than on the CPU. Extremely low latency and system usage! Anyway, I have a full digital routing system built in SSL Mixer so that I can route my streams and split out headphone mixes to be sent to the headphone pods. The problem I had was that the inputs for the first 8 channels to the SSL Alphalink seemed to get feedback from the outputs and it would go full scale digital noise on just those first 8 channels. It would not show this on the SSL Mixer channel strips at all. The other channels were fine. So, this being in the middle of a session, I tell the band to go get something to eat while I figure it out. 1. Close softwares and restart.. Same problem. 2. Reboot computer.. Same problem. 3. Reboot Alphalink AND computer.. Same problem. 4. Check connections to Alphalink and computer.. Same problem. 5. Load in fresh SSL Mixer profile.. Same problem. 6. Start new Reaper project.. Same problem. 7. Turn whole studio off for 5 minutes, let everything power down and reboot.. Same problem. So I'm sitting there with all this noise going, the band walks in from dinner. I'm like "well, I have no idea what's going on, I guess my converter box went bad" and no sooner do I say this and the noise stops and doesn't come back. And it hasn't come back in 4 months. It did this last year when I first got everything together and was working out the workflow bugs, but it went away after a few minutes and hadn't happened again until this last time. I have no idea what caused it. I took my alphalink apart, checked all the connections, solder joints, opamps, etc. Everything looks A-OK with it. I suspect some kind of firmware/software bug that happens with some specific combination of things happening. That's about it for anything within the last 6 years or so. Before that I had my previous computer get a little iffy once, it turned out the power supply was starting to go bad, and the power was dirty/low. It finally refused to boot one day and a new supply was installed and all the strange problems I had prior went away. I realize this was two years ago but per chance was this feedback on the first eight channels of an AlphaLink unit? Manifested by full scale pegged meters and white noise? Just wondering... Yes, that's pretty much the issue. Turns out that it's the data cable that runs between the analog and digital boards. If you take the top off and wiggle the cable, you will likely be able to induce the problem. I removed the socket and soldered the wires directly and the problem went away for the longest time. It did return once and I wiggled the wire and it stopped. I then squeezed the connector on the other end very tightly and the issue stopped again. Next time it happens I'll cut the cable and solder the other end directly too.
|
|
|
Post by subspace on Mar 8, 2017 13:04:35 GMT -6
I don't actually have an AlphaLink, but this flaw goes back to the Soundscape I/O as well as Mackie-badged SDR24/96, all using the Sydec I/O boards. I encountered it on the SDR 15 years ago or so and got a factory fix, but I'll keep your post in mind when it rears it's head again, thanks!
|
|
|
Post by svart on Mar 8, 2017 16:33:35 GMT -6
I don't actually have an AlphaLink, but this flaw goes back to the Soundscape I/O as well as Mackie-badged SDR24/96, all using the Sydec I/O boards. I encountered it on the SDR 15 years ago or so and got a factory fix, but I'll keep your post in mind when it rears it's head again, thanks! Interesting! My first alphalink(serial #3 in the USA) didn't exhibit this problem in the 7 years I used it, however my second one had this problem within 3 months.. Support was just like "send it in and we'll look at it" with no real timeframe for repair. Since I needed it to work, and the problem was initially so rare, that I just toughed it out until it got so bad that I had to figure it out.
|
|
|
Post by ChaseUTB on Mar 9, 2017 0:46:51 GMT -6
Yes trying to configure my buddies CR and monitoring and for some reason even with the monitors connected via analog somehow when switching to L/R or Out 1-2 playback cuts off. Then you get a bluretooth warning and if you restart the Bluetooth the c24 shuts down and won't communicate with PT even tho the AD still passes analog signal into PT ( mic -> pre -> AD -> PT ) but you lose playback and monitoring again. Then i follow the patchbay and reseat some of the connections and now the same input that just had signal into PT that was recording fine has no input, nothing entering PT...
So then I close without saving and the monitoring comes back, the PT input is good but now the AD is showing a multed input. I save as and label it " u87 multed input into channels 1&3 ". Exit and shut down power down completely. Wait a minute or 5 then reboot and power up. Now the Bluetooth can't communicate with the c24 ( never figured out why it needed fukn Bluetooth either ) and there is no playback audio. I go into the I/o settings menu and rest everything to default and of course it went right back to that stupid 1-3 output playback instead of L/ R or 1/2 ( whatever you main mon outputs are labeled ) and we had playback again. Then I narrowed down the PT input issue that was inputting a mult basically to ch 1 & 3 and turns out someone had plugged the output of 1 into input 3 so when ch 1 gets signal so does 3. So that got changed for the better.
Of course now I'm setting up templates, and the beach ball just out of nowhere kept stalling and spinning... every mouse move turned into an ordeal of a spinning beach ball while mutter is this gone be the time it crashes. So I. Save as , quit PT, turn off, power on, reopen PT and everything was working.
Then I go to setup a mixing template and somehow the aux bus availability is all messed up because somehow the aux are bussed to active outputs, therefore the Aux bus is in use rendering mine useless.. So then I had to go one by one and delete every single aux bus that was mapped to an output. I could not default cuz that would have thrown off playback and routing I already setup. Then I had to go thru the rest of the I/O menu and make sure nothing else was double routed via SW as well as crawl back under the desk to check the physical connections.
Beach ball from hell every fifteen dam seconds, it spins for ten seconds, then stops... finally after another save as and a restart everything seemed to be normal, other than I could never get signal to the compressor and back even though I had it physically connected and reseating then changing the Cables as well as tried a couple different pairs of line inputs and no signal...
I was toast after that 4+ hrs
|
|
|
Post by Martin John Butler on Mar 9, 2017 8:25:33 GMT -6
One word, digital. I feel you John.
People thought I was exaggerating the frustration I felt when Slate's plug-ins and iLok had compatibility issues, and shut me out of all my sessions for two days before resolving the issue. It was a combination of Slate's plugs having bugs and iLok having issues too. Same thing happened again when I bought the Relab reverb. I kept getting locked out of my sessions. I had downloaded a demo, then bought the plug-in before the expiration time. I was told by Relab the software had already been in installed, so no need to reinstall. Turned out I needed to uninstall the demo and reinstall the Relab Complete, but not in any of a half dozen emails did Relab mention this. Slate eventually refunded the money for the plug-in that just wasn't working, so I used the credit toward their FG-X, then weeks later, lost use of it because of the switch to 64 bits that took Slate 1 1/2 years to get together. I was stuck with being unable to complete a $300 job one of those days.
The thing that was flat out wrong and should be illegal, is that iLok prevented me from entering into my own sessions, my own property. It would be fine if the one plug in question was disabled, but to lock me out of my own sessions was beyond the pale, and should be illegal. It's been a long time since these issues happened, and I can troubleshoot a bit faster now, but somewhere down the road, I'm gonna go 80% analogue.
So once again, digital.
Did you guys see the news where people can actually hack into your cars operating system and take over your car from you. Digital. We're fucked, let's face it.
|
|
|
Post by svart on Mar 9, 2017 9:07:56 GMT -6
One word, digital. I feel you John. People thought I was exaggerating the frustration I felt when Slate's plug-ins and iLok had compatibility issues, and shut me out of all my sessions for two days before resolving the issue. It was a combination of Slate's plugs having bugs and iLok having issues too. Same thing happened again when I bought the Relab reverb. I kept getting locked out of my sessions. I had downloaded a demo, then bought the plug-in before the expiration time. I was told by Relab the software had already been in installed, so no need to reinstall. Turned out I needed to uninstall the demo and reinstall the Relab Complete, but not in any of a half dozen emails did Relab mention this. Slate eventually refunded the money for the plug-in that just wasn't working, so I used the credit toward their FG-X, then weeks later, lost use of it because of the switch to 64 bits that took Slate 1 1/2 years to get together. I was stuck with being unable to complete a $300 job one of those days. The thing that was flat out wrong and should be illegal, is that iLok prevented me from entering into my own sessions, my own property. It would be fine if the one plug in question was disabled, but to lock me out of my own sessions was beyond the pale, and should be illegal. It's been a long time since these issues happened, and I can troubleshoot a bit faster now, but somewhere down the road, I'm gonna go 80% analogue. So once again, digital. Did you guys see the news where people can actually hack into your cars operating system and take over your car from you. Digital. We're fucked, let's face it. That's sort of an issue with the DAW too. In Reaper, if a plug stops working, it will still load the session, but disable the plug. And yeah, I've been hearing about the hacking stuff for almost a decade from the hacker community, but most average citizens brush that stuff off as "nutty conspiracy-theory" stuff. I know I've had a few more "government always has our best interest at heart" type folks tell me that I was a fool for believing in government conspiracies..
|
|
|
Post by ChaseUTB on Mar 9, 2017 10:47:25 GMT -6
Yes, Cars have computers 🤔
|
|