Would it be possible (or is it already) to increase the backlog of midi files automatically generated by the standalone version? Also, I would like the option to discard sessions that contain nothing of interest from within the app.
Here another supporter to the idea!
And maybe not to create separate midi logs if paused for 1 secs, I'd change that and let it create a one single MID file per session
And maybe not to create separate midi logs if paused for 1 secs, I'd change that and let it create a one single MID file per session
I would not want one single MID file per session. I rely on those pauses for separate sessions.
davidizquierdo82 wrote:And maybe not to create separate midi logs if paused for 1 secs, I'd change that and let it create a one single MID file per session
I would not want one single MID file per session. I rely on those pauses for separate sessions.
Firstly, I agree with scorpio. The present system of recording is very good. And if I want to record everything from the start, I can just press the "record" button. My best gratitudes to Modartt for this automatic recorder! How many improvisations and sudden ideas it saved! It is one of the best functions in Pt for those, who use it as an everyday instrument. But there can be compromise: setting, which define the value of pause, that cuts session. And it would be also good to glue midi-files by draging one on another. Sometimes, when having big pauses in music, it is devided into two files. In this situations it is handy just to glue them by draging in a list
Secondly, I support an idea of little sequencer in Pt, even if it would be very simple - even an ability to cut unnecessary fragments from midi file. And support an idea of increasing the number of saved files!
As also said by others, I personally would like the design team to work on better sounds, more piano;s etc, the core business so to say.
It is already very nice to have this immediate recoding facility in Pianoteq.
For people who seriously like to do recordings, manipulation of Midi data, etc etc, it is far wiser to use specialised software for that.
This software ( reaper f.i.) has so many facilities that are needed for working with Midi ( and audio as well), and is constantly being updated.
Let,s be serious: all the better sound generating software comes as vst-plug-in as well, so it is intended to use a DAW.
Greetings,
Geert
@Geert - to be fair, the request for an increase to the backlist of midi files could be coded in a coffee break.
What I would especially like to see here is the possibility of recorded sessions actually being recorded... I was surprised the first time after hitting "record" to save a session, to then see it disappear after getting bumped down the list of midi sessions. Shouldn't these be saved as midi files automatically into a folder somewhere? Or perhaps they are and I just haven't figured out where??
The auto temp-recording of sessions is an interesting feature, just not one I find especially useful, personally. So why is there a record button at all if these "recorded" sessions aren't actually saved (without exporting them separately).
On OSX and Linux, this is easy: just setup a cron job to periodically copy the recent.mid file to, say, recent-`timestamp`.mid where timestamp might be the date/time in your preferred format.
On Linux the file is "~/.local/share/Modartt/Pianoteq/recent.mid"
On OSX the file is "~/Library/Application Support/Modartt/Pianoteq/recent.mid"
That just leaves windowz users completely dependent on third party malware-infested junk, as usual....
I want to thank Modartt team for the new ability to cut fragments from midi-file (last version 5.4.0 has gotten this function)! May be little, but very practical improvement for those who improvise on piano a lot