Re: DOSBox 0.73 Discussion
Posted on 2009-06-13, 17:22
Can anyone tell me if Srecko's MIDI timing fix patches are in this release? I looked at the changelog and didn't see any mention of them.
Re: confused abiout CVS
Posted on 2009-04-16, 17:10
Thanks for the clarifications!
Re: confused abiout CVS
Posted on 2009-04-16, 06:41
I guess I don't mean release candidates. I mean works in progress for the next release. So .72cvs are works in progress, building on released .72, towards a .73 release someday. I hope I got that right this time.
Re: confused about CVS
Posted on 2009-04-16, 06:38
Ah, maybe that makes more sense then!! I must have somehow missed that .72 was out when this .72CVS came along in October. So my understanding of the numbering system is right? Sheesh.
Re: confused abiout CVS
Posted on 2009-04-16, 04:53
Long time no talk! Nice to see you back. >The CVS releases are the current accumulation of code updates to the >previously released DOSBox v0.72 base code (from a few years ago). My thought was that the .72cvs version was a release candidate for .72. Basically .71 with additions/fixes. Then when …
confused abiout CVS
Posted on 2009-04-16, 02:19
In October some MIDI fixes were added, and reading here they were added to the CVS a few weeks later. When the the .72 actual release version that came out they did not seem to be included. I just assumed an Oct CVS would lead to the feature being added to that next release - .72 - but I guess it …
Re: MIDI clock sync with .72 :(
Posted on 2009-03-12, 17:46
Ah that makes sense. Thanks srecko, Has there been MIDI changes since that October fix? That CVS one is working well for me. Any rough date set for .73 yet?
MIDI clock sync with .72 :(
Posted on 2009-03-08, 08:01
The CVS version of .72 perfectly fixed a problem I had with MIDI clock messages being corrupted that was quite obvious in .70. I finally installed the release .72 version, and the issue is back. Were the MIDI timing fixes not aded to .72? (I think srecko did the fixes..)
Re: what front end?
Posted on 2008-11-08, 18:03
Does this new terminology in the CVS mean it will be standard in the next release?
Re: what front end?
Posted on 2008-11-05, 07:39
I'm using a test build, so maybe will just wait till it's all caught up... So this new syntax isn't in normal .72, but sounds like will be in next release, yes? I hope D.O.G. gets updated. I'm perfectly happy with that one.
Re: what front end?
Posted on 2008-11-05, 01:13
Must just be the test version I have here then..
Re: what front end?
Posted on 2008-11-04, 22:17
Some of the syntax it writes is no longer valid. such as: "cycles=fixed 5000" is the new way to write this
what front end?
Posted on 2008-11-04, 21:51
I've been using DOG and I like it, but it doesn't seem to support .72. Anyone know if that's changing? {I wrote to author and got no response.} If not, what the new standard front end I need to change to? thanks
Re: MIDI input patch
Posted on 2008-10-27, 19:08
Ok, I will specifically turn metronome on and off and such to put SPG / DOSBOX thru it's paces. So far, I was able to playback, record pitch bend, and use clock in *and* out. All looks good. Not yet sure the overall tightness in timing, but I have some stricter tests I will do very soon.
Re: MIDI input patch
Posted on 2008-10-27, 05:32
ok, will test it. Can you elaborate a bit on the problem in Texture? Conducter is a Texture thing? It's be nice to know any little issues.. Also "locking scheme"? Not sure I follow what you mean there..
Re: MIDI input patch
Posted on 2008-10-25, 05:30
ok changed to: mpu401=intelligent device=win32 config= inconfig=0 midioptions=inputmpu401 So is next step is for me to test improved MIDI input whenever you are ready? thnx
Re: MIDI input patch
Posted on 2008-10-24, 19:36
I just changed sbtype to none and the message went away. I am actually using MPU401, so I guess they were both switched on. These are the settings I have had on the whole time as well, just FYI. [midi] mpu401=intelligent device=win32 config= inconfig=0 inmidioptions=inputmpu401 This last line is not …
Re: MIDI input patch
Posted on 2008-10-24, 03:04
Ok I tried this .72 that you just sent using identical setup, only changing the exe. Timing problems back in that one, so your patch is very good so far. By the way both versions say "SOUNBLASTER:raising IRQ" fairly often. Maybe a bit more often during pitch bend messages? Looking forward to a …
Re: window offset each time
Posted on 2008-10-24, 02:39
How safe is it to delete these keys? Will they automatically get recreated?
Re: MIDI input patch
Posted on 2008-10-23, 06:26
Ok, first report is that it does seem to work, which is very nice! I loaded .070 and this new .72 on this same test machine, and this is MUCH better than .70!!! I did direct comparisons between the 070 & 072 versions: The send clock timing does not jump all over now. Steady. The note timing with …
Page 3 of 8