WTB large memory mapper (2mb or 4mb)

Página 3/3
1 | 2 |

Por Avkooi

Expert (99)

imagem de Avkooi

05-12-2022, 21:27

My only experiences are with my Turbo R GT in combination with a Tecnobytes slot expander. I tried to play large VGM files and that was not successful with this 16 MB memory mapper. Files didn't load. No other setups or use cases tested by me. I just wanted to listen to some game music and unfortunately, this product didn't help. As far as I know, this is the only available large (=>4MB) option at the moment, so it is a bummer it didn't work. I hope you have better luck!

Por lintweaker

Champion (448)

imagem de lintweaker

06-12-2022, 10:08

Avkooi wrote:

My only experiences are with my Turbo R GT in combination with a Tecnobytes slot expander. I tried to play large VGM files and that was not successful with this 16 MB memory mapper. Files didn't load. No other setups or use cases tested by me. I just wanted to listen to some game music and unfortunately, this product didn't help. As far as I know, this is the only available large (=>4MB) option at the moment, so it is a bummer it didn't work. I hope you have better luck!

The 16MB cartridge has it's own slot expander (4x 4MB), you'll probably only get 4MB when using it in a slotexpander.

Por Grauw

Ascended (10678)

imagem de Grauw

06-12-2022, 19:14

Avkooi wrote:

My only experiences are with my Turbo R GT in combination with a Tecnobytes slot expander. I tried to play large VGM files and that was not successful with this 16 MB memory mapper. Files didn't load. No other setups or use cases tested by me. I just wanted to listen to some game music and unfortunately, this product didn't help. As far as I know, this is the only available large (=>4MB) option at the moment, so it is a bummer it didn't work. I hope you have better luck!

It could be that this particular mapper hardware has a compatibility problem on turboR, however since VGMPlay was brought up I just want to make sure that the behaviour of VGMPlay is clear;

The normal build of VGMPlay is limited to a maximum of 4 MB to save on TPA memory. There is a custom build where I raised the limit to 8 MB here. The idea was that there are few VGMs larger than 4 MB anyway. In the future this should also reduce the memory use further.

In principle there are no issues addressing memory spread across multiple slots adding up to any amount, including a 16MB mapper in a primary slot on any MSX generation including turboR. I myself regularly combine multiple mappers <= 4MB, and test with PlaySoniq as well. However it needs to keep track of a list of segments somewhere and I limited the length of that list to 256 entries by default. I can increase it as long as I free up some memory elsewhere (e.g. reducing the file buffer size).

Por ToriHino

Paladin (814)

imagem de ToriHino

06-12-2022, 17:48

I took the same approach for RoboPlay i.e. current list is now 'limited' to 256 segments of 16KB. Until now this was always suffcient but, as Grauw also mentions, this can be extended to a bigger number when really needed.

Página 3/3
1 | 2 |