KVR Audio

BONES · Post by **BONES** » Mon Jan 02, 2023 1:30 am

I don't want or need a "K" series anything. It's only music, it's not actually that hard, which is why my current music machine only has a Core i5 CPU, which I am pretty sure is a low power "U" series processor (but I'd have to check to be sure). It's more than adequate and, honestly, I've never felt the need to overclock any CPU, even for properly processor-intensive tasks.

jinotsuh wrote: Mon Jan 02, 2023 12:22 amas usual you haven't got a clue what you are talking about. Here I'll flick you a dollar so you can go out a buy yourself one lol

Of course not, given how little information you have bothered to provide. You put me in a position where I am forced to make suppositions.

apoclypse · Post by **apoclypse** » Mon Jan 02, 2023 2:23 am

SantaClaus wrote: Mon Jan 02, 2023 12:24 am
BONES wrote: Sun Jan 01, 2023 11:04 pm So a small sub-set of 12th gen CPUs require W11 but that's just one of a dozen or so in the series. It's something worth being aware of but hardly the end of the world.
In audio you do want a "K" CPU because of the clock speed, which means having an unlocked CPU for the single thread performance.
It's no coincidence if people in the audio field buy the "K" or "X" version of a CPU, and it's not because it looks shiny on the box.

Does it make a difference right now? Probably not, just like having an i5 10 years ago vs an i7 didn't really matter, but it did after 5-6 years, same thing here.

I'd argue this is not true and not really necessary. "People" who buy K and X series CPUs usually build their own machines (since these are mostly sold to enthusiasts by AMD/Intel). They want something that will last them a bit before they have to upgrade again. If you are buying a laptop (as most people are based on sales numbers), then its a non-issue. You are not buying a K or X based cpu anyway.

I think some folks exaggerate what's needed for audio. You really don't need a lot. Just like folks who think they need a monster machine to game. A decent video card, some nice ram, decent storage and an 8-core machine will get you pretty far.

Also MS/intel back ported a fix for E and P core scheduling issue to Windows 10 so that's not really an issue anymore. Though a lot of OEMs push Windows 11 on you regardless if you are buying a new machine.

Serhii Kot · Post by **Serhii Kot** » Mon Jan 02, 2023 1:08 pm

Does anyone has troubles with render times on apple silicone? v5 was really fast, v6 is way too slow, 1.3 - 2 times slower than realtime.

M1 Pro, 10 cores.

Update:
Found the reason of slow rendering, it was a plugin. Shaperbox 3.

ikoliks · Post by **ikoliks** » Mon Jan 02, 2023 3:19 pm

I have the same trouble with slow rendering on M1 MacBook Pro, however I don't have Shaperbox, it seems like there is something else.

BONES · Post by **BONES** » Mon Jan 02, 2023 10:49 pm

I sometimes have slow renders on PC, too, and it always seems to be one plugin that does it (one of my Ujam guitar plugins).

chk071 · Post by **chk071** » Tue Jan 03, 2023 7:39 pm

SantaClaus wrote: Sun Jan 01, 2023 7:54 pm The chord track was offset (by a semitone or a whole tone), when I pressed say A on a MIDI controller, the DAW would understand a B instead. The playhead was acting up too.

That being said, that was back when Windows 11 was just released, if it's better now that's good news.

I gave it a try. Playhead seems fine, I didn't notice anything unusual. With the chord track, I don't know. I'm zero familiar with it, so I don't know what might reproduce the problems you had with it.

But, really, I think it works fine on Windows 11. I never noticed anything out of the ordinary. ASIO4ALL tends to crash it though, when you're switching from ASIO4ALL to another ASIO driver. But, that's 100% ASIO4ALL's fault. It's buggy.

If there had been many Windows 11 related fixes, they surely would have shown up in the changelogs.

SantaClaus · Post by **SantaClaus** » Tue Jan 03, 2023 8:32 pm

