|
|
Post by svart on Mar 6, 2024 14:46:56 GMT -6
A computational process is a computational process. There is ZERO way that process changes between computers if the plugins and DAW are doing them the same way. It's more than likely a setting that's different. If the CPU changes or the audio driver changes, that would not effect how the plugins and DAW process audio? I guess it's a mystery then why my M1 sounds better than my old Mac. Because it definitely does. Not sure, I'm def not an expert when it comes to computers. Nope. The process is dictated by the program being run. The CPU is only there to carry it out. So, if the program says add 2+2, then the CPU output will always result in 4 no matter how the CPU might differ in design from a previous one. An x86 cpu should have the same result as an ARM. If there was something written differently in different versions of a program, it's not very likely the difference would be enough to hear. It's most likely some kind of setting, like whether or not the interface defaults to a sampling rate that's different from your DAW. |
|
|
|
Post by cademan7 on Mar 6, 2024 14:56:43 GMT -6
Yep, that's the version I have installed. Apogee has been helpful so far. But yeah, communication takes awhile. |
|
|
|
Post by the other mark williams on Mar 6, 2024 14:56:55 GMT -6
cademan7 do you use a separate machine room for your computers, or are they in the control room with you?
|
|
|
|
Post by noob on Mar 6, 2024 15:35:41 GMT -6
If the CPU changes or the audio driver changes, that would not effect how the plugins and DAW process audio? I guess it's a mystery then why my M1 sounds better than my old Mac. Because it definitely does. Not sure, I'm def not an expert when it comes to computers. Nope. The process is dictated by the program being run. The CPU is only there to carry it out. So, if the program says add 2+2, then the CPU output will always result in 4 no matter how the CPU might differ in design from a previous one. An x86 cpu should have the same result as an ARM. If there was something written differently in different versions of a program, it's not very likely the difference would be enough to hear. It's most likely some kind of setting, like whether or not the interface defaults to a sampling rate that's different from your DAW. I think you're right. I could chalk it up to expectation bias influencing my perception. I also wonder if there's a percieved smoothness based on hardware optimization. Like maybe my old machine was lagging just enough to effect the realtime audio playback. But in theory I agree that it should sound the same. |
|
|
|
Post by christopher on Mar 6, 2024 17:05:56 GMT -6
Chances are it’s expectation bias, but I’ve learned to never rule out these type of things until I’ve done some science. Weird stuff happens. Especially anywhere there’s electronics.
Things that can possibly show up after testing: voltages aren’t the same, or frequency roll offs, polarity mismatch. If things look the same, then recording some test tones and sweep using an external device can show stuff. Or least give some reassurance
|
|
|
|
Post by svart on Mar 6, 2024 17:31:32 GMT -6
One thing you can do is render a track from one computer, then do the exact same thing with the same daw/plugs/session file with the new one then do a null test.
|
|
|
|
Post by christopher on Mar 6, 2024 18:21:15 GMT -6
Even better a loopback. It might not be DAW related issue.. possibly driver / MOBO chip related.. thinking back to FireWire days and the dropout errors thanks to OEMs choosing to save a few bucks on the 1394 design, and causing hell for me
|
|
|
|
Post by cademan7 on Mar 6, 2024 18:27:29 GMT -6
Guys I think I figured it out, thanks to Gearspace. Apparently all I need to do is invest in more acoustic treatment! 😂
|
|
|
|
Post by cademan7 on Mar 6, 2024 18:37:29 GMT -6
I ordered a Pro Tools Hd native card and I will try connecting the Symphony with that to see how that sounds. Avid says that it is still supported and the HD drivers will work with the latest versions of OS and Pro Tools. I’ll probably stay in Monterey since everything is working well on that and I don’t want to risk the upgrade at this point. That’s how I ran it years ago before Pro Tools lifted the 32 I/O limit on 3rd party interfaces which is when I switched back to the Symphony 64 I/O option card.
|
|
|
|
Post by Dan on Mar 6, 2024 19:31:03 GMT -6
If the CPU changes or the audio driver changes, that would not effect how the plugins and DAW process audio? I guess it's a mystery then why my M1 sounds better than my old Mac. Because it definitely does. Not sure, I'm def not an expert when it comes to computers. Nope. The process is dictated by the program being run. The CPU is only there to carry it out. So, if the program says add 2+2, then the CPU output will always result in 4 no matter how the CPU might differ in design from a previous one. An x86 cpu should have the same result as an ARM. If there was something written differently in different versions of a program, it's not very likely the difference would be enough to hear. It's most likely some kind of setting, like whether or not the interface defaults to a sampling rate that's different from your DAW. yep. See the crazy talk about the Weiss and UAD native plugs being different from the hardware versions that run on SHARCs, both in floating point. The only difference is double precision 64-bit float on Intel and ARM and only 40-bit on SHARCS so If the filters are stable, there Is no real difference other than less rounding native. Most of the difference with Weiss was people truncating the sound multiple times (floating point daw to 24-bit driver often to rme pci or pcie card that truncated it again) and Softube and Weiss taking away the 2000s butt rock technique of being able to set the ds1 To do nothing from a way too long preview and release delay and then clip the 24-bit fixed I/o or the src. Now with ports of old fixed point reverb algorithms to modern CPUs, they mathematically and physically cannot sound the same or as intended by the original designer because modern CPUs and dsp chips are much more advanced than the primitive custom ics used in the 70s and 80s. The solution is to just not use the ported algorithms and use something else with a similar vibe that works as intended. |
|
|
|
Post by jampa on Mar 7, 2024 2:52:35 GMT -6
I can't answer your question
But I recently set up an old iMac with a modern interface
It ran
Then I installed the manufacturer's drivers. Absolutely nothing else on the computer
And it gave me -3dBFS white noise, continuous
After some trying, I got rid of the drivers, and with just the Core Audio it worked (again)
|
|
