Ah yes! Right you are! I didn't think to go looking there did I!
dRowAudio:
Log file has been sent.
Cheers!
T5 bugs + FRs
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
T4, T5 both have same bug:
Import a midi file in 6/8, 73bpm, the import will down convert tempo to 36.5bpm, the midi metronome click will be off and midi clip editor will be completely off, if you lower the time signature to 3/4 then you can place the tempo back on 73, then click metronome will be fine, but if you edit the midi clip, the bars and measures are completely off, so no way to snap properly.
P.S. This does not happen even in my 15 year old midi only sequencer, all my DAWS imported the file correctly, time sig. tempo, click/metronome correct, midi clips correct. BTW - LOVE Tracktion, just waiting on some bug fixes, editor colors, to get my rack feature back, and the addition of a mixer of sorts
Import a midi file in 6/8, 73bpm, the import will down convert tempo to 36.5bpm, the midi metronome click will be off and midi clip editor will be completely off, if you lower the time signature to 3/4 then you can place the tempo back on 73, then click metronome will be fine, but if you edit the midi clip, the bars and measures are completely off, so no way to snap properly.
P.S. This does not happen even in my 15 year old midi only sequencer, all my DAWS imported the file correctly, time sig. tempo, click/metronome correct, midi clips correct. BTW - LOVE Tracktion, just waiting on some bug fixes, editor colors, to get my rack feature back, and the addition of a mixer of sorts
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
Tried lowering to 3/8 and 73bpm, midi clip looks good, but plays double fast....
-
bobmartinmusic bobmartinmusic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=169078
- KVRist
- 212 posts since 26 Dec, 2007 from UK
I had to go looking there myself..danboid wrote:Bobmartin:
Ah yes! Right you are! I didn't think to go looking there did I!
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Hi AzureCrystal, can you upload an example MIDI file with this time signature/tempo combination for me to test out please?
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
Yes, of course, I will be in the studio tonight and will upload a sample midi file, hope it helps!dRowAudio wrote:Hi AzureCrystal, can you upload an example MIDI file with this time signature/tempo combination for me to test out please?
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
example midi file attached, 6/8 time sig, 73bpm tempodRowAudio wrote:Hi AzureCrystal, can you upload an example MIDI file with this time signature/tempo combination for me to test out please?
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 171 posts since 11 Aug, 2004 from Toronto, Canada
BR: KORG Legacy Collection VST instruments unstable
Plugins instantiate and produce sound, however Tracktion will immediately crash upon opening and closing the plugin GUI. Plugins perform without issue in other hosts. Versions tested: Tracktion v5.3.5, KORG plugins v1.7.0, Mac OS v10.6.8.
FR: add option for 23.976 FPS timecode
This would be huge for me as I generally don't receive locked cuts that aren't in this frame rate. I really hope this is simple to add!
FR: retain freeze state on edit close/re-open
Utilizing the freeze function is a great help with dense projects, but I think it could be even better if the freeze state(s) was remembered and recalled when closing/opening projects. I notice the ".freeze" files hang around in the Tracktion "temp" directory, so it seems they could still be made of use. On a related note, perhaps there is also an opportunity to allow managing/purging of outdated freeze files, but maybe that's a separate FR.
FR: release plugin RAM/memory back to system OS after freezing or plugin delete
This concerns plugins that load a lot of data into system memory/RAM when added to an edit -- mostly applies to sample based instruments (e.g. Kontakt libraries) but also some of the more recent effect plugins: e.g. AmpliTube 3 (swallows up ~175MB RAM on load) and Slate Digital's VTM (~200MB).
Given that RAM use can therefore accumulate fairly easily with plugins, it would be great to have that RAM released back to the system when deleting or freezing one of them. For comparison, REAPER currently has something that allows for this called "Allow complete unload of plugins". An option like this would enable building dense projects on even a modest system that can utilize large Kontakt instruments for example.
To take advantage of this kind of option, Tracktion would also need to remember and load freeze state(s) within an edit (see the previous FR above). These two features combined should also greatly speed up the re-opening of edits that contain plugins with heavy RAM use, but are frozen, as Tracktion wouldn't need to e.g. load a bunch of Kontakt instruments in the background (until needed, of course, upon unfreezing).
Plugins instantiate and produce sound, however Tracktion will immediately crash upon opening and closing the plugin GUI. Plugins perform without issue in other hosts. Versions tested: Tracktion v5.3.5, KORG plugins v1.7.0, Mac OS v10.6.8.
FR: add option for 23.976 FPS timecode
This would be huge for me as I generally don't receive locked cuts that aren't in this frame rate. I really hope this is simple to add!
FR: retain freeze state on edit close/re-open
Utilizing the freeze function is a great help with dense projects, but I think it could be even better if the freeze state(s) was remembered and recalled when closing/opening projects. I notice the ".freeze" files hang around in the Tracktion "temp" directory, so it seems they could still be made of use. On a related note, perhaps there is also an opportunity to allow managing/purging of outdated freeze files, but maybe that's a separate FR.
FR: release plugin RAM/memory back to system OS after freezing or plugin delete
This concerns plugins that load a lot of data into system memory/RAM when added to an edit -- mostly applies to sample based instruments (e.g. Kontakt libraries) but also some of the more recent effect plugins: e.g. AmpliTube 3 (swallows up ~175MB RAM on load) and Slate Digital's VTM (~200MB).
Given that RAM use can therefore accumulate fairly easily with plugins, it would be great to have that RAM released back to the system when deleting or freezing one of them. For comparison, REAPER currently has something that allows for this called "Allow complete unload of plugins". An option like this would enable building dense projects on even a modest system that can utilize large Kontakt instruments for example.
To take advantage of this kind of option, Tracktion would also need to remember and load freeze state(s) within an edit (see the previous FR above). These two features combined should also greatly speed up the re-opening of edits that contain plugins with heavy RAM use, but are frozen, as Tracktion wouldn't need to e.g. load a bunch of Kontakt instruments in the background (until needed, of course, upon unfreezing).
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
I just upgraded to T5 today, was a bit disappointed that the midi export has not been fixed.
if you export a midi project with multiple tracks, it lumps all into one track on the export file, which is old school Midi level 0 style, that is a crucial feature in most if not all sequencers out there. Love Tracktion!
if you export a midi project with multiple tracks, it lumps all into one track on the export file, which is old school Midi level 0 style, that is a crucial feature in most if not all sequencers out there. Love Tracktion!
-
alejandrozalaquett alejandrozalaquett https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=58330
- KVRist
- 240 posts since 18 Feb, 2005 from Chile
There seems to be a problem with T5 5.3.5 on OSX when exporting a mp3 replacing an existing file. The file is not replaced and it is rendered to a new file in the project folder instead.
Also there is still no solution on Fabfilter pluguins black GUI.
Love T5!
Also there is still no solution on Fabfilter pluguins black GUI.
Love T5!
Alejandro Zalaquett
https://www.youtube.com/c/AlejandroZalaquett
https://www.youtube.com/c/AlejandroZalaquett
-
- KVRist
- 51 posts since 15 May, 2014
Just installed Tracktion 5.3.5 over my previous install, install was smart enough to know it was an upgrade, and all went smoothly. I don't really know the program well (at all) but I had two crashes just fooling around. The crashes happened when scanning for plugins. VST scan worked without a problem but the LADSPA scan crashed if performed directly after VST scan. Cleared the list and LADSPA scan completed but reported errors with three files that did not load properly.
I have uploaded my log file.
Running on Linux KX-Studio
I have uploaded my log file.
Running on Linux KX-Studio
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
As someone who makes his living scoring for video games, MIDI exporting is CRUCIAL for turning around music, in many cases the same day.
Here is an example workflow:
* I score pieces initially in Notion, a music notation program
* Then I make a Notion midi file
* I import the file into a midi sequencer to polish/fine tune the midi based tracks
* I export the edited midi file and reload into Notion
* I repeat this process until the midi tracks are perfect
* The final midi tracks gets rendered in Audio
Sadly, without being able to export a multi-track midi file in midi format 1, I am forced to use other sequencers although I have become VERY FAST in Tracktion and the main reason I really love it for editing, would be great to see this fixed!
Here is an example workflow:
* I score pieces initially in Notion, a music notation program
* Then I make a Notion midi file
* I import the file into a midi sequencer to polish/fine tune the midi based tracks
* I export the edited midi file and reload into Notion
* I repeat this process until the midi tracks are perfect
* The final midi tracks gets rendered in Audio
Sadly, without being able to export a multi-track midi file in midi format 1, I am forced to use other sequencers although I have become VERY FAST in Tracktion and the main reason I really love it for editing, would be great to see this fixed!
AzureCrystal wrote:I just upgraded to T5 today, was a bit disappointed that the midi export has not been fixed.
if you export a midi project with multiple tracks, it lumps all into one track on the export file, which is old school Midi level 0 style, that is a crucial feature in most if not all sequencers out there. Love Tracktion!
-
bobmartinmusic bobmartinmusic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=169078
- KVRist
- 212 posts since 26 Dec, 2007 from UK
Export then "Render each track to a separate file"?
-
- KVRist
- 229 posts since 14 Nov, 2003 from Florida - United States
I saw that option, unless I misunderstand, why would I want 100 files of the same project? I simply want one midi file with 100 tracks, like all other sequencers export...bobmartinmusic wrote:Export then "Render each track to a separate file"?
-
bobmartinmusic bobmartinmusic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=169078
- KVRist
- 212 posts since 26 Dec, 2007 from UK
I'm not a regular MIDI user anymore but I was able to render some Drum loops to type 0 and 1 files, but confusingly there is a faulty message, "no midi found" when the files where created.AzureCrystal wrote:I saw that option, unless I misunderstand, why would I want 100 files of the same project? I simply want one midi file with 100 tracks, like all other sequencers export...bobmartinmusic wrote:Export then "Render each track to a separate file"?
It's not intuitive and it would be much better if Tracktion used the standard "0 and 1" in the dialogue box.