exploring a little closer to home (math rock bands on crooked floors)

well, i've either got a mosquito bite on my forehead or i'm developing a third eye. want to take bets on that?

i didn't get any cleaning done the other day; i got stuck in an algorithm on youtube, which ended up crashing the browser. 2500 open tabs. in hindsight, i suppose it's not possible to watch all of youtube. i hope to get that done with the rest of today, and get back at it tomorrow. i'm feeling rejuvenated and eager to move forwards.

i hit a house show last night with two mildly interesting acts, both of which demonstrated some potential, but neither of which held up as well as they could have. reviews in the comments.

in two years here, it was actually the first time i've taken a walk away from downtown after dark. i knew i was going to be walking through the wealthy part of the downtown core, but it took on a different feeling in the moonlight due to how clear it is that i was walking through a neighbourhood built by very old money. the churches, the collegiates, the mansions - these are all still standing, and all still in use. i suppose that it's only different from what i'm used to in ottawa in terms of how explicit it is; it may have been similar to walking through the glebe thirty or forty years ago, but i'm not old enough to remember what that may have been like.

the key thing you notice when you cross the street into the old money is how dark the neighbourhood is. the houses are old, but taken care of - likely professionally. they're dark because they're empty. one imagines widowers living off investments made by ancestors they've never met; sum totals of labour that exist of shuffling portfolios. these ten or fifteen room houses were built for families, and were no doubt once inhabited, but today they are merely equity passed down through generations. you'll see a jogger here and there; a dog walker, a couple. but, these are not castles, not sanctuaries to escape from the blood-thirsty masses. rather, they're empty relics of the past.

and, one exits this space as quickly as one enters it: a highway appears, and once one crosses it they are back to the normalcy of post-industrial decay. buildings that, though a quarter the age, are falling apart due to low maintenance. the whiff of marijuana replaces the soft background scent of professional gardens. but, i am crossing to the right side of the road, not the wrong side of it.

the show was outside, in a large lot (perhaps originally two) that's been split into three: a small house faces the street, with an equally sized secondary bungalow right behind it, that must be accessed via a path along the first one. you could spit from the back deck of the first to the front porch of the other. it seems almost as though the back house was moved in from somewhere else. an empty lot of the same size exists next door, apparently reclaimed by these inhabitants for events, although if the city were to appear out of the bushes with an ordinance, they would no doubt be told to exit the empty and adjacent lot. mosquitoes are endemic; in addition to the bite on my forehead, i've got a dozen on my unshielded arms. should have worn a long sleeve t-shirt...

sly why was up first (after a short set by some kind of radio show). i've seen sly why before, but with a band; i initially thought this was a dj set. rather, it was the front person for the band doing a solo set that integrated live keyboard playing & rhyming over some drum & bass machine work. the sum total was likely meant to exist in a flying lotus type space, but with a heavier emphasis on hip-hop and quite a bit more of a chick corea feel. in principle, this is an excellent idea. unfortunately, the execution was a little off.

the chick corea sound (i'm talking more about miles davis than return to forever) is two things: it's an aesthetic and it's a playing style. related things, but they're different. the aesthetic was pulled off very well, but a musician listening in would be unimpressed by the actual playing. he seemed to want to go into long interludes of piano work; these were effective when they were focused, but often sounded aimless and improvised. it's one thing to try and get the corea aesthetic; it's another to think you seriously actually have the talent to try and pull off that kind of improv. i think he needs to kind of make a choice on that: be more focused and drop the solos, or work on his improv skills.

he's definitely not chick corea.

as i believe i said last time, it's a good proof of concept with a lot of potential but it needs some work to actually come together.

this is similar:

 
this was the first time i've seen noxious foxes, but i remember their early records as being more dynamic than what i got last night. more live playing, intersecting harmonies, leads - less loops. my memory may be skewed; i may go back and listen to their first two records and realize they're more loop-based than i thought. but, it ended up with a pretty strong ian williams feel that really needs to be broken up a bit.

it was fun. i'd pay the $5 a second time. but, they need to be thinking about ways to get out of the box created by writing solely around loop pedals.

http://dghjdfsghkrdghdgja.appspot.com/categories/shows/2015/09/28.html

rap news 35

who created the internet, and why?

the narrative is about stopping certain forces from taking control, as though the internet came to us free of corruption and we need to prevent it from falling into the hands of darkness.

maybe it ought to be about taking control of a system that was handed to us with a precise function that it took some time for us to become aware of.

well, i didn't get much listening done this week, but my mind was elsewhere, so that's ok; i got plenty of thinking done, and feel nicely rebooted. that's the real purpose, that reboot.

the weather was unseasonably nice here this week, and that helped.

i'm going to push my monthly cleaning forward a little this month and do it tomorrow. i plan to hit a math rock band called noxious foxes on monday. i'll also need to make some calls on thursday. but, i'm transferring into a new normal this week and should be back and focused at some point during it.

you can imagine that all this bullshit with the gear has been a force towards apathy. it's just a process of seriously convincing myself it's good now and plowing on with it.

and, i'm thinking about my issues with eye contact. it was what i initially wanted to talk to a psychiatrist about, before i got diagnosed with...well, i guess they got me to social anxiety disorder in the end, which is more along the right lines. but, i never expected it to be declared a disability and to entitle me to a monthly check; i was thinking it was something i could get some therapy regarding.

part of the argument i used to get my extension, which i haven't posted anywhere yet, was a cost-benefit analysis of treatment v. acceptance. it was a catch-22 themed essay that argued that i might seem perfectly ok right now, but if you take me off the odsp then i won't seem ok anymore. i concluded that i ought to be grounded. but, i acknowledged that a significant investment with morally questionable techniques could resolve the issue - even if you had to chain me down and lock me up to administer it.

what i'm wondering right now is whether that's really true.

i avoid almost all eye contact. it's really only when i want somebody to do something for me that i can muster up the courage to look somebody in the eye; it's that aggressive of a gesture, for me. it's clearly not such an aggressive gesture for others.

is that learned, or instinctual?

the earliest memories i have with eye contact are feelings of almost panic due to a desire to avoid confrontation. so, i don't have memories of any theoretical causes, but only memories of effects. the thing is that it goes back very far, to that murky early grade school period; it could be because i changed schools in grade 3, or because i had a concussion shortly afterwards, but i would be almost hopeless in differentiating between events that happened between when i was four and when i was 7. it's quite young, though.

i remember that when people looked at me in the eye, i would become fearful that an argument or fight was about to start. it was just an act of pure aggression. so, i found myself avoiding eye contact both to counter the aggression of others and to prevent others from thinking i was behaving aggressively.

it sounds like i'm talking about an antelope. and, maybe i am in the sense that i have some native american genes. i'm exhibiting behaviour regarding eye contact that is normal in some indigenous cultures, but i haven't been conditioned into any of those cultures. perhaps therapy may be less effective then i'd like to think.

i've liked to think i'm not irreversibly broken; that i could be fixed, but that the investment would be at a loss. and maybe what i'm pointing to only necessitates therapy, rather than negates it's use. but maybe i'm uncovering somewhat of an unrealized truth, whatever it's scale.

i'm starting to become more cognizant of this strange tick in my neck. now, what i'm going to say may seem unscientific, and would probably be rejected by most doctors, but if you ask them to provide a better explanation, you'll be disappointed in their responses. i'm grasping the situation through experiencing it; i'm carrying out the experiment. and, while i may not be the person best positioned to measure my own behaviour, my notes should be analyzed for a mechanism rather than discarded as "impossible".

i seem to have developed too much control over my autonomous nervous system. seems ridiculous, i know. but, can you point me to studies that prove it impossible to gain control over the autonomous nervous system? because i bet i could find some studies that blur the lines pretty substantially.

i seem to have developed a fear of swallowing. that's at the crux of it. due to throat inflammation for various reasons, but one obvious, i may have nearly choked once or twice. i suppose we all cough something up once in a while, and it's a lesson to be more careful when you're eating. but, we mostly tend to shrug it off after a day or two, right? instead, i seem to have internalized it to the point that i'm not able to open my throat to let liquids in. i find myself fighting a battle against my own throat.

that might seem to indicate a loss of control, but not if it's thought about more carefully. if everything was firing correctly, i'd expect my throat would open when i pick up a glass of water. instead, it shuts and i have to consciously struggle with myself to open it. if i were in full conscious control, i would not have to struggle; if it were truly autonomous, it would not close at all. that indicates that it's my subconscious that must be interfering and shutting it out of a repressed fear of choking, which indicates too much control - but not consciously.

i understand i'm not likely to convince anybody with a doctorate in anything of this. but, i believe it's what's actually happening. in theory, the solution should be in the realm of mental health. but, even if i could convince somebody to take me seriously, i'm skeptical that they'd have any good ideas. it's maybe the kind of thing something like yoga might fix, without as of yet understanding the mechanism.

i don't think i actually need to go to a yoga studio. but, the answer may be spending a little bit of time sitting and breathing. i've spent most of my time recently fighting with a computer, and most of my time before that mixing and mastering. maybe i need to spend a little time with the guitar.

i'm not as dismissive of hypnotism as you might suspect i am, i just wish we could get a better handle of the mechanism.

i mean, you have to wonder if that's what demons are - repressed fears - and if that's what an exorcism really is - hypnosis to escape a repressed memory, fear or other such thing. we can do without the spells and religious mumbo jumbo, no doubt. but, it might be getting at stimulating a condition that allows for erasure.

my understanding is that there are actually experimental techniques underway that can erase undesirable memories using electronic equipment. that could be demon removal, on demand.

perhaps certain systems of eastern mysticism may have thrived for the reason that they minimize the onsets of these sorts of stresses.

and, if that's true, the mechanism would be in stimulating the hormonal condition that allows for stress release (jumbled language, it's still sort of magic at this point).

