Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI’m guessing you ctrl+click the first note to start the drag. Ctrl+clicking will toggle selection of the clicked event. You need to first click the selection and then hold the control key when releasing.
ZynewaveKeymaster@Conquistador wrote:
Here is a screen shot of the black borders I mentioned earlier…
…
It sometimes appears when loading projects. I can understand Podium is busy doing something but even if an application becomes unresponsive for a short time (not regularly but under certain condidtions) it should not also shift the screen diagonally left, leaving black borders at the right and bottom of the screen (clearly visible in the image above) until the application (Podium in this case) becomes responsive again.
I’ve seen the “not responding” message before, but that is only when there is a bug that causes Podium to freeze completely (an endless loop in the code, not a crash). How many seconds does it take during Podium startup before the not responding message appears? And does the screen return to normal when Podium is finally ready after startup?
It is the Windows OS that appends the “not responding” text in the title bar. The Podium maximized state hides all window borders and the window title bar (unlike other applications), so that is why the screen shifts when the Windows OS forces the window title to be visible. If you restore the Podium main window so that the window frame is visible, you won’t see the shift when the “not responding” message is appended to the title.
1. Do you run Aero on Vista on your Dev machine?
Yes.
2. Do you have any internet related software running when you use a finished version (not still in Beta) of Podium?
Yes. All the standard Microsoft stuff that comes with Vista, and Avast antivirus.
What model is your CPU?
ZynewaveKeymaster@Conquistador wrote:
I was creating a template in Podium beyond that I am not sure what else you would like to know.
What action were you doing to cause the crash?
ZynewaveKeymasterYou cannot select multiple tracks. To move a range of tracks into a new group, right-click the first track and then use the “Move Track > Move To New Group” submenu.
ZynewaveKeymaster@Conquistador wrote:
2.0.7…
Windows and/or Podium generated this error…thought it might help to post it here.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Podium.exe
Application Version: 2.7.0.0
Application Timestamp: 49286edd
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a81d
Exception Code: c0000005
Exception Offset: 00010e20
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160Sorry, I didn’t yell out “A-HA” upon looking at these numbers. Could you provide more info, please?
ZynewaveKeymasterThanks for the report. It turned out to be a bug. It is fixed in the latest 2.08 beta9. Let me know if everything works as expected.
January 8, 2009 at 19:14 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13622ZynewaveKeymasterBeta9 is up. This is hopefully the final beta. I would appreciate if some of you could try it out and report if everything is ok.
Among a few bug-fixes to the multi-take feature, there is this additional bug-fix:
Fix: Bypassing a mono device chained after a stereo device would only produce output in the left channel.
ZynewaveKeymasterThis FR does not go to the top of the todo pile 😉
It cannot be an accurate duration estimate, as the processing may vary greatly along the timeline depending on the density of MIDI notes and automation. It would behave sort of like the “time remaining” info you get when you download files from the internet.
ZynewaveKeymasterI’ve tried both of your described procedures with various plugins, but I cannot make it crash. I doubt your new audio interface should be the cause of the crashes.
Are the crashes random or can you reproduce it consistently?
Does it crash with different plugins?
Try if disabling the “plugin multiprocessing” option in preferences will get rid of the crashes.
ZynewaveKeymaster@ronin wrote:
btw. how is your guitar evolution proceeding?
I play a little every day. I’ve gotten the habit of grabbing the guitar during TV commercials 😉 (TV muted of course). I soon got bored with the online lessons I purchased, so I now just try to play my own stuff.
January 6, 2009 at 02:31 in reply to: BUG: automatic solo mode vs. bouncing master track (2.07) #13608ZynewaveKeymasterThe latest 2.08 beta8 now finally has a fix for this. Please let me know if you find further problems.
January 6, 2009 at 02:29 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13607ZynewaveKeymasterBeta8:
Using punch-out during recording will no longer deactivate recording mode. This allows punch-out to be used within a loop during multi-take recording.
Fix: The track solo changes introduced in 2.06 had the effect that bouncing the master would not produce sound if Automatic Solo was enabled on the bus returns.
Plus various fixes to the multi-take recording.
January 5, 2009 at 16:59 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13604ZynewaveKeymaster@Conquistador wrote:
@Zynewave wrote:
After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?
The added flexibility is very welcome I must say. However Punch out disabling recording is still useful outside of loop recording. I would definitely want to keep it ❗
I think a global option should easily let a user set and forget the feature one way or another.
The punch out still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not. The only change is that the record button on the transport toolbar is not deselected once the punch-out position is reached. That is done with the new “deactivate record mode when playback is stopped” option. Please explain why you still want punch-out to deactivate recording?
January 5, 2009 at 01:11 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13602ZynewaveKeymaster@Mike G wrote:
Why do you have punch-out enabled if you don’t want the recording to punch out?
For example you only want to try recording the first part of a loop without overwriting the 2nd part of the loop that you are alrady happy with. (1 bar) but the whole loop lasts 2 bars and you want to get the ryhthm, feel of the loop.
After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?
Try this… Set up a loop start/end. and then arm a new track for recording, starting recording from a few seconds before the start of the loop.
The purpose of this space before the loop is so in the first take you get a chance to count in, get your voice in tune with other notes etc.
The composite track (the bit with the right-click drop down list) and the first take start from the place I placed the play cursor to start recording. It took me a good while before I realised why I couldn’t make use of any of the other takes. The other takes are all shorter in length that the main compsite track length.Would it not work as you intended if you set the punch-in at the loop start? That should ensure the comp event is only created at the loop start.
January 4, 2009 at 14:20 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13599ZynewaveKeymaster@Conquistador wrote:
Wave form Peak Display.
As I understand it, this is not something that influences how comping should work, so I would prefer we discuss this another time. I’ve got plenty to do just implementing the composite track feature for this release.