Anyway, I have renewed my interest in this since I often use pianoteq as a Jukebox for background music while I do other things.
I would like to know if anyone has any tips for capturing the title and displaying it in pianoteq's bar just below the menu bar, i.e. where it displays "Blues Demo" when D4 is selected.
This field is filled with the file name (not the title from within the midi file) when a single midi file is loaded via the file menu, I would like it to receive the title of each file from within the file as they are received from play lists.

It would also be nice to display the progress in the time bar, but that is secondary.

EDIT:
Last night I remembered that I had used Winamp for exactly this (a couple of decades ago when I was using Windoze).
It works in a guest virtual machine running Win7 on a Linux host (VirtualBox).
I haven't  plumbed the full depth of the latest version, but from memory I think it can go something like 10 levels deep in a directory tree.
I don't know what 10 levels deep in a directory tree is in windowspeak, - - maybe (folders(folders))**10
The visualization tab is amusing.

The default configuration plays through windows sound something - to change that to use Pianoteq first install Loopbe1 and start that, then go to winamp menu
options>preferences>plug-ins>input
select Nullsoft MIDI player, click on configure
choose Device tab, click on the drop down arrow, select  "midout/LoopBe1 Internal MIDI"
then OK.

You may have to restart it to get the new settings to take effect.
...and of course set Pianoteq to listen to LoopBe1

I know, it seems ODD that you have to do this edit on midi OUTPUT by selecting the INPUT plugin - that is how it is so don't think that the line
"options>preferences>plug-ins>input"
above is a typo.

:END EDIT

No, "batch" comes from English language:

Yeah i know, i was referring to the usage of the word "batch" by the original creators of QDOS because of its resemblance to "bash", not the origin of the english word "batch" itself.

If "powershell" existed back in the day, it "might" have saved me a lot of problems, or not. Or it "might" have caused even more problems. I'm not very familiar with "power shell" so i can't really say.

I might look it up, later, if/when I have nothing better to do - right now I have MUCH better things to do, like leave this topic.

batch
baCH/
noun
noun: batch; plural noun: batches

    1.
    a quantity or consignment of goods produced at one time.
    "a batch of cookies"
        informal
        a number of things or people regarded as a group or set.
        "a batch of hostile letters came"
        synonyms:    group, quantity, lot, bunch, mass, cluster, raft, set, collection, bundle, pack; More
        consignment, shipment
        "when can we expect the next batch of invoices?"
        Computing
        a group of records processed as a single unit, usually without input from a user.

Powershell scripts can definitely do it, they have looping and stuff like that.

I suspect the name "batch" file comes from "bash", but that's just my personal speculation.

On a real OS (in this case, that would be osx or linux) just make a small shell script that does something like:

#!/bin/bash
for dir in "$@"; do
  for file in "$dir"/*.[Mm][Ii][Dd]; do
    "/wherever/you/installed/Pianoteq 5/amd64/Pianoteq 5" --headless --play-and-quit --midi "$file"
  done
done

Just replace "/wherever/you/installed/Pianoteq 5/adm64" by the directory where the Pianoteq executable is located. Now run this script with the directory(ies) containing midi files as arguments, for example: ~/name-of-script.sh /tmp/midi1 /tmp/midi2

If you want the pianoteq window to appear at each midi file, remove --headless.

I tried the Synthfont since it appeared to me an easily implementable workaround. Unfortunately, it does not support my Pianoteq 64bit VST plugin. I am reluctant changing to 32bit VST just for this.

The LoopBE option appears too complex for me - I am not a digital expert.

Thanks anyway.

YossiA

In linux and osx, you can easily write a shell script that does this. For w**dows, it might be a bit more complicated. I don't know if "batch files" would be able to do even such simple task.

By the way, all the shell commands work in Windows, as well. It's simple to add it to a shortcut's Target field. Example:

"C:\Program Files\Modartt\Pianoteq 5\Pianoteq 5.exe" --fullscreen --midi foo.mid --play-and-quit

If you use Windows you can install a virtual device like LoopBe1 (www.nerds.de) and use it to input data on Pianoteq (like aandrmusic recommends) ; then you could use e.g., Windows MediaPlayer to manage your playlists.

Or you can  install an application/utility that plays midi files and supports vst instruments (I use an old version of SynthFont that allows the use of a vst instument by default).

Hope it helps.

core system files being limited to 8.3 filenames

This is not true since NT times. There ARE a lot of 8.3 filenames because they've been there since W95, sure. But newer system files definitely can (and do) have longer filenames.

This is also complete bullshit. I've never had problems with Windows 7 in all 4 years of it being installed. Not a single crash, blue screen, or whatever. It just works! During those 4 years I've seen more Macs freeze and crash than W7 computers. Just to balance things out.

Linux... I guess it's good for programmers and control freaks that know too much for their own good. Me, I like my compatibility with 20 year old programs (impossible on OSX - I assume possible on Linux, but not to the same extent?), and of course familiarity plays a huge role.

DOS is not a part of Windows since ummmmm WinXP? Again - grow up

Windows still drags with it a huge history of "issues" from its DOS/QDOS and windows 95 days, like... core system files being limited to 8.3 filenames, the hideous primary key database at the center of the "OS" called the "system registry" (the last place where such a database belongs)... i/o system calls (files, tcp sockets, IPC, ...) that are completely awkward and contrary to what any sane OS does, etc etc. Having been a programmer since those days for a variety of platforms, it's my personal experience that windows is the ONLY one that constantly, purposely gives both users and developers nothing but constant headaches and trouble. Not surprising, since DOS was a cheap ripoff of a system called CP/M that was popular in the 1970's (look it up on wikipedia) and that was a cheap ripoff of the first Unix systems from the late 60's / early 70's. The making of windows started with the decorations, facade, etc... and now they're still struggling to fit a half-decent foundation under all that hideous mess.

Every OS has its good and bad points, except windows which has no good points - unless you count MARKETING as a good point. In the early 90's, a lot of people gained interest in computers and the internet, but almost no one knew anything about them ...so microsoft found itself in an easy position to use questionable marketing tacticts to sell backdoored, completely deficinet junk with a "pretty" interface to the ignorant masses, and then abuse its position as a monopoly in the IT market to clobber and/or buy out any and all form of competition. Which is the main reason why we have the complete microsoft-infested disaster that is today's IT market.

Another fun factoid is that microsoft even popped into existence by pirating and illegally selling software made by others: gwbasic or however that basic interpreter was called, QDOS "Quick and Dirty Operating System" originally made by a small company, i don't remember the name, which microsoft stole and sold to IBM, who renamed it to DOS for use with their "ibm pc"... If today's IT laws existed back in the 80's, or even the 90's, microsoft would certainly not exist anymore today.

The slogan of pretty much anything made (or stolen) by microsoft should be "designed to sell, not to work".

It's not an insult, it's a plea.

It doesn't come across that way,  Many of us have an extreme distaste for WinDO$ for many reasons.  One of the reasons I love Pianoteq is that it runs natively on Linux.