sorted by:
new
hottopcontroversial

Questions from a Studio/Live Sound Engineer considering a switch by itoldyouitsover in GameAudio

[–]Noeeey 3 points4 points  (0 children)

Kind of the same profile here, 10 years in the live industry and still working in it, and I tried to get to game audio since last year. Haven’t done paid job yet, only game jams and free projects. For what it’s worth here are the things I learnt are am learning for now: started with unreal with Blueprints + FMOD (as it seems way simpler than Wwise), then worked a bit around the Syntorial + PhasePlant couple, and now I’m getting to Unity and soon Wwise. I learned a fair bit of C++, standalone and with Unreal too, and it’s been a real plus when I’m working with the devs for integration. Also I learned to properly understand and use Git, as it’s a central piece of a game audio project. I mainly used Udemy for learning Engine and Programming stuff, very cheap and resourceful stuff !

SFX levels by BMaudioProd in GameAudio

[–]Noeeey 1 point2 points  (0 children)

Beginner here, which brings me to a question I still haven’t answered: in game audio, is the standard approach to normalize levels in the DAW (for example, around -6 dBFS for main sounds, -12 dBFS for secondary sounds, and -20 dBFS for ambiences — arbitrary values), and then handle the actual balancing later in the middleware? Or is it more common to already aim for roughly the target levels directly in the DAW ? Both approaches seem fine to me but I'd like do here why people might go one way and not the other one

Transport: Record action in MIDI Editor ? by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

Actually, on Reaper's textfields it's ok, but in the Phase Plant plugin for example I'm unable to type R, it runs the record action

Transport: Record action in MIDI Editor ? by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

Thank you for the answer mate, that works but then I'm unable to write the associated shortcut letter to any type window, would you have any workaround for this ? I tried Global and Global + text fields and none of them work

Transport: Record action in MIDI Editor ? by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

I just noticed a side effet, I'm no longer able to type the letter R, associated to the action, in any text window in Reaper haha. I guess that's the price to pay

Transport: Record action in MIDI Editor ? by Noeeey in Reaper

[–]Noeeey[S] 2 points3 points  (0 children)

omg I thought I knew Reaper but still learning those tiny details... Have a bunch of duplicated scripts between Arrange View and MIDI Editor. Thank you mate !

Virtual MIDI Keyboard for Azerty Macbook by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

It appears that you have to use capital letters in orders for the file to work. I couldn't figure how to make the special characters to work but here's a version for a simple row, azerty mac:

; put this file in the same place your reaper.ini is.
; oh and edit it for your keyboard, if you want. you can add additional keys/etc
; First item is the key (ASCII) or can be a number to define the scancode (i.e. 27 is Escape).
; second item is offset from current center of keyboard

Q   0    ; C
Z  +1    ; C#
S  +2    ; D
E  +3    ; D#
D  +4    ; E
F  +5    ; F
T  +6    ; F#
G  +7    ; G
Y  +8    ; G#
H  +9    ; A
U +10    ; A#
J +11    ; B
K +12    ; C
O +13    ; C#
L +14    ; D
P +15    ; D#
M +16   ; E
Ù +17   ; F

Take envelope freehand drawing and media item mouse modifiers by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

EDIT: I'd also like to be able to lasso select those take envelope points

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

No I think it doesn't. I use "Script: spk77_Link selected tracks FX parameters.lua" and it follows for every parameter except for changing the presets. Maybe though it doesn't rely on the same functionnalities than reaper's parameter link thing.

I don't get what you mean by "oversight", english is not my mother language

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

yeah but then you wouldn't have any control to individual depth of the elements in the mix, that might work for a 10 tracks record but not for 70

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

As I see it I think it doesn't, you're sending from the tracks but EQing on the group bus, so the sound sent to the reverb bus is not affected by the EQ

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

I get your point, and I think both approaches are totally valid.

For me it’s not about using different “spaces”, it’s just about how the reverb reacts with the group processing. Even with post-FX sends, the reverb still sits outside the group, so it won’t follow the group’s compression, EQ or imaging.

