I have a small problem where if I use the buffers 100-139 ms famitracker will act like it's playing but won't, and if I use any buffer below 95, I have millions of underruns per second while at 95 I barely have any buffer underruns at all, and I have to lower my audio settings from studio to cd to use 96-99 without the same problem. I don't remember buffers working like this in nov 2010 - jan 2011 when I was on linux, they worked properly.
I'm sorry to say it like this but could you please make your windows program more windows-friendly? And if any mods see this as rude you can remove this part, I won't really care.
I'm sorry to say it like this but could you please make your windows program more windows-friendly? And if any mods see this as rude you can remove this part, I won't really care.
hahaha are you joking. upgrade your computer to something decent, famitracker runs absolutely fine even on my terrible PCs.
I'm sorry to say it like this but could you please make your windows program more windows-friendly? And if any mods see this as rude you can remove this part, I won't really care.
hahaha are you joking. upgrade your computer to something decent, famitracker runs absolutely fine even on my terrible PCs.
Hahaha are you joking. High-end everything but graphics, dan.
I'm sorry to say it like this but could you please make your windows program more windows-friendly? And if any mods see this as rude you can remove this part, I won't really care.
hahaha are you joking. upgrade your computer to something decent, famitracker runs absolutely fine even on my terrible PCs.
Hahaha are you joking. High-end everything but graphics, dan.
then clearly, as I first suspected, your stupidity must be clouding your ability to operate the program correctly.
Why you would want a buffer size larger than 30 ms baffles me though. Unless you really do have a pitiful machine in which case there's really no point in us having this conversation.
I just tried that low... wow... it works... I guess I have to get used to this computer... but yeah around the range I described... yeah works completely wrong...
Whenever I use a generic crap-quality USB-Midi adaptor for Midi output/input, uber stuttering occurs, even if there is nothing connected on the other end. (I haven't had anything working so far so my adaptor might be broken anyway.)
It can't be the drivers because I used it under both Windows 7 and Ubuntu.
Can't be my computer; it's a brand new 8-core 2.20 Ghz i7 Dell XPS 15. Nothing changes if I change the audio settings.
But then it might just be the adaptor; I'll try it with other software later...
_______________________
Everything moves real slow when it's 40 below.
RE: Version 0.3.7 final - buglistPosted: 2012-01-11 04:37
If you click on certain places in an instrument editor window while playing back a song while it is using DPCM, the DPCM channel "clicks" (or resets, I guess).
Also, something sometimes happens with the square channels (when the square channel is selected in the pattern editor), but the channel is muted.
_______________________
Everything moves real slow when it's 40 below.
VRC6 - The sawtooth channel volume monitor is inaccurate at certain levels.
0=0, 1=0, 2=2, 3=3, 4=4, 5=5, 6=6, 7=7, 8=9, 9=9, 10=11, 11=12, 12=13, 13=14, 14=15, 15=15
General - Weird artifacts:
1.) Shrink the window size so that all channels do not fit and you can only see some of the next channel on the right edge of the screen.
2.) Instead of using the scroll bar, click anywhere in the rightmost channel and FT will scroll for you so you can see the entire channel.
3.) Repeat this process until you get to the last channel on the right.
4.) Observe the bizarre visual effects on the right-hand edge.
I think the volume issue happens because the VRC6 sawtooth volume actually goes up to 63, so inevitably dividing the resolution by 4 results in some inaccuracies. I could be wrong though...
While we're on the subject, it would be nice to be able to use the full sawtooth volume range. Just a thought...
Ignore what I wrote below. I misremembered. The full range of VRC6 can be used with V01, which gives you 6 more volume steps beyond F. These are possible volume settings for VRC6:
0 V00
1 V00
2 V00
3 V00
4 V00
5 V00
6 V00
7 V00
8 V00
9 V00
A V00
B V00
C V00
D V00
E V00
F V00
0 V01
1 V01
2 V01
3 V01
4 V01
5 V01
After this there is no more increase in volume, and the wave shape begins to distort because the saw accumulator overflows.
Old (wrong) post: You can use the VRC6's full range via V0x, where x is the high two bits of your volume's number. (V01 adds 16, V10 = +32, V11 = +48, V00 = +0) Also, if you use a value higher than 42 the saw shape will overflow.
It gets really loud though. I've never felt the need to use the expanded range via V0x.
We could do like with the FDS and map volumes 0-15 to internal 0-30, maybe, but that would reduce our ability to finely control it at low volumes.
.png){kind=avatar}
so my adaptor might be broken anyway.)
