Navigation
« 

Anonymous




Register
Login
« 
« 

Amiga Future

« 

Community

« 

Knowledge

« 

Last Magazine

The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
More informations

« 

Service

« 

Search




Advanced search

Unanswered topics
Active topics
« 

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube Patreon WhatsApp
« 

Advertisement

Amazon

Patreon

« 

Partnerlinks

Search found 9 matches

by Saga
13.01.2014 - 23:03
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

I found the DBPro 2 replaying routines, but I am not very knowledgeable in M68k assembler (and assembler in general), and since the important parts of the code that I looked to were not documented at all, I was asking here since clearly someone else should know much better what the code is doing. :)
by Saga
09.01.2014 - 18:01
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

Is there any documentation on how 4xx exactly works in DBPro? The vibrato depth seems to be approximately half of the depth of PT-compatible vibrato, but not quite. Also, related to my efforts here, is there a way to get a registered DBPro 2.21 version for player developers for free? Obviously I am ...
by Saga
04.01.2014 - 17:36
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

Cannot confirm. I did compare normal MOD playback and DBPro 2.21 (unregistered) output and it did sound identical. The only difference is at a tick speed of 1, where no portamento happens in MOD at all, but in DBPro it is executed.
by Saga
04.01.2014 - 13:53
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

Well, is there any documentation about how they work exactly then?

Edit: After some quick comparisons, 1xx and 2xx appear to work the same as in MOD, just 3xx is different. 3xx is apparently applied on every tick, while in MOD it's only applied on all ticks but the first.
by Saga
04.01.2014 - 01:58
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

So, after finally getting DBPro 2.21 to run in an emulator, I can definitely say that portamentos are apparently working slightly different from ProTracker and similar. Otherwise I can't explain the differences that I hear when listening to that section described above in OpenMPT / xmp compared to D...
by Saga
30.10.2013 - 13:46
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

This tune was made ten years ago, though, and the file header says it was made with DB2.21. So something must have already been different from MOD/XM in DB2. I'm more intersted in playing things like DB2 would play them, since that's what the majority of DBM files was made with, obviously. Easiest w...
by Saga
29.10.2013 - 23:13
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

By the way, is it possible that portamento effects are working slightly different from how they are known in MOD/XM? Consider this tune ... I have an MP3 recording of it (since I can't get DigiBooster to run in WinUAE, I can't verify it myself), in which you can clearly hear three distinct notes in ...
by Saga
29.10.2013 - 23:03
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

Regarding the panning, I was talking about "2 bytes Instrument panning (−128 = full left, +128 = full right)." - is this also -128...128 in version 2? I'm just wondering because the panning envelopes were also XM-compatible, so I wondered if the same is true for default instrument panning....
by Saga
22.10.2013 - 01:06
Forum: DigiBooster Support
Topic: DBM0 format specification update.
Replies: 17
Views: 30625

I need some clarification on the format, as some parts are rather ambiguous or are treated differently by existing loaders. First, regarding the instrument panning, is it supposed to be an int16? MilkyTracker and OpenMPT treat it like an uint8, although they treat a value of 0 as "do not force ...