Here's something someone might try to reproduce before I fire off a bug report: if you collapse the transport panel, then downsize the application window enough that the master effects slot becomes a button with a pop-up list. If you then try to open a plugin from that pop-up list, Waveform 9 will crash. Additionally, you cannot add a plugin to the master channel when the main window is in this state.
Win 8.1 64... Latest beta...
-Cheers
Announcing Waveform 9 Public Beta
-
- KVRist
- 320 posts since 9 Sep, 2017
I see there is really beautiful interaction, rapport, contact.. going on here.
Though some users unfortunately can get really frustrated.
I beg to really focus on meta-concepts under the hood. In the end this will improve the elegance of the reaction that the software gives to the users' input.
The reason to say this is the sum of many reports about glitches, that must have a connection with the basic data management of tracks, midi notes, plugins, and all the derived object data and meta data about the detailed function, connection, and inter-operation of these data atoms.
It starts with intrinsic sorting of various levels of IDs, and with access inversion (or how to you say this in English) i.e. to access data by 2 or 3 co-existing compound ID/primary key systems that have very different purpose, and thus have to exist and to be maintained very exactly and efficiently.
For example, over the years, you went already to a major version [6] and still had no reliable sorting of racks in the "insert rack" and other pulldown lists.
So, from my experience in creating deep data management concepts, the great and detail-rich innovation that leads to a version [9] can endanger you with the notorious "explosion of complexity", unless meta concepts are not brought up to a definitely higher level of abstraction and management.
From the start, the meta concept has been very symmetric, i.e. a "track" can be mono, stereo, bus, midi etc., and the symmetry seems to get somehow degraded internally by the introduction of folder tracks, automation tracks, ghost tracks etc. so this is really one of the most difficult and mission-critic concept questions, and a playground of hard competition among DAW makers.
But there are new concepts of great data symmetry already, like editing more than one MIDI tracks in the edit window.
This project can have a really great future and deserves it. It has come a very long way already, and has shown exceptional power of survival. Please, be blessed to take the wisest long-time decisions about the inner fabric of all that stuff.
Though some users unfortunately can get really frustrated.
I beg to really focus on meta-concepts under the hood. In the end this will improve the elegance of the reaction that the software gives to the users' input.
The reason to say this is the sum of many reports about glitches, that must have a connection with the basic data management of tracks, midi notes, plugins, and all the derived object data and meta data about the detailed function, connection, and inter-operation of these data atoms.
It starts with intrinsic sorting of various levels of IDs, and with access inversion (or how to you say this in English) i.e. to access data by 2 or 3 co-existing compound ID/primary key systems that have very different purpose, and thus have to exist and to be maintained very exactly and efficiently.
For example, over the years, you went already to a major version [6] and still had no reliable sorting of racks in the "insert rack" and other pulldown lists.
So, from my experience in creating deep data management concepts, the great and detail-rich innovation that leads to a version [9] can endanger you with the notorious "explosion of complexity", unless meta concepts are not brought up to a definitely higher level of abstraction and management.
From the start, the meta concept has been very symmetric, i.e. a "track" can be mono, stereo, bus, midi etc., and the symmetry seems to get somehow degraded internally by the introduction of folder tracks, automation tracks, ghost tracks etc. so this is really one of the most difficult and mission-critic concept questions, and a playground of hard competition among DAW makers.
But there are new concepts of great data symmetry already, like editing more than one MIDI tracks in the edit window.
This project can have a really great future and deserves it. It has come a very long way already, and has shown exceptional power of survival. Please, be blessed to take the wisest long-time decisions about the inner fabric of all that stuff.
-
- KVRist
- 128 posts since 15 Jul, 2017 from Monterrey
Here on version 9.0.22 and works more fluid than version 8.2.7, still no crashes
Quad Core | 16GB DDR4 | 240 GB SSD + 1 TB HDD | FLStudio ASIO | 1 GB Video | W10 x64
-
- KVRian
- 1317 posts since 3 May, 2005 from Victoria, BC
9.0.23 is now in your accounts
- Bugs: Fixed parameter values not updating on Mackie MCU and Mackie C4
- Plugins: Added support for reading vstpreset files
- Faceplates: Scaled large background images down to improve Edit file size and save times
- Stacks: Fixed a possible crash when showing the Stack editor for a plugin without an existing thumbnail
- Automation: Fixed a potential crash deleting a plugin whilst recording automation
- Rendering: Fixed rendering of Edits with only mono sources to correctly render in stereo
- Sampler: Fixed zone editor not refreshing when loading preset
- Sampler: Added confirmation on clear all sound layers
- Sampler: Fixed pan in one shot mode
- Sampler: Allow loop points to be outside the in/out markers
- Racks: Fixed loading racks from preset files
- MIDI: Fixed chord and bass presets including notes hidden outside of clip
- Presets: Allow multiple preset folders
- MIDI: Add support for automatically coloured MIDI notes
-
- KVRist
- 228 posts since 2 Feb, 2015
Would it be possible to add an option to load the same instance of a rack when multiple tracks have been saved as a preset, each track having the same instance of the rack. At the moment it loads a new instance of the rack on each track and all outputs to tracks are lost when using multi-output vsti's. This would allow the saving of complete instrument setups.
-
- KVRist
- 320 posts since 9 Sep, 2017
I think this isn't possible because of structural level boundaries.
Multi-instantiation of the same rack is probably housed on mix level, so you cannot load the required information on track level.
Did you consider to save complex instrument setups in form of project templates?
The bigger question is, how intelligent is the copy-paste system?
Because I would want to load two ore more project templates into edits open at the same time, and then copy-paste a number of tracks i.e. a whole instrument functionality, from one edit into the other.
Which again requires that a copy-paste of multiple tracks must happen on project level, and not as a "collection" of track copy-pastes.
Still, it has to have the ability of rename and re-sort tracks, and reorganize and reconnect the new (internal) track and rack IDs in a consistent way.
It must generate the concise meta-data of a "sub project" on the fly. It must insert this in a totally different project environment, and therefor reorganize all the data in a consistent and coherent way.
copy-paste of multiple tracks in T6 would crash most times. this also seems to depend on available RAM.
Multi-instantiation of the same rack is probably housed on mix level, so you cannot load the required information on track level.
Did you consider to save complex instrument setups in form of project templates?
The bigger question is, how intelligent is the copy-paste system?
Because I would want to load two ore more project templates into edits open at the same time, and then copy-paste a number of tracks i.e. a whole instrument functionality, from one edit into the other.
Which again requires that a copy-paste of multiple tracks must happen on project level, and not as a "collection" of track copy-pastes.
Still, it has to have the ability of rename and re-sort tracks, and reorganize and reconnect the new (internal) track and rack IDs in a consistent way.
It must generate the concise meta-data of a "sub project" on the fly. It must insert this in a totally different project environment, and therefor reorganize all the data in a consistent and coherent way.
copy-paste of multiple tracks in T6 would crash most times. this also seems to depend on available RAM.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
I'm not sure I tested this properly, but I tried creating a couple of tracks, with a new rack, wrapping Collective, and added a couple of outputs to the Rack. On track 1 I routed the ouput from the default stereo outs from Collective, and on track 2 I set the ouputs to use my two new "dummy" outputs.AGreen wrote:Would it be possible to add an option to load the same instance of a rack when multiple tracks have been saved as a preset, each track having the same instance of the rack. At the moment it loads a new instance of the rack on each track and all outputs to tracks are lost when using multi-output vsti's. This would allow the saving of complete instrument setups.
I then highlighted both tracks, and in the properties pane hit "Create Preset", and the only option was "Whole Track". Saved that off, called something like "Drum tracks preset", then closed the edit, opened a new one, and searched for "Drum tracks preset" in the browser on the left. Dragged that preset to the edit, and it added two tracks, with the ouputs mapped as they were in the first edit.
I'm not sure if those are separate instances of Collective or not. I should try this with a proper multi-channel VST, with multiple outs, and see what happens, but is that different to what you're seeing? Or have I got the wrong end of the stick?
"my gosh it's a friggin hardware"
-
- KVRist
- 228 posts since 2 Feb, 2015
Yes that's what I'm doing and it loads new instances of the rack on each track rather than the same instance. You can check this by dragging the icon for adding plugins on to a track and then looking at the entries in the "plugin racks" menu. The instances loaded in the edit are shown below the "Create new empty rack" option.chico.co.uk wrote:
I'm not sure I tested this properly, but I tried creating a couple of tracks, with a new rack, wrapping Collective, and added a couple of outputs to the Rack. On track 1 I routed the ouput from the default stereo outs from Collective, and on track 2 I set the ouputs to use my two new "dummy" outputs.
I then highlighted both tracks, and in the properties pane hit "Create Preset", and the only option was "Whole Track". Saved that off, called something like "Drum tracks preset", then closed the edit, opened a new one, and searched for "Drum tracks preset" in the browser on the left. Dragged that preset to the edit, and it added two tracks, with the ouputs mapped as they were in the first edit.
I'm not sure if those are separate instances of Collective or not. I should try this with a proper multi-channel VST, with multiple outs, and see what happens, but is that different to what you're seeing? Or have I got the wrong end of the stick?
-
- KVRist
- 128 posts since 15 Jul, 2017 from Monterrey
it maybe just me but in latest beta 9.0.23, the midi editor does not show some basic operations anymore like transpose
Quad Core | 16GB DDR4 | 240 GB SSD + 1 TB HDD | FLStudio ASIO | 1 GB Video | W10 x64
-
- KVRian
- 1317 posts since 3 May, 2005 from Victoria, BC
Can you send me screenshot to roland@tracktion.comrosesbyrosex wrote:it maybe just me but in latest beta 9.0.23, the midi editor does not show some basic operations anymore like transpose
thx
-
- KVRist
- 128 posts since 15 Jul, 2017 from Monterrey
done, please checkFigBug wrote:Can you send me screenshot to roland@tracktion.comrosesbyrosex wrote:it maybe just me but in latest beta 9.0.23, the midi editor does not show some basic operations anymore like transpose
thx
Quad Core | 16GB DDR4 | 240 GB SSD + 1 TB HDD | FLStudio ASIO | 1 GB Video | W10 x64
-
- KVRist
- 128 posts since 15 Jul, 2017 from Monterrey
Resources not released when deleting a plugin and references are not being deleted in edit
If i delete a VST from an edit, it keeps loaded on memory and consuming cpu cycles, but the worst part is that it look like the references of the plugin in the edit are not deleted so when open the edit next time the plugin loads even it was deleted before
Look here a this steps to reproduce the problem
1. Delete a plugin problem: (Problem: resources not released)
2. Then save the edit, close waveform and open edit again (plugin still loads in memory even if it was deleted before saving) looks like references for the plugins are not being deleted when deleting a plugin from the edit, so it will load in background when the edit opens, to solve that, you have to copy all tracks to a new clean project or edit.
This problem is present in Wavefrom 9 and Waveform 8, so you may check that problem in the XML save engine
If i delete a VST from an edit, it keeps loaded on memory and consuming cpu cycles, but the worst part is that it look like the references of the plugin in the edit are not deleted so when open the edit next time the plugin loads even it was deleted before
Look here a this steps to reproduce the problem
1. Delete a plugin problem: (Problem: resources not released)
2. Then save the edit, close waveform and open edit again (plugin still loads in memory even if it was deleted before saving) looks like references for the plugins are not being deleted when deleting a plugin from the edit, so it will load in background when the edit opens, to solve that, you have to copy all tracks to a new clean project or edit.
This problem is present in Wavefrom 9 and Waveform 8, so you may check that problem in the XML save engine
Quad Core | 16GB DDR4 | 240 GB SSD + 1 TB HDD | FLStudio ASIO | 1 GB Video | W10 x64
-
- KVRian
- 1317 posts since 3 May, 2005 from Victoria, BC
Can you provide some more details? Which plugin is causing the issue? How are you noticing if resources are released or not? Is plugin in a rack?rosesbyrosex wrote:Resources not released when deleting a plugin and references are not being deleted in edit
-
- KVRist
- 372 posts since 28 Oct, 2005 from Earth
I can not render or flatten any audio clips with the latest Beta (9.0.23). The preview area in the render dialog stays empty. Rendering midi clips works. I run Waveform on Debian Stretch.