which, i believe - through direct personal experience and the observations of others regarding how i appear when i play the instrument - i can stimulate by expression on the guitar.

when you live in a basement, outside lawn mowers can make some rather gorgeous ambient music.

now that i've got my drivers clean, i'm back to the issue with the eqs.

to recall: there seems to be a programming error in cubase (a truncation error, it seems) that corrupts mixer settings on the first save. it's something i'm going to have to fine tooth everything over. i wasn't previously able to tell the difference on a/bs, but i can now. so, i may have to re-upload some of those files one last time.

my fears were unfounded - the machine booted up to a perfectly clean sound. i am finally confident that the machine is fixed.

all i've done since the last reboot is reinstall the operating system firewire drivers. i didn't even swap them, i just disabled them and rebooted, which forced me to also reinstall the mixer drivers. that seems to be the only thing i needed to do (besides locking the drivers).

it might seem like something i should have never overlooked; that it should have been one of the first trouble-shooting steps. but, i've got all my driver installs sequenced in an install script, so when i reinstall the machine i'm dealing with fresh, updated driver installs for every device in the machine. it's reasonable that it never crossed my mind to reinstall drivers for a system device immediately on a clean boot.

but, there's some evidence that it may actually be the registry wipe i run post-install.

before i run the script, i can uninstall the firewire drivers through device manager. after i run the script, it tells me i can't uninstall them because they're locked by a parent driver required for start-up. that sounds wrong - as though i've crossed something during the registry wipe. what i have to do, instead, is disable them first and then uninstall them.

what i've got back now is the "sound stage" - i can hear the reverb in proper stereo and all the effects have their decay back. it's the reversal of that compressed sound that i was associating with bad conversion. so, i have to conclude that the firewire port was somehow truncating the stream. when i put it into the context of the files always nulling when output to disc, it does, in hindsight, make sense to tie the issue entirely to the firewire streaming, as the issue was purely playback related.

that was a long, difficult process for what in the end was a triviality. but, i really think it's figured out now, and i should be able to get some listening in this week and back to mixing next week.

well, i got my forms mailed today. that's to cancel my student loan.

i can't be certain what the bureaucracy will do, but my understanding is that they basically can't overrule the doctor.

so, i'm celebrating this week. which means listening, but carefully - i know i can't mix when i'm celebrating.

and, it means making some different lifestyle choices starting next week.

i suppose i should be happy that i'm healthy enough that my lungs are still able to go into overdrive whenever i quit smoking. i've been through this often enough to know that this is the last phase before normalcy: the white blood cells start coming out in a quantity that sometimes makes me feel like i'm choking. i can literally stand over the sink and watch a connected gob of slimy goop fall out of my throat for upwards of a minute at a time. it only lasts a day or two. rather than clear my lungs slowly, my body seems to want to go into hyperdrive and flush it all out as soon as it can...

i'm actually scarily healthy. i tell people i won't live to 50. the reality is that if i can cut the smoking out now, otherwise keep my lifestyle (healthy eating, but more importantly no car) similar and get a little luck on inheriting dna from my mom's side, i'll probably make it to 90.

and i can't help but feel that this exaggerated response i always get when i quit is a function of being as healthy as i am.

i made a point of not getting anything done today, because i was expecting to pass out. i've actually been awake for a normal 17 hour day at this point and i'm feeling very alert. but, i'm still not doing anything...

tomorrow, i think, will be time to start again.

i determined yesterday, briefly, that the primary problem was, in fact, the firewire driver. i'm expecting it to boot up to a clean signal. perhaps another reason i didn't do anything today is fear that it won't.

not quite.

...what day is it?

i think i'm out of the haze and ready to finish troubleshooting.

so, after caving into various self-rationalizations over the first half of september, i've been de-nicing the last few days and have every intention to stick with it this time. i've said that for a long time. but, i've got my income stable for the next five years, i'm no longer in a hurry to do much of anything and i'm very much intent on getting over this. i had a little heatstroke when i got back on tuesday night and have been sleeping that off as well, but i think i'm alert enough now to at least try and get the machine back up.

i turned it off tuesday morning right before the script runs. i'm going to want to make sure i can get the firewire drivers correctly working before i run the script.

i didn't get my forms on tuesday. it turns out that the psychiatrist has to fill them out, and i'll have to wait until monday. nor does it seem as though the nurse practitioner is going to carry through with my prescriptions. he claims he'll work as a go between if i can find an endocrinologist, but he won't work with the guy from london because he claims he's unprofessional, which i think is a cop out - i think it's a religious thing, again. he said he put out a referral, but i'm kind of sketchy on it. i'm not convinced it's even a real person. but we'll find out. if i don't have an answer by monday, i'm going to have to get in contact with the guy in london.

i can't think of any reason why i should need to actually go to london and physically speak with him. i'm just asking for a refill of something i've been on for years and will be on for the rest of my life. it should be a five minute conversation, and it's not really necessary. and, if he insists on a blood test or something, i don't see any reason why i can't just get the blood test here and have the results sent to him.

the ideal remains trying to get the guy in windsor to see me because then i can indulge whatever silliness he wants at essentially no cost to me.

i'll find out these things in a few days.

and i think i should have the machine up in a few hours, even if i need to spend a few more days sleeping to finish the detox.

yeah, i think it's partly related to the operating system's firewire driver, strangely enough. at the least, this seems to be *one*of the things - and it's pretty pronounced. it seems to be reversing the compressed sound that i was associating with kmixer sample rate conversion and giving it back it's fullness. but, it's still fading...

i ended up breaking the audio in the machine pretty badly before i got there (i wanted to completely isolate the asio, so i did crazy things like delete the windows audio service, purge the registry of all mentions to all drivers, delete the system audio files, etc), so i'm going to have to reinstall again. like, i can't get it to pick up the directsound out on the m-audio card - which is what i wanted to isolate the asio, but now i need it back. so, i just don't really have a clean system to test with. the fading had stopped before i busted it, so i want to get back to where i was, do the firewire reinstall and see what happens.

it's been the same thing almost every day for weeks now. months, even.

i find some fix. it seems like it worked. i go to sleep. i wake up and it's back to where it was.

i dunno. am i playing tricks on myself? the truth is everything is nulling, so i'm not looking for changes in the actual waveform, i'm looking for changes in playback. is it possible that i'm getting used to the sound every night, only to have to start again the next day? are my headphones or my amp warming up overnight, then cooling down?

this morning's apparent fix was deleting the operating system's firewire drivers and replacing them with drivers from a firewire card i have in the other machine. it sort of makes sense relative to the weird tone issues, insofar as it seems bandwidth related. i'm taking guesses. i've been taking guesses for a while.

and, like so many of these steps, it seems vaguely familiar.

we'll see tomorrow if it's the same thing yet again, or if it's actually a meaningful fix, this time.

is it even the coffee?

there's a little box called "direct monitoring" in the cubase vst panel. unclicking this seems to have FINALLY broken through the sample rate issue and given me the sound i remember. that means i'm going to have to go back over this one more time. but it seems to be the answer i've been trying to figure out.

i'm not entirely clear on what this does. it appears to be related to whether i can hear files coming in from the mixer or not. if i was running an input driver all the time, i may have screwed up the output driver. i dunno, that's a guess.

but, i'm feeling good about this. now, though, is sleep...

if i go back to this feeling i was having that i was being eavesdropped on, it kind of adds up. it's probably obvious that i have unusually sensitive ears. the direct monitoring takes the input from the mixer and sends it to the output. just the bandwidth could have been bothering me.

there's been nothing attached to the input the whole time, of course - i've been mixing old four track parts. so, if that's what it was, it's, like, a virtual ground loop on the signal.

false update on just say no to mood altering prescription drugs

this has been updated.

https://jasonparent.bandcamp.com/track/just-say-no-to-mood-altering-prescription-drugs
https://jasonparent.bandcamp.com/track/nope

on second thought, i slept a little later than i planned and i'm not going to be able to hit the show unless i decide not to eat, which i'm not keen on. and, i'm not really up for sitting in that ice cream shop overnight; it's going to be relatively cold. cold snap had to hit tonight, huh? i was a big sonic youth fan years ago, and i'd certainly go if it was across the street but i'm really more focused on what i'm doing...

so, i'm staying in tonight.

