Amberwolf

I think there is an option in Track View Options for "display clip contents"; if unchecked all you get is blocks of color. If the wave drawing files got corrupted or are missing, it can do the same thing; you can force them to redraw by selecting the clip, choosing Clip Properties, and then the Audio Files tab, select everything in the list and choose Recompute Pictures. If that doesnt' work there are other ways.

Does PS use the GPU for anything? (some programs do, some don't, quite a few "AI" coded programs do) Or just raw CPU speed and lots of RAM? (almost everything benefits from those)

Well, I started posting the updates partly because there were virtually no replies to the threads, hoping to eventually get someone to listen and perhaps post feedback on the songs themselves. The updates are (to me) milestones, but it's hard for me to say if I have done anything useful with the edits without feedback. To me each version is quite a bit different from the previous ones, enough to warrant an "update" note. But just so it doesn't bother anyone, I'll stop posting to any of the threads except in response to anyone that does reply with feedback, and I'll only edit them into the first post instead. And I'll go back and delete all the posts (well, replacing them with "." since there's no actual delete function) for the existing updates in all the threads, and sticking that into the original post for each thread instead.

Based on this advice https://discuss.cakewalk.com/topic/83416-if-i-should-wake-wip-looking-for-feedback/?do=findComment&comment=583948 I removed all the posts about various edits (consolidating them into the original post) except for those discussing stuff with other members. (I'll do the same in all my other threads). I can't actually delete the posts so I just made them all "." and nothing else, best I can do. To not add more wasteful posts, this one also includes a major revision of the track, making for a bigger slower feel, with hopefully more emotion. Less of the "funky indian percussion" loop sections, more handbuilt stuff from individual sounds, some new sounds, etc. The previous version is still there, after the end of the "new" one. (the previous one still has the wolf sounds under the vocals, I'm considering removing them there and leaving them only in the newer one before it...what do you think? I left the Bandcamp version alone, and added this one on Soundclick since it is likely to need significant refinement before adding to BC as an alternate version. 010625 000001 500128H extended slower feel - Gareki https://soundclick.com/share.cfm?id=14934398 EDIT 01-28-25: 010625 000001 500146M Further refined the extended version, same link. Many many changes, added sounds, mix changes, timing edits, etc. EDIT 01-30-25: Considerable further refinement of extended version (at same link above), also posted to bandcamp here https://amberwolf.bandcamp.com/track/gareki-ii-alternate-version-cinematic-feel

JellyBeanThePerfectlyNormalSchmoo will probably not even notice if I croak; she'll just wonder why nobody's giving her any more breb snaks. I'll be curious to hear what you do with that. My problem is more that I simply don't have a useful voice for what I want to do, and I can't carry a tune in a locked steel box. With many hours of manual tweaking per word (or phrase, if I'm lucky), I can eventually create usable crappy-demo-level vocals, but it's still the wrong voice, even if that was perfect. The kind of stuff I need to be able to sing is like the vocalists I listed before, or like the stuff in my few most recent bandcamp tracks (all using clip libraries) , but what I can actually do is like my tracks "Who?", "Drying Tears", "As He Lay Dying Alone", and the best of them "Back To The World".

If you still have the ASIO4all driver installed, uninstall it and clean it out of the system. There's a number of posts describing that, just search on ASIO4all. It has been known to cause problems. Then use just the 2i2's manufacturer-supplied driver, whether that is ASIO or WASAPI or WDM/KS, and only that one.

Ah, that seems different than the "I cannot control them" from your other post Best I could recommend is what others have said: If you have an independent set of outputs on the MOTU, that do *not* pass out the headphones, and they are available as separate channels in the drivers (so they show up as a separate pair in your output choices on the buses), then you can connect your speakers to those, and route the main out to that pair. Then create a separate headphone out bus, and put your Sonarworks Reference plugin in that bus, and route it to the MOTU channels that go to the headphone bus. Then create a send in the Master bus that goes to the headphone bus. If there is no channel available in your bus choices that doesn't also go to the headphones, you can't do the above. If there is a routing app or panel for the MOTU that lets you configure it's internal routing so that you can have an output pair that doesn't go to the headphones, then you can still do the above, but you'll need to make sure that's set whenever you want to use this configuration, if you can't make it the default way it powers up. If none of those are options, then yeah, you'll just have to switch between using the SR plugin and not.

