Jump to content

Lord Tim

Members
  • Posts

    2,816
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by Lord Tim

  1. Some VSTs use graphics in a different way and rely more on things like OpenGL to display their interface, while some don't use the GPU at all. @mettelusย has good advice - try to update your graphic driver first.

  2. This isn't XDA. This is a small team with other jobs, plus they need to coordinate between the US and Singapore too, and sometimes with these kind of updates, things aren't always so cut and dried as far as updates goes.

    But analogies and theories aside, complaining that a colour is wrong or some standard isn't being followed when there's very obviously work still being done isn't particularly useful. I'm pretty sure that when this update was put into progress, the devs didn't go "hey you know what would be fun? Let's break the top nav bar so nobody can see the notification and messages icons because... lolz."ย  It's very obvious it's still being worked on.

    • Like 1
  3. My guess is it was more that there was issues with the Legacy site that was preventing people from seeing documentation, etc. so it seemed like an opportune time for the back-end team in Singapore to put in the latest patches and updates while the configs were being sorted out, plus I'm sure you guys have seen the big wad of forum spam we've had over the last couple of weeks too - new software = better spam fighting tools. But it looks like that put a lot of the custom stuff back to square one due to incompatibilities.

    • Like 1
  4. This is all obviously still a work in progress. There's still a lot of stuff that's broken and missing, especially on mobile. I would suggest the goal is to get as functional as possible as quickly as possible and then knock off the rough edges as time permits.

    Basically, I think we should be a bit patient - this isn't the mix, this is the drum edit and vocal comps. Dunno if I'd like to have a client sitting on the studio couch complaining that the mastering is all wrong when I'm still trying to get his snare to sound good.

    I do notice that even the Theme selection is no longer there at the bottom of the page now and it was mentioned that a lot of the new forum software wasn't entirely backwards compatible with the customisations that were done in the past, so I'd say that'll all be returning (hopefully with different forum theme options as well).

  5. Yeah, on desktop there's a summary of the thread on the right. Kind of annoying, honestly.

    I think the bulk of things are more or less working again now, which would have been the priority for @Jesse Jostย to tick off first, but I'd say there's still a good amount on the list that still needs fixing. The mobile version especially is still missing some stuff like the Notifications and Messages items in the top bar and things like that (probably cut off because the padding isn't set correctly yet).

  6. What kind of noise is it?

    I know that the 18i20 is pretty damn quiet, and the NT is a good mic, so it's unlikely coming from those parts of the chain (environmentally, getting noisy audio into the mic is definitely a thing if the gain structure is set up badly, or there's heaps of noise in the room with the mic).ย 

    Sorry, slight side story for context. I was originally tracking on a Mackie 1620 with a Firewire card onboard, and it was pretty decent. The preamps were quiet and did the job until it died and wasn't worth fixing. I replaced that with a TASCAM 16x08 and bought a cheapie Behringer mixer to act as a bit of a front-end to it all, so I could do headphone routing, do monitoring effects, etc. What I ended up doing is basically using the mic preamps of the Behringer and splitting the signal off at the track insert point to go into the TASCAM, so basically not really using any EQ or faders or anything to actually record with but the mic pre was still in the path. Worked fine, but I've since upgraded the TASCAM to a 18i20, which also works great (and better latency too).

    The reason I wandered down that side street is to say that nothing in this chain was really giving me much noise at all, and I'd suggest the preamps in my old 1620 are pretty similar to your friend's 1402.

    I wonder if he has the gain structure set up in a way where he has the input of the 1402 down super quiet (which is corroborated by him saying he's finding it hard to hear himself) and then compensating by having the 18i20 cranked? That way you'd be also boosting up the small amount of preamp noise in the 1402 so it starts to become a real problem.

    The cleanest path would be directly into the 18i20 but that will prevent you from using any onboard routing and headphone sends, etc. on the 1402. But if he wanted to use the 1402, get the gain exactly right at the input gain knob first, and then I'd run a send from one of the Aux channels out to an input on the 18i20. But at every step, watch the gain. You'll ideally want to have the gain as high as possible without clipping from the input gain in, to the Aux send going out, and the gain lower on the 18i20.

    You can also do the split input insert thing like I've done with the Behringer but that is quite a bit of screwing around and needs special cables made - I don't recommend it unless it's crucial for how you want to work.

    • Thanks 1
  7. I think that's a good thing, I always wondered myself (that sounds like a gag, but I only just hopped on the other week to help with the spam when we got utterly belted the other week, so I'm still a n00b). I'm sure there'll be some fiddling here and there getting some familiar stuff back, but hopefully this bit stays.

  8. Everything is still very much WIP at the moment, so we can expect some funkiness for a little while until @Jesse Jostย gets everything back into place. The forum software just had a huge update, so there'll be a few bits and pieces to reconnect.

    Looks like great progress so far though :)ย 

    • Like 1
ร—
ร—
  • Create New...