i think the mix for nine is done; i was actually fighting with the drivers again last night, as it's fading again. i made the error of accidentally uninstalling the underlying windows drivers, and it seems to have screwed up the asio. i'm going to try to avoid reinstalling, but i may have to. now that i've got asio connected directly to foobar, i have tested it with the windows driver completely uninstalled and it does seem to be stable - lthough i'd like to be able to bring these back in. for now, it seems like i can get the drivers to stay put for a while before i have to reinstall them....it's workable, but i'm still tinkering because i'm still not clear exactly what is causing it to randomly resample...

i think 09 should be up pretty soon.

that was trivial to fix, actually. and i even remember...

at some point, i brought in the original 1998 mix to do a compare, which meant i had to take the effect off the master (otherwise it would run through the effect) and set the rest of the tracks up to their own fader. i seem to have never put the effect back. i must have accidentally saved this, then forgot about it. those vague memories, right?

putting the effect back on the master got me back where i want to be. i will need to replace this file.

track 09 is just sounding funny one way or the other; i remember it having a nice compressed punch, and instead it's sounding very digital. i dunno.

but, i hope to get a bit done tonight.

i'm going to hit thurston moore tomorrow night, and use it as sort of a head clearing. i got almost nothing done this summer, which is disappointing. and, i have what is hopefully my last appointment for a while on tuesday. so, hopefully, i can get this past me and start refocusing on wednesday.

expect sporadic uploads over the next few days; hopefully, i can be almost done cleaning this up by wednesday.

i just got an email...

i want to be clear.

i will never, ever, ever press anything on vinyl. you could say i'm boycotting the technology.

there's two reasons:

1) it's terrible, obsolete, shitty sounding technology that should be rounded up and bunker bombed.
2) i record everything using digital technology. even if you want to pull some wrong argument out of your ass about "tape saturation" or something, transferring material that is recorded over digital technology at a relatively low bit rate on to vinyl can never have any possible result but sound degradation.

i will not degrade the sound quality. i will not sell you garbage. i will not press vinyl.

if you want a crappy sounding but nice looking commodity, you'll have to look elsewhere.

vinyl sounds like shit.

it's never happening.

obligatory "influential on the featured track" post.

i suppose, in hindsight, that this is the beginning of the radiohead that most people know, isn't it? at the time, it was just dark. i've never been able to find a mix that sounds like i remember first hearing it, with a really pounding bottom end. it might have been a bad realaudio encoding that muddied up the bottom. you don't want to know what realaudio is, if you don't know. but, it came out as the weirdest funk i'd ever heard - because it was both dirty and reflecting; it was like shaking your booty on the floor and hiding and crying in the corner at the same time. but, all in your head. of course.

(relevant tracks: thug culture is enforced by the media from the top down)

obligatory "influential on the featured track" post.

i just remember dark rides on the bus; stuff passing by outside the windows, humans i couldn't care less about all around me and wishing they'd just go away (although i should have been trying to communicate with them), self-consumed introverted thoughts that i have no recollection of...

it's the harmonies. through a good pair of headphones, and sufficiently disconnected from the things around you, it's a lift-off. a little cliched, if you demand to over-analyze it. but it's incredibly effective.

(relevant tracks: thug culture is enforced by the media from the top down.)

not updating i still don’t fully understand this

so, i've convinced myself that the version of this that is already uploaded is superior to anything i could reset with the eqs, and that i probably initially outed it post-save in the first place.

i know i re-opened it and re-rendered on the 12th of july, but i think i even vaguely recall that the file nulled, but i replaced it anyways thinking the initial was corrupted in metadata or something. this was when i didn't yet realize the cards were misbehaving...

this needs to be blared at almost dangerous levels to get the effect of it. that's generally true - it's all headphone music. but, it's especially true with this. the layers of distortion need to cascade at high volume; at low volumes, it's going to sound compressed.

https://jasonparent.bandcamp.com/track/i-still-dont-fully-understand-this

switching to skaters in the alter-reality

alter-reality update tonight at midnight.

i'm certain that my computer is working again. i've worked my way back to where i was when i left off, and am playing with options on the 8th track for inriclaimed. it's passing an a/b with a full reset of the eq settings, but not passing an a/b with more subtle changes. and, i'm feeling the bass is not defined enough on either, so i'm essentially remixing it. i should have some uploads before the next sleep.

https://www.youtube.com/watch?v=H9L98As4DjE

aha!

if you go to device manager, right click on the driver, select properties, and then select the properties tab there is an option to disable the mixer for each device. this appears to have stopped all windows fuckery and given me a clean stream through directsound. it has the strange effect of no longer launching sndvol32, and claiming i have no audio devices installed when i launch mmsys.cpl. but, that's a minor annoyance if it's giving me a clean stream. and, it's actually also uninstalled the wdm device from the device manager altogether.

i've got it set up to play through asio now, and i don't see any value in disabling it. but, it's useful to have the reference of checking to see what it sounds like through a clean directsound out.

i vaguely recall doing this, and vaguely recalling undoing it to access the midi out on the soundblaster. it's the only thing i've done so far that seems to actually turn off the windows interference.

the closer it gets, the further it remains...

but, i've found a workaround. the problem is now solved. i will be cleaning up this morning and back at it tomorrow, after groceries.

i've been operating under the assumption that there's a solution. the truth is that i can't state with any certainty that all of it ever sounded right through foobar at the same time. i was always mixing through cubase. there were always subtle differences. when i get one track to sound better through the kmixer, another sounds worse.

it kind of struck me this morning that even if i can get an ideal answer, it's not worth any more time - because this is just a playback issue. playback is very important, of course, for sequencing - and for what i'm doing right now. but, i've kind of spun myself around in a hole - i'm fixing the playback to get on to the task at hand, but it's only the task at hand because it was broken in the first place.

so, what i've done instead is upgrade foobar so that i can use the asio plugin. playback is now over asio, completely bypassing the kmixer and any resampling it was doing.

again: it's not that the results were terrible across the board. i kept saying it felt like i was close, but it was just not quite right. some of the tracks were sounding absolutely perfectly - others were sounding flat. fixing the buffer size, or unlocking the sampling rate on the device, or 100 other things would fix one song and break another. and, so i just can't be certain there is an across the board answer. and am really leaning to the idea that there isn't. that is, if i want the tracks to sound as they were mixed, i may have to switch buffer sizes mid-record, or some other crazy thing. i may be partly at fault for not standardizing things, but as i mentioned in the last post, it shouldn't be happening anyways; i think i'm trying to create something that never existed, and am exposing the flows in the windows sound architecture in the process.

moving to asio just throws the whole problem out the window. i get everything i want. it's technically superior, even. and, i can move on.

i can state for certain that i did move buffer sizes around from song to song on playback through foobar, because i had to to get the sound right. given that truth, i probably shouldn't have expected a stable set-up in the first place. that is, the culmination of the last year of work has created a playback mess over that system.

but it's done now...

i'm almost certain it's good to go. the last thing had to do with setting the buffer sizes, and this isn't supposed to make any difference on playback, but it definitely does. i can't really explain it, but it seems to be the last piece.

when you hear the term "streaming audio", it gives the impression of audio flowing from start to finish with no interference. that's what the language is meant to invoke. but, it's a digital process, so of course it's not true. rather, there's a continual process of small amounts of data moving into buffers, and the buffers moving forward like a conveyor belt. the buffer size is how big those chunks of data are, measured in samples or seconds or bytes. this is user configurable for largely historical reasons.

the conventional wisdom is that this shouldn't matter because it's just a determination of how big the copy operation is. it's broadly seen as a largely legacy issue, mostly to do with processor speed. older processors had to take larger buffers because they couldn't work as fast. what that would create is choppy playback, rather than differences in tone, because it was struggling to process fast enough to put the stream together in real time. but, modern processors don't have that problem, so it's supposed to be that it doesn't really matter.

but, that's not happening. i'm noticing that i need to get the buffer size to a certain minimum point in order to maintain tonal integrity, which is sort of weird. sometimes it's the bass that sounds a little thin, other times it's the higher parts - but mostly sustained parts. it's almost more like it's a reverb issue. and, this is known in some sense. if you put a reverb plugin on an out, then the reverb calculation will be different if it takes the stream in in small chunks than it will be if it takes it in in large chunks - because it's reverberating over different lengths. but, that only makes sense on playback if windows is interfering somewhere along the way.

in fact, i have noticed this previously, so reducing the issue back to an issue i've dealt with on a functioning system indicates i'm back in functional territory.

i need to eat. but, i think i'm very close.

this is also from before, and i won't post it there again, but i'll post it here:

this isn't just bowie's best record, it's one of the decade's best records. that little comeback stint in the 90s was his most interesting period, musically. but, will we ever hear it in it's initial and intended form?

(relevant file: schizoid, confused, on sexual confusion in adolescence)

obligatory influential post.
 

the last thing i need to point to for this feature is socal punk. my entry point was ultimately nirvana, but the real entry point was the offspring. i probably wouldn't agree much with gurewitz if we were to order his catalog; the offspring and bad religion are really the only two pop punk bands i'd bother with, because they have that higher level of harmonic complexity. and, coming out of the grunge collapse, it was increasingly socal punk that i turned to for my rock kicks. as a guitarist, the guitar style in those offspring and bad religion records up to about 97 had a big effect on me that you can hear for years afterwards in the fast, dissonant chord work - and often in more subtle ways, as well. and, if you've been reading my rambling, this should not surprise you, either.