Are they still included? There was a topic a short while back discussing things that weren't, and those weren't, AFAICR. (and I think the company that made them is long gone) Maybe it was just the DX versions, and the VST was still included? (EDIT: was wrong--not VST, just 64bit?) Anyway, if you have them on your system from an old install, they should still work (I use them all the time in my ancient Sonar version, in every project, especially the Multiband Compressor and the Delay). EDIT: I can't find the thread now (was going to link to it and quote the relevant part), though there are a lot that mention Sonitus... I did find one of the 2024 Sonar threads by Morten Saether that specifically lists that at least one Sonitus plug was updated, so I guess they are still including and fixing them. https://discuss.cakewalk.com/topic/82965-sonar-202411/#comment-575840

If tha'ts this one you just turn the knob above the headphone jack to set your level. The main out level is under the MOTU marking, the big knob, for your speaker mix. Normally you'll set those and leave them, so your mixes will all be consistent.

What specific settings do you have in the Sonar8 Audio Options window, in each tab? What are the specific track settings for your project, in the tracks you're trying to record? What are all the hardware knobs and connections setup as on the Tascam US-2x2, front and back? What is connected as the input audio source to the Tascam, and what are it's levels?

"Generic Low Latency Asio driver" may be something installed by some other software (such as realtek sound chip, or came wiht some audio program or standalone synth, etc. As long as it is a *real* ASIO driver, it shouldn't cause you problems if you deselect it from the available drivers in CbB/Sonar/CW, so that when you are using the Yeti driver it can't affect anything. Only one ASIO driver can be used at a time within CbB/etc, so you probably already have to do this in order to use the yeti's actual driver anyway. If the generic one is a wrapper like ASIO4all, and not a real ASIO driver for a specific piece of hardware, and just lets you use "any" device on your system as ASIO, then it's not what you want to use either. If you find it impossible to deselect within CbB/Sonar/etc so that you can use the Yeti driver instead, you can disable it in Device manager in Windows itself (rightclick My Computer and choose Manage) or you may be able to disable it in the Sound control panel (rightlcick on your windows volume control speaker icon, and choose Playback devices. Rightlcick on the generic one, and choose Disable. Click the recording tab, and do that again. Ok to dialog, go restart CbB/Sonar and it shouldnt' show up in the audio devices list anymore. )

It should be on a yellow sticker on your CD case. (that's where mine is.)

I'd recommend removing all vestiges of ASIO4all from the system entirely. It's known to cause various issues in CW/CbB/Sonar/etc, because of the way it works. It doesn't work in "low latency", it's minimum latency is whatever the WDM/KS or other driver your device has, *plus* it's own latency, plus...whatever you have to use to get it to "work" in your program. It isn't really an ASIO driver, it's a wrapper for whatever other non-asio audio drivers are on the system, and it does them "all", so if there's a problematic driver somewhere (even if you never use it) it could cause problems for anything using A4A. It could easily be causing your issue, especially if that Blue ASIO driver worked before installing ASIO4all or on a previous system that didn't have A4A on it.

Sounds like the long-defunct Mason Jar here in the Phoenix area.

Ah, yes, I use that too, but more often just the slection filter which is basically the first half of interpolate, because that way I have the chance to actually see what has been selected and verify that is correct, before I do anything to it. (because it's a modal dialog I can't get "behind" it to zoom, scroll, etc., as I can rarely fit everything I want to deal with on one screen at one time with enough zoom to see whats going on).

Unfortunately that feature wasn't created yet in the ancient version of SONAR I use. So I use Edit - Select - by Filter and then whatever process I need to. But yes, it is primarily with velocity-switched samples, and some with non-sample synths that have different stuff going on with velocity for different oscillators, LFOs, modulators, or effects,

It's also a little closer and easier to play, with slightly higher bandwidth. FWIW, I used to have a SC page https://soundcloud.com/user-792388526 , but after so many spam-likes I removed all the tracks and just use it as a link-page to my Bandcamp https://amberwolf.bandcamp.com/ . (and soundclick https://www.soundclick.com/amberwolf , but that's a virtually dead site; anything I post there can get like 1 listen and suddenly be in the top 1000 of the entire site's charts :lol: . I still use it to host experimental stuff that isn't ready to go on the bandcamp page or alternate / older versions of BC "final" songs).

Neither does my present dog (who isn't really a dog, just a schmoo-alien in a dog costume, who occasionally goes on vacation back to her home planet and leaves the costume behind, which gets lonely and thus acts like an actual dog). One of the things I like about this song is the parts you've got in your song, but also the vocals, which are a type I like (along with some of Yazoo / Alison Moyet, Eurythmics / Annie Lennox, etc). I don't have a useful voice for this kind of thing, but it would be how I would sing if I could.

I added some other stuff I found to my first reply, but this one may be the "easiest" solution so I'll post it separately as well, to make it easier to find: This page http://recordinghacks.com/microphones/Blue-Microphones/Yeti-Pro says there is already a 1/8-inch stereo headphone jack, which the "fact sheet" says is "Zero-latency headphone output with volume control for direct monitoring". This has to be post-preamp (and so have the sound quality you're after), so you could use this signal directly into your regular audio recording interface, and thus have only the IF's latency to worry about.

That is a pretty long latency. I wonder what they have the driver doing that it takes that long to process--it seems pretty unusable for a mic presumably intended to be a live audio source. EDIT2: This page https://sharklatan.com/fix-microphone-blue-yeti-usb-advanced-audio-device/ has info on fixing certain issues; I don't know if any of them would fix a latency problem. EDIT3: YOu didn't say which driver or driver mode you're using, but if you're using ASIO4all to get this mic working with ASIO, it would probably work better to uninstall that and use the native WDM/KS or WASAPI driver it has instead (since that's what the ASIO4all is actually using anyway, and just adding ASIO4all's own latency on top of that. EDIT4: Also, it may make a difference whetehr you have it plugged directly into the computer's USB port (and which port it's plugged into), vs thru a USB hub or some other device's USB plug that then feeds into the computer (like some computer keyboards have, for mice and other things to be used without using up your computer's ports). Do you mean something that automatically shifts the clip position after recording is stopped to put them where they should have been? Other thoughts: Depending on the version of software (CbB, Sonar) you have, there is a "time+" to adjust the playback time of tracks. It doesn't affect the recording of new material, so you would basically just be syncing the existing stuff in the project to whatever is coming in on the new one. With a delay of a whole second, that would be pretty hard to work with. There isn't a way to add a negative value to the incoming stuff to match the unaltered playback time of the existing project (it would have to play before the signal was actually coming into the program ). FWIW, if there is no other solution, you could open the mic up and trace out the circuits, then find the output from the preamp (if it's a separate piece from the USB conversion; it might not be), then install a jack for that to run to your regular interface. Not necessarily an easy task, and there is risk of damage that could leave it inoperative or even unrepairable. EDIT5: this page http://recordinghacks.com/microphones/Blue-Microphones/Yeti-Pro says there is already a 1/8-inch stereo headphone jack, which the "fact sheet" says is "Zero-latency headphone output with volume control for direct monitoring". This has to be post-preamp (and so have the sound quality you're after), so you could use this signal directly into your regular audio recording interface, and thus have only the IF's latency to worry about. EDIT1: This video (for a different purpose) shows the disassembly of one of the Yetis (dunno if it's the same model) to give you an idea of what is involved in disassembly. ... https://youtu.be/1yxUSUbJkwk

What specific synth is "GW synth"? Is it a separate piece of software you're running outside CbB? Or is it a synth within CbB? What MIDI driver do you have installed on the computer? And what software outside of CbB are you trying to route it to?

What synth are you using to play the midi with, and how is it routed to your speakers? Meaning: Are you routing the midi to a hardware synth or keyboard outside your computer? Or are you routing the midi to an internal softsynth inside CbB? Details on how your midi is routed to the synth, and how your synth is then routed to your speakers, will help us help you figure out where the problem is and how to fix it.

A quck google found this on reddit (yeah, a bastion of truth and reality :lol: ) for an instance where someone tagged a vehicle: https://www.reddit.com/r/AirTags/comments/17vjfac/just_found_an_airtag_hidden_in_my_truck_how_can_i/

FWIW, it's much much safer to let it save as a copy, not over the original. If something bad happens during the save, and it's saving over the original, you lose *ALL* of your work (unless you are constantly backing it up to another file somewhere else). Unless you have a really tiny harddisk, it is not going to be using much space for the project file itself (since the save doesn't resave the audio files that take up all the real space--those are already saved in your audio folder(s) and are just streamed off the drive as needed).

I'd also like an ability to constrain drawing values of (assorted things); for me something like holding a modifier key while dragging would do the job 99% of the time, as long as doing that doesn't alter my selection (so I can perform the action on just selected notes when necessary). FWIW, there are certain sounds in certain synths that respond using different samples or different sound variations when the velocity is at specific value transitions; in these cases I have to set the specific velocity that triggers that if I didn't manage it while attempting to play in some notes where I miraculously got the timing I wanted (that I'd never be able to repeat). For these cases, I'd generally do something like what the OP is doing, except that I'd probably select by a filter like a velocity range and cut and paste those notes to separate track or clips in another lane, etc., and then alter just the velocity of those notes by just setting them to the specific velocity, or by adding or subtracting enough velocity to trigger the sound I want. Mostly this is done for percussion sounds, but sometimes it's a synth track (most often Z3TA2+) used for some mostly-repetitive pattern (that usually used to be an arp pattern that was then edited in the track as individual notes).