Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Development Corner / URL in testing update notification
« Last post by jmkz on October 08, 2017, 04:03:22 »
I've recently activated notifications for testing update notifications, but seems that there's still an old URL to update download (I just look on the original topic Update notification for test builds), so shows other obsolete link inside http://update.openmpt.org/info/testing.
It's supported the https://update.openmpt.org/check/testing/$VERSION/$GUID URL?
22
That was it. Thank you so much!!
23
You need to select the correct output device in OpenMPT's sound card setup. Depending on the driver used in OpenMPT (e.g. with WASAPI), it may not know about the new default output device and keep using the old default.
24
Help and Questions / Open MPT plays from speakers when headphones are plugged in
« Last post by ellobo on October 07, 2017, 23:17:58 »
Hello fellow trackers.

I just bought a new iMac and I'm running Windows 10 on it via Bootcamp. Everything works as it should do in Windows when headphones are plugged in, with the exception of Open MPT. For some reason it plays out of the speakers instead of the headphones. I can even play 2 different tracks simultaneously, one via speakers in Open MPT and one via headphones in any other program on Windows. Any solutions you can think of?

Thanks in advance.
25
https://pastebin.com/dpprgJTy
Can you please allow to build 32bit wrapper on 64bit system (-m32 or something)?

Theoretically possible, but certainly will not happen to be supported in the near future.

There is a hidden setting [WineSupport]ForeignOpenMPT. If you set that to 1, OpenMPT will try to build for non-native bitness, however that feature is unsupported and not very well tested and I cannot remember right now if it even ever worked even on Debian systems where I test mostly.


We do explicitly not provide active support for this situation though, because of various reasons:

The amount of differences between distributions in the way compiling for Wine is already amazingly huge as it is, even when only targeting the native platform. Targeting foreign bitness will increase the amount of situations to support manyfold.

Library placement in the file system differs completely between Debian, Ubuntu, other Linux, other platforms (i.e. at least 4 ways to handle it). Some systems completely special case Wine and do not allow to even install general 32bit packages on 64bit systems at all. This implies having to consider which packages are even available there at all. Detecting available foreign packages is also not really portable (yes, pkg-config, but we would have to GUESS the actual host triplet and pkg-config path used for 32bit) (also, this would not be any easier when building by hand).

So no, this is an experimental feature, and only supports a subset of available configurations. You either have to use native bitness OpenMPT (and are thus limited to 64bit VST plugins due to the Wine UI rendering problem, though we might be able to provide a work-around for that sometime, albeit not soonish either), or use 32bit OpenMPT on your 64bit system and not use the Wine integration feature (WASAPI support in Wine and OpenMPT works nearly perfect these days, so you would not lose all that much anyway).

In any case, this is and will stay to be a highly experimental feature because it requires an unproportionally huge amount of development time to implement and test (the test matrix is incredibly huge, compared to other features), and I do not want to invest the time to extend the scope that much for ever so smaller diminishing returns.


We might support building by hand some time, but not right now.
26
https://pastebin.com/dpprgJTy

Can you please allow to build 32bit wrapper on 64bit system (-m32 or something)?
27
Help and Questions / Re: Unicode-aware
« Last post by Wodd on October 03, 2017, 20:45:44 »
Ah
Thank you, Saga Musix. I did look at that, but must have forgotten what I read.
28
Help and Questions / Re: New user to OpenMPT who is blind
« Last post by Darkside on October 03, 2017, 13:13:40 »
Hi, One more blind dude here. I didn't want to start a new topic just to show myself. I recently revived my old MPT use - last track with it was made in 2010, as I switched almost completely to hardware these days, but decided to keep the old alternative actually alive. Fortunately managed to find an old keymap created by yet another blind friend for both of us to use and it still works fine. I use both jaws and nvda, but the jaws version is pretty old, 5.10, as I decided not to invest in software any more and didn't upgrade anywhere. As a proof of tracking, here is a link to one of my older tracks to listen. Here MPT is used actually more as a vst host type daw and not that much as a typical samplebased tracker. Later the trackwas edited with Adobe Audition 1.5 which is still used as a main audio editor although it's definitely not the freshest version of the product, but is still probably the most accessible version and it's a purchased one after all - yep, I don't like cracking. So please injoy and give feedback!

https://soundcloud.com/drxid/watch-out
29
Help and Questions / Re: Unicode-aware
« Last post by Saga Musix on October 03, 2017, 12:59:11 »
I will answer this by quoting the full changelog item instead of just the two words that you picked: "OpenMPT's file handling is now fully unicode-aware".
If it's still not clear, there is even a forum post explaning it: https://forum.openmpt.org/index.php?topic=5827.0
30
Help and Questions / Unicode-aware
« Last post by Wodd on October 02, 2017, 19:59:42 »
I read that OpenMPT is now "fully Unicode-aware." What does that mean exactly? Does it apply only to reading of module file names? I noticed that, when naming module components (channels, patterns, samples, instruments, and sequences), the characters display correctly in the text input fields (sometimes)*. But, they don't display correctly in the tree view. For example, when I placed a superscript four character in the sequence name box, it displayed a digit four character in the tree view. Many characters (such as Japanese text or emoticons) display 1 or 2 question marks in the tree view. Switching away from the named component and switching back to it replaces the Unicode character inserted with 1 or 2 question marks. I am using code revision 9021.

* (sometimes): When I loaded a file that was named ↓.wav, both the sample name and the file name are ?, not ↓. The audio works with no problems. But, the name looks odd.
Pages: 1 2 [3] 4 5 ... 10