(relevant tracks: on sexual confusion in adolescence, to spin inside dull aberrations, anything with a guitar, really)

this is a post from about a year ago, and i won't post it there again, but i'll post it here again:

this more or less replaced fixed as my go-to nin record for busing and had a big influence on me in terms of rhythms slowly developing over time. it's something that mostly comes out in the remixes, this sort of evolving, mutating thing...it's very much process music....

(relevant tracks: on sexual awkwardness in adolescence, symphonies 4 & 5, teenage jesus (suicide), others)

obligatory "influential on the featured track" post.

i often describe what i was doing in this period as synth pop, and tend to point to a lot of industrial influences, but there's also a large gaze component coming from bands like curve, garbage, mbv, the cure and (ultimately) the smashing pumpkins. it's just that it's a lot more subtle and kind of buried in the production. it's the flange on the guitar, the gate on the snare. for this particular feature track, though, you can really hear it - i'm just pulling this curve track out of a hat, though. this is a strong disc, but a lot of this music is very stylistically similar and i could point to virtually any of it as influential in the context i'm constructing it in.

(relevant tracks: on sexual awkwardness in adolescence, virtually anything after 1998)

obligatory "influential on the featured track" post.

it's sampled. in a sarcastic song about necrophilia. hey spidey, what are you doing out all night by yourself, anyways?

(relevant track: on sexual awkwardness in adolescence)

obligatory "influential on the featured track" post.

the prodigy kind of hit be my surprise in 1997. i don't know if the kids realize it, but 1997 was the year that techno really broke. there was that huge daft punk record. the chemical brothers. and, the fat of the land.

i was veering in this direction, but i was following more of an underground path, through offshoots of 80s industrial, which i'd been set on by a mild obsession with a couple of nine inch nails remix discs released before 1996, and a beginning exploration of the warp records catalog. research was largely done over the internet, and through conversations with people 5-10 years older than i was. i was aware of the raver kids around me, but i didn't really understand what they were. my intuition was that a rave was really just another kind of high school dance, and my punk instincts put me squarely against it as a consequence of it. looking back, i regret keeping an arm's distance from it - in hindsight, i understand that this was a very wrong perspective and that the truth is that if i was looking for punks in the mid to late 90s then the place i'd be most likely to find them at was actually a rave. i never really came face-to-face with the prodigy until they were roaring at me over muchmusic.

this isn't a record i've come back to much over the years. the fact that i was exploring much more abstract types of electronic music should say a little bit about where my head was always really at in relation to the genre, and what i'm really looking for; even jilted doesn't really hold up well, despite it's importance. but, the fact that something comparable to what i was searching out over usenet was coming at me from mainstream media was exciting to me for a little while, and it coerced me into biting into this disc pretty hard, for a little while. you can hear little bits of it all over the discography.

(relevant tracks: on sexual awkwardness in adolescence, evil is a human construction, subtle nods elsewhere)

obligatory "influential on the featured track" post.

i came at the aphex twin from a different angle. i do wonder if he's ever bothered to listen to a nine inch nails record, all these years later. but, reznor was a hell of a gateway to a fifteen year old in the mid 90s, and the aphex twin wasn't the first thing i delved into - it actually came at me via a roundabout way, through the skinny puppy side project called download, which is what really branched me out into the warp sound. i was initially more attracted to the more chaotic reaches of industrial music - i was a punk. and, as a "rock fan", i largely self-segregated myself from music in the electronic sphere. so, it took several years of easing into it before i could handle listening to "techno music". these mental shackles did of course eventually lift themselves, and i am certainly better off for it.

anybody coming from a multidisciplinary background and claiming rdj as an influence is going to be expected to point mostly to the breakbeats, and there's a few in there, but he was actually just as much of a compositional influence for me, as i moved on. i think we share a big influence from coil in that respect - although he's got about ten years on me. but, the orchestrated soft synths coming from rdj are what really defines him differently, and something i've made various attempts to emulate.

(relevant tracks: on sexual confusion in adolescence, clarity, the time machine, untitled; pretty much everything from 1998 on)

i've pointed out here a few times that my soundcards have been behaving poorly, and that i've isolated it, only to realize i hadn't.

i'm not sure what happened near the end of june, but it seems to have undone things in a way that i wasn't fully aware of. i'm running a very stripped down version of xp on my recording pc that cuts a large amount of the operating system out. in the process of trying to fix the problem, i seem to have put in place problems related to the windows xp sound mixer, which is known to be not very good for audio processing due to the way that it interferes with audio streaming. i think my initial script had broken the kmixer, and i had reinstalled it in an attempt to fix the problem, which created a whole other slew of problems.

i think i've fixed it in a two step process:

1) lock all sample rate conversion in the drivers.
2) delete the streaming drivers (mskssrv, mspclock, mspqm), which seem to be involved in conversion.

my initial script had deleted the streaming drivers, but not locked the sample rate. the result was that if i deleted the streaming drivers, i'd end up with fading because something was moving back and forth in the drivers. but, if i left the drivers in place, i'd get bad results from the windows conversion process.

locking the audio drivers without deleting the streaming drivers resulted in the files playing at the wrong speed, which seems to have been a consequence of an incomplete conversion process. but deleting the streaming drivers with the audio drivers locked in place seems to have resolved the issue.

i'm still testing, but i think i've got it figured out.

in the meantime, the alter-reality has caught up with me, and is now entering the synth-pop phase of my musical career (which was all of 1998 and early 1999). the catalyst was a four-track recorded that i got for christmas at the end of 1997. it's january 8th in the alter-reality; my first completed, uploaded track is dated to january 9th and will be featured tonight at midnight.

the featured tracks will now begin to change more frequently, which means i'll be posting more influences. there will not be any more lengthy pauses in this process for several years.

http://www.youtube.com/watch?v=bJ-_rMcOPD0&t=15m50s

shifting to period 1.2 in the alter-reality

i ended up losing yesterday after all in a haze of election ramblings. it's another six weeks still. but i'm going to do some listening this evening, and think i'll quick lose myself back in it as soon as i'm sure it's actually fixed.

the alter-reality updates tonight at midnight, which is the long awaited movement directly into the synth pop phase. the updates will be more frequent moving forwards, as the lull over late 97 has come to an end.

i made a decision last year to upload pieces from this period in larger segments, so the updates are going to be a little strange, with tracks moving in and out until the period closes a little over a year from now. this video has the first six songs from the first demo, but i'm really drawing attention to fourth track, which starts at 15:50.

http://www.youtube.com/watch?v=bJ-_rMcOPD0

i've been kind of moping around the last few days, wanting to keep my distance and my mind elsewhere, but i came back to it last thing tonight and i think i've finally got it.

locking the sample rate ended up consistently playing the files too quickly through wdm - a clock issue. again - sort of, maybe. so, i broke it again. and, this time, it seems to have come out ideally.

i've noticed that the streaming device is not reappearing. that suggests to me that it's part of the sample rate conversion. this may be the combination i had previous stumbled upon which broke the kmixer in the right way: it both locks the rate on the device and uninstalls the conversion driver, leading to a straight stream. or so it seems...

i have a little more testing to do, but it's a big shot of hope. best it's sounded in some time. i will get right to this in the morning, as i've got my focus and drive back.

well, this is hilarious - setting it to "headphones" seems to have made a rather dramatic difference.

i....think...i..

i can't remember.

that's some hope. i'll try it again when i wake up. i think it's another step to it, anyways.

not ants, but water

hi.

i've been checking for ants periodically, and it seems to be ok for right now. but i've noticed that some of the drywall in that enclave is rotting. it's over in the corner, pretty much directly underneath where the water from the air conditioner is constantly falling off the porch. i haven't touched it, but it's pretty obvious from looking at it that if i were to touch it, it would cave right in.

now, i don't know for sure that the reason the drywall is rotting through is water from the air conditioner. it's been humid, then cold, then humid, then cold, then humid. but, it *is* directly under where the water is coming down.

and, i don't know how substantial a problem it is - i just don't know.

but, i thought i should let you know that it appears to be rotting and that a good guess is that the water is dripping into there.

j

yeah, no, it's gotta be that fucking sample conversion - even on seven. because now that i've played it through bandcamp, it sounds better through youtube and locally through foobar. fuck. it's set up right. there has to be a way to stop it.

i'm going to see what happens if i just completely disable the entire wdm architecture and force it to play through directsound. will that even work?

i am so remarkably discouraged right now. literally nothing sounds right, and i don't have the slightest understanding as to why.

i have five years, now.

i'm considering putting it down for a few weeks and focusing on some reading, instead. the closest i can get to a decent sound is through bandcamp, which is a streaming mp3 at 128kbps. everything else through every other combination is completely wrong.

i dunno. like, if somebody wants me to give up on this, they might be disappointed at what i do instead. it's not going to be more productive. it's going to be writing essays of eighteenth and nineteenth century literature and posting them to a website nobody reads.

yeah. i think i got it.

