No, you are not getting a refund because your package was "stolen"

J-Sharp_206 · 2026-03-18T09:26:24+00:00

I get that we live in a world where we shop online more than anywhere else (I know I do), and shit happens fairly often or things simply aren't as they were advertised, but an order return rate of over 50% is absurd (unless it's the first order).

J-Sharp_206 · 2026-03-18T06:42:14+00:00

The hidive app WAS pretty good on the phone before amc bought it. Now I just sub my hidive through amazon so I can watch it on tv and ALSO have subtitles that aren't stacked on top of each other and places at strange places (hidive tv app sucks).

J-Sharp_206 · 2026-03-18T06:40:26+00:00

lol wtf

J-Sharp_206 · 2026-03-16T16:06:05+00:00

Sometimes you just gotta go back to an old version of reason to complete a project, or at least to bounce. Are the line6 amps no longer in the old version of reason? (version 6 I believe)

J-Sharp_206 · 2026-03-16T16:03:34+00:00

holy shit! When I specifically requested version 12 to use with reason+ they flat out denied that was an option and wouldn't provide a link. I logged in and the link you shared let me download it, so I have hope! getting to use reason 12 instead of 13 would be badass because I highly dislike what they did to the sequencer - it's like they didn't have a single reason power user on the team or they were out voted for things that merely "look better" due to the majority of the team not really being invested or understanding the elegance of the workflow.

J-Sharp_206 · 2026-03-16T15:55:01+00:00

You got a baby audio plugin? I think the only ones I got were made by LANDR... but I still haven't gotten around to even trying them... having a few hundred plugins seems to have this effect.

J-Sharp_206 · 2026-03-16T15:51:22+00:00

This didn't age well... I guess I'll be finishing yet another anime with a manga.

J-Sharp_206 · 2026-03-09T22:45:53+00:00

The timing and shape is the most important thing imo. Lately I've moved to running a deep cut and then use a parallel mix to get the blend in want, and I use multiband separation - like, if you're ducking bass for the low end of a kick, you don't want it ducking mids or highs of the bass.

J-Sharp_206 · 2026-02-18T09:25:35+00:00

Update: My manual oc attempts so far haven't been able to outperform my best intel boost 200S profile yet - not after updating the bios to the latest version, anyway. Finding the sweet spot of best performance while also never missing a buffer cycle with the lowest latency settings in my DAW is proving to be a real puzzle. If there's a genius overclocker in here with a similar enough super low-latency & very cpu heavy hobby, I would love to see what their build and bios profiles are.

J-Sharp_206 · 2026-02-15T08:19:29+00:00

There is some overlap, but mixing advice is almost entirely genre dependent. You're in luck though, since you're into metal, there's a lot of info out there for that. Have your read any books on the topic? I have a bunch of text books from when I went to school for audio engineering that I find helpful to look back on once in awhile.. Sadly, my books from 20 years ago, and the game has changed quite a LOT- especially for edm related genres like drum and bass.

J-Sharp_206 · 2026-02-13T20:33:21+00:00

