Sunday, July 6, 2014

i'm practicing a four bar piece. it's simple enough, should be in quick. but these are the timings on the four bars, in succession:

15/16
16/16
20/16
13/16

it might seem hard to count, but, see, the things is that you'll note it adds to 64/16, which equals four "regular" bars of 16/16. i was thinking consciously in those terms at the time, trying to find ways to make the signatures unusual without breaking the four. and it's why it works as a techno tune, despite being all over the place in terms of timings.

i could conceivably re-bar it to 16/16, but it would make the emphasis on the bass notes make no sense. bars aren't really about time signatures (i don't actually ever notate time signatures), they're about splitting up phrases...

so, if you tried to dance to this, you'd be confused, but you wouldn't get lost - you wouldn't know why you're confused.

well, unless you're a musician, then you'd get it.
i posted this to the wrong profile. whatever. not like anybody in my facebook list really cares...

but the truth is, while i'd like to say i've entirely given up on trying to sell anything directly, the actual truth is that i never really made a serious effort to market any of it. i've played something like four open mic nights over almost twenty years. i've never even asked anybody for a show, because i know better than to think i have enough friends to fill up a bar, so why bother playing in an empty room? meanwhile, those bars get filled by social groups producing music that i consider to be nowhere near as interesting, which keeps me out of the social scenes i'd need to interact with.

and i realize i'm too old for that, now.

maybe i should take a marketing class, but what i've instead always been interested in focusing on is ways to take myself out of the game and just create, under some kind of fatalist conception that it will find an audience after i'm gone. i used to think i could find a day job and just create in my spare time, but i learned that's not really feasible - and i've since lost the ability to gain a day job, anyways, making it unrealistic to think in those terms.

a self-fulfilling prophecy, i suppose, brought on by an unshakable (if naive) belief that it will all work out. all i can do now is continue creating, and hope somebody finds some parts of it that they connect to in some way.
i just woke up, and i have to keep going back to the same point.

i've tried to avoid friendships with market advocates over the last few years by reducing them solely to intellectual opponents, but i've heard a lot of those arguments and they're hard to shake if you're insecure, as all artists have to be. they're also a part of day-to-day life, whether we choose to reject markets or not....

in the end, after all the arguments, the only important conclusion is this: how am i supposed to know what kind of reaction my larger, serious pieces are going to get in society at large when they've been heard by around 100 people, on average? and, that 100 number is relative to recent attempts to promote better through social media. for a long time, it was more like twenty people, most of them friends and relatives.

it just doesn't provide for a large enough sample. and, i know that's my fault (i guess) for not having the slightest idea of how to sell a product. but there's just simply no logical connection between being a good salesperson and being an interesting musician, despite requiring both skills to be a *successful* one.

i've been through this so many times. there's no use going through it again. i just wish my brain would fucking drop it already.

Saturday, July 5, 2014

cool.

i'm going to ask an obscure favour, and actually throw it right out there for general request. i'm used to writing drum patterns in general midi over track ten using a staff and actual music notation. the reason i like to do it that way is that it provides absolute freedom in terms of time signatures, note lengths, etc. i mean, i may want to drum from 5 to 7 to 13 to 17 and back around to 8 in the space of a few bars, and have 64th note crashes (which may not be possible in reality, but reality isn't important when you're programming drums). vst drum machines generally just cannot provide that kind of flexibility, because they carry the interface forward. i get why they do it - it's what everybody wants - but it would be immensely useful if they'd take on track 10 compatibility so they can read a "regular" midi file, instead of forcing users to reduce themselves to their limitations and quarter note, bar-based interfaces.

that leaves me stuck more or less with using a soundcard emulator (like bandstand) for drums, which gets the job done but kind of takes me out of the drum machine universe, as well.

could you program this thing to read a standard midi file?

why are all the linn demos on youtube trying to make it sound like an 808? these were high end machines, put to good use mostly in art rock by the likes of peter gabriel and laurie anderson, not low end club devices that djs could afford.


uploading the time machine (vst mix) to youtube

i've created a video for the vst mix.

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



original video taken from here without requesting permission:

http://www.youtube.com/watch?v=ZNc-OzFhDnw

uploading the time machine (vst mix) to thru (final mix)

written in early 2001. drastically rearranged in june, 2014. this render was initially created on june 28, 2014 and updated on july 5, 2014 to fix a minor error in transcription.

the time machine (vst mix) (final mix)