the sound architecture in xp is much maligned. it's one of those examples of microsoft taking too much control over something that ought to have minimal operating system interference. they never *really* fixed this, but it changed a lot in vista.

i've known this the whole time but it was never really a problem before, so why would it be a problem now? well, i may have changed a few settings at some time in the past and forgotten...

the kmixer seeks to resample everything, in ways that often make little sense. it seems like the people that designed it didn't really know a lot about audio, they just figured that upsampling everything to the highest formats possible would be a best practice strategy across the board. that's not true, for reasons i won't get into.

both the m-audio and the alesis come with lock settings that prevent any modification of the sample rate from outside sources. locking the devices to 44.1 had a big effect on the wdm driver outs for both devices, presumably because it's stopping any sample rate conversion. an a/b with the asio outs through cubase actually suggest that this minor fix creates an inaudible difference through wdm and a larger difference through directsound. before i locked them, it was directsound that clearly sounded better. so, this is a big difference.

i want to draw attention to this, though. because i had both outs to 44.1. why would windows upsample a stream when the source and hardware are set to the same value? that is entirely absurd. and, who would think you need to lock the rate in place to prevent the operating system from interfering? it's utter madness, truly.

but, i think this is at least a partial fix. i'll need to do more testing over night to determine if it's fully fixed or only half fixed. but, the difference is quite positive and quite obvious, so i think this is the solution to the bulk of the problem.

the problem was less fixing the problem once i figured out what it was and more trying to figure out what it was.

and, the reason the soundblaster stayed stable was because 44.1 was the max - which was also the reason that switching from the soundblaster to the m-audio fixed the m-audio [it went back to 44.1, until it was re-opened].

what i'm leaning towards with the sound issue is that the windows kmixer is resampling and the directsound isn't; that is, that by playing through directsound, i'm avoiding resampling. so, i'm going to play with some things to see if i can try and lock it in at 44.1.

the m-audio and alesis can both stream at over 200K. but i don't want windows doing conversions on the fly, dithering, etc.

when i brought in the student loan forms, the psychiatrist and nurse practitioner got into an argument as to who ought to fill them out.

i don't blame them. the language is over the top. i would have a hard time declaring myself "severely permanently disabled", as well. the truth is that i'm really just an anarchist.

i left them with the forms. i have no idea if they'll fill them out. and, to be frank, i would not begrudge them for refusing to.

i may have to get used to living on $60/month less. if i'm not smoking, that's entirely feasible.

i called the student loan people today and they extended the waiver, meaning i'm good for another two months, anyways.

the psychiatrist also claims that he can't fill out hormone prescriptions - i don't think that's actually true. the nurse practitioner will do it, but only on the instruction of an endocrinologist. and, i don't think i'm likely to get through to this guy in london again. he's going to look into it. i don't want to go to toronto, but if i have to...

i was hoping this would just be dealt with yesterday, i'll be back on the 15th and have to make decisions about things as they come up.

as i've posted here before, the feminizing hormones are kind of secondary to me at this point. the more important thing is that i'm able to keep taking the testosterone suppressors. i'm more into rejecting sexual identity altogether. it's not that the identification has changed, i will continue to identify as mentally female whether i'm on the hormones or not, it's more that i'm at a point in my life where i've accepted that my gender identity is almost entirely irrelevant, because i'm going to spend the rest of my life by myself in my bedroom. it's hard to care about how you present yourself when you're not presenting yourself anywhere. but, the testosterone reduction is very intellectually liberating and of extreme importance. i never, ever think about sex anymore. i'd like to maintain that. i'm not a sexual creature. returning testosterone levels are just likely to be an annoyance and a distraction.

worst case scenario, i could probably get the testosterone suppressors prescribed by carrying out some kind of deviant sex act, like hanging out downtown naked for as long as it takes to get arrested. it would of course be a non-aggressive act. just enough to get the prescription.

it turns out that directsound is just a layer on wdm since 2000. weird. can't explain this, but it's clear...

so, the reason it sounded correctly through smplayer and poorly through foobar is that i was accessing devices in smplayer through the directsound interface and devices in foobar through the wdm interface. there is a workaround to this: i can set the device to default and then set foobar to the primary sound driver. this gets around the wdm kmixer and doesn't merely sound clean but sounds far superior..

kmixer is known to be crappy in certain circumstances, but what i'm experiencing over and over is far worse than anything i was experiencing previously.

i need to play with some things still, but it's now clear - seriously this time - that it's a windows/wdm thing. i just don't know if i can fix this, or if i should be working around it.

see, now it seems like it's fading through foobar and not fading through smplayer.

i'm falling asleep...

i'll have time when i wake up, before the appointment.

but, i ended up breaking it to the point where i had to do a last known good, which brought me back to a point where i'd might as well reinstall. one more time. shit to do tomorrow. back at it soon.

so, i was getting funky results out of the other players after all - it's not just a foobar issue.

the soundblaster actually stayed consistent out of the box for quite a while, until i broke the sound. it came back a little after a few things, but it's really the cleanest sound. and, i think i got the m-audio card stable through nothing more complicated than uninstalling and reinstalling the drivers, which is ridiculous - because i just installed them. but, that was after a number of over things...

i think i want to avoid breaking the system, because the soundblaster never really came back.

i've been noticing since day one that the m-audio card seems to perform better when a suite of system devices are running: the audio echo canceller and the kernel splitter, especially. the issue seems to have something to do with this. but it's completely inconsistent. sometimes, it drops out as soon as those devices do. sometimes, it sounds fine without them even turning on.

the only way to consistently turn these devices on is through cubase.

so, i'm coming to what is an endpoint. if everything is working except that card? i'm better off ignoring the card. i'll just disable it. and, so, i'll be back to work soon.

my goal today is to figure this out, finally, so i can get back to work on wednesday.

no, it's the same weird shit. grargh. well, at least it's clear, now.

if i open foobar on the laptop while there is no open stream in youtube, i get exactly the same blunted sound i'm getting on the recording pc. but, if i open it while there is an open stream (or i open a stream while it's open), it snaps back to the right sound.

so, it's like it can't load the drivers right, but if something else loads the drivers for it then it knows what to do.

keep in mind that this is subtle. i previously just thought it was inherent hardware differences.

deleting replaygain seems to have helped.

yeah. wow.

my baseline was screwed. lol.

yeah.

i'm noticing that this track, which is the one i'm using for testing, sounds better through youtube (with the obvious caveats of compression) than it does through foobar - on the *laptop*.

there's something funny with foobar on both machines.

which means my metric necessarily requires some shifting.

https://www.youtube.com/watch?v=vGbKDq95-Ro

i got most of my end-of-month errands done today (i'll have to do laundry tomorrow), and i've been lost in ranting on election articles in between it. i'm not sure i'll get much done with the rest of the day, but i did get the machine fully installed and it does seem like i'm getting clean signals from the two pci cards out of smplayer and winamp. i'm going to make sure i do solid testing before i even open foobar, to be absolutely certain it's the source. but, it's looking like it may just have been a triviality..

two months. ugh. at least i have five more years now, though.

it took me a few weeks to come to terms with the fact that i got the five years, but i'm also now completely done smoking. this is the necessary incentive. i set my september budget this afternoon, and it had zero for cigarettes - which means i should be able to finally build those shelves at the beginning of october with the money i save. i was waiting to see how it turned out because...what's the use in building shelves if i'm hitting the streets...but, five years is enough to get me comfortable down here, and maybe even lead to a change of mind if things turn awry when the next renewal comes up. i'm not going to pretend that i can predict what i'll be thinking by then. but i think i may be unlikely to want to move, at any cost.

i have one last appointment with the psychologist on tuesday. it was meant as a follow-up to see if the results came in and how i feel about it, which they have, and which i feel good about. but, i'm going to try and get him to fill out those student loan forms. the condition is supposed to be permanent disability. it's kind of shady. but, you'd think five years on odsp is enough to get the message across: this loan is merely going to generate interest indefinitely. i've decided that if i gets cleared and i somehow come into money, i will....i'm not going to give it to the state flat out. i'm going to donate it to a career services organization that helps young people determine what they want out of life before they go to school through objective skills testing. i think that's what the system is missing. i'm not talking about some kind of soviet-style forced study or something, i'm just talking about a little guidance that's able to put people through aptitude and psychological testing and able to provide suggestive results. there's obviously a problem. i don't think we need corporations to take over the education system. i just think we need to invest in guidance, and remove the taboo around it.

i'm also going to see if he'll just fill my prescription for five years. that would be the easiest answer. as far as i can tell, the doctor i saw in london has also shut his practice down. that's two doctors in a row that have shut down, and there's only one doctor here in windsor and he's a prick. at least these guys know me a little; it's a simple request, and i can't think of any good reason they'd deny it.

if that all happens as planned, i should have all this annoying calling around everywhere and getting forms filled out stuff completely out of the way for years into the future. and, that will be good.

so, it seems like i'll be good to go and back at it in a few days. hopefully, that works out.

well, this is embarrassing.

both smplayer and winamp seem to be functioning just fine. it's a problem in foobar.

that really should have been a very early troubleshooting step. i guess when i realized that the clock was screwing with the asio output, my head get locked into something under the hood. and, it may be that there's two problems here, not one. but that's still something i should have ruled out early.

i'm going to get the whole thing set up properly and test again. if it works out, i'm left concluding that foobar is foobared.

my best guess is that i'm transferring something over from a past install and it's just a question of reinstalling the program.

but, then again: winamp is ancient. and does smplayer (a linux port) use kmixer?

hey, if it's a workaround i'll take it...

i'm mixing in asio, mostly. through cubase. i just need a playback strategy. if foobar is foobared because of windows (see, i know i could often hear a difference, but i can't quantify this - and it seems much worse now than it ever did before), and smplayer gets around it, then great.