chk071 wrote: Tue Jan 03, 2023 7:39 pm
SantaClaus wrote: Sun Jan 01, 2023 7:54 pm The chord track was offset (by a semitone or a whole tone), when I pressed say A on a MIDI controller, the DAW would understand a B instead. The playhead was acting up too.

That being said, that was back when Windows 11 was just released, if it's better now that's good news.
I gave it a try. Playhead seems fine, I didn't notice anything unusual. With the chord track, I don't know. I'm zero familiar with it, so I don't know what might reproduce the problems you had with it.

But, really, I think it works fine on Windows 11. I never noticed anything out of the ordinary. ASIO4ALL tends to crash it though, when you're switching from ASIO4ALL to another ASIO driver. But, that's 100% ASIO4ALL's fault. It's buggy.

If there had been many Windows 11 related fixes, they surely would have shown up in the changelogs.

That's good to hear then, and yeah I wouldn't blame Windows 11 for the drivers, ASIO4ALL is a mess.

Trensharo · Post by **Trensharo** » Wed Jan 04, 2023 12:56 am

If you only need Stereo I/O, you should use Windows Audio (WASAPI) over ASIO4ALL.

Studio Saturn · Post by **Studio Saturn** » Thu Jan 05, 2023 9:06 pm

Every single time I initiate Melodyne studio one freezes. Anybody has this issue ? I asked personus and they have not responded yet.

skijumptoes · Post by **skijumptoes** » Thu Jan 05, 2023 9:51 pm

Studio Saturn wrote: Thu Jan 05, 2023 9:06 pm Every single time I initiate Melodyne studio one freezes. Anybody has this issue ? I asked personus and they have not responded yet.

Melodyne and Studio One both up to date?

Studio Saturn · Post by **Studio Saturn** » Thu Jan 05, 2023 10:10 pm

skijumptoes wrote: Thu Jan 05, 2023 9:51 pm
Studio Saturn wrote: Thu Jan 05, 2023 9:06 pm Every single time I initiate Melodyne studio one freezes. Anybody has this issue ? I asked personus and they have not responded yet.
Melodyne and Studio One both up to date?

Yes they are. I believe so. Studio One is 5.5.2 and Melodyne is 5.3 I also tried studio one 6 it is the same thing for me.

tonedef71 · Post by **tonedef71** » Fri Jan 06, 2023 12:28 am

Studio Saturn wrote: Thu Jan 05, 2023 10:10 pm Studio One is 5.5.2 and Melodyne is 5.3 I also tried studio one 6 it is the same thing for me.

I had not used Melodyne for a couple of months, so I was concerned when I read your post. I was unable to reproduce the issue you encountered within my Windows 11 environment. When I created a fresh project in Studio 6.0.2, dragged in a stereo WAV file (32-bit 44.1 kHz) to a track, right-clicked that audio clip and then selected "Edit with Melodyne", it opened up without issue for editing in Melodyne Studio VST3 plugin version 5.3.0.011.

Perhaps the differences between your environment and mine (e.g. OSX vs Win11) are significant to this issue.

pekbro · Post by **pekbro** » Fri Jan 06, 2023 2:16 am

Melodyne Studio is working fine for me in Studio One as well, win 10.

Studio Saturn · Post by **Studio Saturn** » Fri Jan 06, 2023 4:20 am

I'm on Mac OS Monterey M1 pro. I don't know if that is a problem I wish I could figure out to fix this problem. Situation like this keeps me away from trying new DAW. I'm not saying I'm new to studio one but just in general.

skijumptoes · Post by **skijumptoes** » Fri Jan 06, 2023 10:00 am

Studio Saturn wrote: Fri Jan 06, 2023 4:20 am Situation like this keeps me away from trying new DAW. I'm not saying I'm new to studio one but just in general.

So it works ok in other DAWs? I'd be thinking it was a Melodyne issue rather than Studio One based on what you've posted... But if it's working with others, then i'm not sure.

Was going to say an uninstall & re-install of Melodyne is what i'd probably try, but perhaps not.

Studio One 6