Modartt user forum » Pianoteq user forum » Issue with sleep mode (or hybrid mode), M-track 2*2 and Pianoteq
Hi,
When i set Pianoteq's buffer size to an another mount than M-track's panel (exemple : 64 samples for Pianoteq and 256 samples for M-track) and i wake up my computer (Win 10 anniversary) from sleep mode (before the sleep, i have remained Pianoteq opened), i have always this :
How to solve this issue ? I don't want to see this panel again...
I wouldn't use hibernation or sleep on a laptop that is used for low-latency audio. Ever!
Or at least close Pianoteq before hibernating.
I don't use laptop...
Or at least close Pianoteq before hibernating.
LOL !
Hibernation is usually used on laptops to preserve battery life, so it's the first thing that crossed my mind. It is absolutely not necessary to use it on a desktop system (especially if your boot drive is on an SSD - makes it very fast to load anyways).
In any case, there can be driver-related issues with hibernation, which is not Pianoteq's fault, it's the fault of whoever wrote a particular driver (in this case, M-Audio) on one side, and Microsoft on the other side. So, no, it's not "LOL" to close Pianoteq before hibernating if you see issues after bringing the computer back from hibernation. It is common sense
Hibernation is usually used on laptops to preserve battery life, so it's the first thing that crossed my mind. It is absolutely not necessary to use it on a desktop system (especially if your boot drive is on an SSD - makes it very fast to load anyways).
On my dekstop (SSD, Haswell-E i7 5820K, 16GO DDR4, fast boot, some bios's features disabled) :
Normal boot : between 40 and 50 sec (for this mother board it's an normal time boot)
sleep mode boot : 8 sec and i can find all my previous session...
So, It can be advantageous to use the hybernation boot...
In any case, there can be driver-related issues with hibernation, which is not Pianoteq's fault, it's the fault of whoever wrote a particular driver (in this case, M-Audio) on one side, and Microsoft on the other side.
I have not the same issue with Reaper, so i think Modartt can probably solve the issue...
So, no, it's not "LOL" to close Pianoteq before hibernating if you see issues after bringing the computer back from hibernation. It is common sense smile
I have wrote LOL because this answer was so obvisious... Any dumbs would find this solution... But i don't like this solution...
This problem also exists on Linux. Basically, when resuming from hibernation, Pianoteq comes up before the ASIO/sound drivers (ALSA/JACK for Linux) finish initializing.
Under Linux, I use a "on resume" script that kills & restarts Pianoteq.
Here are some programs that may work on Windows:
https://www.raymond.cc/blog/automatical...bernation/
This would be the path I'd look into. Have a utility that can run an arbitrary program upon resume. That program would be a batch file that kills Pianoteq and launches it again.
Yes, it seems to be the issue. It would be great if we add to pianoteq a feature which inactive this automatic panel when there is no sound card detected by Pianoteq. Maybe it will not resolve the issue. I'm asking myself how Reaper acts pretty well to manage this issue.
I have made a mistake in my previous description. With the hibernation mode, Pianoteq seems to work perfectly. Problems happen's with the sleep mode... or the hybrid sleep mode...
Problems happen's with the sleep mode... or the hybrid sleep mode...
Why do you need it anyway ?
What is your long time experience with M-audio M track?
I am planning to buy M- audio M-track HUb or Air HUB interface. How stabile it is, how good are the DA converters, ...?
I have seen som problems reported with M-audio devices. Originally I have planned to buy a Steinberg UR22 MK2, but I do not need the inputs. Also I can use the additional Usb ports to connect my SL88 controller.