this is the vst mix, which hooks up the constructed score to a series of vst instruments through the magic of midi sequencing and outputs the notes through various effects processors to create something approaching the sound of a live band.

written in early 2001. drastically rearranged in june, 2014. this render was initially created on june 28, 2014 and updated on july 5, 2014 to fix a minor error in transcription.

well, silly me. it seemed to be a latency issue, but this is weird and maybe something to take note of if you do these things.

with a bit more experimenting, it didn't seem to be any specific plugin. if i unfroze 2 or 3 of about ten running simultaneously, it would run fine. so, i'm back to cpu or ram. except that doesn't make sense because one freezes to open up cpu and ram.

i noticed that some of the frozen tracks were frozen at different latencies. the drums were frozen at 256, but i had to increase the latency in the process of finishing the thing, so i froze the bass at 736.
what i did to fix it was to go back and make sure everything was frozen at 256. then, when i played back at 736 it was smooth.

i'm not sure how that makes sense. maybe what was happening was that i was getting some kind of wave interference on the playback, due to the sample rate.

whatever it was, it's working now and i hope to get some work done today.

what i mean is that the files may have been out of phase, and what seemed like a stutter was actually a cancellation.

just a guess...

Friday, July 4, 2014

the time machine (vst mix) (third correction)

written in early 2001. drastically rearranged in june, 2014. this render was initially created on june 28, 2014 and updated on july 4, 2014 to fix a minor error in transcription.

http://jasonparent.bandcamp.com/track/vst-mix-2

the time machine (soundblaster mix) (final mix)

this is a primitive mix, built up in noteworthy, that suffers from a slightly blurry drum sound due to everything being run through channel 10 in the soundcard synthesizer. specifically, i'd like to turn the snare down (because it blurs the toms) but it doesn't seem to be possible to do this. obviously, i've fixed this as i built more sophisticated mixes of the track. however, this is what the track sounded like on playback as i was actually arranging it....

written in early 2001. drastically rearranged in mid june, 2014. this render was initially created on june 23, 2014 and updated on july 4, 2014 to fix a minor error in transcription.


formatting this thing is really just a guess, but i can't figure out why else the corruption would be so random. the way i figure it is that either:

1) it goes looking for file blah.wav and finds a half dozen entries, then spits back something mangled.

2) that part of the drive is really badly fragmented, and it's not able to put the files together in real time without stuttering.

either way, i figure it can't hurt, but i'm going to need to copy the files off, format, scan, copy back and then defragment.

that'll likely take me to the end of the day. argh. but i don't want to lose the vst mix when i start redoing the new one.

i think something i can check is to see if it's doing the same thing from the other drive or not.
the files are updated, btw.
i'm actually going to right up and format the thing to clean out the partition table...
nope. now it's screwing up with other plugins, too.

i'm going to try a scandisk/defrag. this drive gets massive amounts of data copied to and from it. it almost sounds like it's getting confused with pointers. and, i keep creating and deleting files with the same name, so it's not off the wall.

i'm just going to back up first, though, because i already lost one drive of this type. the four drives are of the same type and age.
on second thought, it only happens when i copy the directory.

which is necessary.

it's gotta be some kind of screw up in memory management or something. i'm still blaming bandstand, but i don't think reinstalling will fix it. i'm going to try to copy first, then freeze. i suspect that will work.
.....aaaaaand, it turns out it was a plugin after all. the same skips were coming back, but turning off bandstand did it.

it's too bad this is the only general track 10 plugin i'm aware of because it's not the bestest. it was working before, so i see no reason to think a reinstall won't work.

but, fuck.
i actually have another hypothesis.

cubase seems to want to keep track of files when they're copied out of the directories. it may have gotten confused when i copied it over to the external drive. that would explain why they were both acting funny, and refreezing worked to get around it.

anyways, i'll be reuploading as soon as the a/b test has convinced me the files are the same, except for the Gb.
hrmmn.

turns out the file was corrupt, after all. the chopping went away by unfreezing and refreezing.

weird. wondering if it's the hard drive, now...

it's resolvable, no use in worrying about it.
i just want to clarify because people are going to say that doesn't make any sense, but it does. we're taught that ram disappears on a reboot, but it doesn't actually. it's just discarded and written over. reusing the information in ram just means going back to where it was and finding it.

so, all the os has to do to reuse the boot information in ram is make sure it never writes in the sector that it assigns for boot.

but, again, it's the cpu cache i'm hypothesizing about...