i also need to point out that the alter-reality is on the verge of finally shifting entirely into the synth-pop phase. i was hoping to have the reconstructions that i'm doing complete by the time i got here, but the bloody machine won't co-operate. i can't put the alter-reality on pause, it needs to keep flowing. and, in some way, this is an addendum to the process. but, the posting cycle is going to be a little unclear until i determine exactly what i'm using to promote the exact releases.

but, this is the primary release that the alter-reality will be exploring over the next six months, starting a few days into september. the disc is split into songs and experiments. the bulk of the songs (5 of 8) were recreated from the demos that the alter-reality has already gone through, but they have been updated to include synthesizers, drum machines and other types of electronic noise - they are very different from their initial incarnations as noise-punk demos, although it still comes off as relatively lo-fi due to the fact that i only saved the material in low quality mp3 files (112-128 kbps), although i've cleaned it up quite a bit and the fidelity is really no longer poor. some of the experiments were retroactively constructed into inrisampled, but they were almost all initially constructed originally for this disc.

i've seen traffic go down a lot over the last couple of months, as the alter-reality has run through a pause that corresponded to a period where i did not have recording equipment available to me. as this shifts out and back into an active phase, i'll be more actively promoting the material again, and will hopefully see a corresponding return of traffic.

that said, the audience for the synth-pop period would necessarily be rather different than the audience for the noise-punk period. and, all i can say about that is that i'm curious as to what happens.

the alter-reality is currently just after christmas, 1997. the release date for this record is june 20, 1998. so, this will be a process of promoting songs intended for this record as they were completed, until i get there some time early next year.

https://jasonparent.bandcamp.com/album/inri-3

this may turn out to be a lot more trivial than i thought.

i've started from the absolute beginning: i'm not even installing chipset or video card drivers. the soundblaster drivers are on the install disc.

when it first comes up, before installing anything further at all whatsoever, it's a little trebly sounding. i recognize this as the way it sounds when it's broken. a reboot brings back the same cut highs i've been fighting with for weeks.

first, i tried to break the plug & play and this did work - until i re-opened foobar. what? how? so, i deleted the config file in foobar. it went back to a clean sound - until i re-opened it again.

this is the only thing i've found, up to this point, that consistently creates and recreates the issue. could it just be a corrupt setting in the foobar configuration file? could it be that easy?

see, here's the thing: essentially everything i've done up to this point forces me to reset the driver in foobar. breaking the plug & play, reinstalling the drivers, etc all has the step of repointing foobar to the right driver. meaning i'm always resetting the configurations.

what's interesting to me is that this is basically the same type of error that i'm getting in cubase: something is saving incorrectly, or loading incorrectly on the save. could there be an underlying issue at the root of both? if so, it's not ram, because i got it on the other machine, too.

i'm going to slowly continue the reinstall and see if this remains constant.

the only thing i can think of is that when i installed the vanilla xp on the pentium III, it was a version that had been slipstreamed up to the end of the product cycle. i guess that takes me back to the idea that i need to remove something from the xp install - that an update has broken something fairly central. if i get to the end of the install process and am face-to-face with something as trivial as this, i'll have to start from scratch with my sp1 disc and slowly move forwards, service pack by service pack, until i get to the problem.

i think the error that a lot of these studies make is that they compare serious music before 1955 to folk music after 1955. there's certainly been a merging of the ideas starting with zappa and the beatles and pink floyd. but, i really don't think these differences come out if you do like comparisons: debussy to stockhausen or nirvana to ledbetter or bjork to billie holiday or one direction to traditional nursery rhymes.

the only thing i'd pull out as probably being substantially different is that you previously wouldn't expect people in their 20s, 30s, 40s and 50s to experience the kind of arrested development they experience today. they would have grown out of the nursery rhymes, not latch on to successive ones until they're grandparents. so, the real issue is the juvenilization of society.

www.smithsonianmag.com/smart-news/science-proves-pop-music-has-actually-gotten-worse-8173368/?no-ist

dammit, i got it. finally. and then it disappeared.

it's hard to know what is exactly the right set up, because i'm dealing with relatively subtle shifts. there's been a few times where's it's not been clear. but, when it is clear, it's crystal clear.

i broke everything, to the point that i had to install the m-audio card to get the audio subsystem back up. i then restarted the computer with the plug and play service disabled, then turned it on when the computer came up. there was about four minutes of beautiful clarity. and, then something turned on and it clicked back out.

i didn't have process explorer open. when i tried to recreate the scenario, i couldn't. which suggests to me that whatever it was that clicked in wrote something to the registry, and i'll have to rebreak it again to get back to where it was.

i think that points to the wmi as the most likely culprit.

i'm still testing. but that's the closest i've been yet. something is loading on startup in windows that's doing this.

i'm testing on a system that doesn't have my script implemented because i want to isolate what the fuck. but it may be the case that such a process would have a different result on a fully installed system because whatever's clicking in may not be able to reinstall itself.

again: i vaguely remember playing with this before.

actually, you know what i can do is turn the boot log on and isolate one by one...

nope. came back. i'm going to have to start breaking more stuff, i guess. plug & play, maybe.

it's just this cut at the high end...like a low pass...

ok, so it seems like i'm making good progress on the bust-it-and-reconstruct-it approach. and, i have a vague memory of doing this about a year ago. these vague memories. sometimes, it would be nice if life had a rewind feature so i could go back and see.

i'm on the brink of convincing myself this is stable and good. next step will be seeing what happens when i get the m-audio drivers in. i just need to let the ram clear and do a fresh start-up...

thoughts on the latest spencer krug recording

i've listened to a few tracks off this record, and i'll admit that i grasp why a pop audience would react positively to it - it sounds fancy. i'm not being an ass on purpose (although i probably couldn't prevent myself), but it's the basic idea. it gives you the opportunity to put down the garbage you normally listen to and feel sophisticated and upper class for an hour. and, maybe it might act as somewhat of a gateway.

but, it's just so terribly contrived. the cadences. the crescendos. it's blatant cliche, and clearly consciously designed to maximize itself as such. and, on top of that, he plays the instrument like a blunt poke in the eye - most of the record sounds like a player piano. not a sequencer. you can program dynamics into a sequencer. this is just straight artillery fire.

the guy has demonstrated potential. and his refusal to do what he's expected is definitely refreshing. but, i'm sorry to say that this is some of the deadest piano music that i've heard.

thoughts on the new pinkish black single

the last one took a bit to click, but it eventually did, and this is likewise a bit disorienting. you have to give this band full marks for a subtle evolution. but it comes with the caveat that they're getting harder to follow because they seem to be getting poppier and poppier.

this is moving slowly into something like spencer krug territory.

(that one record he did, organ music - not vibraphone music like i hoped, is actually uncharacteristically interesting. it's a saturated space, with a lot of mediocrity, but nothing hits you in the gut like a good, dark, smart synth pop song.)

nope. soundblaster is doing the same damned thing with no further drivers installed.

it's a windows problem. i knew it was a windows problem from the start. and i can fix it for a bit, but it never sticks.

i need to get groceries. but, i'm going to have to start breaking some stuff when i wake up. it's gotta be installing broken.

it may be that i have to break everything immediately and then install it all on top of that.

*sigh*. that got me nowhere. it's back to the bleeding on the m-audio card.

i'm going to take a step back and test with the soundblaster on an m-audio non-install, because i don't think it's doing this. if i can convince myself of this, i'll try leap-frogging the m-audio install and testing directly with the mixer.

i don't actually use the m-audio card for recording. i put it in the system years ago as a playback card, meant for more living room type applications. if the setup is stable without it, it's not worth fighting with it - i'll just take it out.

on 800th thought, i'm getting the same outcome from the m-audio card on immediate install, without even turning the mixer on, suggesting the conflict is probably with the soundblaster. and, listening to some stuff i've done over the last year indicates it's definitely not the setup i've been using.

so, i'm back to checking things on and off, one at a time. at least i have a reduced set of options, this time.

yeah, this driver conflict is persistent. and, to be entirely honest, i don't really have the will to resolve it - i just want it to be stable so i can get back to actually making stuff.

hopefully the following plan is workable. i'll have to test it...

1) restrict the wdm to the m-audio card. that is, do not install the wdm drivers for the alesis device.
2) only use asio to interact with the alesis device.

i think that this will avoid conflicts. and, if i can determine that the outs are essentially interchangeable, it won't matter much.