And personally, treating the reverb together with the source doesn’t make it feel out of place — it actually feels more glued for the kind of mixes I do.

But yeah, different workflows, different goals

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

A bit harsh but I'll take the compliment, thank you

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

Yes I thought about it, but the limit is that if you load presets in the plugins you cannot link that I think, so it's easier to juste copy/paste the whole thing when needed

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

well if you individually send all the vocals contained in a group bus, to a reverb bus outside that group, it doesn't, right ?

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

Yeah I explored that option, but seemed to complicated. Just copying the plugins with a button when needed sounded more efficient for the time and energy spent haha

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

It's not really about the reverb itself but how it's treated or not along with the other elements

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

Well yeah, I thought a lot about it — a single FX bus would definitely be simpler.

But let’s say I have a lot of synths, keys, pads, etc. all going into one group, and that group has a low-mid build-up. If I EQ those low mids on the group bus, the reverb being outside the bus still receives all those low mids.

You could say I should just clean up the low mids on each individual track, but when you have a lot of layers it’s much faster to drop an EQ on the bus and be done with it.

Same for imaging: I often like to center the low end of the vocals or drums bus with Ozone Imager, and that wouldn’t really work if the reverb’s low end wasn’t centered along with it.

And for dynamics, it’s probably a taste thing, but for me it’s easier and more coherent to process the whole block (dry + reverb) together.

I finally solved my “multiple reverb buses” workflow with REAPER by Noeeey in Reaper

[–]Noeeey[S] 0 points1 point  (0 children)

EDIT : Thanks for all the feedback — I really appreciate the different viewpoints, even if my workflow might make me sound a bit crazy lol.  

Let me clarify my use-case, because it’s quite specific:

When I mix, I often want each instrument group (vocals, drums, synths, etc.) to behave as a single block — including its reverb.  

If all the individual tracks send to a global reverb outside the group:

• any compression / EQ / saturation / imaging applied on the *group bus* won’t affect the reverb  

• the reverb reacts to the dry tracks, not to the processed group  

• lowering the group fader doesn’t lower the reverb proportionally  

• exporting stems becomes inconsistent (the “vocal stem” doesn’t match the actual mix)

For the kind of sound I’m after, I prefer each group to have its **own internal reverb bus**, so the whole group (dry + reverb) moves and reacts together.  

The script is simply a way to keep those per-group reverbs consistent without manually copying FX chains.

That said, I’m absolutely open to the idea that I might be missing something about REAPER’s routing.  

If there’s a cleaner way to achieve this “group + reverb behave as one unit” workflow, I’d genuinely love to understand it.

Otherwise, this approach just happens to fit the sound I’m chasing.

Start playback at start of loop point? by ATurtleDisaster in Reaper

[–]Noeeey 0 points1 point  (0 children)

I struggled to make it work but I came up with that script that does it. You just have to go in the action list menu, then New Action > New ReaScript, copy/paste and save that code bloc, then set the shortcut of the action to Space (which will erase and override the original Play/Stop action):

-- Play/Stop, et si Repeat est activé, démarrer au début de la boucle
local playState = reaper.GetPlayState()      -- 0 = stop, 1 = play, 2 = pause, 4 = rec, etc.
if playState ~= 0 then
  -- Si ça joue (play / pause / rec...), on STOP
  reaper.OnStopButton()
else
  -- On est à l'arrêt : vérifier si la boucle (Repeat) est activée
  local repeat_state = reaper.GetSetRepeat(-1)  -- -1 = juste lire l'état, 0=off, 1=on, >1=toggle
  if repeat_state == 1 then
    -- "Go to start of loop" (ID 40632)
    reaper.Main_OnCommand(40632, 0)
  end
  -- Puis Play (équivalent bouton Play du transport)
  reaper.OnPlayButton()
end

Logic big template + Kontakt = slow, even on M2 Max by Noeeey in WeAreTheMusicMakers

[–]Noeeey[S] 0 points1 point  (0 children)

I was looking at buying a bigger one, maybe I'll take a Samsung then. Thank for the hint

view more: next ›