@pavouk100 wrote:
I have also one FR regarding ‘Follow play cursor’ option. It would be nice if view would not scroll in case that the end of the arrangement/loop(if activated) is already present on the screen, but on the very right end. Most prominent example is doubleclicking navigator (ie. zoom exactly to the whole arrangement) and let the whole arrangement play. The view scrolls when play cursor reaches cca 3/4 of the arrangement length, although scrolling in this case is actually distracting and counterproductive.
I believe it already would not scroll if the loop end was within the display range, but I’ve now extended it so that it also won’t occur if the arrangement end is within range (unless recording is enabled).
@all:
2.17 beta1 is uploaded. Please give this a try, and let me know if you find problems. If all is well, I plan to release it this weekend.
@thcilnnahoj wrote:
1- Ghost notes that shouldn’t be there
Fixed. Thanks.
2- Tempo/scale markers confuse selection
In this example I want to move this tiny arrangement back to the start of bar 1. I press Ctrl-A, which also selects the tempo event, which I manually deselect. However, it still won’t let me move the remaining events that extra bar and behaves as if the first event already was at bar 1 (which was the case with the no longer selected tempo event).
I can’t really explain this one properly, hopefully you’ll understand. 😉
Tricky, this one is. The select all command currently also selects events on hidden tracks. So I’m guessing you have a bounce event selected (starting at bar 1) that prevents you from moving the selection to the right. Maybe the “select all” command should only select events that are currently visible on the tracks? Meaning hidden bounce events and events in collapsed group tracks should not be selected.
@Conquistador wrote:
Possible Bug…
Maybe this has been fixed already in 2.17 but…if you click on either side of the Navigator (during playback) PDM’s (Podiums) gui will freeze up completely. I can hear playback but several seconds pass before the GUI returns to normal. Also playback stopped after the GUI recovered here.
Confirmed. It can happen if you have enabled the “follow play cursor” option in the view menu. I’ll fix this.
@em32sn003 wrote:
It would also be good if the data was somehow recoverable – after a crash. I imagine the data is being written to some temporary file space? Currently all data is lost after a crash. You can probably understand the frustration of recording a one-off concert and losing it entirely due to a crash after an hour of recording.
Yes, all recorded/edited sample data is written to temporary cache files, and only committed to sound files once you save all changes to the project. I’m considering different solutions for recording directly to the sound files. This will make it possible to do a recovery of recorded audio should the project crash before it has been saved.
I apologize for this late reply. I was deep into some code changes that I wanted to finish first.
Today I tested recording multi-channel files for longer periods. I managed to record a 32-channel 32-bit sound for over an hour. The saved .wav file was at +20GB. I noticed that the Podium CPU usage increased as the recording progressed. When I had passed one hour recording the UI had become very sluggish. That may be the same symptoms you experienced after 15 minutes. It will depend on the system specs of the machine.
How much memory do you have installed?
I’m going to work on improving the performance of long recordings in one of the next releases. Thanks for bringing this issue to my attention.
Done.
@Pigini wrote:
Would it be possible to have one vst-folder within the podium directory without needing a drive letter in the path? When using a usb stick, the assigned drive letter keeps changing from system to system.
When possible, the Podium.ini setup file will store folder paths using relative references, such as: [program]Vstplugins. So if you have copied projects, plugins etc. to subfolders of your Podium folder on a flash drive, then they should load even if the drive letter changes.
@Conquistador wrote:
@Zynewave wrote:
The “Sound file cache folder” setting in Preferences can be left blank to use the Windows temp folder. The default setup now uses this instead of the Cache folder previously created by the installer.
Any possible degradation in performance by using Windows temp folder? Also might it not be easier to wipe (by mistake) when using a Windows utility (maybe)?
It should not degrade performance. Podium keeps the cache files locked while running, so the files cannot be deleted by Windows by mistake.
Also when installing Podium it is not possible to install by using the Run as an Administrator command. Can you please change the installer to reflect this? Any thing to help with compatibility and reliability when installing on Vista /W7 can only help. Thanks.
The installer tool I’m currently using is very basic, so I don’t think I can control this. I’m going to look for alternative installer solutions in the near future. Why do you want to run the installer as administrator?
Thanks for the input. Here’s a screenshot of the revised startup dialog:
So, the new default folder layout is a “Zynewave Podium” folder created in the users Documents folder. Within are two subfolders: “Projects” and “Library”. The Library folder has further subfolders for project templates, track templates and hardware definitions, like in previous Podium installations.
Further additions to the changelog:
• The installer no longer creates the “Zynewave Podium Projects” folder in the Documents folder. Instead the user is presented with a “project folder preferences” dialog the first time Podium is started. The user can let Podium build the default folders, or configure the folders in the preferences.
• Removed the “Relative to project path” option from the sound properties dialog. Sound files are now always referenced with a relative path in the project file, if the sound file is located within the project folder.
• Removed the “Relative path” plugin file option from the Device Mapping properties dialog. Plugins are now always referenced with their full path in the project file.
• Multiple VST plugin scan folders can be specified in the preferences dialog.
• Added “automatically search for missing plugins when loading a project” option to preferences. This option is enabled by default.
• Redesigned the “create new project” page. The page can be scrolled vertically if it does not fit within the window. This can be necessary with for example 1024×600 netbook screen resolutions.
• The track inspector embedded in the project window is automatically opened/closed when an arrangement editor is opened/closed.
Hi,
Which Podium version?
32 channels into one .wav file?
What bit-resolution is the .wav file set to?
Are there any other soundfiles playing/recording simultaneously?
What does the Podium CPU indicator Mix/File percentages read before the problem starts occurring?
How do you detect the problem, i.e. is it the Podium CPU File indicator that starts blinking red?
Is the buffer overflow only a problem with the monitoring, or is it also detectable in the recorded .wav file?
@druid wrote:
One question at this time; I’m confused about what you mean that it will by default use the user’s main documents folder… Do you mean that, without intervention, it will save projects right there, instead of in a Zynewave folder? If so, I don’t think that’s a good idea…
Yes, saving a new project will create a project subfolder directly in the Documents folder, unless the user has changed the “new projects” folder in Preferences. I understood from one of your posts about this in another topic, that you did not like having the “Zynewave Podium Projects” subfolder created?
@Mike G wrote:
Oh and another very, very minor thing the small version of the start menu icon isn’t as nice as the newer large podium icon, could you fix this too?
The big Podium icon does not look good when scaled down to 16×16 pixels.
The reason that it is ordered as L/R/C/LFE/Ls/Rs, is because this is the standard channel assignment order used in multichannel media files and studio mixer/effect devices. Some time in the future I intend to make a simple VST plugin that allows channel reassignment, so that it is possible to arrange channels for playback on devices expecting a different channel order. Currently you cannot reorder the channels in Podium.
Depending on how you connect your monitors to the Auzentech soundcard, perhaps you can just swap the cables for channel 3+4 and 5+6.