after i've tested this a bit, i'm also going to see if i can find an asio media player. foobar ought to work, but i can't find an xp-period component.

both devices can connect over asio. i don't think there's a conflict over asio, it seems to be specifically in the kmixer. but i guess we'll see.

actually, i think i can answer that. it was fine until i reinstalled the mixer drivers, then the pci card went back to the same flat sound - and consistency remained across the cards. so, it's a driver conflict. but, then i fixed it by running the registry part of the driver install.

i'm spinning myself around in circles. if i leave the registry part of the driver install on, i get the clock fades. if i don't, i get a driver conflict. i'm going to have to hone in on that and just take out specific parts - probably just the clock driver.

mild levels of testing are still necessary, but i think this is it.

....and, then it clicked.

i'm getting the same dead tone out of both cards.

so, if i was mixing on the mixer, and i listened to it through the pci card, it would sound the same. and i'd never know.

so, out of desperation, i busted the wdm by uninstalling it, moving the driver, restarting and reinstalling.

this actually worked.

i'll have to test it a bunch more. but i think that's it: i need to bust the underlying windows architecture flat out and reinstall it.

why that might be is a different question....

it doesn't seem to be actually recognizing the device as the same device when i turn it off and on, and further experiments have just brought me back to randomness: sometimes i get the high filter, sometimes i don't. it's not the flash that's actually doing anything, or the driver reinstall. it's just turning the device off and on. it keeps adding a new unique streaming device in: sad 12, 13, 14, 15....

i think i kind of have to get that right, first. none of the other devices are doing this.

it suggests in the documentation that i should turn the device on before the machine. i never have. but, i'm going to see if it make a difference in recognizing the device as the same device or not.

it's not actually connected to the streaming proxy service, it just seemed to be. it must have been something else running under there.

i'm at somewhat of an impasse again. the flash is fixing it, which again seems to reduce it to a driver issue.

i'm running out of patience. i'm going to see if i can stabilize it on this install. if i can't, i'm going to do a final install and just flash on every use. i'm really sick of this, take no enjoyment in it and want to get back to what i was doing.

my understanding of the situation is continuing to evolve. i've isolated the proper components, it's just a question of getting them in the right order.

the reinstall with the registry run removed eliminated all bleeding, but brought me back to the point where the highs are turning off and on. but, i've learned that this is not random, as i previously thought. rather, it's connected to the streaming proxy service - the broken clock.

when this service is launched, i get the full spectrum. when it's not, i get reduced highs. and, when it turns off [as it does], i get those annoying cut-outs.

but, the service doesn't launch through foobar - it only launches through cubase. again, this is explanatory, as i was noticing that cubase sounds differently than foobar. the service will sometimes stay on after i close cubase, at which point the foobar out will keep the highs - until it stops, when the highs drop. further, whether it launches with cubase or not is sporadic.

the firmware flash is no longer modifying the output, which indicates that the issue was in fact in the registry. but, it's also made it more difficult to get back to the sweet spot. the flash doesn't always work.

i strongly suspect that the point i'm at right now was the starting point; the sound is acceptable, and probably defines the differences i was noticing previously between the different hardware, and just thought was hardware dependent. it's relatively mild. but, now that i know it's not clean, i have to fix it.

the basic problem seems to be that the service is no longer connected to the devices.

but, i know that if i connect the service to the devices via the registry run on the install then i get fading.

i'm also noticing that the other card in the machine is maintaining consistency with the weak highs. in the past, i may have misinterpreted this - i may have taken the consistency as indicating both cards were working, and then concluded the output was solid, when in fact there seems to be a root problem that is affecting both cards.

there's two things i can try.

the first is that i can try a reinstall without breaking that first aspect of the clock. as mentioned before, it's only that first part that i'm certain i was reinstalling and only the first that windows is recognizing post-break. the other two, i'm just blurry about. i'll have to check to see what i get out of that - and i can do partial installs for this purpose.

if that creates the same basic issue, the next step is to put that part back in the registry run on the driver install.

if that brings me back to the bleeding, i can try and take out the entire clock break.

so, that means i'm now going beyond trying to get back to where i was and trying to fix a problem that was there the whole time but that i never noticed.

i don't think it will be much longer. i'm pretty sure i've got my head around this, now - i'm no longer taking guesses. the guesses have isolated the issue, and now i'm zeroing in on it.

i tested the issue by flashing the device and leaving it on for a reboot. if it was a firmware corruption, it should have come up clean on the reboot - because the device stayed on. but, it didn't. so, it's an error that's happening when windows recognizes the device. and, because it's not happening on the flash, it has to be the result of some kind of corrupt registry setting - because everything else would be the same, whether it's rebooting itself on the flash or being read as a device by windows.

when i do the reinstall, i'm going to try and clean as much out of the registry as i can get out of it - and i do think i can probably get this to work. but the class installer uses long strings of numbers that are difficult to track down.

i can't explain why this wasn't happening previously - except that it maybe was, and i didn't notice. which is another layer to keep in mind as i'm reanalyzing material.

the other thing is that i have a vague recollection of deleting the filters on the install a while back. so, those filters might have been gone for quite a while. i can't clearly remember. that's something i can script, and should so i don't forget.

the driver reinstall helped substantially, but it still seems a little distorted, so i'm going to reinstall a final time - i feel i have to to be sure i've actually hit the root of the problem. but i think i'm starting to finally get my head around what actually happened.

1) i think i cleared out the registry on the last reinstall, some time ago - whenever it was. spring of 2014, maybe.
2) then at some point in may i put that file back (streamci.dll).
3) on a driver reinstall (these are done from time to time, to deal with funny plugins), that screwed up the registry.
4) when i deleted the clock before, it didn't matter - because i wasn't really using it for this device. but, the combination of the driver install and the undeletion of the clock created a conflict. i suspect i should be able to reinstall the clock after i stop the drivers from entering that information into the registry.

the root cause of all of this, then, seems to be the driver install with the streamci.dll in place. i suppose i may have exaggerated something with that codec install, but it wasn't the actual crux of the problem.

it's continuing to behave poorly, but it really has to be a registry issue. i'm going to try a driver reinstall, but if that doesn't work i'll have to back up and do it again - this time inserting a wipe before the reboot, to prevent the install from completing.

on a clean sweep install with everything the way it was saved a few weeks ago, which means that the streaming proxy bit & clock are broken, it no longer bleeds. it's stable on the out. but, the out is missing a layer at the high end. it sounds like less an eq dive and more like a straight low pass, but i'm suspecting it's more along the lines of that a part of the stream is broken. it's pretty high - around 10 Khz or so. and, if you'll recall, this was the basic problem i noticed in the first place, which had me mixing higher than i wanted.

but, here's an interesting fact: i've pointed out before that a firmware flash resolves the issue. and, that's what is continuing to happen, but only until i reboot the device. it's quite strange.

in theory, i could just flash the firmware every time i turn the device on. but, that's kind of scary. if the power goes out when it's flashing, i could brick the device. and, if the issue is that the firmware is instantly corrupting, i want to think about replacing it.

this is a track i mixed with the highs faded out, and it sounds extremely tinny to compensate.

https://jasonparent.bandcamp.com/track/im-sure-your-mom-is-probably-a-very-nice-person

the exaggerated painfully tinny distortion is a consequence of having the volume cut at that frequency.

as mentioned previously: i'm absolutely certain that i've updated those streaming drivers before. and, when they're installed, the audio has a thicker sound that is preferable. but, it's the only thing left to test.

no. it ended up fading again...

i'm down to my last reinstall. i'm going to not reinstall the clock at all this time. if this doesn't work, i'll be forced to conclude i have broken hardware.

i'll at least now have time to save up. i'll have to think carefully about whether or not i decide i want to mix on the m-audio card in the mean time.

well...the last, final check will need to be an install on a vanilla xp. but, it would make no sense to think that would work. it's just a final confirmation.

the fade ultimately sounds like some kind of limiter that kicks in around 5000 hz, and makes the end result sound very compressed. i can't mix around this.

and, the highs are a little weak in the same spots. ok. it seems like i'm flat. let me convince myself entirely. but i think i'm back in business. i may have to revisit a few things for a slight treble boost, but i think i'm ready to go.

from the rooftops, shout it out...

things are back to "normal", now. i'm just not sure that's for the best, quite yet.

returning back to the initial script actually created the following flow:

1) install windows - with streamci.dll & the clock in place
2) install the m-audio drivers & other basic drivers. reboot.
3) install tons of software & the mixer & line6 drivers. reboot.
4) on the reboot, streamci is run as a dll. then the script runs: which deletes streamci.dll and breaks the clock.

when it came back up, something familiar happened that i hadn't seen in a while: it took a very long time to load cubase. i can see now that this is a consequence of breaking the clock. but, only the streaming server needed to be reinstalled. the other two appear to be unused by any of the cards. i was certain about that one, and less certain about the other two.

my hypothesis is that what i want to happen is for the drivers to install properly, and then i want to break the clock and reinstall it in such a way that the drivers aren't directly connected to it. that would make sense if i was essentially getting a conflict between the clock in the mixer and the clock in software. i don't want these synced. i think that breaking it and reinstalling it essentially unsyncs them.