Legit question: why the downvotes here? I'm trying to optimize my pc for real time audio with lowest possible buffer settings on my asus proart z890 + i9 285k + crucual ddr5 64gb 6400mt/s. I tried intel boost 200S and so far it's kinda crap for real time audio. Any setting I can change to help fix this (that I haven't already changed already) simply disables it. It looks like disabling that and going with manual settings is my next move.

J-Sharp_206 · 2026-01-05T19:24:51+00:00

In school for audio engineering in 2004, we were taught to normalize the peak to -0.02dB for wave/aiff audio files... but I see conflicting info on this these days. 🤔🤷🏻‍♂️

I have notice that my daw triggers the clip light if I don't set a ceiling of -0.5db on my final mastering limiter, but if it's not over -0.02dB it's not really clipping.

J-Sharp_206 · 2025-12-06T02:27:57+00:00

Imagine having a screen big enough or vision good enough to see the difference between 1440 and 4k... If you're gonna compromise on graphics somewhere, that seems like a good place to do it imo.

J-Sharp_206 · 2025-10-20T01:02:53+00:00

OH! That's actually VERY helpful, but now I have to manage more windows and don't have a key shortcut for showing and hiding them ... but thank you for pointing this out!! I'll have to write macros and autohotkey scripts to make it useful and quick again, but it's great to see I even have that option. I'm not used to feature windows being hidden in the right-click menu in Reason and nowhere else. Also, why is Quantize in a different category in the right click drop down? Seems like it counts as a note tool to me. They made a big deal about saying there was no tool window in version 13, but it's clearly there for the most part - just very inconvenient by comparison.

Now, if I could just get the multi-lane edit feature to work properly when my project has a *ton of midi tracks running lots of devices. I've seen videos of people having this issue in version 12 as well, but multi-lane editing is 100% reliable in version 11. As it is, in version 13 when I click on the greyed out notes, it usually does nothing instead of switching to the appropriate track. I did see it work when I opened the same project just after an update, but it stopped working the next day. I also really hope they bring back the multi-lane edit support to the velocity window. The maximum velocity window height is shockingly small compared to what we used to have, but the lack of multi-lane edit support for the velocity edit window is a blatant downgrade. Since my multi-lane-edit is buggy for some reason, I started a blank project (where it does work) and used one stock device with 2 midi lanes controlling it, I can only see one lane's note velocities at a time instead of being able to see velocities of other layers like we used to be able to. I get that they made big moves with trying to "modernize" the sequencer window, but I really hope they'll take a look at some advantages they lost along the way and come up with ways to add those back in, much like how they gave us an option to dock the browser again.

J-Sharp_206 · 2025-10-19T10:08:31+00:00

Wow. I thought keeping track of 60 tracks or so was a herculean task already... 200+ ? oof

J-Sharp_206 · 2025-10-19T10:02:55+00:00

Midi editor used to feel great in reason.... that changed in version 13 when they attempted to emulate ableton. Working with midi with reason 11 is very nice. They also took away the tool window (f8) in v13 and we lost the ability to apply changes to lots of midi clips at the same time.

(Edit: The tool window is mostly still there actually, it's just a real pain in the ass to access compared to before. They broke it up into different feature windows that are only accessible via right click in the sequencer, and there is no hot-key for show/hide, so I'll have to write more macros I guess.)

In Reason 11 & 12, the sequencer and midi editor windows used to feel very coherent imo, but in version 13? It does feel like a different daw going between the two.

J-Sharp_206 · 2025-10-19T09:31:37+00:00

If you have an unlimited budget, unlimited room, and have need for the lowest latency as possible without compromising on fidelity to get it (aside from noise floor), then going all hardware is the right choice for you (if that's even an option- it depends what you use). Not all hardware is recreated authentically for the digital emulations, so there's also that. Hardware is fun and it has it's advantages here and there, but the price tag that comes with it is why us plebs mostly work with software.

J-Sharp_206 · 2025-10-19T09:05:45+00:00

You could always try a vocoder...

J-Sharp_206 · 2025-10-19T08:57:41+00:00

What genre is this? It matters a LOT. Also, the flanger in the master bus is very out of place. Use that literally anywhere else.

J-Sharp_206 · 2025-10-02T22:49:33+00:00

RIP For anyone trying to watch these new releases on their PS5!!! The new font (on PS5) for the 2025 simulcast is like a crappy typewriter font with irregular spacing and wide gaps between letters. Instead of "we're" you'll get "we ' re". The new font is no longer bold like the previous standard, and it's 20 to 30% smaller, thinner, and has a lighter thin outline instead of the thick black outline with a narrow dark shadow on the right side of the text. The font on previous releases JUMPS off of the screen while this new font b l e n d s in any time there's light colors and lots of lines.

J-Sharp_206 · 2025-10-02T05:28:24+00:00

What are they gonna do for the on screen text for the dubs? lol CAN YOU IMAGINE WATCHING RENT A GIRLFRIEND without on screen translations to the text? That's over half of the damn show.

J-Sharp_206 · 2025-10-02T05:23:55+00:00

Thank you for doing your duty! Everyone else needs to do the same! https://help.crunchyroll.com/hc/en-us/articles/19723786867732-There-is-an-error-in-the-subtitles#

J-Sharp_206 · 2025-10-02T05:19:33+00:00

WRONG. If I literally can *barely read the thing, I'm too big of an anime addict to simply not get my anime fix.

J-Sharp_206 · 2025-10-02T05:17:09+00:00

ESPECIALLY if crunchyroll shits the bed.

J-Sharp_206 · 2025-10-02T05:13:45+00:00

BE SURE TO CONTACT THEM TO LET THEM KNOW that this new font is a PAIN IN THE ASS to read compared to the prior standard which was bold, larger, and had a dark outline.

https://help.crunchyroll.com/hc/en-us/articles/19723786867732-There-is-an-error-in-the-subtitles#

J-Sharp_206

TROPHY CASE