Jump to content

mettelus

Members
  • Content Count

    558
  • Joined

  • Last visited

Everything posted by mettelus

  1. That is a good deal. For those who are not familiar with iZotope, their deals often have "from any advanced product" as a pricing option for bundles and such. This is a good opportunity to get into that pricing bracket if not there already.
  2. Another endorsement for Jim. He has been a member of this community for a LONG time, and streamlining PCs for music production is his forte (all of the bullet points in the OP). He is great person to touch base with if not outright buy from, since he will cater a system to your specific needs. He ships his machines with the unnecessary Windows apps disabled and optimized for music production specifically. As far as "power, speed, memory"... an i7-8th generation CPU with 16GB of RAM is one of the more cost-effective builds these days. Just in case you have need for more RAM going forward, getting two 8-GB RAM sticks initially will allow you to double RAM to 32GB by only buying two more (i.e., you can still use the initial 2 purchased that way). In my experience, 32GB was overkill, and 8GB isn't enough once a project gets into the mixing stages.
  3. Edit: DOH! Read that wrong on my phone, answered for the wrong plugin, sorry.
  4. Thanks for the clarification. It made me think when I saw that picture that indexing errors can lead to such situations, especially if off by an integer value. Index values start at zero, and that picture looks like the audio is set one frame forward (index starting at 1, rather than zero). It may be coincidence, but I was led to believe the padding was akin to an audio buffer in size, but a full frame is 1600+ samples, which is far more than I expected to see. I am not sure if an indexing error is at play here, but "one full frame" is suspicious.
  5. I do not work with video, so that last picture caught me offguard. I was expecting to see "sample offset" but that appears to be "ms offset." It looks like it is off half a frame (~16.7 ms)... Am I interpretting that correctly? Is that offset exactly a frame interval (1/2, etc.)... meaning if the audio was shifted by a frame interval, would it be synced properly?
  6. This is known for mp3s, and the lead padding is variable depending on the specific file (no set offset will solve it). Unfortunately that padding is front-loaded, which is why sending mp3s for collaboration can cause a headache without an audio transient to align to. I can only assume this is similar for compressed video, so the advice above to convert to uncompressed prior to editing would be wise.
  7. I got 8 during the Gibson debacle, and demo'd 9 but the layout didn't click with me and I was too lazy to dedicate time to it. That new sampler did stick out, since there are very few "quick and dirty" ways to do loop backs via software. They seem to be putting some real effort into features, so I will give them another go. I need to actually make something with it rather than just screwing around testing features. 😳
  8. Doh! Thank you, lol. Good thing that wasn't a car or I would have been hit.
  9. mettelus

    Input Echo Latency

    That RX7 Breath Control has a look ahead buffer on it, IIRC. What that means is it needs to see what is coming to react in a smooth fashion, so ”real time” it is forced to delay the rest of the project. Some FX are only designed for mixing, and others have a ”low latency” setting on them, or even ”low CPU” if you need to track with them enabled. I am not sure if RX7 has those, but it is something to be aware of... both look ahead buffers and high CPU hit will mess up tracking. Global FX bypass is a quick solution for most cases.
  10. I downloaded the demo, but not used it much yet. Does the upgrade apply for the 8 versions as well? I couldn't find info on the "upgrade" aspect. Looks like some features got inspiration from other DAWs, but no harm in that. One thing that really stands out is the quality of their web page and videos. Their marketing folks are really on the ball with that stuff. Very nicely done on both fronts.
  11. That is one of the weirder things I have seen. The "Building Transient List" flashes so quickly I had to download the gif and go through the frames to make sure that was what it said. Are any files (these "transient lists") being saved when it is doing that? That may be easier to search for files "modified today" after it finishes whatever it is doing. Overall that is very confusing, since there is no need for a transient list to play anything, and if it was making such a thing I would expect it to be real-time (or just prior to playing). I am also curious if that is really CbB or a plugin. Either way, I am not getting "the point" of what it says it is doing. Edit: I just tried that out and those flashing messages do appear when cycling through wav files with the browser prior to playing some (about 50%) of the files I previewed, but CbB otherwise closed cleanly for me (no residual work going on). No files saved that I could find with this.
  12. That video is a great overview of how the internal caching functions, both in theory, and under (extreme) testing. His point about "intended use" is also very valid in that the average user isn't going to be stress-testing writes to the drive, which allows the drive to clean up its caching between uses. For this, you will not see significant performance issues for reading if the cells have only been written to once (when you are done copying them). But as shown in the video, if you try to write ALL libraries to the drive at once (his test was a 230GB file copy), you will see the write hit when the cache gets saturated. Basically, the drive is setting aside a portion of itself to use SLC (1/4 density) as a "fast cache" to give the slower QLC writes time to catch up. If it gets filled quicker than the QLC writes, you will start seeing QLC speeds until the drive has enough idle time to "re-orient itself." Initially the drive is 250GB as "SLC," but as you fill it that cache will drop proportionally to 1/4 of the free disk space. Once written, it shouldn't be anything noticeable to you for reading samples from it, which is your intended use.
  13. Best advice is to download the demo and kick the tires for yourself. Regardless of input here, this will come down to you. The "What's New" at the bottom of the product page is a good place to start. Personally, I was a bit underwhelmed by TH-U, so will hold off on it. It seems the "Rig-To-Model" technology is not something they plan to release, which is unfortunate since a lot of folks have amps they cannot continuously (or ever for some) run at wide open throttle and/or want to capture their studio space.
  14. A lot of things will linger on an OS drive (temp files, log files, dump files, Windows updates (which can be rather massive), etc.), or be installed to odd places (e.g., XLN installs to ProgramData) unless user intervention occurs. A few great utilities exist to monitor folder sizes (I personally use TreeSize Free - Administrator), which are excellent tools to see what is eating up your OS drive. There is a thread on the old forum called "Optimizing an SSD" that has a bit more detail for this. I did a high-level look at junction creation in post #8 on that thread which hopefully can still help folks curious how to keep the OS drive lean. Again, the only concern that I have with large OS drives is the time they take to image/restore, and the size of that image.
  15. I think that is the crux of the OP... a 1TB drive should be used, especially if fast, otherwise is extreme overkill (and waste of money) to leave it mostly empty. In that situation a 200GB "C" drive partitioned to an 800GB "Sample Drive" would make a lot of sense. Imaging the C partition would be small and quick, and the rest of the drive could be used for "fast read" material.
  16. That board is similar to mine. You have two M.2 slots on the motherboard and the M.2_1 socket (page 1-2 just below the CPU) can be set to X4 mode in UEFI (BIOS) at the expense of losing SATA 5/6 connections (M.2_1 Configuration on page 50) . You want the faster NVMe in that slot if using x4, but will lose SATA 5/6 in doing so (essentially two drive slots).
  17. Unlike SATA connectors, M.2 slots are far more limited in most machines. This is one situation where a partition argument would make sense. You want the most bang capacity-wise from those limited M.2 connections (fast and big), but at the same time keep the OS size "reasonable."
  18. A massive OS drive makes disk imaging problematic, both in time and space. That is one situation where I would consider using a partition. My OS drive is only 256GB, and I use junctions to keep it under 150. Images of a mostly full 1TB drive would take an hour or so, and need another massive drive to store the images to.
  19. Even (especially) if you have the paid version, get this release. When I got this machine last year, I had issues getting my serial to take for authorization (customer support was still alive then, so got it resolved). I am assuming that this download going away also means that the registration servers will go offline. This free version is unlocked and may be the only way to re-install RiffStation in the future.
  20. My first reaction is "ouch," "lackluster," or possibly Kevin Klein's "Disappointed!" (from A Fish Called Wanda). Jim posted in another thread that the Rig Player doesn't allow recording "for the time being," so I ratcheted down my expectations before popping off the demo. It took another hit when the text insert in the TH-U manual for the Rig Player states "Overloud does these rig modelling in house using top quality tools and procedures, to allow users to play with the best guitar tones possible." "In house" makes me assume Rig Modeling will not be "in studio" any time soon (defeating the purpose of ambient modeling as well). The Amp Tweak is also not available on Rig Models as far as I can tell, which drove another nail in the coffin for me (even if I could model my tube amp, I cannot alter it). With all of the hype behind the Rig Player, it would have been nicer to be upfront to what it actually is... which appears to be a method to market other people's rigs, not capture your own. This left me with putzing around what I could find new and the new shimmer effect (nothing earth-shattering for me). The search feature would have been nice back in the TH2 days, but at this point I have already sorted things manually, so that is OBE for me. I will hold off till I get a better feel for what is actually new (I missed some things), and what is intended going forward. Just wanted to give folks this heads up, since Rig Player got touted pretty heavily in the past month. In reality, this fell far short of what got marketed.
  21. Limiter No6 is a very nice and powerful freebie. The on/off switches for the modules are in the bottom/left of each section. Best way to use that would be one of two ways: Peak Limiter Module only: Gain: 0, Threshold: -1, Mode:Brickwall, Type: I, II, or III, Peak Limiter:Linked, and Speed:Normal Protector Module only: Output:0, Ceiling: slightly less than 0, Protection: ISP Fast You actually have to get the manual via the "downloads page" link, the other is broken. Direct link to the manual is here. Your comment about only "the master buss" now makes me wonder if this is a rogue VST (feedback) or if the tracks are too hot (digital clipping). Let me explain... positive feedback (if unchecked) will grow exponentially and will definitely clip the track the VST is on. When summing audio, two identical signals will double volume (+3 dB), 4 will be +6 dB, 8 will be +9 dB, etc. Every "doubling" adds +3 dB. A quick check on this is to lower the master buss fader by 6 dB or so and play the project through and see where it peaks... if your project is getting digital clipping, it should 1) occur in the same places each time, and 2) "go away," which you mentioned in the OP. Is it possible you are actually seeing digital clipping (which can also sound rather bad, but is not feedback)? Edit: Quick clarification on the above... although digitally it is possible to prevent digital clipping, some VSTs definitely do not take well to being run too hot. I would do a quick check on this to see if it is always occuring in the same location during playback. While you may not be digitally clipping a track, you could be clipping a VST on that track which doesn't tolerate high input.
  22. Thanks for that Larry. I was confused with the initial upgrade offer, since on the Overloud site itself it is listed as 59 Euros versus 49 Euros (I checked ZincT's post twice to make sure I didn't misread it). It is still day one, so that will probably play out shortly, and others are lower. Regardless, can nab the demo now to check it out. Ironically, when I watched the video when this thread first posted, what immediately stuck out for me was the search box in the lower left corner of the GUI (finally!). I am very curious to try out the new Rig Player and Amp Tweak features (swapping tubes is a royal PITA and not cheap).
  23. No transport looping for this. The 2-bar section mentioned in the OP can be dragged from the track into the Matrix View and set to loop, synced to the transport. That "track" will then be driven by the Matrix View, while the rest of the project will still be driven by the transport. The Matrix View is a looper that outputs to a project track.
  24. I am not familiar with Boost 11, but as mentioned above, a compressor can be used for the same functionality (technically, some define a "limiter" as a compressor with greater than a 10:1 compression ratio). A high threshold (-1 to 0 so you do not see it functioning as a compressor (no active gain reduction)) and steep ratio (10:1 or better) should suffice. When tracks digitally clip, small red boxes will appear at the top of the VU meter for that track (and on busses as well); very similar to the red boxes in this picture at the top of the right track/buss. They need to be reset manually after a clipping/feedback event (and will be reset by default when a project opens). Do you see which track the clipping is occuring on? If you have a VST on a buss, the tracks feeding it may in fact not be clipping, but the buss itself can be, so check both tracks and busses (may be easiest in the Console View - ALT-2). Shift-D is the keyboard shortcut to maximize the multidock so you can easily see the full view... D toggles the multidock viewable/non-viewable. This should help you narrow it down to which VSTs are in play causing it.
  25. I would recommend trying the Matrix View. Unlike a groove clip, you do not need to specify length of it (where the last groove clip will be the end), but merely start/stop it and it will continue to loop cells indefinitely for you. You can leave it looping till the cows come home, and for this reason is also a good tool for jamming with. Here is an older tutorial video for the Matrix View that is still relevant (a few controls have changed).
×
×
  • Create New...