so, it's stable. i'm quite confident that this is the setup that i've had over the last year and a bit - that is, this is workable and i'm not worried about it breaking.

but in the course of playing with a hundred things, i think i managed to make it sound a little better. and, now i'm wondering if i can't find a way to get back there.

what i'm going to want to do is test it against other cards. what i want is not the "best" sounding output but the most accurate sounding output. the bass sounds great, and the highs are stable but they seem a little weaker than they were at points, previously. but, is it the case that i was exaggerating the highs (and just like that better) or is the case that i'm still a little flat?

obviously, i can't expect everything to sound identical. but, the laptop is still the flattest source, and the best comparison i have.

should i be convinced that the tracks are clean, i can get back to mixing. if i'm not convinced, i'll have to take a look at possible approaches to aligning the output on the card. and then lock that down into the script.

the laptop is not quite able to produce the same bottom end, but i am legitimately happy with these mixes. it'd be really nice if i could just move on already. soon, hopefully....

my original script notes indicate that i had the file deleted along with a pile of networking files. i no doubt thought it was for network streaming. deleting anything that could be used for behind the scenes network traffic was the primary motivation in cutting the install up. it was just purely by accident that i was deleting it, and the only reason i put it back was that the dialog box was annoying.

so, this is a little embarrassing, really - i caused this problem myself. but i'm now absolutely certain it's resolved, too....

my idea that i got a corrupted dll in an update is not right. the modify date seems to be connected to the burn date on the dvd; the dll is passing a crc with a version from 2001 - meaning the dll has probably *never* been updated.

this piece of gear has a bad reputation, and i guess this is a plausible explanation for it - the driver install breaks it. i just never noticed because i always deleted the class installer before the install finished.

yeah. that was it. i'm getting very, very clear and stable highs - so clear, it's kind of shocking that i ever thought what i was getting before was clear. but, the bass seems a little weak. i'm not sure if that's relative, or if there's some remnants floating around in the registry, so i'm going to put the script back to the way it was - delete streamci.dll and break the clock on install - test a little further and then probably do another reinstall.

yeah, my back-up script change-log is dated to april 26th and it doesn't make mention of streamci.dll. so, it was taken out of the script in may or june. i may have previously never attempted to install drivers without deleting streamci.dll first.

the streamci.dll file on my xp disc is dated to april, 2014. so, it must have been updated in one of the very last xp updates that i slipstreamed in. it might have broken something. if i can demonstrate that this is stable, i'm going to try another reinstall with an older version of streamci.dll - one that is at least as old as the drivers.

simply disabling the wdm driver produced a stable output, but it was a little flat - it didn't sound right.

the autorun in the registry is running streamci.dll as an executable and carrying out a number of commands related to the wdm and the clock. that makes perfect sense - it's the class installer. but, that seems to be what's screwing it up. and, it's still the clock. and still windows, like i thought at the very start...

streamci.dll was also in my initial delete script, but i took it out a while back because i'd get "missing or corrupt" errors on the first boot after a driver reinstall. i can't date this, but it's not that long ago. april, maybe, even. i can see now why that is. but, in the past, that means the autorun didn't actually execute - because the dll wasn't there.

so, i tried reinstalling the drivers with the streamci.dll deleted and the autoruns removed (i'd just get the error if they were there...) and it seems to be stable.

no, it seems like it's a driver conflict after all. the driver that's in conflict?

itself.

might explain why it didn't want to isolate...

the mixer loads two drivers: one for direct access, one over "wdm". i'm almost certain that the final solution, for now, is to disable the wdm driver.

the wdm driver is being used to playback final mixes over foobar, and i would absolutely like to resolve the concern. it wasn't like this before. but it seems to be a registry add.

if i uninstall and reinstall the drivers, it will be stable after the first reboot and gets funny on the second. some values are added to the registry on start-up. this seems to be the actual cause.

for now, i'm not worried about fixing the wdm streaming. i'll just leave it off when i get back to it. when i wake up...

but, again: it's bizarre, difficult to isolate for problems, one after another.

dammit.

again.

ugh.

i'm going to break the clock again and see what happens...

it seems like that flattened it out. which is weird. because i thought it was the problem in the first place. and it left it a little jagged - but at least it's not bleeding.

i have an idea...

there's three drivers attached to the system clock in xp. there's the streaming proxy, which i'm nearly absolutely certain was functioning before this mess. there's the microsoft streaming proxy clock, which i'm pretty sure was functioning. and, then there's the microsoft streaming proxy quality manager which i have little to any memory of. i suspect it's the third of these...

when i modified the script, i removed the deletion on all three. so, the issue may have been sitting under my nose the whole time.

i'll have to test. again. ugh. but, it's gotta be it.

i swear, my body has loosened up by a factor of 80%, if such things can be measured, which of course they can't. but whatever stress buildup existed is fading away. and, that should actually help me focus a bit better.

it should also help me kick the cigarettes. it seemed pointless when i didn't know how much longer i'd be alive...

i bought one more pack for the next day or two. i need to put the election shit down and get through the remaining tracks for this. that last track is bugging me, because it just sounds kind of odd. i may end up replacing it after all. and, the next few should be pretty quick to pass over.

my odsp was extended until 2020.

i can stop worrying about that, now.

by 2020, i am exceedingly confident that i will complete my discography and be moving into phase 2.

checks

hi.

just letting you know that my disability extension was approved, so i have checks ready to give paul for the rest of the year, whenever he's home to take them.

j

not updating i still don’t fully understand this

this one is a little different. i initially rendered it on july 5, with an unknown combination of ram and save mixer settings - but that i think was close to mostly saved settings. the fact that it sounded bad was one of the first things that tipped me off to the broken drivers. i noticed that it sounded better in cubase than it did through foobar, so i re-rendered and re-uploaded it on july 12th with completely saved settings.

it doesn't pass an a/b with reset mixer settings. so, i'm just going to leave it as it is.

https://jasonparent.bandcamp.com/track/i-still-dont-fully-understand-this

not updating in some neighbourhoods the boogeyman is slightly more than an imaginary monster

same as the others.

https://jasonparent.bandcamp.com/track/in-some-neighbourhoods-the-boogeyman-is-slightly-more-than-an-imaginary-monster

https://jasonparent.bandcamp.com/track/ogyanemob

not replacing thug culture is enforced by the media from the top down

yeah, this is static.

the gain on the tracks is clipping mildly, but it's covered by the compression on the master. it took me a few tries to figure it out (and fears my drivers were broken again...), but rendering the tracks separately through the initial eqs is introducing clipping that transfers over - because they clip clean, when not sent through the compression. that's not something i can work around. modifying the volume will modify the null.

again: the neurotic geek in me wants bitwise perfection, but the a/b's tell me this is pointless, anyways.

https://jasonparent.bandcamp.com/track/thug-culture-is-enforced-by-the-media-from-the-top-down

contemplating replacing thug culture is enforced by the media from the top down

i'm still determining whether i want to replace this one or not for idealist mathematical reasons of it being bitwise identical to the initial save - although that's going to be false for the bulk of what i end up constructing. but, the reality is that it also fails the a/b and anything i replace the existing file with will be inaudibly different from the existing file. so, this is also done, for all intents and purposes.

https://jasonparent.bandcamp.com/track/thug-culture-is-enforced-by-the-media-from-the-top-down

not updating use value is somewhat difficult to define in the human propensity towards artistic expression

this track has also not been modified, and also failed the a/b.

https://jasonparent.bandcamp.com/track/use-value-is-somewhat-difficult-to-define-in-the-human-propensity-towards-artistic-expressio

not updating there is definitely something wrong with hipster homophobia

i've skipped a few tracks because they have more complex constructions. this track does not pass an a/b, either, but the version that's uploaded is already the mathematically correct one, so there is no change.

https://jasonparent.bandcamp.com/track/there-is-definitely-something-wrong-with-ironic-hipster-homophobia

i'm getting a better understanding of the mixer error.

it's 1/3 of a decibel somewhere in the bottom mids. like, honestly: 0.3333333333.....

that suggests some kind of rounding error as a consequence of a type conversion. but it seems to be hard coded into the program.

i'm not hearing it in most a/b's, and the compression i'm using is wiping it out almost entirely with that mild adjustment.

as mentioned: i'm neurotic. i must check.

but, it's almost certainly going to be more or less universally inaudible in anything with any compression. and, that's good news.

updating the threat of terrorism is used to restrict civil liberties

i've corrected this mix, but i doubt you'll be able to hear the difference - because i can't. the eq on the bass was demonstrating the mixer problem that i've now determined is widespread. i've corrected it to be the same mix that i initially created in ram in a mathematical sense, but this is a kind of an idealist triviality. multiple a/b testing has determined that i cannot identify which is which. in fact, the difference file even nulls over the verses under the mastering compression.

initially written in 1996. recreated in feb, 1998. reclaimed june 29, 2015. corrected to control for malfunctioning electronics on aug 11, 2015. 

https://jasonparent.bandcamp.com/track/the-threat-of-terrorism-is-used-to-restrict-civil-liberties


https://jasonparent.bandcamp.com/track/werso-smidits